Bar Code Scanner Implementation
-
We have a .NET App that uses USBSerialEmulator so when you plug a USB scanner in you can assign a COM port. The original developer of our application used this idea to be able to use multiple scanners. Well there are several problems with this because the floormen are always swithing out scanners or they break, etc and we have to reconfigure the scanners and our application for COM ports. Plus the scanner manufaturer says it does not support multiple scanners when using the USBSerialEmulator. I was thinking of using the Microsoft.PointOfService assembly for USB. Any thoughts or ideas before I proceed....???? And I'm new here...seems like a great site.
-
We have a .NET App that uses USBSerialEmulator so when you plug a USB scanner in you can assign a COM port. The original developer of our application used this idea to be able to use multiple scanners. Well there are several problems with this because the floormen are always swithing out scanners or they break, etc and we have to reconfigure the scanners and our application for COM ports. Plus the scanner manufaturer says it does not support multiple scanners when using the USBSerialEmulator. I was thinking of using the Microsoft.PointOfService assembly for USB. Any thoughts or ideas before I proceed....???? And I'm new here...seems like a great site.
I'm not sure I understand your problem; I assume you have peripherals (bar code scanners) with a serial interface, and are using USB-to-serial cables. If so, I don't see where the USBSerialEmulator comes in: 1. a USB-to-serial cable comes with its driver, making the serial port available to Windows and all interested apps. You typically can have as many as you want, and choose the port name. 2. bar code readers just emulate a keyboard, all they do is emit a string corresponding to the bar code, so a little code snippet based on SerialPort should be good. 3. furthermore most bar code scanners can be taught to add a prefix and a postfix string of your choice, so you could e.g. prefix something that identifies the scanner, and postfix a newline combination. If all the above applies, simply have one serial data receiver handle all the scanners, look for the prefix, and dispatch the actual data to the appropriate destination. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
I'm not sure I understand your problem; I assume you have peripherals (bar code scanners) with a serial interface, and are using USB-to-serial cables. If so, I don't see where the USBSerialEmulator comes in: 1. a USB-to-serial cable comes with its driver, making the serial port available to Windows and all interested apps. You typically can have as many as you want, and choose the port name. 2. bar code readers just emulate a keyboard, all they do is emit a string corresponding to the bar code, so a little code snippet based on SerialPort should be good. 3. furthermore most bar code scanners can be taught to add a prefix and a postfix string of your choice, so you could e.g. prefix something that identifies the scanner, and postfix a newline combination. If all the above applies, simply have one serial data receiver handle all the scanners, look for the prefix, and dispatch the actual data to the appropriate destination. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
I may have to read up on this a bit. Who created USBSerialEmulator? and what is the scanner's vendor, make and model? :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
I may have to read up on this a bit. Who created USBSerialEmulator? and what is the scanner's vendor, make and model? :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
Honeywell 3820...the emulator is Honeywell also. We have delt with Honeywell support on this and their response is "You cannot connect two scanners to the same PC using the USBSerialEmulator." We've tried, but it's just flaky. And when they switch the scanners around...its messy. We'd like plug and play with the ability to use both sections of the application at the same time on the same PC with two different scanners....that is why I think the original programmer tried the COM port.
-
Honeywell 3820...the emulator is Honeywell also. We have delt with Honeywell support on this and their response is "You cannot connect two scanners to the same PC using the USBSerialEmulator." We've tried, but it's just flaky. And when they switch the scanners around...its messy. We'd like plug and play with the ability to use both sections of the application at the same time on the same PC with two different scanners....that is why I think the original programmer tried the COM port.
Well, if they are positive it isn't supposed to work for more than one, you should drop them and go for regular, non-USB, scanners, with a good old RS232C interface; then use USB-to-serial cables, with its driver, etc, as I laid out in my original reply. Make sure the model you choose has prefix/postfix capability. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
Well, if they are positive it isn't supposed to work for more than one, you should drop them and go for regular, non-USB, scanners, with a good old RS232C interface; then use USB-to-serial cables, with its driver, etc, as I laid out in my original reply. Make sure the model you choose has prefix/postfix capability. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
If Honeywell can't solve it, it will cost you. With what you have, it is either keep the hardware and have new software, maybe a totally new USB driver or something (is anyone going to do that with a total cost of ownership significantly less than 7000$?); or replace the hardware, add USB cables (15 to 25$ each), and a little piece of code in your app. I have done some bar code projects before, and I know which way to choose here; rather than spending money locking you deeper into a suboptimal choice, I'd go for the open approach that works just fine. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
If Honeywell can't solve it, it will cost you. With what you have, it is either keep the hardware and have new software, maybe a totally new USB driver or something (is anyone going to do that with a total cost of ownership significantly less than 7000$?); or replace the hardware, add USB cables (15 to 25$ each), and a little piece of code in your app. I have done some bar code projects before, and I know which way to choose here; rather than spending money locking you deeper into a suboptimal choice, I'd go for the open approach that works just fine. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
That is why I want to use USB and get rid of the com port configuration in our custom .NET pack&ship appl. I don't think your following my post. I've already came to the conclutions you've suggested. The com port configuration is what is the problem. I would like to implement USB into the application and if you have any suggestions on how then please suggest something :)
-
That is why I want to use USB and get rid of the com port configuration in our custom .NET pack&ship appl. I don't think your following my post. I've already came to the conclutions you've suggested. The com port configuration is what is the problem. I would like to implement USB into the application and if you have any suggestions on how then please suggest something :)
AFAIK you need a good USB driver then; and that would be specific to both the peripheral and the operating system (some drivers survive a single major Windows upgrade). I don't think it is up to a customer to create drivers for a manufacturer's hardware, but if you were to go that route: I wish you good luck. And I wouldn't mind reading a CP article when it's done. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.