Packet CRC invalid

[dennis48755]

Hello,

I'm a new CumulusMX user.

The installation and starting CumulusMX went well.

Cumulus MX v.4.4.0 build 4083
Working Dir: C:\Programs\CumulusMX\

Cumulus running at: http://localhost:8998/
http://192.168.92.7:8998/
http://172.17.208.1:8998/

Open the admin interface by entering one of the above URLs into a web browser.

Opening station type 1 - Davis Vantage Pro2
Last update: 2025-03-09T15:40:00
Connected to station
Opening Ecowitt extra sensors
3/9/2025 3:49:01 PM
Type Ctrl-C to terminate

Downloading Archive Data
- No Archive data available
Downloading Archive Data
- No Archive data available
Connecting real time FTP
Normal running

And browsing around the different menus such as the Dashboard and Charts, etc my data and CumulusMX in general look like they are working.

However, the following errors are continuously logged with both CumulusMXDist4070 and CumulusMXDist4083 ...

2025-03-09 16:18:57 - LOOP: 18 - Packet CRC invalid
2025-03-09 16:18:57 - LOOP: 18 - Expected data not received, expected 99 bytes, got 90
2025-03-09 16:18:17 - LOOP: 24 - Packet CRC invalid
2025-03-09 16:18:17 - LOOP: 24 - Expected data not received, expected 99 bytes, got 91
2025-03-09 16:17:25 - LOOP: 49 - Packet CRC invalid
2025-03-09 16:17:25 - LOOP: 49 - Expected data not received, expected 99 bytes, got 93

At first I thought the errors may be due to the Davis IP Logger attached to my Davis Envoy, so I swapped it with an USB (serial) logger, the errors continued.

Note: The IP Logger is NOT connected/uploading to WeatherLink cloud.

Then I thought it may be caused from CumulusMX running on a PC that also has Davis WeatherLink 6.0.5 running. So I moved the CumulusMX folder to a different PC. The errors continue to be logged.

Attached are a couple samples of the MXdiags logs.

Help would be appreciated
Thanks
Dennis

[water01]

There is a new release (4084) that fixes problems with the Logger.

[dennis48755]

Thanks David and the CumulusMX Team,

I installed 4084, but unfortunately the errors continue.

2025-03-09 18:34:21 - LOOP: 23 - Packet CRC invalid
2025-03-09 18:34:21 - LOOP: 23 - Expected data not received, expected 99 bytes, got 68

Dennis

[PaulMy]

Hi,

Attached are a couple samples of the MXdiags logs.

The log file is not very long and no errors reported. However it is quite a short time. It may be more informative if Debug and Data logging were enabled and then check the logging file.

Some other observations:

Code: Select all

2025-03-09 15:48:50.963  ========================== Cumulus MX starting ==========================
2025-03-09 15:48:50.963 Command line: C:\Programs\CumulusMX\CumulusMX.dll 
2025-03-09 15:48:50.964 Cumulus MX v.4.4.0 build 4083

Your install is in the C:\Program\ folder and it is recommended that it be installed directly in C :\

At first I thought the errors may be due to the Davis IP Logger attached to my Davis Envoy, so I swapped it with an USB (serial) logger, the errors continued.

Then I thought it may be caused from CumulusMX running on a PC that also has Davis WeatherLink 6.0.5 running. So I moved the CumulusMX folder to a different PC. The errors continue to be logged.

Either IP or serial logger should work fine, but can run only one program from the same console/logger at the same time. As you say it seems to be running, then that is likely not an issue.

Enjoy,
Paul

[dennis48755]

Paul...

Your install is in the C:\Program\ folder and it is recommended that it be installed directly in C :\

Yes, C:\ is just a recommendation.
My use of C:\Programs should not be an issue. It's not within the Windows Program Files hierarchy.

but can run only one program from the same console/logger at the same time

I am well aware of this, I have multiple loggers for use individually with my software. And on the current computer CumulusMX (b4084) is the only weather-related software running with only one logger.

The Packet CRC invalid errors are continuing.

Attached is a resent log.

Dennis

[mcrossley]

It looks like most of the data is coming through OK, less than 1% error rate for the loop data I would say.

If nothing else is "talking" to the station, then I'd be looking at possible interference?
But you say it is happening on both TCP and USB loggers.

Is the network connection via a USB adapter? - I'm thinking USB going into sleep mode.

[dennis48755]

Thanks Mark,

No, the network connection is an 1G Intel NIC on an Asus motherboard.

Not knowing if a "Loop" was used for communicating with Ecowiit GW3000, I removed HTTP Ecowitt form the Extra sensos dialog and that had no effect.

FYI, the logger is attached to an Envoy (not 8x).

Dennis

[mcrossley]

I've run out of ideas for now - I cannot reproduce this on my old VP2 with a serial logger (and USB-Serial adapter).

[dennis48755]

Mark,

Thanks so much for posting back, that's very appreciated.

I think I'm making some progress. I've gone from many, many "Packet CRC Invalid" errors to a few "Expected data not received, expected 99 bytes, got 0"

I haven't come back here to post yet because I'm still working on it, and frankly the more I do the more confused I get.

Are the Loop entries in the logs for example "SendLoopCommand: Starting - LOOP 50" the communications for just the network? Or are communications with the station also do by Loop Commands?

Besides the Davis VP2 as my primary station, I have the Ecowitt GW3000 configured as an Extra Sensor - Use a second station for extra sensors via HTTP Ecowitt, for my LDS01. Would Loop Commands be involved with communicating with them?

I followed the on-screen information for setting up the GW3000 and allowed for port traffic on port 8998 but I don't know how to tell if the GW3000 is getting to CumulusMX or the cause of any of the Loop errors.

Thanks Again,
Dennis

[dennis48755]

A while after writing my previous post, thinking about what troubleshooting steps to do next, I noticed build 4085 became available.

It is now over three hours since I installed build 4085 and NO ERRORS, YAY.

Previously CumulusMX would not run for longer than 5-10 minutes without errors appearing.

Dennis