
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. Try running the Apteryx software as Administrator.


Finally, Browse to the local folder C:\Program Files (x86)\Gendex\Vixconfg and run GXStart.exe to restart GXPicture. Browse to the local folder C:\Programdata\Kava Kerr\NimF\ and locate the folder name that matches the current sensor's serial number, then delete that folder. Right-click on the blue GX icon next to the flashing yellow icon and select Exit/Close. ( Specifically for Gendex Titanium / KaVo IXS sensors) If the sensor icon is flashing yellow, then there is an issue with that sensor's correction file. 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.


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 in the system tray is white with a red 'X', the sensor is not recognized as plugged in. If GXPicture is not installed, please reference the article Integrating Gendex/Dexis/KaVo Sensors and Cameras.Dexis Imaging will need to be uninstalled from the PC before the sensor will become usable for other imaging software.Ĭheck to make sure GXPicture drivers are installed and that the sensor icon in the system tray is green. This lets GXPicture see them, but does not allow the use of the sensor. 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.
