Protocol: Wrong checksum

This is intended for WMR100, WMR200, WMRS200 and RMS300 specific topics

Moderator: Mattk

Post Reply
Vetinari
Junior Boarder
Junior Boarder
Posts: 39
Joined: Tue Aug 11, 2009 9:01 am

Protocol: Wrong checksum

Post by Vetinari »

Under the protocols i have at the meteohub-protocol very many wrong checksums? What is it?

logger (21.09.2009 18:56:01): station 0 (WMR-200), wrong checksum (0325 vs computed 02f2) for sensor model d7 in byte sequence: d7 10 37 12 15 09 09 00 bd 00 3e a0 00 00 25 03
logger (21.09.2009 19:19:01): station 0 (WMR-200), wrong checksum (024d vs computed 0405) for sensor model d7 in byte sequence: d7 10 d1 d6 0d 13 13 15 09 09 c4 23 02 34 4d 02
logger (21.09.2009 19:59:40): station 0 (WMR-200), wrong checksum (d7d1 vs computed 0337) for sensor model d7 in byte sequence: d7 10 3a 13 15 09 09 00 f0 00 42 aa 00 00 d1 d7
logger (21.09.2009 20:08:24): station 0 (WMR-200), wrong checksum (0000 vs computed 0222) for sensor model d6 in byte sequence: d6 0d d3 10 08 14 15 09 09 0d 0c 00 00
logger (21.09.2009 21:11:51): station 0 (WMR-200), wrong checksum (0909 vs computed 0305) for sensor model d6 in byte sequence: d6 0d 0b 15 15 d1 d7 10 0b 15 15 09 09
logger (21.09.2009 23:29:31): station 0 (WMR-200), wrong checksum (4200 vs computed 035f) for sensor model d3 in byte sequence: d3 10 1d 17 15 d7 10 1d 17 15 09 09 00 f1 00 42
logger (21.09.2009 23:43:40): station 0 (WMR-200), wrong checksum (10d7 vs computed 01b2) for sensor model d9 in byte sequence: d9 08 00 00 00 d1 d7 10
logger (21.09.2009 23:48:32): station 0 (WMR-200), wrong checksum (3010 vs computed 0609) for sensor model d4 in byte sequence: d4 16 d1 d7 10 30 17 15 09 09 00 f0 00 43 b4 00 00 3c 03 d3 10 30
logger (22.09.2009 00:02:55): station 0 (WMR-200), wrong checksum (10d3 vs computed 02fa) for sensor model d7 in byte sequence: d7 10 02 00 16 09 09 00 f0 00 43 b4 00 02 d3 10

logger (24.09.2009 15:30:57): station 0 (WMR-200), wrong checksum (0109 vs computed 0270) for sensor model d7 in byte sequence: d7 10 1e 0f 18 09 09 00 d3 10 1f 0f 18 09 09 01
Nimbus43
Senior Boarder
Senior Boarder
Posts: 66
Joined: Mon Jan 28, 2008 4:43 pm
Location: 28865 Lilienthal, Germany

Re:Protocol: Wrong checksum

Post by Nimbus43 »

Hello,

The same here, especially after update from ver 4 to ver4a.
As stated already in the NSLU forum part, am unable to stop data logging ...

In addition an error message on the System Information Page: Error file open /home/meteohub/meteohub.conf
Ettershaus
Junior Boarder
Junior Boarder
Posts: 27
Joined: Fri Oct 02, 2009 4:47 pm
Location: Germany
Contact:

Re:Protocol: Wrong checksum

Post by Ettershaus »

Hello, i'll the same Message in the "meteohub.log".
Software-Version: 4.5g

Code: Select all

logger (29.10.2009 18:26:48): station 0 (WMR-200), wrong checksum (0100 vs computed 0000) for sensor model d9  in byte sequence: d6 d1 d3 10 17 12 1d 0a 09 0b 0c 00 00 00 00 20 73 01 d7 10 17 12 1d 0a 09 00 d1 00 34 6e 00 00 b3 02 d2 31 2e 0f 1a 0a 09 00 00 00 00 04 00 38 00 14 16 10 0a 09 0d 0c 00 00 00 00 20 ff f3 03 25 34 01 00 ce 00 32 64 00 00 21 d6 00 39 82 00 00 94 07 d2 31 2f 0f 1a 0a 09 00 00 00 00 04 00 38 00 14 16 10 0a 09 0d 0c 00 00 00 00 20 ff f3 03 25 34 01 00 ce 00 32 64 00 00 21 d6 00 39 82 00 00 95 07 d2 31 30 0f 1a 0a 09 00 00 00 00 04 00 38 00 14 16 10 0a 09 0d 0c 00 00 00 00 20 ff f3 03 25 34 01 d2 31 32 0f 1a 0a 09 00 00 00 00 04 00 38 00 14 16 10 0a 09 0d 0c 00 00 00 00 20 ff f3 03 25 34 01 00 ce 00 32 64 00 00 21 d6 00 39
The Software don't recognize the Rain-Sensor.
Hardware:
WMR200
Alix1.D
Vetinari
Junior Boarder
Junior Boarder
Posts: 39
Joined: Tue Aug 11, 2009 9:01 am

Re:Protocol: Wrong checksum

Post by Vetinari »

The wrong checksum does not harm the logging of the data (for my station).

Boris mentioned some time before that this is not critical.
skyewright
Platinum Boarder
Platinum Boarder
Posts: 873
Joined: Fri Jan 25, 2008 6:27 pm
Location: Isle of Skye, Scotland

Re:Protocol: Wrong checksum

Post by skyewright »

Vetinari wrote:Boris mentioned some time before that this is not critical.
It most likely means that there was a bad packet of data for some reason or other. There are very many reasons why data might occasionally get "damaged" in transit - that's what checksums are there to protect against. :)
Post Reply