Linux cdc-acm-driver

Discussion:

Johan Hovold

2012-02-29 14:58:10 UTC

Hello Johan,
i hope, you can help me. I try to get a barcode-Scanner (Metrologic
Focus MS 1690) to work. If i take a look at the Windows driver, this
scanner should work in serial-mode as CDC ACM.
{ USB_DEVICE(0x0c2e, 0x0720), /*Metro Metrologic MS7120 Barcode Scanner
(bi-directional serial mode) */
},
and recompile the module. If i plug the device in, the module cdc-acm is
loaded. But no device ttyACM0 appears.

What does lsusb -v say? If it is a cdc-acm device you should not need to
add the pid/vid to the cdc-acm driver.

What is written to the system logs?

Is there a possibility to debug the module? I would like to know, what
happens.

If your recompiling the module you can enable debugging by changing the
following "undef"

#undef DEBUG

to "define", or you can enable dynamic debugging (see
Documentation/dynamic-debug-howto.txt).

Thanks,
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Manavendra Nath Manav

2012-03-01 05:52:09 UTC

Permalink

Hi Johan

Barcode Scanner

(bi-directional serial mode) =A0*/
=A0 =A0 =A0 },
and recompile the module. If i plug the device in, the module cdc-ac=

m is

loaded. But no device ttyACM0 appears.

What does lsusb -v say? If it is a cdc-acm device you should not need=

add the pid/vid to the cdc-acm driver.
What is written to the system logs?

Is there a possibility to debug the module? I would like to know, wh=

happens.

If your recompiling the module you can enable debugging by changing t=

following "undef"
=A0 =A0 =A0 =A0#undef DEBUG
to "define", or you can enable dynamic debugging (see
Documentation/dynamic-debug-howto.txt).
Thanks,
Johan

Sorry for jumping in the middle of the thread, but I too have a
similar problem with Metrologic Focus MS1690 Barcode scanner.
Currently, I am getting the device as bi-directional serial mode but I
want to make it work as a USB HID Keyboard device. In the
manufacturer's manual there is a barcode to configure the device as
such. After this I can see from dmesg that first the device gets
registered as USB HID v1.11 Keyboard, the I guess the scanner power
cycles disconnecting the USB and again gets registered as a new
device.

*** dmesg snip ***
[69818.065741] input: Honeywell Scanning and Mobility Honeywell
Scanning and Mobility Scanner as
/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/input/input6
[69818.065810] generic-usb 0003:0C2E:0200.0003: input,hidraw2: USB HID
v1.11 Keyboard [Honeywell Scanning and Mobility Honeywell Scanning and
Mobility Scanner] on usb-0000:00:1d.1-1/input0
[69823.804854] usb 7-1: USB disconnect, address 2
[69827.180717] usb 7-1: new low speed USB device using uhci_hcd and add=
ress 3
[69827.355585] usb 7-1: New USB device found, idVendor=3D0c2e, idProduc=
t=3D0720
[69827.355590] usb 7-1: New USB device strings: Mfr=3D1, Product=3D2, S=
erialNumber=3D0
[69827.355593] usb 7-1: Product: Honeywell Scanning and Mobility Scanne=
r
[69827.355596] usb 7-1: Manufacturer: Honeywell Scanning and Mobility

[***@pe1800xs ~]# lsusb -v
Bus 007 Device 003: ID 0c2e:0720 Metro Metrologic MS7120 Barcode
Scanner (bi-dir ectional
serial mode)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0c2e Metro
idProduct 0x0720 Metrologic MS7120 Barcode Scanner
(bi-directional se rial
mode)
bcdDevice 1.00
iManufacturer 1 Honeywell Scanning and Mobility
iProduct 2 Honeywell Scanning and Mobility Scanner
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3 POS USB
bmAttributes 0x80
(Bus Powered)
MaxPower 450mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
** UNRECOGNIZED: 09 21 11 01 00 01 22 3f 00
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
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 10
Device Status: 0x0000
(Bus Powered)

[***@pe1800xs ~]# cat /proc/bus/usb/devices
T: Bus=3D07 Lev=3D01 Prnt=3D01 Port=3D00 Cnt=3D01 Dev#=3D 3 Spd=3D1.5=
MxCh=3D 0
D: Ver=3D 1.10 Cls=3D00(>ifc ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D =
1
P: Vendor=3D0c2e ProdID=3D0720 Rev=3D 1.00
S: Manufacturer=3DHoneywell Scanning and Mobility
S: Product=3DHoneywell Scanning and Mobility Scanner
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3D80 MxPwr=3D450mA
I:* If#=3D 0 Alt=3D 0 #EPs=3D 2 Cls=3Dff(vend.) Sub=3D00 Prot=3D00 Driv=
er=3D(none)
E: Ad=3D02(O) Atr=3D03(Int.) MxPS=3D 8 Ivl=3D10ms
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 8 Ivl=3D10ms

How to make this device work on Linux?

Please note this link http://forums.gentoo.org/viewtopic-t-852806.html
says that "They tracked it down to the scanner registering itself as a
keyboard and then power cycling and registering as a custom POS
device. I contacted the manufacturer and they sent me a barcode
(99940) which when scanned locked the device into USB keyboard mode.
It then worked fine as a standard keyboard."

--=20
Manavendra Nath Manav
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Stefan Dreyer

2012-03-01 08:27:30 UTC

Permalink

Hi,

allthough the answer is offtopic for cdc-acm-driver, i will answer,
because maybe it helps other people in future.

Post by Manavendra Nath Manav
Hi Johan
Sorry for jumping in the middle of the thread, but I too have a
similar problem with Metrologic Focus MS1690 Barcode scanner.
Currently, I am getting the device as bi-directional serial mode but I
want to make it work as a USB HID Keyboard device. In the
manufacturer's manual there is a barcode to configure the device as
such. After this I can see from dmesg that first the device gets
registered as USB HID v1.11 Keyboard, the I guess the scanner power
cycles disconnecting the USB and again gets registered as a new
device.
*** dmesg snip ***
[69818.065741] input: Honeywell Scanning and Mobility Honeywell
Scanning and Mobility Scanner as
/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/input/input6
[69818.065810] generic-usb 0003:0C2E:0200.0003: input,hidraw2: USB HID
v1.11 Keyboard [Honeywell Scanning and Mobility Honeywell Scanning and
Mobility Scanner] on usb-0000:00:1d.1-1/input0
[69823.804854] usb 7-1: USB disconnect, address 2
[69827.180717] usb 7-1: new low speed USB device using uhci_hcd and address 3
[69827.355585] usb 7-1: New USB device found, idVendor=0c2e, idProduct=0720
[69827.355590] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[69827.355593] usb 7-1: Product: Honeywell Scanning and Mobility Scanner
[69827.355596] usb 7-1: Manufacturer: Honeywell Scanning and Mobility
Bus 007 Device 003: ID 0c2e:0720 Metro Metrologic MS7120 Barcode
Scanner (bi-directional serial mode)
How to make this device work on Linux?

I can tell you exactly, what is going on. If the scanner switches to
ProductId=0720 (0c2e:0720) the scanner is working in Serial-Mode. If you
want the scanner let work as serial device, you have to use the driver
metro-usb. The manufacturer has this driver, but that one is outdatet
and doesn't compile on actual Linux kernel.
I found an actual driver, which compiles even with kernel 3.2
<https://gitorious.org/other/metro-usb/commits/master>

In HID/keyboard-mode, the Scanner identifies as ProductId=0720
(0C2E:0200). If you want to let the scanner work in keyboard-Mode, you
have to scan Code Number 3 on the following document:

<http://entwurf.ddnetservice.de/scanner/Factory_Recall_Defaults_39.doc>

If you use keyboard-mode with alphanumeric Barcodes, you have to set
your keyboard-Layout correctly. In my case, i have to set the scanner in
german-keyboard-mode. You find all scancodes for configuration on the
manufacturer-website:
<http://www.honeywellaidc.com/en-US/Downloads/Docs/Pages/default.aspx?pid=1690>

Don't bother to contact the technical support, if you have some more
problems.

Stefan

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Manavendra Nath Manav

2012-03-01 09:48:09 UTC

Permalink

On Thu, Mar 1, 2012 at 1:57 PM, Stefan Dreyer

Hi,
allthough the answer is offtopic for cdc-acm-driver, i will answer, because
maybe it helps other people in future.
I can tell you exactly, what is going on. If the scanner switches to
ProductId=0720 (0c2e:0720) the scanner is working in Serial-Mode. If you
want the scanner let work as serial device, you have to use the driver
metro-usb. The manufacturer has this driver, but that one is outdatet and
doesn't compile on actual Linux kernel.
I found an actual driver, which compiles even with kernel 3.2
<https://gitorious.org/other/metro-usb/commits/master>

Thanks a lot for the prompt reply, this should adequately solve my
problem. I am able to download the driver source and compile. However,
I have run into a trivial module format error.

[***@pe1800xs serial]# modinfo metro-usb.ko
filename: metro-usb.ko
description: Metrologic Instruments Inc. - USB-POS driver
author: Aleksey Babahin <tamerlan311-***@public.gmane.org>
author: Philip Nicastro
license: GPL
srcversion: AF4C7DDE2804EBB1578A05F
alias: usb:v0C2Ep0710d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0C2Ep0720d*dc*dsc*dp*ic*isc*ip*
depends: usbserial
vermagic: 2.6.35.6-45.fc14.i686 SMP mod_unload modversions 686
parm: debug:Print debug info (bool 1=on, 0=off) (bool)
parm: vendor:User specified vendor ID (ushort) (ushort)
parm: product:User specified product ID (ushort) (ushort)

[***@pe1800xs serial]# modprobe -f -v metro-usb
insmod /lib/modules/2.6.35.6-45.fc14.i686/kernel/drivers/usb/serial/metro-usb.ko
FATAL: Error inserting metro_usb
(/lib/modules/2.6.35.6-45.fc14.i686/kernel/drivers/usb/serial/metro-usb.ko):
Invalid module format

[***@pe1800xs serial]# uname -a
Linux pe1800xs 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC
2010 i686 i686 i386 GNU/Linux

[***@pe1800xs serial]# dmesg
[84119.755750] metro_usb: version magic '2.6.35.6-45.fc14.i686 SMP
mod_unload modversions 686 ' should be '2.6.35.6-45.fc14.i686 SMP
mod_unload 686 '

I am running Fedora14 with "Force module loading option disabled". How
can I turn it ON without recompiling the kernel. Or, since I have the
souce files of the driver (attached), how can I modify the metro-usb.c
file to provide suitable "module version".

--
Manavendra Nath Manav

Manavendra Nath Manav

2012-03-01 12:18:04 UTC

Permalink

On Thu, Mar 1, 2012 at 3:18 PM, Manavendra Nath Manav

Post by Manavendra Nath Manav
On Thu, Mar 1, 2012 at 1:57 PM, Stefan Dreyer

Hi,
allthough the answer is offtopic for cdc-acm-driver, i will answer, =

because