Cumulus MX gathering data slower than Cumulus 1 through VVP

[Atlas]

Hi

I installed Cumulus MX for the first time yesterday and I'm watching through the Activity Window in Virtual VP that Cumulus MX is a little slower than Cumulus 1 collecting data so I've also noticed in missing some wind gusts (about 2 or 3 missing data for a minute interval)
Allow fast looping is enabled in Virtual VP.
Some fix to improve fast looping and not to miss wind gusts? Something editable in Cumulus.ini?

Best regards

[steve]

Are you using TCP/IP or a virtual com port? Have you disabled LOOP2?

If you turn on data logging and attach the MX diags file, I'll take a look, but I can't promise anything.

[steve]

turn on data logging

and debug logging.

[Atlas]

Hi Steve

Reading other posts I've put in Cumulus.ini:

UseDavisLoop2=0
VP2SleepInterval=0

Still the same effect

Virtual VP and Cumulus MX are communicated through virtual COM port (com0com) though I can put TCP/IP communication if there's faster looping communication doing so.

I've attached the MXdiags file with data and debug logging enabled.

And nothing to promise... it's a great job what you are doing about this software

Thanks

[steve]

Data logging doesn't seem to be turned on.

[Atlas]

Sorry

If I close Cumulus then Data logging is unticked.

I've attached another one

[steve]

I can't see any problems there. It's getting a loop packet every 2 seconds or so, which is the rate the console sends them out, and it's getting 50 back every time it asks for 50, and there is no delay between each set of 50. So if data is missing, it seems to me that the problem must be with VVP.

[Atlas]

I only see missing data in the update of the wind values in Cumulus dashboard in the browser.
I suppose it's for the scripts updates.
What is important to me is that the max gust is recorded by Cumulus.
If you say there's no problem collecting data I'll feel more relaxed...

Thanks

[steve]

The dashboard update rate has nothing at all to do with the reading of the data from the station. Using web sockets (the default) the update interval is currently fixed at 3 seconds. If you want to have a faster update, you can switch to Ajax and set the rate yourself. See the instructions in the release note when I introduced the option, a few builds back.

[Atlas]

Well, following your instructions I've changed the setinterval for Ajax requests to 2 seconds on those pages. Still the same...

Thanks anyway

[steve]

VVP is occasionally sending two packets with no delay between them. You're not going to see the values from the first of those two packets on the display, whatever update interval you use, as the values from the second packet are going to replace the values from the first packet immediately.

[Atlas]

Ok thanks for the answer

As I said before collecting Cumulus all the data is the most important thing to me so never mind if it is not all displayed in screen