Do not use the Optime extension when attempting to integrate an Optime device. Always use the Instrumentarium extension.
Hardware:
Optime, Novus, CranexD, Snapshot Sensor, OP300 (3D Pan), OP200 (2D Pan), OP30 (Pan), Digora, Novus
"Resolution Error 0x0" or "Resolution Error 0x33" - UA Flag Issue
Running this file on the customer’s computer will complete the below steps
UA Flag that needs to be reset for the Optime in the system registry:
Select Windows key+R
Type out regedit and hit okay
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Soredex\Dsd\Uid
OR
HKEY_LOCAL_MACHINE\SOFTWARE\Soredex\UID
Right click UAFlag and choose modify
Change from 1 to 0.
Restart XV/XVCapture
noteContinual UA flag errors are typically remedied by driver update - Client would need to reach out to Kavo/Instrumentarium to update Optime drivers if the issue is persistent
Continual UA flag errors are typically remedied by driver update - Client would need to reach out to Kavo/Instrumentarium to update Optime drivers if the issue is persistent
"Cannot Mount Sensor" Issue:
Check permissions on Apteryx Install
Check permissions on IAM folder (C:\Program Files (x86)\Palodex Group\IAM)
Add the IAM path to the Environmental Variables
Check permissions on "C:\Soredexworkingdirectory" folder
3D Capable Units
Typically, units that are 3D capable must use TWAIN for 2D. Units that are not 3D capable can typically use instrumentarium extension for 2D. Additionally, 3D integrations must be exported from the capture software, and imported into Apteryx, or XVCapture’s CT Importer.
Calibration File Locations
Check "C:\Program Files\Palodex Group\dicc\Ortho\GainFiles"
If they don't exist there check "C:\Windows\TWAIN32\Instrumentarium\devices\Cranex_d\Ortho\Gainfiles"
Post Capture Filters Not Applying
Delete all filters within PCF filters list and recreate them
TWAIN Working/Direct Integration showing “Hardware Disconnected”
-
GainFiles are missing:
Copy folders from the C:\Windows\twain_32\Instrumentarium\Devices folder
Paste them into the installation folder’s Devices folder
-
Conflicting Optime Driver Files:
Check for a dll within our directory called "dicc.dll." This dll is part of the Optime drivers, and is injected into our software if the Optime extension had been installed at some point. If this dll is in our directory, rename it to .old or remove it, and it should resolve this issue. This dll should exist within the PaloDex Group folder, and removing it from our directory will tell our extension to look for it there instead. The Optime should be integrated via the Instrumentarium extension instead as well.
TWAIN working in 3rd party tool (Twack, iView)/XVC TWAIN extension showing “Hardware Disconnected”
This is usually due to the Instrumentarium TWAIN settings not configured correctly in XVCapture. Ready the pano in Twack or iView and hit the options button in the Instrumentarium drivers. Note the pano model that is currently selected and navigate to the hardware options in the pano window and verify the IP of the pano. Attempt to ready the pano in XVC, and when it fails, go into the Instrumentarium TWAIN options and verify the hardware settings match. (Screenshots needed)
Instrumentarium upgrader crashing Windows 10/New Kavo Driver
Avoid running the instrumentarium upgrader. It includes the drivers for instrumentarium which crash Windows 10 PCs
Instead, just supply the Instrumentarium.SED or .IXDLL and tell the customer to contact Kavo for drivers
Instrumentarium Drivers Website
https://tech.kavo.com/content/instrumentarium-twains
Instrumentarium Novus producing extremely dark images in XVCapture
Try the following settings:
NOTE: In this office’s case, the only device using the Instrumentarium extension was their Novus, so we were able to delete all filters and leave the modality restriction as “none.” If the office uses an optime, snapshot sensors, etc., be sure to only delete the PX filters, add these, and set the modality restriction to “PX.”
Windows Installer appears when accessing Preferences or selecting Capture Images
All cases we have seen of this issue have been due to an issue with the currently installed Instrumentarium drivers, rather than the extension or installation of XVCapture itself.
The resolution to this issue will be to have the current instrumentarium/kavo drivers on that machine uninstalled, then reinstall a newer version - this process would be handled by Kavo/Dexis. The older version of the drivers install a HASP driver which commonly fails to install on Windows 10, and as the HASP driver failed to install, the windows installer appears when any action is made that invokes instrumentarium.ixdll, such as going to Preferences or clicking "capture images." Once old drivers are uninstalled and newer ones are obtained and installed, the issue should be resolved.
Otherwise, if the client does not need the Instrumentarium extension on the workstation this occurs on, Instrumentarium.ixdll can be renamed to .old or deleted to resolve this issue as well.
How to recover images that did not make it to XVCapture
Navigate to c:\programdata\Palodex group\captured images. All raw images are stored in this location. You can drag the images into the red square in the screenshot below. This will allow them to be opened in the twain and returned to XVcapture. Best method of determining who the image belongs to is based on the date and time created. Which is listed in the folder.
This only pertains to units using the below Instrumentarium twain. This will not work for older twains.