Work TBD, but dropping info here to save for later. Devices being sent/received should typically be handled by the Product Manager for Apteryx, but this is being created as a guideline to assist while we do not have a Product Manager or when the new one arrives.
All devices being received must be documented in this spreadsheet. Only the person receiving the device and the person returning the device should be entering information in this spreadsheet. Do not share with anyone that is not at least a Senior Technician without approval from a Supervisor. PACKAGE DOCUMENTATION.xlsx
From a compliance perspective, see this article if a customer is providing the device: Handling Customer Property - PDDS Compliance and Security Policies Handbook - Confluence
Here are a few expectations I wanted to confirm in writing from us as well as provide shipping information to send us the device.
We would need the device for a minimum of 6 months. Our device inventory is regularly tested against new releases to ensure stability. Not having a device to test against means that we would be unable to validate compatibility with each upcoming release.
We do not have an ETA we can provide at this time for when the issue will be resolved should we receive the hardware.
We are currently only targeting integration via TWAIN, and not direct integration.
-
Please provide a link we can use to download and install the sensor's hardware drivers and TWAIN drivers.
Please include any capture workflow documentation for your TWAIN interface that would help us operate the TWAIN if you have it.
Please provide anywhere that your TWAIN and/or hardware capture logs are stored.
-
Please send the device to the below address with Attn: Austin Servantes
Planet DDS
159 S. Main St
Suite 414
Akron, OH 44308
Please send us tracking information so we can track the shipment and confirm we have received the device.
Please include a return label we can use to return the device.
Please enter any support-initiated documentation when having a device sent to us. Please include links to the website advertising the device and clarifying whether or not the device is being supplied by a customer, prospective customer, the manufacturer of the device, or the vendor(or “manufacturer”) of a rebrand of the device if that is known.
Device Name/Link |
Support Ticket |
Notes |
|---|---|---|
|
Being supplied by a vendor of the device, A2ZImaging. A to Z imaging |
||
Sensor from Henry Schein One. |
||
|
Sensor from Nathaniel Jacob DDS 00024894-00024894 who churned but is easy to work with. Possible that he might sign back up for Apteryx if this sensor can capture via TWAIN in Apteryx Online Capture. Tracking number shows as received on 11/30/24: 1Z6GJ1T14220014211 |
FAQs
The below questions will be separated by the ticket number. This is currently just a compilation of questions and answers provided thus far.
This is for TWAIN support for our sensor, correct? Not native SDK integration?
Yes, that is correct. Thank you for helping to clarify.
The issue you mentioned with TWAIN and Apteryx, is it only with a small subset of sensors? Or do all Twain sensors experience this issue?
We have tested with our current device inventory log and have been unable to reproduce the issue via TWAIN. But I can anecdotally say that we have encountered a few devices that work in 3rd Party TWAIN software, such as Twacker 32, IrfanView, and our legacy TWAIN extension, but not our CCB TWAIN Extension. We suspect there is an issue with our TWAIN Plugin, but we have yet to confirm that.
Were you able to check with your management team if we can have access to Apteryx software, so we can perform our own testing with a DUO sensor here at A2Z Imaging?
Yes! Our team has advised that we can provide that access and would evaluate that access following successful integration with the device.