fit-PC Slim and Wrong Checksum

[Edzo1]

Greetings,

I'm a MeteoHub Rookie still figuring things out and loving it! I'm running:
OS WMR-200A
MeteoHub Version 4.2rc4
fit-PC Slim using recommended Transcend TS4GIFD25
Running WLAN
All sensors (7) checking in with good signals

My Q is regarding the MeteoHub Log. It shows constant wrong checksum. I'm not technical enough to understand all the log files but that sounds like a problem. Could someone please advise? Thanks.

logger (22.03.2009 00:00:39): station 0 (WMR-200), wrong checksum (0009 vs computed 0000) for sensor model d5 in byte sequence: d7 10 00 00 16 03 09 00 d5 00 21 32 00 d7 10 00
logger (22.03.2009 00:06:17): station 0 (WMR-200), wrong checksum (0909 vs computed 02da) for sensor model d7 in byte sequence: d7 10 05 00 d7 10 05 00 d3 10 06 00 16 03 09 09
logger (22.03.2009 00:06:17): station 0 (WMR-200), wrong checksum (00e0 vs computed 021d) for sensor model d7 in byte sequence: d7 10 05 00 d3 10 06 00 16 03 09 09 0c 11 e0 00
logger (22.03.2009 00:07:23): station 0 (WMR-200), wrong checksum (d600 vs computed 021f) for sensor model d7 in byte sequence: d7 10 06 00 16 03 09 d7 10 07 00 16 03 09 00 d6
logger (22.03.2009 00:09:53): station 0 (WMR-200), wrong checksum (0903 vs computed 022a) for sensor model d3 in byte sequence: d3 10 09 00 16 03 09 0a 0c d7 10 09 00 16 03 09
logger (22.03.2009 00:10:23): station 0 (WMR-200), wrong checksum (d500 vs computed 0225) for sensor model d7 in byte sequence: d7 10 09 00 16 03 09 d7 10 0a 00 16 03 09 00 d5
logger (22.03.2009 00:10:53): station 0 (WMR-200), wrong checksum (0316 vs computed 0222) for sensor model d3 in byte sequence: d3 10 0a 00 16 03 09 09 0c 0d d7 10 0a 00 16 03
logger (22.03.2009 00:14:03): station 0 (WMR-200), wrong checksum (2600 vs computed 03ca) for sensor model d7 in byte sequence: d7 10 0d 00 fc d7 10 0d 00 16 03 09 03 c1 00 26

[admin]

please update to a recent version (4.2c for example). Please post again, when problem not being solved by this.