Corrupted Template Export File

[slrpwr]

[I am using Meteobridge 5.1 (Feb 9 2021, build 2116), FW 1.3 on an RPi 4]

I have a template I have created to export a Cumulus format file to be used with WXSIM. It occasionally, usually at the top of the hour (hh:00) is corrupted with a rain tag like this:

Code: Select all

12/02/21,09:59,24.1,84,19.9,4.8,8.9,341,0.0,0.0,30.373,0.0,60.6,40,8.9,18.3,24.1,0.0,40,,,,,,
12/02/21,10:00,0,0,00,5.5,11.0,328,0,0,30.375,[rain0total-daysum=in.1],60.6,40,11.0,17.7,0,0,40,,,,,,
12/02/21,10:01,24.2,84,20.0,4.1,10.1,34,0.0,0.0,30.375,0.0,60.6,40,10.1,19.6,24.2,0.0,40,,,,,,

The template I wrote looks like this:

Code: Select all

# MeteoBridge: Cumulus-style export to feed WXSIM
#
# See: https://cumuluswiki.org/a/Standard_log_files
#pragma exportfile=[MMM][YY]log.txt
#pragma crlf=y
#pragma append=y
#pragma emptylines=n
[DD]/[MM]/[YY],[hh]:[mm],[th0temp-avg=F.1:0],[th0hum-avg.0:0],[th0dew-avg=F.1:00],[wind0wind-avg=mph.1:0],[wind0wind-max=mph.1:0],[wind0dir-avg.0:0],[rain0rate-avg=in.1:0],[rain0total-daysum=in.1:0],[thb0seapress-avg=inHg.3:0],[rain0total-daysum=in.1],[thb0temp-avg=F.1:0],[thb0hum-avg.0:0],[wind0wind-max=mph.1:0],[wind0chill-avg=F.1:0],[th0heatindex-avg=F.1:0],[uv0index-avg.1:0],[sol0rad-avg.0:0],,,,,,

I call the template with a Services: Events: Data Export / after every full hour: Time Frame / Previous Hour: Resolution / Minutes

Am I doing something wrong? Thanks!

[Mattk]

Not sure if corrupted would be the right word but obviously something in the background is occurring exactly on top of the hour being basically a zero time period between the end of the last hour and the beginning of the next hour. Does this occur on the hour when there has been rain to total? This type of issue is more common at exactly midnight depending on the syntax pointing to Yesterday or Today as there is a period when it's not either.

If you included a Replacement parameter like :--- this would maybe stop the sensor text from showing

[slrpwr]

Thanks for the reply.

No, it doesn't appear to be related to precipitation and on days that it does appear, it appears for several hours, but not all hours. it's almost like something else is happening?

In any event, I can try the replacement parameter suggestion and see what happens.

[weatherist34]

[I am using Meteobridge 5.1 (Feb 9 2021, build 2116), FW 1.3 on an RPi 4]

I have a template I have created to export a Cumulus format file to be used with WXSIM. It occasionally, usually at the top of the hour (hh:00) is corrupted with a rain tag like this:

Code: Select all

12/02/21,09:59,24.1,84,19.9,4.8,8.9,341,0.0,0.0,30.373,0.0,60.6,40,8.9,18.3,24.1,0.0,40,,,,,,
12/02/21,10:00,0,0,00,5.5,11.0,328,0,0,30.375,[rain0total-daysum=in.1],60.6,40,11.0,17.7,0,0,40,,,,,,
12/02/21,10:01,24.2,84,20.0,4.1,10.1,34,0.0,0.0,30.375,0.0,60.6,40,10.1,19.6,24.2,0.0,40,,,,,,

The template I wrote looks like this:

Code: Select all

# MeteoBridge: Cumulus-style export to feed WXSIM
#
# See: https://cumuluswiki.org/a/Standard_log_files
#pragma exportfile=[MMM][YY]log.txt
#pragma crlf=y
#pragma append=y
#pragma emptylines=n
[DD]/[MM]/[YY],[hh]:[mm],[th0temp-avg=F.1:0],[th0hum-avg.0:0],[th0dew-avg=F.1:00],[wind0wind-avg=mph.1:0],[wind0wind-max=mph.1:0],[wind0dir-avg.0:0],[rain0rate-avg=in.1:0],[rain0total-daysum=in.1:0],[thb0seapress-avg=inHg.3:0],[rain0total-daysum=in.1],[thb0temp-avg=F.1:0],[thb0hum-avg.0:0],[wind0wind-max=mph.1:0],[wind0chill-avg=F.1:0],[th0heatindex-avg=F.1:0],[uv0index-avg.1:0],[sol0rad-avg.0:0],,,,,,

I call the template with a Services: Events: Data Export / after every full hour: Time Frame / Previous Hour: Resolution / Minutes

Am I doing something wrong? Thanks!

in your code you are calling
,[rain0total-daysum twice in a different ending format

[rain0total-daysum=in.1:0],[thb0seapress-avg=inHg.3:0],[rain0total-daysum=in.1],

is that for a purpose ?
or maybe causing a delay due to limitations of resources at the hourly point . in recent months since introduction of multiple mapping of sensors I have seen similar outputs particularly on the hour . whilst meteobridge is rich in capabilities I do think at times if many multiple services, networks are running at the hourly mark there is a lot to compute in some very small timeframes especially if you are writing to a file outside your network i.e website or network not on same as meteobridge.