Mehrez Kristou

Hi there, early versions of the UST-05LN were released when Windows 10 is just released. So it was not supported. Please use Windows 7 to do the configuration. If it is cretical for you to use Windows 10, please contact your distributor to discuss your options.

It is not possible to make a simple update to add this functionality. However, your proposal will be considered in the development of the next generation scanners. Unfortunatly, I don't have a time line to share with you.

Sorry, it took me few posts to understand the situation. I assumed you are using a aquisition board to do the pulse detection and the data reception. In the case, your plus is timestamped in an embedded boad and the data recption is on a non-realtime OS, you get a sync problem as described. Adding a pulse id information to the data packet would solve partially the problem as you need to recieve the first pulse and track it to stay in sync. Another option would be to use Arduino like device to do...

Sorry, ot took me few posts to understand the situation. I assumed you are using a aquisition board to do the pulse detection and the data reception. In the case, your plus is timestamped in an embedded boad and the data recption is on a non-realtime OS, you get a sync problem as described. Adding a pulse id information to the data packet would solve partially the problem as you need to recieve the first pulse and track it to stay in sync. Another option would be to use Arduino like device to do...

Thank you for expaining the CURRENT_NUM_SYNC_PULSES_EMITTED. Is it possible to timestamp s# and d# with your own timestamp. Then look for the nearest pair in the time space knowing that: s# should happen before d# t(d#) - t(s#) should be less that the scanner cycle and more than the 1/8 of the cycle.

You can querry the CURRENT_HW_TIMESTAMP using the II command which includes a timesamp field. Sorry I could not understand the behavior of CURRENT_NUM_SYNC_PULSES_EMITTED. Please elaborate on this.

Sorry for the confusion. In the specification document of each scanner, the pulse timing is clearly stated. The back of the scanner is set as the reference point of the pulse. The pulse can occure within 1ms from the time the motor pass by that reference point.. The scanner is controlling its speed to stay within 25ms +-1ms. The time stamp corresponds to the first step or the current scan.

Sorry for the confusion. In the specidication of each scanner, the pulse timing is clearly stated. The back of the scanner is set as the reference point of the pulse. The pulse can occure within 1ms from the time the motor pass by that reference point.. The scanner is controlling its speed to stay within 25ms +-1ms. The time stamp corresponds to the first step or the current scan.