Page 1 of 1
RFXCom Red led solid lit after reboot Synology, needs unplug
Posted: Wed Mar 26, 2014 7:03 pm
by pwhooftman
Lately, after rebooting my Synology DS412+ the red led on the RFXTRX433 stays lit solid. I have to disconnect & reconnect the RFXCom repeatedly until communication with the RFXCom is restored.
There seems nothing wrong with the RFXCom when connected to a PC & RFXManager. Any clues how to prevent the RFXCom from being hung up after a reboot?
(firmware v 69)
Edit: The Synology log reads:
Code: Select all
Mar 26 11:02:50 Synology hotplugd: hotplugd.c:892 Fail to recognize usb DEVNAME=, DEVPATH=usb3
Mar 26 11:02:50 Synology hotplugd: hotplugd.c:1417 failed to setup usb config, (DEVPATH, DEVICE, ACTION, DEVNAME, INTERFACE)=(usb3, /proc/bus/usb/003/001, add, , )
Mar 26 11:02:50 Synology hotplugd: hotplugd.c:1118 failed get usb status from usb config, DEVICE=/proc/bus/usb/003/001, usbid=1d6b:0002:0000:04:00.0
Re: RFXCom Red led solid lit after reboot Synology, needs unplug
Posted: Wed Mar 26, 2014 10:27 pm
by b_weijenberg
It seems an enter bootloader command string is transmitted by the Synology.
After start up send this string to exit the bootloader: 0x02 0x02 0x00 0x00 0x00 0x03
Re: RFXCom Red led solid lit after reboot Synology, needs unplug
Posted: Thu Mar 27, 2014 10:10 am
by nawikre
Maybe not the place to ask it as it is not related to the problem, but i wil do it anyway. How are you using RFXcom i.c.w Synology and with what software/app?
Re: RFXCom Red led solid lit after reboot Synology, needs unplug
Posted: Fri Mar 28, 2014 10:00 am
by pwhooftman
b_weijenberg wrote:It seems an enter bootloader command string is transmitted by the Synology.
After start up send this string to exit the bootloader: 0x02 0x02 0x00 0x00 0x00 0x03
Thanks.
Alas, none of these commands make the RFXCom strt responding again, the red led stays solid lit.
echo 0x02 0x02 0x00 0x00 0x00 0x03 > /dev/usb/ttyUSB0
echo '0x02 0x02 0x00 0x00 0x00 0x03' > /dev/usb/ttyUSB0
echo "0x02 0x02 0x00 0x00 0x00 0x03" > /dev/usb/ttyUSB0
Re: RFXCom Red led solid lit after reboot Synology, needs unplug
Posted: Fri Mar 28, 2014 10:03 am
by pwhooftman
nawikre wrote:Maybe not the place to ask it as it is not related to the problem, but i wil do it anyway. How are you using RFXcom i.c.w Synology and with what software/app?
I'm using Domoticz (you'll have to compile from sources yourself). Also usbserial.ko and ftdi_serial.ko should be loaded.
Re: RFXCom Red led solid lit after reboot Synology, needs unplug
Posted: Fri Mar 28, 2014 10:22 am
by b_weijenberg
Sorry, the string must be: 0x55 0x55 0x00 0x00 0x00 0x04
Re: RFXCom Red led solid lit after reboot Synology, needs unplug
Posted: Fri Mar 28, 2014 3:49 pm
by pwhooftman
b_weijenberg wrote:Sorry, the string must be: 0x55 0x55 0x00 0x00 0x00 0x04
Too bad, this string doesn't seem to get the RFXCom out of the bootloader.
Its odd, the RFXCom used to start up succesfully in the past after a Synology reboot.
Re: RFXCom Red led solid lit after reboot Synology, needs unplug
Posted: Sun Mar 30, 2014 10:32 pm
by jeroen_
Your kernel/user-space is likely probing/initing the device, which is what is causing this. You should check which modules are attempted to load and if you maybe have a serial console defined in /etc/inittab or /etc/init.d/* (and other locations depending on your distro)
Re: RFXCom Red led solid lit after reboot Synology, needs unplug
Posted: Mon Mar 31, 2014 10:47 am
by pwhooftman
jeroen_ wrote:Your kernel/user-space is likely probing/initing the device, which is what is causing this. You should check which modules are attempted to load and if you maybe have a serial console defined in /etc/inittab or /etc/init.d/* (and other locations depending on your distro)
Hi Jeroen, thanks, yes, that seems to be the case, the log show more references to different USB devices being probed and not recognized properly during boot. Those devices (UPS, DVB-C receiver, DVB-T receiver) don't seem to care though, as they function properly afterwards. I'll examine inittab and init.d tonight (not sure what to look for btw, is there a way to exclude a certain USB device from being probed during boot (is that even the way to solve things)?)