Api max values (changing 5 min db update)

mchd17 · Post by **mchd17** » Sat Feb 09, 2019 2:07 pm

Here is what I have done now

Moved WL passthrough to my Vue console with mb nano. WL passthrough was connected to my Vantage Pro2 console with MB so I was able to record soil station data to WL2.0. I won't be able to view my soil station data on WL2.0 but it'll be a good test to see if the WL passthrough was my issue on MT. So now it looks like this

Davis VP2 console-->MB-->MT
Davis Vue console-->MB nano-->WL passthrough

Curious to see what happens now. Supposed to be windy here this coming Tuesday, so will report back.

mchd17 · Post by **mchd17** » Wed Feb 13, 2019 1:35 am

So sad

MB shows 45 mph at 6:43pm

MT shows 40.9 mph at 6:45pm

Its aggravating showing wrong data. I posted over in MB forums with no responses, and limited responses here.

BTW, I am currently using 10 second update from MB. So I went from 1 min to 10 sec and still same issue. Moved WeatherLInk passthrough to different console with a MB Nano SD, same issue. Removed some weather sites from MB to MB Nano.....same issue. Only thing left to try is moving MT upload to the Vue console with the NanoSD, which then I would lose my soil info on MT. Have to see if I get any response here or MB forums first.

mchd17 · Post by **mchd17** » Wed Feb 13, 2019 2:28 am

Just had higher gust

MB shows 47 mph at 7:51 PM
MT shows 47 mph at 7:55 PM

That's how it should always be.....

mchd17 · Post by **mchd17** » Wed Feb 13, 2019 12:03 pm

I guess next test will be to setup a test MT site, feed that site with the Vue console with MB Nano and see if max G values are off there too.

mchd17 · Post by **mchd17** » Thu Feb 14, 2019 6:41 pm

Lol.....getting things narrowed down now....I think

Vue console->Nano reports follow
Console wind max 33 at 8:23 am
MT test site max G 33.1 mph at 825 am
MBnano shows 33.1 at 823am
WL shows 33 at 825 am

VP2 console->MB TL-MR3020 reports as follows
Console max wind 33 mph at 8:23 am
MT site G max 32 mph at 1235am
(MT shows G at 28 mph at 825 am)
MB shows 33.1 at 823am
PWS weather shows 33.1 at 832 am (10 min updates)
Ambient Weather 33.1 at 825am

It has to be my main MT site or the MB hooked up to my VP2 console. Next step I guess would be Vue Console nano uploads to my main MT site and VP2 console with older MB to my test site and see what happens then. The story continues......

mchd17 · Post by **mchd17** » Fri Feb 15, 2019 1:15 am

That didnt take long

Switched MB's that feed my main site and test site

I am only going by the combinedGraph block at the moment,

Main MT site with Vue-Nano updating................ max G 14.1 mph at 7:05 pm
Test site with VP2 console and other MB............ max G 16.1 mph at 7:05 pm

That's telling me, at this moment, there is nothing wrong with the updates from either MB, theres a problem with the template. I will know more the longer i run with this setup. I need to compare both MT sites to both MB's max data. Tomorrow should show more results. Will post back.

Differences between main MT site and test MT site

main MT site version 17.1
test MT site version 17.0

main MT site has alot installed on it
test MT site plain, just 3 blocks (current conditions, stationData, graphsCombined)

mchd17 · Post by **mchd17** » Fri Feb 15, 2019 2:59 am

Had a high wind gust just now, here's the results

Main MT site updated by Vue Console and Nano.......max G value 33.1 mph at 8:45 pm
Vue console nano shows max wind of 34 mph at 8:43 pm

Test MT site updated by VP2 console and MB TL-MR3020 ....max G value 34 mph at 8:45 pm
VP2 console MB TL-MR3020 shows max wind of 34 mph at 8:43 pm
(remember, this console/MB setup was giving me incorrect data before)

So it doesn't matter which of my Console/MB setups is doing the updates to my main MT site, the data is some how incorrect.

Is the 17.1 api different than the old 17 api?

I guess that's the next question. Should I update my test site to 17.1 and see if that starts to show incorrect data? Starting to run out of ideas and what to do next to get my test site to show incorrect data from either of my Console/MB setups.

Dehatter · Post by **Dehatter** » Wed Feb 20, 2019 1:39 am

I have gone back and checked the past several days, and MT and MB agree on gust (within rounding error). Obviously for me the time is different as MB is on a 10 second timer and MT is on a 5 min timer.

I have some pretty big differences with reg wind, but this is due to MB averaging over 10 secs, and MT averaging over 5 minutes, and that is expected.

I have an Ambient WS-1401-IP station and use the Ambient Observer IP unit that sends updates every 16 secs. The MB reads the OIP directly, so I have no pause as you seem to have.

Tom

mchd17 · Post by **mchd17** » Fri Mar 08, 2019 9:40 pm

Thought I should report back, almost forgot. After trying several different things, all it took was a reboot of the Davis VP2 console. Been running well for a little over a week now.

Dehatter · Post by **Dehatter** » Fri Jun 14, 2019 7:35 pm

I could not find this thread so i started a new one, sorry!!

I too am now having this issue.

I think that MB has changed the format of the data string and max gust is a different string number than it used to be.

I am trying to find out if this is correct. I think the API is using the wrong value.

Tom

Meteotemplate Forum

Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)

Re: Api max values (changing 5 min db update)