🧾 Description
This article covers common OPOS driver troubleshooting tips
🛠️ Resolution Steps
Upon trying to claim the scanner you get an error similar to this…
This simply means OPOS does not see the scanner. What to check for:
Click on the specific interface type to jump to the troubleshooting steps for that interface...
RS-232 Standard, RS-232 Single Cable, USB Com Single Cable
USB Com for handhelds (Or scanner only Magellan devices)
Interfaces (OPOS Service names): RS232 Standard (RS232Scanner), RS232 Single Cable (MagellanSC or SCRS232Scanner), USB Com Single Cable (MagellanSC or SCRS232Scanner)
- Make sure your scanner is programmed for the Interface type you intend to use.
- Check the cable connections, make sure your interface cable is plugged into the blue port on our scanner/scale devices. This port is marked “Host Port” on the scanner.
- Check to make sure OPOS is configured for the correct comport using the OPOS Editor, Scanners tab…
- Sometimes defaulting the scanners communication settings is necessary. You can do this by scanning the Return to defaults barcode…
Datalogic Handhelds…
Datalogic Magellan…
- The default configuration for OPOS is to request the Identification, Health and Status of the scanner upon claiming. If something is interrupting this, you will also receive the no hardware error. If you do not see this error in Dualtest but your POS software cannot seem to claim the device, it maybe that the POS software does not allow enough time for the scanner to report back this information causing a failure to claim. It is recommended to resolve this in the POS software, but an alternative is to disable the “IHS On Claim” by setting it to “False”.
Interfaces (OPOS Service names): OEM USB for Magellan (TableScanner or USBScanner); OEM USB for Handhelds (HandScanner or USBHHScanner)
- Make sure your scanner is programmed for the OEM USB Interface type. In the device manager of windows an OEM USB device will show up under Human Interface Devices with two handles for both a handheld and scanner only device and four handles for a scanner/scale device. The names that come up are generic so you have to pay attentiong to what shows up when you plug it in to check the VID for Datalogic which is 05F9.
- Check the cable connections, make sure your interface cable is plugged into the blue port on our scanner/scale devices. This port is marked “Host Port” on the scanner.
- Note that when a Datalogic scanner is in the OEM USB interface and is initially plugged into the USB port on the host, the scanner will be disabled by the host usually resulting in a slow blink of the green LED. If this does not occur, make sure you are using the correct cable for the current product.
- If all these are previous points are good the host may have an application that claims the device before the Dualtest or your POS software can claim it. When this occurs, you can figure out what app is doing this and disable the feature, or you can add a registry key to your OEM USB OPOS Service name called “PortShareMode”.
You can do this by right clicking in the window, hover over “New” and then select “String Value”. 3
Type in the name “PortShareMode” and set the value to “1”. This allows more than one application to claim the device in this interface.
You will need to restart Dualtest or your POS software to see the results take effect.
- The default configuration for OPOS is to request the Identification, Health and Status of the scanner upon claiming. If something is interrupting this, you will also receive the no hardware error. If you do not see this error in Dualtest but your POS software cannot seem to claim the device, it maybe that the POS software does not allow enough time for the scanner to report back this information causing a failure to claim. It is recommended to resolve this in the POS software, but an alternative is to disable the “IHS On Claim” by setting it to “False”.
Don’t forget to apply it in the OPOS editor after making the change.
- Make sure the Datalogic USB Com driver is installed before connecting the scanner. You can find the latest version here.
The “RS232Imager” OPOS Service name has a setting called “Use Virtual Port” in the OPOS editor. This is set to “True” by default. This allows OPOS to find a working USB virtual comport when a device is plugged in and allows the changing of this port unlike the RS232 interface mentioned in the beginning of this document because these ports do not always behave statically. Sometimes the OS changes them and OPOS needs to adjust because of it.
Make sure your scanner is programmed for the USB Com Interface.
Check the cable connections.
The default configuration for OPOS is to request the Identification, Health and Status of the scanner upon claiming. If something is interrupting this, you will also receive the no hardware error. If you do not see this error in Dualtest but your POS software cannot seem to claim the device, it maybe that the POS software does not allow enough time for the scanner to report back this information causing a failure to claim. It is recommended to resolve this in the POS software, but an alternative is to disable the “IHS On Claim” by setting it to “False”.
Don’t forget to apply it in the OPOS editor after making the change.
Search for the latest USB Com Driver (For USB Com interfaces only)