Cumulus Support

You're on Windows. You probably need an ingress firewall rule to allow your console to send to MX.

The setting in the computer have not changed and the console IP is still the same as it was before it all fell apart.
+ firewall rules to me are like brain surgery
CMX runs OK until the second full minute before all stops

davepaterson wrote: ↑Thu 24 Oct 2024 3:19 pm CMX runs OK until the second full minute before all stops

It doesn't run at all with the console. It downloads the historic data from Ecowitt.net when it starts, then waits for your station to send it some more data - none arrives.

Something must have changed. Have you always run MX on port 8999 rather than the default port?

yes 8999 is used because I also run CMX from a GW110 on 8998.
This all started after doing resets on the console. Is it the Console is goosed

Possibly. Why did you reset it?

If it is the console refusing to send to a custom server (I think it unlikely myself), but it is still sending to ecowitt.net, then you could change the station type "Ecowitt.net Cloud", you would only get 1 minute data updates though.

The origin of all probs was I wanted to get the historic back up data on to a SD Card. It went through the actions and showed the progress bar which went the full distance and showed 100% but nothing was on the card, tried other disks - not working. Power off and resets but still not putting anything on the card.
Where do I select change to "Ecowitt.net Cloud"?

Now on Ecowitt cloud but still the same
What I can't understand is (from the Diag file
2024-10-24 17:31:59.900 Wunderground: Rapid fire
2024-10-24 17:32:00.012 Wunderground: Successful upload
All is OK
2024-10-24 17:32:00.397 *** Data input appears to have stopped
No it is NOT

I'd need to see the log file.

That message just means MX is not receiving updated sensor data.

File attached

There are certain rules that the SD card must follow.

The SD card has to be formatted as FAT32 and at a maximum can only be 32GB, did you follow those rules (they are in the manual)?

Looking at the log I do not understand why it creating and supposedly uploading the realtimegauges.txt every 2 seconds, that is a bit weird.

Other than that it is not telling us much. Could you switch debug and data logging on (Program Settings > Logging Options), stop CMX and then start it again and let it run for 10 mins and then send us the log file please.

David Diag file attached As far as the sdcard :from the HP2552 PDF manual :-'memory card is not included. If you want to use one you will need a microSD memory card. There is no required size for this card. A 1GB card will store more than 10 years’ worth of data, so you do not need a very large capacity card. There is also no requirement on the speed class of this card.'
I was using a 64gb. which I am sure I have used before with no probs,
Good luck with the file
Dave

I thought you were changing the station type to Ecowiit.net Cloud?

The log file shows MX is still configured for HTTP Ecowitt

Mark I do not think that the HP2551/2 can do Ecowitt Cloud, mine is set up as a Ecowiit (and clones) and HTTP Custom Sender.

SORRY Mark I did change to cloud but didn't save.
Now done so and all is working again, logfile and realtimegauges updating.
thanks to David , Freddie and MARK, where would be without them.

Dave

Everything working OK :-but a spanner in the works, Just has a big shower of rain and nothing showing on CMX, but shows on the console and WSview ????????