From a friend:
Well not so technical but if it doesn’t detect exposure it should be one of Six things:
1. Dose hitting sensor – looks like he has confirmed that is not issue – if he cranked exposure up to 200ms to test and it doesn’t expose then it is probably Not Dose from the source causing the issue.
Is this a handheld low ma x-ray source? That can be more challenging but have not heard many/any issues with Dexis sensors detecting low exposure as they are very sensitive.
2. Coning – if not enough of a sensor is illuminated by radiation then it doesn’t matter if one corner of the sensor was exposed at 300ms, it won’t detect/trigger. Can happen but he should know if he sees some coning on the images he does get if they are having consistent problems with positioning of the sensor.
3. PC incompatibility – This would not be typical and should cause other issues IN ADDITION to not detecting exposure – like Not Arming to start with to even get to waiting for exposure. The only thing that cautions me a bit is “Windows 8”…
4. Cable issue – this is one of the most likely issues – cables get bent with high radius and pressures when in holders and when they ARE ACTUALLY PLACED into the oral cavity. When doc says sensor exposes when not in the mouth but in the holder then make sure to test that thoroughly. For example when it doesn’t work in the mouth what holder is it in and what placement (anterior vertical, bitewing horizontal, etc…) and test THAT exact position externally to the mouth in the holder with the cable bent just like it happens in the mouth. Bend the cable when in the holder and take an image, bend it another way try to take an image, simulate this many times and as close to the exact position as when placed in the mouth.
5. Known Issue – Dexis sensors have some issues with certain sensors that “lose communication” with the USB port while in the armed state – this can be caused by a non-compatible PC, an early highly intermittent cable failure, or environmental issues like magnetic interference from an ultrasonic cleaner. There is a software fix for this symptom that checks for this condition and re-attaches/re-syncs the sensor should this occur. It has been out for a couple years but if this doc has not updated his DEXIS software in the last year or so he may not have that fix.
6. Technically it could be inside the sensor and a problem with the actual response of the sensor (CMOS die) or the A/D convertor not outputting properly/proper data – but again typically you would see that in other areas such as bad / not as good images when it did detect radiation and delivered an image.
I would say it is #4 or #5 and possibly #3 (if it has been an issue since day one and his PC’s are all the same)– Does he have another sensor – if so, it becomes very easy to rule in or out a specific sensor or a specific computer or computers they are being plugged into.
What the Schein rep should have done was brought another Dexis sensor for comparison which would have most likely narrowed it down to root cause.
If it is highly intermittent (works 99% of the time) then can be harder and might need a loaner sensor for a day or two to figure out…
Also, does it happen on all his machines, are they all the same model or does it just happen on one machine, if he has other models does it work on that machine, etc…
Hope that helps.
p.s. The person above who recommend Jackie is good as well – Jackie is a very good clinical trainer, - not technical but because she is a trainer has seen most everything at least once and may have some good input or if there are any “new” gremlins in Dexis software or sensor…
thanks
===================================
Justin - me... would like to add that few people on earth are as "technical" as my friend.
