rub3n.47
Posts: 4
Joined: Wed Apr 22, 2015 2:05 pm

USB barcode scanner not working

Wed Apr 22, 2015 2:17 pm

I have a Symbol Technologies USB barcode scanner plugged into my brand new Rasp Pi 2 (Woohoo!).

I've installed Raspbian as the OS - and everything seems to be working.

My issue is that the Barcode scanner isn't sending the Pi any information.

How can I go about troubleshooting this device?
Do I need to download a driver?

User avatar
topguy
Posts: 5755
Joined: Tue Oct 09, 2012 11:46 am
Location: Trondheim, Norway

Re: USB barcode scanner not working

Wed Apr 22, 2015 2:29 pm

> My issue is that the Barcode scanner isn't sending the Pi any information.

How do you know ?

> Do I need to download a driver?

Usually no, but had you provided a link to a product page or something I could have made a more educated guess.

> How can I go about troubleshooting this device?

Start with reading this:
viewtopic.php?f=28&t=53832

Do the parts related to "lsusb" and "dmesg" and post the results here.

rub3n.47
Posts: 4
Joined: Wed Apr 22, 2015 2:05 pm

Re: USB barcode scanner not working

Wed Apr 22, 2015 3:23 pm

My issue is that the barcode scanner isn't sending the Pi any information.
> How do you know ?
>>I opened Text Editor and tried to scan a barcode - nothing showed up. So it may very well be passing data - but not in a format that can be interpreted as text.

Do I need to download a driver?
> Usually no, but had you provided a link to a product page or something I could have made a more educated guess.
>>Here is the link: [url]http://www.scansource-europe.com/motoro ... _ss_en.pdf[/url]

How can I go about troubleshooting this device?
>Start with reading this:= view ... 28&t=53832
>Do the parts related to "lsusb" and "dmesg" and post the results here.
>> lsusb :

[size=85]Bus 001 Device 010: ID 05e0:1200 Symbol Technologies Bar Code Scanner[/size]

>> dmesg:

[size=85][email protected] ~ $ dmesg:
[ 7953.838618] usb 1-1.3: USB disconnect, device number 8
[ 7964.058951] usb 1-1.3: new full-speed USB device number 10 using dwc_otg
[ 7964.176331] usb 1-1.3: New USB device found, idVendor=05e0, idProduct=1200
[ 7964.176356] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7964.176374] usb 1-1.3: Product: Symbol Bar Code Scanner
[ 7964.176392] usb 1-1.3: Manufacturer: \xffffffef\xffffffbe\xffffffa9\xffffffbe\xffffffa9Symbol Technologies, Inc, 2002
[ 7964.176410] usb 1-1.3: SerialNumber: S/N:E2E75F443E543647B002B82F24B53BB4 Rev:NBRMSAABDM:13MAY103
[ 7964.191873] input: \xffffffef\xffffffbe\xffffffa9\xffffffbe\xffffffa9Symbol Technologies, Inc, 2002 Symbol Bar Code Scanner as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:05E0:1200.0005/input/input4
[ 7964.193351] hid-generic 0003:05E0:1200.0005: input,hidraw0: USB HID v1.10 Keyboard [\xffffffef\xffffffbe\xffffffa9\xffffffbe\xffffffa9Symbol Technologies, Inc, 2002 Symbol Bar Code Scanner] on usb-bcm2708_usb-1.3/input0[/size]

rub3n.47
Posts: 4
Joined: Wed Apr 22, 2015 2:05 pm

Re: USB barcode scanner not working

Fri Apr 24, 2015 3:31 pm

I still have not been able to configure the scanner in a way that sends ANSII data to the Pi.

riklaunim
Posts: 265
Joined: Tue Apr 22, 2014 7:34 pm

Re: USB barcode scanner not working

Fri Apr 24, 2015 8:08 pm

Plain scanners will "type" text when a barcode is scanned. More advanced have some settings and need to be set into such mode - usually by scanning a special barcode given by vendor.

ktb
Posts: 1380
Joined: Fri Dec 26, 2014 7:53 pm

Re: USB barcode scanner not working

Sun Apr 26, 2015 3:55 pm

riklaunim wrote:Plain scanners will "type" text when a barcode is scanned. More advanced have some settings and need to be set into such mode - usually by scanning a special barcode given by vendor.
That has been my experience whether a scanner uses USB or Bluetooth. If the scanner works as a simple HID keyboard, it should just work. For example, I just plugged an old CueCat into the Pi2B, slid the CueCat over the barcode on the Element 14 Pi2B box and it spit out 640522710515

BTW, it seems as though the CueCat will (at least sometimes -- maybe only with the Pi) power itself off if not used for a certain amount of time and at that point it will not wake up or be usable again until being unplugged and plugged in again. I haven't experimented with it much.

Code: Select all

~ $ lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. 
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 007: ID 1058:0820 Western Digital Technologies, Inc. 
Bus 001 Device 005: ID 0461:4d0f Primax Electronics, Ltd HP Optical Mouse
Bus 001 Device 009: ID 0458:0101 KYE Systems Corp. (Mouse Systems) CueCat
Bus 001 Device 006: ID 04ca:002a Lite-On Technology Corp. 

~ $ lsusb -s 001:009 -v

Bus 001 Device 009: ID 0458:0101 KYE Systems Corp. (Mouse Systems) CueCat
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0458 KYE Systems Corp. (Mouse Systems)
  idProduct          0x0101 CueCat
  bcdDevice            1.00
  iManufacturer           0 
  iProduct                1 :Cue:CAT
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower               48mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      1 Keyboard
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      47
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               8
Device Status:     0x0002
  (Bus Powered)
  Remote Wakeup Enabled

Return to “General discussion”