Build 3191 sync messages

[rons47]

Hi
Installed 3191 yesterday - ran fine until this afternoon. seeing "Start syncronising with console", immediately followed by Stop Syncronising. Seems to be happening every 10 seconds or so, then stops for a while. Startup messages below. Have run with debug and logging - two files attached.
Thanks Ron.

Cumulus MX v.3.19.0 build 3191
Working Dir: C:\CumulusMX\

Cumulus running at: http://localhost:8998/
http://192.168.20.3:8998/

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

Today.ini = data\today.ini
Last update=2022-07-07T17:20:00
Looking for Fine Offset station
Fine Offset station found
Connected to station
7/07/2022 5:29:24 PM
Type Ctrl-C to terminate
Downloading Archive Data

Completed read of history data from the console
Start Synchronising with console
Normal running
Stop Synchronising
Start Synchronising with console
Stop Synchronising
Start Synchronising with console
Stop Synchronising
Start Synchronising with console
Stop Synchronising

[HansR]

This issue might be similar to this one.
You could try the same solution and if it works, wait for the fix to be released.

[rons47]

OK - have turned off synchronisation. See how we go for a while.

[rons47]

Running 30 minutes now. Data logs updating OK every 10 minutes. Weather Underground updating OK. Dashboard etc looks ok. No spurious messages as yet.

[HansR]

So we assume it is solved like th eother issue.
When Mark is back he'll release the fix no doubt.

[rons47]

Build 3194 installed. Synchronisation turned on. Strange messages on console. Please advise.

[mcrossley]

Yes, I have made the sync process a bit more chatty on the console - it's still a work in progress to get the right balance.

What is slightly concerning is that the sync process did not detect any change in your solar data, was the data current on the console at that time?

And another thought comes to mind - there is no point in looking for the solar data changing during local night time! I'll have to think about changing the regular re-sync to run during daylight hours for FO with solar.

EDIT: I see it was way after your local sun set, so actually it's no surprise the solar data wasn't changing!

[rogerthn]

Are those the strange messages?

Code: Select all

2022-07-14 14:51:06.918 Normal running
2022-07-14 23:57:36.204 Connected to station
2022-07-14 23:58:11.262 Connected to station
2022-07-14 23:58:36.199 Connected to station
....

There are also messages like below in then MXdiags-file.

Code: Select all

2022-07-14 23:56:40.471 GetLiveData: Error - Value cannot be null.

and

Code: Select all

2022-07-14 23:57:37.524 GetLiveData: Invalid response

Please let me know if you would like to have the full 21M file!
Maybe zipped

[rons47]

Thanks Mark
I'll upload a logfile after sunrise my time.
What's the message about no station clock change time found?

[mcrossley]

That just means that MX did not detect a change in the logging block used. That is the only reliable way I can see of detecting when the minute rolls over on the console. That will only happen once every archive interval on your console, so unless you use a 1 minute logging interval it is unlikely to be detected.

I have come up with a scheme to "shift" the regular resyncs to within daylight hours of you have a station that measures solar data. Next release.

[mcrossley]

Are those the strange messages?

Code: Select all

2022-07-14 14:51:06.918 Normal running
2022-07-14 23:57:36.204 Connected to station
2022-07-14 23:58:11.262 Connected to station
2022-07-14 23:58:36.199 Connected to station
....

There are also messages like below in then MXdiags-file.

Code: Select all

2022-07-14 23:56:40.471 GetLiveData: Error - Value cannot be null.

and

Code: Select all

2022-07-14 23:57:37.524 GetLiveData: Invalid response

Please let me know if you would like to have the full 21M file!
Maybe zipped

I think those messages are symptomatic of either an unreliable USB connection, or the station returning bad data.

[rogerthn]

I think those messages are symptomatic of either an unreliable USB connection, or the station returning bad data.

Then the questions is, whom is "fiddling" with my WiFi and/or my WS Ecowitt GW1000/GW1003 around midnight
It did start at 2022-07-14 23:56:40, the last message at 02:05:09

[mcrossley]

Sorry, I thought you had a Fine Offset station as that is what this thread is about.

If you want to start a new thread and zip up your file I can take a look. But the answer will be the same I think, either network issues or the station doing "something" or too busy.

[rogerthn]

OK

[rons47]

Mark this all looks good now. Started at 09.15 - through to 17.15 (dusk now).
No messages on the console. Logfile attached.