Page 1 of 1
RFXTRX - problems with THWR800
Posted: Wed Jun 13, 2012 6:36 am
by SMB_weather
I have a THWR800 being read with RFXCOM RFXTRX. The sensor and its data appear on the sensor page but data is not being saved. Does anyone know how to solve? My hardware is iConnect with meteohub 4.9j.
Re: RFXTRX - problems with THWR800
Posted: Thu Jun 14, 2012 12:53 am
by admin
you need to assign an id for it on "sensors" page.
does "meteohub log" report any errors?
Re: RFXTRX - problems with THWR800
Posted: Sat Jun 16, 2012 3:00 pm
by SMB_weather
Hi Boris,
The sensor has been assigned as follows:
Station 3 (RFXTRX 433MHz): RFXCOM
THWR800 26:1 t3 37sec 20.8°C
The log shows some unknown lacrosse messages, these are not my devices:
logger (16.06.2012 21:38:25): station 3 (RFXTRX 433MHz): unknown lacrosse sensor: 9: 03 04 00 27 aa 00 00 01 ac
logger (16.06.2012 21:40:25): station 3 (RFXTRX 433MHz): unknown lacrosse sensor: 9: 03 04 01 27 aa 00 00 01 ac
logger (16.06.2012 21:42:25): station 3 (RFXTRX 433MHz): unknown lacrosse sensor: 9: 03 04 02 27 aa 00 00 01 ac
logger (16.06.2012 21:44:25): station 3 (RFXTRX 433MHz): unknown lacrosse sensor: 9: 03 04 03 27 aa 00 00 01 ac
logger (16.06.2012 21:45:25): station 3 (RFXTRX 433MHz): unknown lacrosse sensor: 9: 03 04 04 27 aa 00 00 01 ac
logger (16.06.2012 21:46:25): station 3 (RFXTRX 433MHz): unknown lacrosse sensor: 9: 03 04 05 27 aa 00 00 01 ac
logger (16.06.2012 21:47:25): station 3 (RFXTRX 433MHz): unknown lacrosse sensor: 9: 03 04 06 27 aa 00 00 01 ac
logger (16.06.2012 21:48:25): station 3 (RFXTRX 433MHz): unknown lacrosse sensor: 9: 03 04 07 27 aa 00 00 01 ac
logger (16.06.2012 21:49:25): station 3 (RFXTRX 433MHz): unknown lacrosse sensor: 9: 03 04 08 27 aa 00 00 01 ac
There are also the following messages, repeated several times each day:
logger (16.06.2012 21:34:00): no signal from station 3 (RFXTRX 433MHz) for 450 seconds, station to be restarted.
logger (16.06.2012 21:34:00): disconnect station 3 (RFXTRX 433MHz).
logger (16.06.2012 21:34:34): connect station 3 (RFXTRX 433MHz via USB serial).
But no data is saved.
Re: RFXTRX - problems with THWR800
Posted: Sat Jun 16, 2012 7:02 pm
by admin
Could you please open ports 22 and 7777 on your router and forward these to the LAN IP of your Meteohub?
Please send the WAN IP to "info(at)meteohub.de", so that I can check on your rig.
Re: RFXTRX - problems with THWR800
Posted: Mon Aug 06, 2012 12:52 pm
by SMB_weather
Hi Boris,
I have relocated the RFXTRX module and the communications with the THWR800 are now stable. I upgraded Meteohub to 4.9l but the data is still not being saved. Can you help?
Re: RFXTRX - problems with THWR800
Posted: Sun Aug 12, 2012 1:49 am
by admin
did you apply an id at "sensors" page?
Re: RFXTRX - problems with THWR800
Posted: Sun Aug 12, 2012 12:45 pm
by SMB_weather
Hi Boris,
Yes ID assigned as follows:
Station 3 (RFXTRX 433MHz): RFXCOM_RFXTRX
THWR800 109:3 t10 15 sec 21.7°C
But still no data being saved.
Re: RFXTRX - problems with THWR800
Posted: Sun Aug 12, 2012 12:58 pm
by admin
could you please give me acces by browsing to "
http://ip-of-your-meteohub/cgi-bin/help.cgi".
Re: RFXTRX - problems with THWR800
Posted: Mon Aug 13, 2012 6:15 am
by SMB_weather
Hi Boris,
I have opened ports 22 + 7777 and http on another port. I will email you the ip address and port.
Re: RFXTRX - problems with THWR800
Posted: Mon Aug 13, 2012 7:20 pm
by admin
some findings:
1) when you have more than one USB serial device you shouldn't use the enumerated "/dev/ttyUSBx" device names,
as the enumeration of these devices is more or less random on reboot. I changed that to device names which reference
physical ports on your meteohub, like "/dev/ttyMH112".
2) log files indicate with messages like the ones attached, that the storage media is somehoe corrupted.
I did a clean of 201208 raw data by correxponding functions on "inspect data" page. Hopefully,
this will fix it ongoing.
Code: Select all
loggereval (13.08.2012 18:26:49): illegal data record in line 523265 while reading from file /data/weather/201208/raw: 2012080411u724 data22 59700
loggereval (13.08.2012 18:27:15): illegal data record in line 523265 while reading from file /data/weather/201208/raw: 2012080411u724 data22 59700
loggereval (13.08.2012 18:27:26): illegal data record in line 523265 while reading from file /data/weather/201208/raw: 2012080411u724 data22 59700
loggereval (13.08.2012 18:28:14): illegal data record in line 523265 while reading from file /data/weather/201208/raw: 2012080411u724 data22 59700
loggereval (13.08.2012 18:29:11): illegal data record in line 523265 while reading from file /data/weather/201208/raw: 2012080411u724 data22 59700
loggereval (13.08.2012 18:30:17): illegal data record in line 523265 while reading from file /data/weather/201208/raw: 2012080411u724 data22 59700
This error also blocks computation of data, so some values might not appear on graphs etc as expected.
3) Normally Oregon sensors send data packets twice (with a very short delay inbetween), but your THWR800 sensor does not.
I changed evaluation logic to handle this. Is it a "regular" Oregon THWR800 or something just sending similar data?
Please test if the system does now operate as expected. I will make the changes to be part of 4.9m coming soon...
Re: RFXTRX - problems with THWR800
Posted: Tue Aug 14, 2012 1:56 am
by SMB_weather
Hi Boris,
Thank-you for your advice about the physical port names, I will do these names in the future.
I have tested the system this morning and the data is being saved! I will upgrade to meteohub 4.9m tonight and build a new SLC drive.
The THWR800 is "out of the box" from Oregon Scientific but I noticed is is stamped "V3". I googled this morning and found some info at
http://jeelabs.net/projects/11/wiki/Dec ... 2_protocol:
The major differences beween the V2 and V3 protocol are:
•the packet is sent twice
•the preamble is based on long pulses and the start bit is a short bit.
•each bit of data is serialized twice but the second is logically inverted.
So, it sounds like Oregon Scientific V3 may only send data once.
Re: RFXTRX - problems with THWR800
Posted: Tue Aug 14, 2012 8:52 am
by admin
I got information from Bert from RFXCOM, that second packet is generally stripped by TRXRFX.
New version 4.9m should now handle that corectly for all Oregon sensors.