Office: 503-443-2000 | Fax: 503-968-1877 | Email:
Nu Tech Software Solutions is an Information Technology Services and Software Development company.
We focus on highly available applications for both the Internet and Enterprise. Expertise in both the Microsoft and Linux/LAMP environments.
If you need a Content Management System (CMS) we can do it! We are experienced with both Joomla! and Drupal!
Contact us at: Phone: (503) 443-2000, Email:

Home
AlarmDecoder/AD2USB
Contact Us
AlarmDecoder Forum
FAQ
Online Store
 Home
Welcome, Guest
Please Login or Register.    Lost Password?
Linux "disabled by hub (EMI?)" for rev2? (2 viewing) (2) Guests
Discuss our ADEMCO Emulator hardware.
Go to bottom Favoured: 0
TOPIC: Linux "disabled by hub (EMI?)" for rev2?
#118
Linux "disabled by hub (EMI?)" for rev2? 4 Years, 8 Months ago Karma: 1  
Any ideas why the rev2 emulator would suddenly trigger a change of device on Linux? I've been using it on a 24/7 system where it has been /dev/ttyUSB0, but suddenly I notice it occasionally switched to /dev/ttyUSB1 and back, and I'm not sure why....

The only thing unusual I note in the log when it switches is like the following where it complains about being "disabled by the hub (EMI?)"?



hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [8] = 0x00020101 PESC PPS CCS
hub 2-0:1.0: port 9 enable change, status 00000101
hub 2-0:1.0: port 9 disabled by hub (EMI?), re-enabling...
hub 2-0:1.0: port 9, status 0101, change 0002, 12 Mb/s
usb 2-9: USB disconnect, address 7
usb 2-9: unregistering device
usb 2-9: usb_disable_device nuking all URBs
ohci_hcd 0000:00:02.0: shutdown urb e4693440 ep1in-bulk
ohci_hcd 0000:00:02.0: urb e4693440 path 9 ep1in 5f160000 cc 5 --> status -62
usb 2-9: unregistering interface 2-9:1.0
ftdi_sio 2-9:1.0: device disconnected
usb 2-9:1.0: uevent
usb 2-9: uevent
ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
usb 2-9: new full speed USB device using ohci_hcd and address 8
ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
usb 2-9: ep0 maxpacket = 8
usb 2-9: default language 0x0409
usb 2-9: uevent
usb 2-9: usb_probe_device
usb 2-9: configuration #1 chosen from 1 choice
usb 2-9: adding 2-9:1.0 (config #1, interface 0)
usb 2-9:1.0: uevent
usbserial_generic 2-9:1.0: usb_probe_interface
usbserial_generic 2-9:1.0: usb_probe_interface - got id
ftdi_sio 2-9:1.0: usb_probe_interface
ftdi_sio 2-9:1.0: usb_probe_interface - got id
ftdi_sio 2-9:1.0: FTDI USB Serial Device converter detected
ftdi_sio: Detected FT232RL
usb 2-9: FTDI USB Serial Device converter now attached to ttyUSB1
drivers/usb/core/inode.c: creating file '008'
usb 2-9: New USB device found, idVendor=0403, idProduct=6001
usb 2-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-9: Product: FT245R USB FIFO
usb 2-9: Manufacturer: FTDI
usb 2-9: SerialNumber: A2001wLc
ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [8] = 0x00020101 PESC PPS CCS
hub 2-0:1.0: port 9 enable change, status 00000101
hub 2-0:1.0: port 9 disabled by hub (EMI?), re-enabling...
hub 2-0:1.0: port 9, status 0101, change 0002, 12 Mb/s
usb 2-9: USB disconnect, address 8
usb 2-9: unregistering device
usb 2-9: usb_disable_device nuking all URBs
usb 2-9: unregistering interface 2-9:1.0
ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
ftdi_sio 2-9:1.0: device disconnected
usb 2-9:1.0: uevent
usb 2-9: uevent
ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
usb 2-9: new full speed USB device using ohci_hcd and address 9
ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
usb 2-9: ep0 maxpacket = 8
usb 2-9: default language 0x0409
usb 2-9: uevent
usb 2-9: usb_probe_device
etc....
bigbadwolf (User)
Fresh Boarder
Posts: 10
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
The administrator has disabled public write access.  
#119
Re:Linux "disabled by hub (EMI?)" for rev2? 4 Years, 8 Months ago Karma: 7  
Effects both V1 and V2 boards this is what happens when the USB hub in your computer senses a glitch on the USB line caused by power spikes and unlike serial that just keeps going USB shuts down the hub and on most systems restarts it. On some it requires a reboot.

I have a few things to look for.

Have you added any new appliances to your house or anything near the alarm panel's 12v transformer. This seems most common with motors such as found in a fridge or power tools.

I have been looking at an adapter solution the engineer at FTDI suggested. I was thinking about putting it on a usb cable for situations where power noise is a problem. I will order the chip today and see how it works but i have my doubts. I am also looking for some usb hubs that will buffer the noise and remove it if you have any usb 1 or 2 hubs try them and see if it help and let me know if any work.
mathewss (Admin)
Admin
Posts: 512
graph
User Offline Click here to see the profile of this user
Gender: Male
Logged Logged  
 
struct SoftwareProfessional {
double salary;
long lunches;
float jobs;
char unstable;
void work;
short tempers;
};
 
The administrator has disabled public write access.  
#120
Re:Linux "disabled by hub (EMI?)" for rev2? 4 Years, 8 Months ago Karma: 7  
I ordered this board today I will test it in my lab and see if the the isolator chip ADuM4160 on this board does the job.


http://www.circuitsathome.com/store#adum4160_usb_isolator_kits
mathewss (Admin)
Admin
Posts: 512
graph
User Offline Click here to see the profile of this user
Gender: Male
Logged Logged  
 
struct SoftwareProfessional {
double salary;
long lunches;
float jobs;
char unstable;
void work;
short tempers;
};
 
The administrator has disabled public write access.  
#121
Re:Linux "disabled by hub (EMI?)" for rev2? 4 Years, 8 Months ago Karma: 1  
Any hints on a particular type or length of USB cable to use to minimize the effect?
bigbadwolf (User)
Fresh Boarder
Posts: 10
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
The administrator has disabled public write access.  
#122
Re:Linux "disabled by hub (EMI?)" for rev2? 4 Years, 8 Months ago Karma: 1  
By the way, in case this helps anyone else, in the short term I've added the following to the file /etc/udev/rules.d/44-ad2usb.rules (all one line) on my Debian linux host:

KERNEL=="ttyUSB[0-9]*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A2001wLc", NAME="alarmpanel", MODE="0660"

This will at least ensure the device is always at /dev/alarmpanel even if it disconnects and reconnects. The match is not perfect since there is not a lot of unique info returned about the device rather than the general interface chip, but I don't plug a lot of USB devices into this machine. FYI, I got the value for the "serial" attribute by running the command "udevinfo -a -p `udevinfo -q path -n /dev/ttyUSB0`"
bigbadwolf (User)
Fresh Boarder
Posts: 10
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
The administrator has disabled public write access.  
#123
Re:Linux "disabled by hub (EMI?)" for rev2? 4 Years, 8 Months ago Karma: 7  
Cool. Thats an excellent tip thanks!
mathewss (Admin)
Admin
Posts: 512
graph
User Offline Click here to see the profile of this user
Gender: Male
Logged Logged  
 
struct SoftwareProfessional {
double salary;
long lunches;
float jobs;
char unstable;
void work;
short tempers;
};
 
The administrator has disabled public write access.  
Go to top





Lost Password?
©2014 Nu Tech Software Solutions, Inc. | Terms and Conditions | Service Level Agreement | Acceptable Use Policies | Contact Us