logger (06.06.2009 13:08:07): station 0 (WMR-200), wrong checksum (0809 vs computed 0227) for sensor model d3 in byte sequence: d3 10 0d 0d 06 06 09 0c d3 10 0d 0d 06 06 09 08
logger (06.06.2009 13:14:25): station 0 (WMR-200), wrong checksum (060d vs computed 0222) for sensor model d4 in byte sequence: d4 16 13 0d 06 06 09 00 00 00 00 00 00 00 00 00 0c d3 10 14 0d 06
logger (06.06.2009 13:33:05): station 0 (WMR-200), wrong checksum (d32f vs computed 012f) for sensor model d5 in byte sequence: d5 0a 26 0d 06 06 09 08 2f d3
logger (06.06.2009 13:36:47): station 0 (WMR-200), wrong checksum (d720 vs computed 0220) for sensor model d7 in byte sequence: d7 10 2a 0d 06 06 09 42 48 01 0c 00 00 56 20 d7
logger (06.06.2009 13:51:38): station 0 (WMR-200), wrong checksum (0906 vs computed 0288) for sensor model d3 in byte sequence: d3 10 39 0d 06 06 09 08 0c d4 16 39 0d 06 06 09
logger (06.06.2009 13:55:08): station 0 (WMR-200), wrong checksum (001e vs computed 0364) for sensor model d4 in byte sequence: d4 16 00 0e 06 06 09 00 00 d7 10 00 0e 06 06 09 40 f4 00 19 1e 00
logger (06.06.2009 14:01:00): station 0 (WMR-200), wrong checksum (2209 vs computed 01e6) for sensor model d5 in byte sequence: d5 0a d7 10 06 0e 06 06 09 22
logger (06.06.2009 14:06:13): station 0 (WMR-200), wrong checksum (060e vs computed 025e) for sensor model d6 in byte sequence: d6 0d 0b 0e 06 06 09 5f d3 10 0b 0e 06
logger (06.06.2009 14:10:48): station 0 (WMR-200), wrong checksum (d719 vs computed 0119) for sensor model d5 in byte sequence: d5 0a 10 0e 06 06 09 07 19 d7
logger (06.06.2009 14:17:08): station 0 (WMR-200), wrong checksum (0028 vs computed 0355) for sensor model d4 in byte sequence: d4 16 16 0e 06 06 09 00 00 d7 10 16 0e 06 06 09 00 f8 00 1a 28 00
logger (06.06.2009 14:29:31): station 0 (WMR-200), wrong checksum (014c vs computed 0292) for sensor model d7 in byte sequence: d7 10 22 0e 06 06 d7 10 23 0e 06 06 09 42 4c 01
logger (06.06.2009 14:30:49): station 0 (WMR-200), wrong checksum (02c9 vs computed 0481) for sensor model d7 in byte sequence: d7 10 d1 d6 0d 24 0e 06 06 09 5f 13 fa 33 c9 02
Data from Meteohub log...what does it mean?
Moderator: Mattk
-
- Junior Boarder
- Posts: 38
- Joined: Thu Mar 26, 2009 5:02 am
-
- Platinum Boarder
- Posts: 873
- Joined: Fri Jan 25, 2008 6:27 pm
- Location: Isle of Skye, Scotland
Re:Data from Meteohub log...what does it mean?
Wrong checksum essentially means that Meteohub received a packet of data from the station (WMR0200 in this case), but when Meteohub performed an integrity check on the data (comparing the last couple of bytes against the result of a special calculation performed on the other bytes) it was found to be faulty.FishAlaska wrote:station 0 (WMR-200), wrong checksum (0809 vs computed 0227)
The checksum failures shown in the sample seem to be intermittent (but quite frequent), and seem to affect a range of different sensors. There are many possible causes, but the first I'd check out would be somthing affecting the signal as it passed through the USB cable, e.g. see if using a different USB cable, or altering the route of the cable between the console and the Meteohub, helped.