Code: Select all
device not accepting address **, error -22
Got it. I understand the device is violating USB specs, but I wonder if there is any workaround you can suggest / think of to folks still interested in using it -- unfortunately there aren't a lot of other good alternatives in the market and I think lots of folks will want to use this with the Pi 4.My opinion is that it's not a fault of the USB chip to refuse to talk to a device that could potentially fry the port logic.
Completely different USB controller.
I purchased the above and am having trouble getting consistent working results. I did eventually get it to work, but the pi suddenly stopped detecting the Aeotec Z-Wave USB Stick Gen5 for some reason. I don't know if it overheated causing it or if it was due to the voltage issue described by jdb (who is obviously very knowledgeable). jdb, your help and insight into the topic is much appreciated and I completely understand your frustration with the non-compliant device. There is no excuse for developing devices that do not adhere to USB standards; however, unfortunately, we appear to be stuck with this misbehaving device since there appears to be no better alternative. Is it possible for jdb to suggest a workaround that will function consistently. Again, I want to thank you for your time and attention.
As you say, there is no excuse. It is not reasonable to except RPF/T to fix someone else's broken design. They have many other things to fix that affect far more Pi users.
This device have an internal battery to allow standalone in-place z-wave associations with remote modules that may be too far from the machine hosting the home management stuff. This was a nice feature, as secured z-wave associations needs a symmetric key exchange & you don't want it to be catched... So association must be done closely because of reduced radio power.
Soo.. not to be sarcastic or anything, but are we sure that raspberry 4 is following USB specifications?jdb wrote: ↑Wed Jul 17, 2019 11:06 amThis device has some very non-compliant behaviours.
- On initial connect, it pulls D+ to +5V through a strong pull-up. After 20ms, the pull strength drops which results in D+ dropping to about 4.1V. This is a gross violation of the USB electrical spec.
- If I plug this device into either the Pi 4 or a USB3.0 hub with VIA chipset, the 20ms pull to 5V appears to trigger some sort of protection within the upstream port - both D+ and D- lines end up at >3.3V (SE1) and a device attach does not occur. Plugging a different device into the same port results in an attach event, so it appears the behaviour is temporary.
I can get it into a state where the device does actually attach, by forcing D- to 0V temporarily. In this state, the D- line floats up to 3v3 after every packet so it looks like the upstream port 10k pull-down resistor(s) aren't enabled.
My opinion is that it's not a fault of the USB chip to refuse to talk to a device that could potentially fry the port logic.