lost serial gateway after un plug power Rpi
-
is it a genuine arduino nano? I thought they where all using atmega32u4 for usb interface nowadays
-
is it a genuine arduino nano? I thought they where all using atmega32u4 for usb interface nowadays
-
Hi.
I had the same issue with (original) FTDI chipset ARDUINO.
I use FTDI chipset because that enables me to FIX the USB to stick at for example USB20 and not to a different port. Comes in handy after a reboot. Domoticz will continue to work.However ... I had the same issue you described.
I replaced ARDUINO with new one for testing with CH340.
Gateway was recognized again.
The failing FTDI Arduino that was nog recognized works perfectly well with my Windows 10 PC however not with Raspi.Keep in mind the CH340 has no serial number. I was unable to fix at a certain USB position.
From your logs I can confirm I had the same issue.
try: dmesg | grep "ÜSB"It will not show you a USB1 or USBx device.
I bought a new FTDI arduino and said bye bye to the problem. All is working again.
-
Hi.
I had the same issue with (original) FTDI chipset ARDUINO.
I use FTDI chipset because that enables me to FIX the USB to stick at for example USB20 and not to a different port. Comes in handy after a reboot. Domoticz will continue to work.However ... I had the same issue you described.
I replaced ARDUINO with new one for testing with CH340.
Gateway was recognized again.
The failing FTDI Arduino that was nog recognized works perfectly well with my Windows 10 PC however not with Raspi.Keep in mind the CH340 has no serial number. I was unable to fix at a certain USB position.
From your logs I can confirm I had the same issue.
try: dmesg | grep "ÜSB"It will not show you a USB1 or USBx device.
I bought a new FTDI arduino and said bye bye to the problem. All is working again.
-
No problem.
I had problems with original FTDI arduino.
For testing i changed to 340 arduino that worked.Than ordered new FTDI arduino.. And it worked again.
Do you have a spare ARDUINO that you can flash with your gateway software??If your gateway is not assigned a /dev/ttyUSBx address It will not work.
-
No problem.
I had problems with original FTDI arduino.
For testing i changed to 340 arduino that worked.Than ordered new FTDI arduino.. And it worked again.
Do you have a spare ARDUINO that you can flash with your gateway software??If your gateway is not assigned a /dev/ttyUSBx address It will not work.
@sincze
sorry again , i am beginner :)
first i do this Instructions (https://www.domoticz.com/wiki/PersistentUSBDevices) and dont work , after this , @tbowmo told me :
lsusb-> provide the output
unplug / plug the usb device
once more in your terminal
lsusb
-> provide output
also i do :
dmesg-> provide the output
unplug / plug the usb device
so now after unplug/plug , my gateway dont detect and dont work
-
No problem.
I had problems with original FTDI arduino.
For testing i changed to 340 arduino that worked.Than ordered new FTDI arduino.. And it worked again.
Do you have a spare ARDUINO that you can flash with your gateway software??If your gateway is not assigned a /dev/ttyUSBx address It will not work.
-
after you have powered on your raspberry, you log in
then at the command prompt you type:
lsusb
-> provide the output
unplug / plug the usb device
once more in your terminal
lsusb
-> provide outputthe same for dmesg. In a terminal type "dmesg" hit return, and provide the output, both before you unplug a device that is not working, and after you have done it, and it is working.
@tbowmo
now i run this
lsusb-> provide the output
unplug / plug the usb device
once more in your terminal
lsusb
-> provide outputthe same for dmesg. In a terminal type "dmesg" hit return, and provide the output, both before you unplug a device that is not working, and after you have done it, and it is working.
but after unplug power . there is my problem yet
-
@Reza just to be sure: unplug power you mean:
Unplug the power cord from raspberry right?
Not unplug and replug FTDI device?@sincze said:
just to be sure: unplug power you mean:
Unplug the power cord from raspberry right?
Not unplug and replug FTDI device?my serial gateway is always plug and connect. i mean unplug power of raspberry.
Suppose i use solar panel and battery for home and in cloudy day . power's home is off... so raspberry will be turn off...(or other reason for power off...) -
from the initial logs, after powerup, there is no FT232 listed in your lsusb listing, then you unplug and plug it again, and THEN the FT232 is present..
This IS not a bug in mysensors, as it's an HW chip (FT232) that your linux doesn't see before it's unplugged / plugged, it smells of a hardware issue with your nano. Now @sincze mentioned to you that he have had the same issues, and he cured it by exchanging the arduino, maybe it's worth a shot?
@awi also linked to a document, that describes how to make USB devices persistent in the naming (this can happen once in a while, that a USB device enumerates as a different device number.. That is, /dev/ttyUSB1 instead of /dev/ttyUSB0).
@Reza said:
-
from the initial logs, after powerup, there is no FT232 listed in your lsusb listing, then you unplug and plug it again, and THEN the FT232 is present..
This IS not a bug in mysensors, as it's an HW chip (FT232) that your linux doesn't see before it's unplugged / plugged, it smells of a hardware issue with your nano. Now @sincze mentioned to you that he have had the same issues, and he cured it by exchanging the arduino, maybe it's worth a shot?
@awi also linked to a document, that describes how to make USB devices persistent in the naming (this can happen once in a while, that a USB device enumerates as a different device number.. That is, /dev/ttyUSB1 instead of /dev/ttyUSB0).
@Reza said:
-
from the initial logs, after powerup, there is no FT232 listed in your lsusb listing, then you unplug and plug it again, and THEN the FT232 is present..
This IS not a bug in mysensors, as it's an HW chip (FT232) that your linux doesn't see before it's unplugged / plugged, it smells of a hardware issue with your nano. Now @sincze mentioned to you that he have had the same issues, and he cured it by exchanging the arduino, maybe it's worth a shot?
@awi also linked to a document, that describes how to make USB devices persistent in the naming (this can happen once in a while, that a USB device enumerates as a different device number.. That is, /dev/ttyUSB1 instead of /dev/ttyUSB0).
@Reza said:
