Custom Logs in CMX 4 no longer working properly as before

[LSchenk]

Hello,

I used CMX V3.23.1 to generate indivualized CustomLogs to have my station data in a readable CSV format with ";" spacers. This worked proper.

Now, in CMX 4, the generation of CustumLogs has to run with a comma as separator between the tags. (Build 4043)
This means that CSV usage doesn't work furthermore in the german an widespread european locales, because separator "," and decimal sign "," are identical.

This might be a consequence of using .NET 8 as running platform. Are there suggestions to work on this topic?

For now, I switched back to V3.23.1 and all is fine.

Best Regards

[mcrossley]

No, as stated in the Important Additional Information, all CSV data files now use the same format of comma separator and dot decimal - and that includes custom log files.

I have added a section to the Important Additional Information to highlight that you need to make changes to the custom log files.

[Tigro11]

hi guys, migrating from version 3 to version 4 I noticed that the log files transformed all the separators of ; in ,. Where do I have to edit to get the separator back; ?

Thank you

[freddie]

Where do I have to edit to get the separator back;?

This can't be done. See viewtopic.php?t=22051

[Tigro11]

ok back to the old version.

thanks for the reply

[HansR]

ok back to the old version.

thanks for the reply

Strange, why would you do that? You are missing out on progress and stability!
CMX itself can handle the new separators.

I don't know your situation but it can't be that difficult, many went before you.

[Tigro11]

I have a program that loads every day and processes these files: nov24log.txt now I think it has changed its name with the new version but it's not a problem, the problem remains of the field separator which must be; and not,

[HansR]

I have a program that loads every day and processes these files: nov24log.txt now I think it has changed its name with the new version but it's not a problem, the problem remains of the field separator which must be; and not,

Well you could pre-process the file before feeding to that external program. That would give you the possibilities to progress into v4 and maintain your old system. And then think about how to continue. CMX v4 is really better and more stable and better in general. Unless you do not need progress of course. Up to you.

[Tigro11]

I wouldn't know how to reprocess the file, the problem of ; I think other friends have the same problem, I was hoping for a change in version 4 to make it compatible with old programs to process data.
We hope perhaps later on to be able to change the separator independently.

[broadstairs]

If we knew the program you use we might be able to help with a way to resolve this issue, can you not contact the original author?

Stuart

[Tigro11]

the program I use to create the graphs is graph weather, it processes the monthly file that is created every day, which then sends it in xml format which is processed in php by my site to create the graphs that I attach.
It would be great if cumulus mx created the xml files directly but for now I don't think it's available.

[freddie]

MX probably could create the XML file with webtags. Could you upload a sample file?

[broadstairs]

I assume that this GraphWeather is the one at https://graphweather.protosigma.com and so have you asked on the forum whether they can support this new version of CumulusMX, looks to me that it would be in their interest to do this.

Stuart

[Tigro11]

MX probably could create the XML file with webtags. Could you upload a sample file?

the file 2024.xml represents the year: 2024:11.xml represents the month 2024_11_19.xml represents the day

[HansR]

MX probably could create the XML file with webtags. Could you upload a sample file?

the file 2024.xml represents the year: 2024:11.xml represents the month 2024_11_19.xml represents the day

That is clear, thanks.

Unless I miss something I don't think CMX can create these files out of the box.
You can create these, but you would require some spec and some programming.

I think Stuarts suggestion is the best. That might make it also easily available to others (if wanted).
It is a Canadian/French tool though, I did not see any English on their site or did I miss something?