New USB Device
Hi Greg,
using a serial device driver is the idea of the manufacturer "www.gns-gmbh.com". In the LINUX instructions of the ADS-B receiver some hints to use the device are given via usbserial.
In practice the "GNS 5890 ADS-B Receiver" is similare to some GPS Receivers with NMEA 0183 interface starting to send information on the serial interface after power on and signal availabillity (with 115200 boud data rate).
does this help?
best regards
Markus
Am 03.07.2019 18:38, schrieb Greg KH:
Quoted 39 lines · Markus Breunig
Quoted 22 lines
Hello,
my Raspberry Pi told me to send you the following information. I hope it helps ...
best regards
Markus
--------------------------------
[ 2.081893] usb 1-1.2: new full-speed USB device number 4 using dwc_otg [ 2.219804] usb 1-1.2: New USB device found, idVendor=04d8, idProduct=f8e8, bcdDevice=48.12 [ 2.219821] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.219830] usb 1-1.2: Product: GNS 5890 ADS-B Receiver [ 2.219839] usb 1-1.2: Manufacturer: www.gns-gmbh.com [ 1517.863755] usbcore: registered new interface driver usbserial_generic [ 1517.863830] usbserial: USB Serial support registered for generic [ 1517.863916] usbserial_generic 1-1.2:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes. [ 1517.863927] usbserial_generic 1-1.2:1.0: TellQuoted 8 lines
[email protected] to add your device to a proper driver.
[ 1517.863939] usbserial_generic 1-1.2:1.0: device has no bulk endpoints [ 1517.864009] usbserial_generic 1-1.2:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes. [ 1517.864018] usbserial_generic 1-1.2:1.1: Tell [email protected] to add your device to a proper driver. [ 1517.864028] usbserial_generic 1-1.2:1.1: generic converter detected [ 1517.865108] usb 1-1.2: generic converter now attached to ttyUSB0This device isn't even a generic usb to serial converter, why did you tell your module configuration to bind to this specific device?
thanks,
greg k-h
Greg KH
maintainerQuoted 5 lines · Markus Breunig
Hi Greg,
using a serial device driver is the idea of the manufacturer "www.gns-gmbh.com". In the LINUX instructions of the ADS-B receiver some hints to use the device are given via usbserial.
Any pointers to those instructions?
Quoted 6 lines
In practice the "GNS 5890 ADS-B Receiver" is similare to some GPS Receivers with NMEA 0183 interface starting to send information on the serial interface after power on and signal availabillity (with 115200 boud data rate).
does this help?
Does the device actually work with those instructions?
Can you provide the output of 'lsusb -v' with the device plugged in?
thanks,
greg k-h
Hi Greg,
also the company GNS has a fragmented homepage, the handbook ist available here:
http://www.servicedocs.com/ARTIKELEN/7200284490001.pdf
habe a look to page 10 "Remarks to Linux"
This is the log of "lsusb -v" (full scan result attached):
Bus 001 Device 004: ID 04d8:f8e8 Microchip Technology, Inc. Harmony 300/350 Remote
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x04d8 Microchip Technology, Inc. idProduct 0xf8e8 Harmony 300/350 Remote bcdDevice 48.12 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 1.10
CDC ACM:
bmCapabilities 0x02
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Call Management:
bmCapabilities 0x00
bDataInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
best regards
Markus
Am 05.07.2019 07:21, schrieb Greg KH:
Quoted 16 lines · Markus Breunig
Quoted 5 lines
Hi Greg,
using a serial device driver is the idea of the manufacturer "www.gns-gmbh.com". In the LINUX instructions of the ADS-B receiver some hints to use the device are given via usbserial.
Any pointers to those instructions?
Quoted 6 lines
In practice the "GNS 5890 ADS-B Receiver" is similare to some GPS Receivers with NMEA 0183 interface starting to send information on the serial interface after power on and signal availabillity (with 115200 boud data rate).
does this help?
Quoted 8 lines
Does the device actually work with those instructions?
Can you provide the output of 'lsusb -v' with the device plugged in?
thanks,
greg k-h
Bus 001 Device 006: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc05a M90/M100 Optical Mouse bcdDevice 54.00 iManufacturer 1 iProduct 2 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 98mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 67
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 0x0006 1x 6 bytes
bInterval 10
Bus 001 Device 005: ID 046a:0001 Cherry GmbH Keyboard Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046a Cherry GmbH idProduct 0x0001 Keyboard bcdDevice 0.26 iManufacturer 1 iProduct 0 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 100mA
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.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 64
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 10
Bus 001 Device 004: ID 04d8:f8e8 Microchip Technology, Inc. Harmony 300/350 Remote Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x04d8 Microchip Technology, Inc. idProduct 0xf8e8 Harmony 300/350 Remote bcdDevice 48.12 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 1.10
CDC ACM:
bmCapabilities 0x02
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Call Management:
bmCapabilities 0x00
bDataInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0424 Standard Microsystems Corp.
idProduct 0xec00 SMSC9512/9514 Fast Ethernet Adapter
bcdDevice 2.00
iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 2 TT per port bMaxPacketSize0 64 idVendor 0x0424 Standard Microsystems Corp. idProduct 0x9514 SMC9514 Hub bcdDevice 2.00 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 1 Single TT
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 2 TT per port
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 1 Single TT bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 4.19 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
[ Pleas avoid top posting. ]
Quoted 11 lines · Markus Breunig
Hi Greg,
also the company GNS has a fragmented homepage, the handbook ist available here:
http://www.servicedocs.com/ARTIKELEN/7200284490001.pdf
habe a look to page 10 "Remarks to Linux"This is the log of "lsusb -v" (full scan result attached):
Bus 001 Device 004: ID 04d8:f8e8 Microchip Technology, Inc. Harmony 300/350 Remote
Are you sure this is the right device? This looks like a remote control, and one that should be using the cdc-acm driver.
Quoted 87 lines
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific ClassbDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x04d8 Microchip Technology, Inc. idProduct 0xf8e8 Harmony 300/350 Remote bcdDevice 48.12 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 1.10
CDC ACM:
bmCapabilities0x02
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Call Management:
bmCapabilities0x00
bDataInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress0x82EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize0x00081x 8 bytes
bInterval 2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress0x03EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize0x00401x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress0x83EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize0x00401x 64 bytes
bInterval 0
Quoted 14 lines
Am 05.07.2019 07:21, schrieb Greg KH:
Quoted 13 lines · Markus Breunig
Quoted 5 lines
Hi Greg,
using a serial device driver is the idea of the manufacturer "www.gns-gmbh.com". In the LINUX instructions of the ADS-B receiver some hints to use the device are given via usbserial.
Any pointers to those instructions?
Quoted 4 lines
In practice the "GNS 5890 ADS-B Receiver" is similare to some GPS Receivers with NMEA 0183 interface starting to send information on the serial interface after power on and signal availabillity (with 115200 boud data rate).
Johan
Am 16.07.2019 um 11:23 schrieb Johan Hovold:
Quoted 10 lines
[ Pleas avoid top posting. ]
Quoted 7 lines · Markus Breunig
Hi Greg,
also the company GNS has a fragmented homepage, the handbook ist available here:
http://www.servicedocs.com/ARTIKELEN/7200284490001.pdf
habe a look to page 10 "Remarks to Linux"
Quoted 8 lines
Quoted 4 lines
This is the log of "lsusb -v" (full scan result attached):
Bus 001 Device 004: ID 04d8:f8e8 Microchip Technology, Inc. Harmony 300/350 Remote
Are you sure this is the right device? This looks like a remote control, and one that should be using the cdc-acm driver.
The output of lsusb before plugging the GNS5890 device into the USB-port:
Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 046a:0001 Cherry GmbH Keyboard
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and the result of the lsusb after plugging the GNS5890 device into the USB-port:
Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 046a:0001 Cherry GmbH Keyboard
Bus 001 Device 006: ID 04d8:f8e8 Microchip Technology, Inc. Harmony 300/350 Remote
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Quoted 104 lines
Quoted 87 lines
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor0x04d8Microchip Technology, Inc.
idProduct0xf8e8Harmony 300/350 Remote
bcdDevice 48.12
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 1.10
CDC ACM:
bmCapabilities0x02
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Call Management:
bmCapabilities0x00
bDataInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress0x82EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize0x00081x 8 bytes
bInterval 2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress0x03EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize0x00401x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress0x83EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize0x00401x 64 bytes
bInterval 0Quoted 14 lines
Am 05.07.2019 07:21, schrieb Greg KH:
Quoted 13 lines · Markus Breunig
Quoted 5 lines
Hi Greg,
using a serial device driver is the idea of the manufacturer "www.gns-gmbh.com". In the LINUX instructions of the ADS-B receiver some hints to use the device are given via usbserial.
Any pointers to those instructions?
Quoted 4 lines
In practice the "GNS 5890 ADS-B Receiver" is similare to some GPS Receivers with NMEA 0183 interface starting to send information on the serial interface after power on and signal availabillity (with 115200 boud data rate).
Johan
Quoted 34 lines · Markus Breunig
Am 16.07.2019 um 11:23 schrieb Johan Hovold:
Quoted 10 lines
[ Pleas avoid top posting. ]
Quoted 7 lines · Markus Breunig
Hi Greg,
also the company GNS has a fragmented homepage, the handbook ist available here:
http://www.servicedocs.com/ARTIKELEN/7200284490001.pdf
habe a look to page 10 "Remarks to Linux"Quoted 8 lines
Quoted 4 lines
This is the log of "lsusb -v" (full scan result attached):
Bus 001 Device 004: ID 04d8:f8e8 Microchip Technology, Inc. Harmony 300/350 Remote
Are you sure this is the right device? This looks like a remote control, and one that should be using the cdc-acm driver.
The output of lsusb before plugging the GNS5890 device into the USB-port:
Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 046a:0001 Cherry GmbH Keyboard
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root huband the result of the lsusb after plugging the GNS5890 device into the USB-port:
Quoted 8 lines
Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 046a:0001 Cherry GmbH Keyboard
Bus 001 Device 006: ID 04d8:f8e8 Microchip Technology, Inc. Harmony 300/350 Remote
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Ok, thanks for confirming.
Based on the below descriptors, this device should be handled by the cdc-acm driver and show up as a /dev/ttyACMn.
Do you have that driver enabled? Can you enable debugging in that driver and post the syslog from when plugging the device in if it still doesn't work?
You can enable debugging using
modprobe cdc-acm dyndbg==p
or through sysfs, see
Documentation/admin-guide/dynamic-debug-howto.rst
Quoted 49 lines
Quoted 49 lines
Quoted 49 lines
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor0x04d8Microchip Technology, Inc.
idProduct0xf8e8Harmony 300/350 Remote
bcdDevice 48.12
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 1.10
CDC ACM:
bmCapabilities0x02
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Call Management:
bmCapabilities0x00
bDataInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
bEndpointAddress
0x82EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize0x00081x 8 bytes
bInterval 2
Interface Descriptor:
Johan