If the sensor is a Dexis Sensor, and was working within the Dexis Imaging software on the current PC prior to using the sensor in Apteryx software, the Dexis drivers built into Dexis Imaging are most likely locking the sensor to themselves. This lets GXPicture see them, but does not allow the use of the sensor. Dexis Imaging will need to be uninstalled from the PC before the sensor will become usable for other imaging software.
- Check to make sure GXPicture drivers are installed and that the sensor icon in the system tray is green.
- If GXPicture is not installed, please reference the article Integrating Gendex/Dexis/KaVo Sensors and Cameras.
- If the sensor icon in the system tray is white with a red 'X', the sensor is not recognized as plugged in. If the icon appears this way while a sensor is plugged in, KaVo Support will need to be contacted for further troubleshooting.
- If the sensor icon is permanently blue, the drivers are stuck and have not passed back the last exposed image. KaVo Support will need to be contacted for further troubleshooting.
- Check C:\Program Files (x86)\Gendex\ folder, verify that there is a \*CorrectionFiles\ folder, and confirm that it contains files matching the serial number of the sensor being used.
- If both of the above are true, the issue is more than likely permissions related. Try running the Apteryx software as Administrator. If the sensor works, try adjusting permissions on the Gendex driver folder (C:\Program Files (x86)\Gendex\) to give Everyone Full Control and make sure the Apteryx folder permissions and share are configured the same.
- If the sensor works when Apteryx is launched directly, but does NOT work when bridged, configure the NameGrabber to start as Administrator.
- If bridging directly from a PM software (ie. OpenDental), make sure that it is not set to run as admin while XV is configured to run normally or vice-versa. This has been known to cause issues.
Article Version 1.1 2020.07.17