Cumulus Support

freddie wrote: ↑Fri 19 Aug 2022 7:45 am

stefanbagnato wrote: ↑Fri 19 Aug 2022 1:53 amBTW, I am curious as to your 2s realtime? Why did you go with 2s? I went with 15s since that's the update time of the VP2 wind data. I assume you have something that updates more frequently?

The VP2 sensors actually send updates every 2.5 seconds. That's why I use 2s realtime interval. See https://www.davisinstruments.com/pages/ ... e-interval

You are right! Man, I am not on my smarts game haha, between this and the 'monthly' table comment yesterday. And I should know this as I've had a Davis station (several) since I was a teen. Sighhhhhhh

Well, I like you're thinking. Mark may need to chime in on this as well, but thoughts on switching from 15 to 2? Besides of course the increase in logs and i/o between CXM and MySQL, any potential compatibility issues with the switch (not like it's changing from F to C or inHg to mb, etc)? I've had it set to 15s since inception.

stefanbagnato wrote: ↑Fri 19 Aug 2022 12:39 pmWell, I like you're thinking. Mark may need to chime in on this as well, but thoughts on switching from 15 to 2? Besides of course the increase in logs and i/o between CXM and MySQL, any potential compatibility issues with the switch (not like it's changing from F to C or inHg to mb, etc)? I've had it set to 15s since inception.

Give it a try for a couple of days and see how it goes. It's not affecting any permanent records as it is just realtime data. MX does its own thing internally with realtime data - this setting is purely about how often "exports" of realtime data are made by MX, regardless of whether it is to file (realtime.txt, for example) or to a DB.