Closed GoogleCodeExporter closed 8 years ago
I am receiving these messages all of the time. Is it hardware related? It happens to all packets received. @mainframe ~ $ /usr/local/bin/python /opt/rfxcmd/rfxcmd.py -d /dev/ttyUSB0 RFXCMD version 0.1j Error: Configuration file not found (config.xml) ------------------------------------------------ Received = 0D 01 00 00 02 53 34 07 8F FF 01 00 00 00 Date/Time = 2012-12-03 15:05:35 Packet Length = 0D Packettype = Interface Message Subtype = Interface response Sequence nbr = 00 Response on cmnd = Get Status, return firmware versions and configuration of the interface. Transceiver type = 433.92MHz (Transceiver) Firmware version = 52 Display undecoded = Off Protocols: Enabled AE (433.92) Enabled Rubicson (433.92) Enabled FineOffset / Viking (433.92) Disabled RFU3 Disabled RFU4 Disabled RFU5 Disabled RFU6 Enabled Mertik (433.92) Enabled AD (433.92) Enabled Hideki/UPM (433.92) Enabled La Crosse (433.92/868.30) Disabled FS20 (868.35) Disabled ProGuard (868.35 FSK) Disabled BlindsT0 (433.92) Enabled BlindsT1 (433.92) Enabled X10 (310/433.92) Enabled ARC (433.92) Enabled AC (433.92) Enabled HomeEasy EU (433.92) Enabled Meiantech (433.92) Enabled Oregon Scientific (433.92) Enabled ATI (433.92) Enabled Visonic (315/868.95) ------------------------------------------------ Received = 04 02 00 00 00 Date/Time = 2012-12-03 15:05:35 Packet Length = 04 Packettype = Receiver/Transmitter Message Subtype = Error, receiver did not lock Seqnbr = 00 Message = ACK, transmit OK ------------------------------------------------ Received = 04 02 00 01 00 Date/Time = 2012-12-03 15:05:35 Packet Length = 04 Packettype = Receiver/Transmitter Message Subtype = Error, receiver did not lock Seqnbr = 01 Message = ACK, transmit OK
Original issue reported on code.google.com by perolavs...@gmail.com on 3 Dec 2012 at 2:07
perolavs...@gmail.com
This is most likely a hardware issue with the RFXtrx433, please contact RFXCOM for support.
Original comment by sebastia...@gmail.com on 6 Dec 2012 at 7:08
sebastia...@gmail.com
Original issue reported on code.google.com by
perolavs...@gmail.com
on 3 Dec 2012 at 2:07