Home Automation Domotica Forum Europe, Bwired Forum

Hi,

Just found that my RFXPower counter had a roll-over in July. That means the device starts counting from '0'. This breaks applications that create statistics, charts and use SQL queries to compare this years usage with the previous year.

What is the best procedure?
- Add 16777215 to the calibration value of the RFXPower device as soon as you detect a rollover.
- This should add 16777215 to the value before dividing by 1000 and writing to the DB.
- Update the DB for those records just after the roll-over so the numbers are in sync. (I use an SQL query to update the incorrect values but be careful)

Next:
- With upcoming rollovers, should I change the calibration value to 2x 16777215?

Each time the counter rolls over you have to add the correction value 16777216 to the calibrate value.

I will have a look in the plug-in to update the calibrate value automatically. But there is a risk that the calibration value is added due to wrong data received. I have to minimize this risk so this needs some tests.

Funny... I had the same discusion with Bert yesterday. Mine rolled over in may and now I have incorrect charting readinds. I hope there will be a robust solution for this and let me know if I need to do some testing.

/Rien

I had a rollover; RFXCOM(display_M) counter rollover detected for device ]16 16777216 added to the Calibration value.
Now my water usage looks very funny ... same applies for gas

3.355522E+07l beganegrond meterkast RFXWater \9 Today Water Usage
167774.7m3 beganegrond meterkast RFXGas \4 Today Gas Usage

I guess something is wrong .....

I seem to get false rollover detected messages from time to time. Over the last week for instance, I have had this about 6 times. It will then run for many months without any, and then start again for no apparent reason. I have switched off automatic calibration value adding in the RFXCOM plug-in because it was causing problems with my database every time a false rollover was detected.

This only seems to happen with my RFXPwr device. I have 4 pulse counters in 2 other RFXMeter devices and these have never given a false rollover.

I seem to remember Bert saying that he coded the RFXCOM plug-in it so that it needed to read a new lower value more than once before a rollover was assumed.

Based on my power average usage, I should have a rollover about every 30 months.

Paul..

Database extract at the time of the rollover, something went very wrong ..... spurious counts ??

| 1442765 | 2011-07-31 14:42:34 | ] | ]3 | 37456 | 37455 |
| 1442818 | 2011-07-31 14:53:12 | ] | ]3 | 37457 | 37456 |
| 1442825 | 2011-07-31 14:54:48 | ] | ]3 | 8426048 | 37457 |
| 1442850 | 2011-07-31 15:00:07 | ] | ]3 | 25203264 | 8426048 |
| 1442922 | 2011-07-31 15:16:37 | ] | ]3 | 25203280 | 25203264 |
| 1443023 | 2011-07-31 15:33:38 | ] | ]3 | 33591896 | 25203280 |
| 1443074 | 2011-07-31 15:46:23 | ] | ]3 | 33591903 | 33591896 |
| 1443080 | 2011-07-31 15:47:27 | ] | ]3 | 33591913 | 33591903 |
| 1443086 | 2011-07-31 15:47:59 | ] | ]3 | 33591915 | 33591913 |
| 1443169 | 2011-07-31 16:08:43 | ] | ]3 | 33591920 | 33591915 |
| 1443178 | 2011-07-31 16:10:19 | ] | ]3 | 33591930 | 33591920 |
| 1443197 | 2011-07-31 16:15:06 | ] | ]3 | 33591936 | 33591930 |
| 1443204 | 2011-07-31 16:15:38 | ] | ]3 | 33591941 | 33591936 |
| 1443207 | 2011-07-31 16:16:10 | ] | ]3 | 33591944 | 33591941 |

The version 14.0.0.67 and up of the RFXCOM plug-in have an additional check on RFXMeter packets. It needs to receive 2 identical packets for each counter increment. And it needs 3 rollover detects directly after each other before it adds the calibration value. The risk having unwanted corrections is limited by this but not fully suppressed. It seems that when using two receivers and having an RF noise source that it happens sometimes. On the RFXCOM General configuration page you can deselect "Auto update RFXMeter overrun"
In the RFXCOM User Guide is a description which steps you need to do to correct the counter value and calibration value.

After further investigation it turned out that RFXmeter didn't have a rollover on its internal counters (using rfxreceiver) the values were as expected. I do see that RFXCOM detects noise. I really would like to have a counter which is attached directly to the network don't really trust 432 Mhz ....

Willem4ever wrote:Database extract at the time of the rollover, something went very wrong ..... spurious counts ??
| 1442765 | 2011-07-31 14:42:34 | ] | ]3 | 37456 | 37455 |
| 1442818 | 2011-07-31 14:53:12 | ] | ]3 | 37457 | 37456 |
| 1442825 | 2011-07-31 14:54:48 | ] | ]3 | 8426048 | 37457 |
| 1442850 | 2011-07-31 15:00:07 | ] | ]3 | 25203264 | 8426048 |

I guess something similar like this will happen next year to me when I get a new elek meter. Now I have an old one registering 75 pulses per kw and the new one registers 1000 pulses per kw. That just changes the devider but the new meter starts @ zero whereas the old one now is @ 107000 kw.
I guess I will have to incorporate a ghost counter that refers to my 107000kw while counting from zero but to check if RFX is correct I also need to have the new value that started from zero. Foud for thought when the time comes...
Same goes for the gas meter. Old one has two digits behind the comma and the new smaller one will have three, but also starts @ zero again.

Perhaps adding a negative value for calibration ?

I will probably continue the old value and store the last old elek meter value and subtract that from current data to get the new meter value. Otherwise I would run into negative values. I don't see any other way. Maybe Essent can set the new meter value to my old meter value because it is digital but that cannot be done with the gas meter. I'll figure it out when the time comes..