-
If the problem, in this configuration, disappears: there may be a
faulty Ethernet cable or junction connected between the PC and the
3D sensor
-
If the problem is still present, try to connect the sensor to another
network interface Ethernet port (e.g. Invert the “Ethernet” (MCU) and
3D sensor connections setting the right IP address on the network
interfaces – see paragraph 7.7.1.
If the problem is solved, it can be related to the network interface
board.
2.
Fix the PC network settings or replace the faulty/not compliant components.
Update the network interfaces board drivers (see paragraph 11.2.4).
Verify if the error is still present
3.
Configure the Network interface board as required by paragraph 7.7.1 and
activate the sensor logs (see paragraph 11.2.1.4).
Verify if the problem is still present.
4.
Set the 3D sensor network with a static IP address (see paragraph 11.2.6)
Verify if the problem is still present..
5.
Perform the tests reported by Error E760 (see paragraph 9.2.7.11).
6.
Verify if the following values matches the ones stored in the EEPROM memory
(see paragraph 11.2.5):
-
0x0084 – 3D Std RX on time = 17
-
0x0085 – 3D Std RX off time = 33
-
0x0086 – 3D HD RX on time = 17
-
0x0087 – 3D HD RX off time = 33
-
0x0088 – 3D SHD RX on time = 17
-
0x0089 – 3D SHD RX off time = 33
Correct the values if they do not match and verify if the problem is solved.
7.
In case the problem is not on ceph exam, perform both a 3D and a panoramic
acquisition:
a.
If the problem is systematically present only on 3D acquisitions, verify the
integrity of the sensor trigger signal cables:
-
X43-J14 (from 3D Power Sensor board A10 and the 3D sensor)
-
X38-X25 (from 3D Power Sensor board A10 and MCU board A1)
-
X32-X15 (from Generator board A2 and MCU board A1)
If the cables are OK, replace first the 3D Power Sensor board, then the MCU
board and then the Generator board.
b.
If the problem is present both on 3D and panoramic acquisitions, verify if
To Next Page
Loading...
