Cloud Capture:
XVCapture Extension: https://apteryximaging.zendesk.com/hc/en-us/articles/4412758829595-Current-Imaging-Downloads
XV/XVL Extension: https://apteryximaging.zendesk.com/hc/en-us/articles/4412764698779-Legacy-Downloads
Known Rebrands:
Related Image Quality References:
General Image Quality Tips
Troubleshooting
Auto Calibration File Download
Download and run newest upgrader from https://apteryximaging.zendesk.com/hc/en-us/articles/4412758829595-Current-Imaging-Downloads to attain calibration downloader and dependencies.
Device Descriptor Request Failed Error
In Windows 10; if the device manager shows the sensor as USB Device Descriptor Failure follow these steps.
1.) Unplug all Tuxedo A Sensors from the computer.
2.) Transfer the below file
3.) Run the driver patch under the ADMIN User account for the computer.
4.) Log back in under the regular user and test in device manager / demo program / XV software.
Please report any bugs or issues with this patch back to Patrick Williams, and Dave Robles.
Getting Calibration Files
Each Tuxedo sensor requires a calibration file to ready properly. Assuming the install has already had the Tuxedo A upgrader ran against it, it should be able to pull the calibration file from the web automatically when you ready the sensor for the first time.
There are numerous ways to get a calibration file otherwise in the expanded sections below. If the calibration file cannot be grabbed by a technician on their PC, notify the hardware department who can contact Teledyne to have them ensure the file is available.
Manual Sensor Calibration File Download
Copy "\\ai4\ClientDirs\e2v\CalFileDownloader\FtpClient_FFC.zip" to the client PC.
Extract and run the "FtpClient_FFC.exe" program.
-
There are 3 ways to download the calibration file:
Automatic Detection - Have the user plug one sensor in and click "Refresh". Select the sensor in the device list and click "Next". Specify the output folder for the cal file and click "Next" again. File will download to specified folder. Repeat process for any other sensors they have.
-
Manually Enter Serial Number - This option prompts for the serial number a sensor, one at a time. Delete the empty space in the text box first. Then enter serial number found on the sensor label or sensor box:
Specify the folder for file output and click next.
-
Enter List of Serial Numbers - Create a notepad document and list all serial numbers in the following format:
Select the location of the saved file and click "Next". Specify a destination folder for the cal files and click "next".
All operations will generate a log file once the process completes to review the file transactions.
The folder in which these calibration files are supposed to load needs to be exactly "Tuxedo A-Series" without quotes. Path is ..\Devices\Tuxedo-A Series
Error Sensor SerialNumber:XXXXXX Downloading file failed:Failed to open file
Teledyne must be contacted by Hardware dept. for them to resupply the calibration files to their FTP site
Manual e2v Calibration File Creation
Warning - Image quality using this flat field correction file has not been thoroughly vetted, but prelim results look good
Plug sensor in
Run "C:\Program Files (x86)\IntraOralUSB\IntraOralUsbDemo.exe" Path may slightly differ
Select XrayDevice menu > Re-select > OK
Tools Menu > FFC & Images Acquisition
Check the box 'Enable multiple image acquisition
Number of images to acquire = 16
Check the box 'Generate FFC'
Select 'Get Serial Number' (this should change the file name automatically
ffc output folder - Desktop or anywhere that you can move it from
Apply
XrayDevice menu > Arm > Normal
Capture all 16 images with sensor facing tube head at nominal radiation - File should be saved to chosen directory
Calibration files for Apteryx Online Capture’s E2VII plugin are stored and used at C:\PlanetDDS\Apteryx Online Capture\Plugins\E2VII\Correction Files\<serialnumber>.FFC
Image Not Returning
On a laptop you may run into an issue of the USB ports not providing enough power to the sensor to return an image. If this is the case, try https://planetdds.atlassian.net/wiki/spaces/DIKB/pages/3467444451/Power+Management#Disabling-Power-Management-for-USB-devices.
Tuxedo-A TWAIN Install Instructions
Use zip below for deploying all files
Take the Tuxedo-A Calibration Files folder and put that on the root of C of each PC you get into
Put your calibration Files here
Ensure no sensor is plugged in during the next step
Run the e2vIITWAINSetup.exe, then the SetupIntraOralUsb_32bit.exe
Pass E2VTWAIN Settings.reg and run this file - This will write all necessary configs to that PC (confirmed working with W10)
Pass and run Irfanview to register the program
Repeat for each PC
Slow Capture Speed and/or Banding
If a practice asks if there is a way to speed up image capture when using Tuxedo sensors, and you have already disabled the layout auto-save option, you may be able to adjust the "Integration Time" setting for the sensor to get it to return images faster. A value of 3,000 ms (3 seconds) should be an acceptable amount, but if needed you may lower this to 2,000 ms (2 seconds). Try to aim for a value above 1,000 ms (1 second) or you may see too much banding in the image.
Navigating to the sensor hardware options, the clicking the "Sensor Configuration" tab should allow you to see and adjust the value under the "Acquisition" section.
*Upping the integration time from 1000 ms to 2000 ms on some XDR sensors will also clear up issues with banding in the output images.
Extremely Long Time to Capture
If the time to capture an image is taking an extremely long time (45 seconds or so) the images may be being taken in a RAW, uncompressed format. If you check in their XV directory and find a lot of RAW files, that could be the issue. To fix this, download the Tuxedo extension from the PDDS updates page and install it/replace the old extension. After that is done, delete ALL of the raw files, and that should resolve the slowness.
If things are still slow from that point it may be a good idea to check the sensor "Integration Time" setting from the Sensor Configuration tab for the sensor. (3,000 ms is usually a good time)