Can't access USB port for serial communication via infrared

[maverick]

Hello guys,

I have a Bubba|2 since september 2010. I enjoy it very much as it works really as my central network router, dhcp server, dns, firewall and http proxy

I've been trying to use my Bubba|2 server to read out the my electricity meter. I've purchased an infrared read/write-head-to-usb cable to access the electricity meter through a serial infrared connection.
I've got this cable and connection to the electricity meter working on windows using the HTerm program.

However when I try to use python scripts on the Bubba server to access the /dev/ttyUSB0, it seems that the shell can't access the USB port whatsoever. It won't get any response and it seems that access is denied, even though I'm root.

This is the log (/var/log/messages) when I reconnect the cable:

Code: Select all

Aug 27 20:56:13 bubba kernel: usb 1-1.1: USB disconnect, device number 3
Aug 27 20:56:13 bubba kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Aug 27 20:56:13 bubba kernel: cp210x 1-1.1:1.0: device disconnected
Aug 27 20:56:16 bubba kernel: usb 1-1.1: new full speed USB device number 4 using fsl-ehci
Aug 27 20:56:16 bubba kernel: cp210x 1-1.1:1.0: cp210x converter detected
Aug 27 20:56:16 bubba kernel: usb 1-1.1: reset full speed USB device number 4 using fsl-ehci
Aug 27 20:56:16 bubba kernel: usb 1-1.1: cp210x converter now attached to ttyUSB0

I know that bubba has some sort of support for external harddisks via usb. Does anyone know how I can disable that support to make sure that isn't hogging the USB connections?

[Gordon]

Probably a driver issue. You may find some useful information here

[maverick]

I've reviewed that driver page numerous of times.
Can you tell me how I can reinstall the driver or how I can debug the communication when using the pythons scripts for communication?

[Gordon]

The way that I understand is that this device can have a vendor code that is unknown to the driver. So if the driver doesn't work this can be the result of the driver not recognizing the device. In that case you need to edit the source of the driver to include that vendor code and recompile. A simple reinstall of the stock driver will not work.