LAN RFXCom not initialized properly?

[Headworx]

Hi,

I am trying to get sensor data from LAN RFXCom receiver. I have two sensors (one Oregon and one RFX), but none shows in the MeteoPlug (I use Sheeva Version 4.5).

When I log directly to the RFXCom via port 10001 using the RFreceiver application, I keep getting
[38C8184338C81843 WEIGHT1[1] BWR101,BWR102 ERROR: weight value is not a decimal value. bits=56 ]

until I hit "32-bit mode" that results in:
[Init cmd to receiver => F029]
[29 ACK ]

and then the sensor data starts flowing as below:

[38C81843 RFXsensor[14536]T RFXSensor addr:38C8 ID:14536 Temp:24,25ºC | 75,65ºF ]
[38C81843 RFXsensor[14536]T RFXSensor addr:38C8 ID:14536 Temp:24,25ºC | 75,65ºF ]
[00F01483 RFXsensor[240]T RFXSensor addr:00F0 ID:240 Temp:20,5ºC | 68,9ºF ]
[00F01483 RFXsensor[240]T RFXSensor addr:00F0 ID:240 Temp:20,5ºC | 68,9ºF ]
[00F01483 RFXsensor[240]T RFXSensor addr:00F0 ID:240 Temp:20,5ºC | 68,9ºF ]

Then when I try to connect to the RFXCom with MeteoPlug, I get no data...

The meteohub log is not helpful here:
logger (17.09.2009 22:19:21): data logger started.
logger (17.09.2009 22:19:21): connect station 0 (Vantage via TCP/IP).
logger (17.09.2009 22:19:21): connect station 1 (System Data via Plug-in).
logger (17.09.2009 22:19:21): connect station 2 (RFXCOM via TCP/IP).
logger (17.09.2009 22:19:21): station 0 (Vantage), syncing.
logger (17.09.2009 22:19:35): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (17.09.2009 22:19:35): station 0 (Vantage), transmitter 1 active as station type (#0) "ISS".
logger (17.09.2009 22:19:35): station 0 (Vantage), ready logging data.

My guess is the MeteoPlug does not initialize the RFXCom properly... something like
[Init cmd to receiver => F029]
[29 ACK ]
may be missing...

Any ideas how to make it work?

Cheers,
Headworx

[HeinrichH]

As far as I know Meteohub and RFXcom support only the RFXmeter (Powermeter) and the Oregon sensors showed in the Meteohub manual, see downloads

I don't know which Oregon sensor you are using, do you see the sensor when using the RFreceiver program? I don't see the OS sensor in your question

[Headworx]

While this is true (per Appendix G)... I do not se the reason why it would be so... RFXCom readings are identical in format for both Oregon and native RFX sensors....

And in my setup one of the sensors is the Oregon-THN132N... And MH still does not see it...

Cheers,
Headworx

[HeinrichH]

The log of your RF receiver program shows two RFXsensor's with two different addresses

[38C81843 RFXsensor[14536]T RFXSensor addr:38C8 ID:14536 Temp:24,25ºC | 75,65ºF ]
[00F01483 RFXsensor[240]T RFXSensor addr:00F0 ID:240 Temp:20,5ºC | 68,9ºF ]

Is one of them the OS sensor?

If the receiver see those sensors as RFXsensor's, those are not supported by Meteohub so you don't see any sensor data in Meteohub.
I suggest to send a mail to RFXcom (support(at)rfxcom.com) how to use the OS sensor

[Headworx]

Yes, this one:

[38C81843 RFXsensor[14536]T RFXSensor addr:38C8 ID:14536 Temp:24,25ºC | 75,65ºF ]

is the OS THN132N sensor

What is the reason the RFX sensors are not supported? Will they be supported in future?

I will ask rfxcom support in the meantime...

Cheers,
Headworx

[HeinrichH]

The reason the RFXsensors are not supported? I don't know, maybe in the future or put it in the wishlist, only Boris can give you a answer on this question

[admin]

You are the first one with RFX sensors. They are not supported by Meteohub so far, but I think this can be easily added. Can you please give me access on your Meteohub on ports 22 and 7777. Please mail WAN IP to info(at)meteohub.de.

[Headworx]

Hi I have just forwarded the IP to you via email.

The reason I opted for RFX sensor is it provides an interface to 1-wire bus, thus additional sensors can be supported this way...

And to be honest I was not aware the RFXReceiver distinguishes between various types of sensors - I thought it just reports ID ad actual values.

Hope you will be able to support them without too much extra effort... A friend of mine who has not yet purchased MeteoHub license is running identical system, so this may be an additional potential incentive :)

Cheers,
Headworx

[Headworx]

And I have just got a message from RFXCom support saying "You have to use Variable Length mode. In that mode they will be reported as Oregon sensors". I've had some problems yesterday with RFX receiver in variable length mode... Nothing was reported until I switched to 32-bit mode... But may try again tonight...

[HeinrichH]

I'm using 16 Oregon sensors and they are reported fine with the RFX receiver program.
Settings: Variable length mode, enable all RF, decode and time stamp selected.

Regards, Henk

[admin]

Meteohub does not set RFXCOM to "variable length" & "receive all" mode when using a TCPIP connection. I just fixed that and now your Meteohub takes up data.

I just see one Oregon sensor there. Should there be more? Do you have native RFXsensors for temperature?

Changes will go into the next update.

[Headworx]

Wow that is fantastic....:)

There is one Oregon sensor and one native RFX reporting to the RFXCom LAN receiver.

I have just switched the RFXCom receiver to their naitve application and it goes like this:

44EA4C10BC0022A00313 TEMP2[48129] THN132N,THWR288,AW131 CH 1 addr:BC temp:22°C | 71,6°F bits=68
2000F0122B RFXsensor[240]T RFXSensor addr:00F0 ID:240 Temp:18,125ºC | 64,625ºF bits=32

The first one is OS, the second is native RFX.

In MH I have this now: error connect socket 127.0.0.1:5555 :Connection refused Warning: Data logging has been halted.

Cheers,
Headworx

[HeinrichH]

Don't forget to disconnect the receiver from the RFX program before connecting to Meteohub...

[Headworx]

I did... But Boris is probably still at it... I'll wait till the morning...

Still only the OS sensor is showing... The RFX one is not being reported...

[admin]

RFXsensor is not reported in received low level data so far. Is it still frequently sending?