CMX Reading 0°F Minimum

[Cambium]

So CMX is reading 0°F minimum temp with the NOAA Report when I open it in the morning after shutting it down the previous evening.

I attached the Diags, Dayfile, NOAA Report, and Dec21 log.

I used the CreateMissing to fill in everything in the NOAA report so thats why the minimums are filled in before the 18th. But notice December 18th and Dec 20th minimum temps. Those are the day I had shut down CMX the evening before. On the 19th I had kept it open all night.

Is there anything I can do to let CMX read the minimum temp from start up to shut down?

Thank You

[mcrossley]

Can you also zip and attach the backup folder that was created for the start of this run at 07:12?

And the previous runs MXdiag file for 20/12/21.

Thanks.

[mcrossley]

All your "low" values are zero, and all set to the time 07:07 on 20/12/21 which is rather odd. All the "high" values are OK.

[Cambium]

All your "low" values are zero, and all set to the time 07:07 on 20/12/21 which is rather odd. All the "high" values are OK.

Yup, thats when I started running it. 07:07 or 07:08.
I assume the high values are ok because the highs happen in the afternoon.

I'll keep it running all night tonight and it will read a minimum for tomorrow ok.

[Cambium]

Can you also zip and attach the backup folder that was created for the start of this run at 07:12?

And the previous runs MXdiag file for 20/12/21.

Thanks.

Thanks. I attached 2 backup folders. The one at 07:07 and 07:12.
I dont have a MXdiag folder for 20/12/21. See attached of whats in that folder.

[mcrossley]

So you started MX @ 07:07, then stopped it, and started it again @ 07:12 ?

You have found an issue with the log file retention, as CMX is supposed to keep the last 12 in the MXdiags folder. The CreateMissing log files are accidently being included in the file count I'll get that fixed. Meantime please delete those CreateMissing log files.

On the first run @ 07:07, the backup shows that the today.ini file has valid values for all the low values. So the previous run terminated OK, and saved the values as it should.

On start-up CMX reads the highs/lows from today.ini and for the HTTP Ecowitt because it has no historic catch-up the first thing it does is check if the day has changed and the previous day needs closing off and writing to the dayfile. It will do that using the highs/lows it just read from the today.ini file.

When I restored your backup from 07:07 and ran it against an install set to use the HTTP Ecowitt station, it correctly wrote the dayfile entry with all the expected high/low values.

However, I can see that because of the way these HTTP stations work, there is a small window (0.4 seconds on your machine) where if a packet is received from the station it could alter the high/low values before they are written to the dayfile. I have fixed that for the next release. But that would not explain all your low values being set to zero, unless the packet from the station did contain all zero or null values! That would be a bit of a coincidence.

Without a log file with debug logging enabled that includes the incident I'm now struggling to take this much further.

[Cambium]

So you started MX @ 07:07, then stopped it, and started it again @ 07:12 ?

To be honest now I dont remember but I may be thinking it was 2 seperate days. Monday at 07:07 and Tuesday at 07:12. I left it running all night last night so we'll see tomorrow how it shows up. Should be ok. Just to show it only happens with the startup in the mornings.

You have found an issue with the log file retention, as CMX is supposed to keep the last 12 in the MXdiags folder. The CreateMissing log files are accidently being included in the file count I'll get that fixed. Meantime please delete those CreateMissing log files.

Deleted and cool I found something, I feel like I contributed now after all the help the forum has given me.

On the first run @ 07:07, the backup shows that the today.ini file has valid values for all the low values. So the previous run terminated OK, and saved the values as it should.

On start-up CMX reads the highs/lows from today.ini and for the HTTP Ecowitt because it has no historic catch-up the first thing it does is check if the day has changed and the previous day needs closing off and writing to the dayfile. It will do that using the highs/lows it just read from the today.ini file.

When I restored your backup from 07:07 and ran it against an install set to use the HTTP Ecowitt station, it correctly wrote the dayfile entry with all the expected high/low values.

However, I can see that because of the way these HTTP stations work, there is a small window (0.4 seconds on your machine) where if a packet is received from the station it could alter the high/low values before they are written to the dayfile. I have fixed that for the next release.

Good info and thanks!

Without a log file with debug logging enabled that includes the incident I'm now struggling to take this much further.

Ok, lets give it a day or so and I'll have more files to show I guess.

FYI.. Woke up this morning and the 20/12/21 disappeared from the dayfile, 21/12/21 shows 0 for minimum value because I had started it up in the morning yesterday. I added the 20/12/21 from the Dayfile I had attached yesterday here into the dayfile.

Just wanted to mention that to not confuse things if you saw it written somewhere.

I'll post back here tomorrow or Friday

[mcrossley]

FYI.. Woke up this morning and the 20/12/21 disappeared from the dayfile

??? Cumulus never deletes anything from the file (unless you use the dayfile editor and delete a record) it only ever appends.

[Cambium]

Ok, so I left CMX open all night yesterday and last night.. and now its not even reading the day report for 22/12/21. Odd. But I am positive it would be reading the lows, not sure why the entire day isnt showing up now.

It says Im not running the latest version build 3160. Could that be why?

[Cambium]

There it is...... I left Cumulus opened all night again and it read the minimum temp fine. No idea why its missing the 22nd data in the day file though. See attached. Is there anything else I can check, do or send regarding the low temp reading of 0 after shutting down before midnight and the missed day?

Thanks!

[mcrossley]

Regarding the missing entry for the 22. The log file shows that the day rollover processed OK, and the entry was written to the file without any error ? So I have no idea why it is not in the file. No one has ever reported anything like this before.

Code: Select all

2021-12-23 00:00:00.396 Dayfile.txt entry:
2021-12-23 00:00:00.396 22/12/21,23,15,15:52,32.4,19:59,44.1,14:48,1002.0,14:43,1013.3,23:41,0.17,06:31,0.14,36.7,70.2,13,15:54,41,18:42,99,07:42,0.000,0.5,44.1,14:48,36.3,07:42,22.8,23:56,0.09,07:03,25.8,23:56,38.9,07:42,12.6,19:18,322,20.3,0.0,118,14:44,1.0,14:44,39.9,14:43,25.8,23:56,6.7,14:48,99.6
2021-12-23 00:00:00.396 Dayfile.txt opened for writing
2021-12-23 00:00:00.396 Writing entry to dayfile.txt
2021-12-23 00:00:00.396 Dayfile log entry for 22/12/21 written

[HansR]

I would like to remark, that the 22/12 entry is not entered correctly to the dayfile. It is not missing but without a newline it is added to the line of the twenty-first.
And that is why it is not seen in the NOAA report.

The strange thing is the deletion of that line from the dayfile earlier on which has not been followed up.

Cambium reports he has manipulated the dayfile to correct something. I suspect something there has gone wrong (as went wrong before with some manipulations with excel causing quite some confusion).

Maybe I am wrong, but that is how I am looking at this after the previous error reports, mail support and now this thread.

[mcrossley]

I would like to remark, that the 22/12 entry is not entered correctly to the dayfile. It is not missing but without a newline it is added to the line of the twenty-first.
And that is why it is not seen in the NOAA report.

Ah, I hadn't spotted that. Could be indicative of the dayfile being opened and saved in a text editor that is stripping the blank line at the end maybe?

[Cambium]

Thanks guys. I used the CreateMissing to fill it and all was well the next day. I did not have CMX opened all day yesterday so you will see the 26th missing now too. Dont worry about that. The 0°F minimum is the bigger issue and still continues.



Attached are the latest files. (I just opened up CMX right now (06:37)

[flort]

Has anyone noticed that the first entry in the log for the 25th & 26th reads as below which is why it's picking up 0 degree minimums?

25/12/21,07:28,0.0,0,0.0,0,0,0,0.00,0.00,0.0,1.10,0.0,0,0,0.0,0.0,0.0,0,0.000,0.000,0.0,0,0.0,0,0.00,0.00,0.0,0.0
26/12/21,11:27,0.0,0,0.0,0,0,0,0.00,0.00,0.0,1.27,0.0,0,0,0.0,0.0,0.0,0,0.000,0.000,0.0,359,0.0,0,0.00,0.00,0.0,0.0

Regards,
Trevor