jhm783
Posts: 5
Joined: Tue Jul 05, 2016 4:20 pm

Tripplite Keyspan

Tue Aug 09, 2016 4:00 pm

I am just getting started with the Rasp Pi and have been testing different connections to the OS. I have used Putty to connect across the network. Works fine. I also have a Keyspan UAS-19hs USB to Serial adapter, so I’m trying to use it with an old PC running a VT100 emulator through the serial port. Following another piece of advice, I did the following:
apt-get update
apt-get install firmware-linux-free
Now the Keyspan blinks (I think indicating a good connection), but I’m not sure how to configure the OS to recognize the connection.

You can see how new I am to this, so if I’m completely bonkers, I apologize.

Any thoughts.

jhm783
Posts: 5
Joined: Tue Jul 05, 2016 4:20 pm

Re: Tripplite Keyspan

Wed Aug 10, 2016 9:34 pm

Actually it is being recognized, but is not responding to key strokes.
dmseg |tail -20 follows:

[ 12.098561] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 12.098757] Bluetooth: HCI UART protocol BCM registered
[ 12.313253] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 12.313266] Bluetooth: BNEP filters: protocol multicast
[ 12.313279] Bluetooth: BNEP socket layer initialized
[ 33.169310] usb 1-1.4: new full-speed USB device number 7 using dwc_otg
[ 33.322143] usb 1-1.4: New USB device found, idVendor=06cd, idProduct=0121
[ 33.322162] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 33.322175] usb 1-1.4: Product: Keyspan USA-19H
[ 33.322188] usb 1-1.4: Manufacturer: Keyspan, a division of InnoSys Inc.
[ 34.391142] usbcore: registered new interface driver usbserial
[ 34.391250] usbcore: registered new interface driver usbserial_generic
[ 34.391350] usbserial: USB Serial support registered for generic
[ 34.397930] usbcore: registered new interface driver keyspan
[ 34.398046] usbserial: USB Serial support registered for Keyspan - (without firmware)
[ 34.398145] usbserial: USB Serial support registered for Keyspan 1 port adapter
[ 34.398249] usbserial: USB Serial support registered for Keyspan 2 port adapter
[ 34.398342] usbserial: USB Serial support registered for Keyspan 4 port adapter
[ 34.398470] keyspan 1-1.4:1.0: Keyspan 1 port adapter converter detected
[ 34.399045] usb 1-1.4: Keyspan 1 port adapter converter now attached to ttyUSB0

User avatar
Doctorwho8
Posts: 56
Joined: Mon Dec 31, 2012 11:00 pm
Location: Astoria NY
Contact: Website

Re: Tripplite Keyspan

Sun Dec 30, 2018 2:00 am

Hello!
I confess I just went through the same problem, now about two years later, and found that after installing the firmware describe there, I needed to unplug it and to then plug it back in, this is a regular USA-19 device:
pi@raspberrypi:~$ dmesg | tail -20
[ 722.164066] usb 1-1: New USB device found, idVendor=06cd, idProduct=0103
[ 722.164086] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 722.179401] keyspan 1-1:1.0: Keyspan - (without firmware) converter detected
[ 722.179506] usb 1-1: Direct firmware load for keyspan/usa19.fw failed with error -2
[ 722.179529] usb 1-1: ezusb_ihex_firmware_download - request "keyspan/usa19.fw" failed
[ 722.179537] usb 1-1: failed to load firmware "keyspan/usa19.fw"
[ 722.179594] keyspan: probe of 1-1:1.0 failed with error -2
[ 722.179709] keyspan_pda 1-1:1.0: Keyspan PDA - (prerenumeration) converter detected
[ 722.263652] usb 1-1: USB disconnect, device number 4
[ 722.263817] keyspan_pda 1-1:1.0: device disconnected
[ 723.963413] Indeed it is in host mode hprt0 = 00021501
[ 724.173271] usb 1-1: new full-speed USB device number 5 using dwc_otg
[ 724.173579] Indeed it is in host mode hprt0 = 00021501
[ 724.415392] usb 1-1: New USB device found, idVendor=06cd, idProduct=0104
[ 724.415413] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 724.415421] usb 1-1: Product: ACME USB serial widget
[ 724.415429] usb 1-1: Manufacturer: ACME usb widgets
[ 724.415435] usb 1-1: SerialNumber: 47
[ 724.434172] keyspan_pda 1-1:1.0: Keyspan PDA converter detected
[ 724.434766] usb 1-1: Keyspan PDA converter now attached to ttyUSB0
pi@raspberrypi:~$
And as all of us can see the device is now properly assigned. It is the firmware that does it. This is for a project concerning an older RS computer as a serial console.
-------------------
Gregg
Doctor Who8

Return to “Interfacing (DSI, CSI, I2C, etc.)”