Does the barcode scanner use a keyboard wedge that you cannot confirm receipt of the scan?

Question

I have a very simple application that runs a series of legacy scanners that capture barcode scans from the serial port and send them back to the scanner in the order in which it received the scan. Based on this, the scanner flashes green and the user knows that he can continue.

I like this model compared to my understanding of the keyboard, because if something happens with the application that picks up the scan (the application freezes, the shape with focus changes, the PC freezes, the PC cannot keep up with the choice of scanning), the person holding the scan console will know that there is a problem because they will not receive a green flash and they will not be able to continue scanning.

I am looking at adding some scanners, and it seems that many people use barcode scanners that act effectively as keyboard wedges. Some of these scanners have ranges in excess of 100 feet, implying that people use them away from the PC (like my users). Therefore, I am wondering if I am missing something regarding the wedge keyboard model. Is there some mechanism that I'm missing to make sure that a scan decoded by a scanner that acts like a keyboard wedge actually reaches an application running on a PC? A full-fledged laptop running Windows Mobile seems like a massive overflow, just wanting my user not to scan data that is not in the application, and even even a mid-range scanner with a keyboard and screen,but is it the last entry point for any scanner programmability?

Answer 1

You are right: when working as a wedge on the scanner, there is no feedback loop. We often use wedge scanners, and in a modern environment (that is, Windows, several applications, etc.), Focus, "scanned scans", etc. - all these are real problems.

. , USB- - , ( , ACK'd , / - ACK). , USB HID POS ( ), USB-, , ( HID- , , ). POS , , , .

Answer 2

, Symbol MC9090-G, . , factory - . , , . , .