After "crash" I cannot use export templates

[Bagtjesen]

Hi,

My MB is protected by backup power (hours) and surgeprotector. And we had no electric problems last night.

While making export templates for two purposes, and they worked, I did get som errors that MB Pro+ had lost its settings for my Davis VP2+.
I reentered correct info, and then it needed to reboot. Another error from some setting lost, which was reentered, and a new reboot.

Not much was working...

By mishap I got the version 5.5 after these reboots.

I got the suggestion to roll back to version 5.4 and did so and got back my settings backup. Much better...

I can see that data is coming in because it updates MeteoTemplate, and can Generate Chart with Type "allinone-iso" which is correct.

So, MB gets data and sends it away correctly.

However, none of the standard export templates work any longer, nor my new made one from yesterday.

I have tested a lot of things:
Transmitter #1 : Integrated Sensor Suite (ISS) with 0.2mm
With and without any mapping
With and without any calibration

A simple export template as:

Code: Select all

$date,time
[YYYY]-[MM]-[DD],[hh]:[mm]

will work, but any sensors will not produce data, as in:

Code: Select all

$date,time,outdoortemp
[YYYY]-[MM]-[DD],[hh]:[mm],[th0temp-avg.1:]

will only produce lines like:
date time outdoortemperature

Code: Select all

2022-10-24,00:00,
2022-10-24,00:01,

What might have gone wrong? "[th0temp-avg.1:]" is used in many places in the export templates that which were there with the installation?

Regards,

Bagtjesen

[Gyvate]

my standard-iso.exp template looks like this:

#---start template---------
# Standard CSV template with data in metric units
#
$# date, time, temperature[C], humidity[%], dew point[C], sealevel pressure[hPa], avg wind speed[m/s], gust speed[m/s], winddir, rainfall[mm]
[YYYY]-[MM]-[DD],[hh]:[mm],[th0temp-avg.1:],[th0hum-avg.0:],[th0dew-avg.1:],[thb0seapress-avg.1:],[wind0avgwind-avg.1:],[wind0wind-max.1:],[wind0dir-avg.0:],[rain0total-sum.1:]
#---end template----------

looks like a "#" is missing behind your "$" sign compared to mine ....
give it a try ...

[Bagtjesen]

Thanks Gyvate,

I tested your suggestion with my file and it didn't make a difference. I also tested the contens of your file and it worked. I will have to use the binary file viewer to find the explanation!

Late here so I'll check things out tomorry morning. Short walk with my dog and down into the "flea bag". Exhausted by all problems today.

Again thanks!

Bagtjesen

[Gyvate]

if you want to use a copy of "my" standard templates, see attached zip file.

[Bagtjesen]

Thanks Gyvate,

I have had a look at your files, they are exactly the same I had backuped to my NAS.

The only difference I see, using Binary Viewer is that the originals seems to have only 0A line endings but some of mine and your std export contained line endings 0D0A. I also had some thought about whether the last line would have to end without any form om new line characters.

I kept my MB Pro+ without power the whole night until an hour ago, I and I set it to "forced check on reboot".

I read up on the System, Administration part of https://www.meteobridge.com/wiki/index.php/System, and "maybe" the statement there: " you can define a boot delay in order to make Meteobridge wait before starting operation". What I saw when the problems started with the 3-4 messages of lost settings after update to 5.5, could have come from too many rather frequent reboots.

Any way, I have now set it to 2 minutes delay. Since it is now supposed to only work, and work, and work... no more need to fiddeling about in it, other than doing exports and sending to other places like WU, WOW and others. All such things has been done through WD, which I will now only keep reading direct from the console, and being a backup. Redundance ...