Cumulus Support

Vossenberg wrote:Unfortunately the firmware I received did not solve the problem, it was a 3.0 firmware. Jim, did you receive another revision 3.01 or something?

Jim's firmware is 3.12.

Vossenberg wrote:Steve/Jim,

Unfortunately the firmware I received did not solve the problem, it was a 3.0 firmware. Jim, did you receive another revision 3.01 or something?

Kind Regards,

Pascal

I received firmware version 3.12. And the console displayed that version number after the update completed when I pressed the appropriate key sequence. I'm not familiar with the Envoy so I don't know how it tells you the firmware version.

Are you sure the upgrade actually worked? It took a few minutes for it to complete, with a progress bar showing during that period. There is a Help screen that shows detailed screen-by-screen, and clock-by-click of what should happen.

The Cumulus diags file will (should) show the firmware version.

Thank you for the number of the firmware. I have received a firmware 3.00 and reflashed it. This has not been very helpful then. I will report back to Davis, and ask for the 3.12 firmware for the Envoy.

The story continues...

Kind Regards,

Pascal

Just received firmware 3.12 from Davis and installed it on my Envoy.
I am now checking if the problem still occurs.

Just another question, in the 1058 build (the real version) a delay has been introduced for receiving the data, maybe it is nice to check if it also works without the delay.

I will report tomorrow to see if this evening it will run without any error.

Kind Regards,

Pascal Willemssen

Vossenberg wrote:Just another question, in the 1058 build (the real version) a delay has been introduced for receiving the data, maybe it is nice to check if it also works without the delay.

If by delay you mean the automatic "sleep interval", then you will need that if this firmware behaves like version 3 and returns the data without a delay. Otherwise, Cumulus will use a lot of CPU, and some things will not work properly as not enough space is allocated to hold the amount of duplicated data which will be read.

I believe Jim found that version 3.12 did return the data without a delay on his station, and hence did need the automatic sleep interval.

steve wrote:

Vossenberg wrote:Just another question, in the 1058 build (the real version) a delay has been introduced for receiving the data, maybe it is nice to check if it also works without the delay.

If by delay you mean the automatic "sleep interval", then you will need that if this firmware behaves like version 3 and returns the data without a delay. Otherwise, Cumulus will use a lot of CPU, and some things will not work properly as not enough space is allocated to hold the amount of duplicated data which will be read.

I believe Jim found that version 3.12 did return the data without a delay on his station, and hence did need the automatic sleep interval.

That is correct - I have it set back to "1"

Steve,

With firmware 3.12 the problem is solved! After a night testing I can confirm that there has been no time-out error whatsoever.
Thank you very much for your support!

Now i'll ask the same question Jim asked Davis support when the official release will be.

Kind Regards,

Pascal

JimDantin wrote:That is correct - I have it set back to "1"

I'm confused. Setting it to 1 in the ini file overrides the automatic value and effectively removes the effect, so I would expect it to be using a lot of CPU and re-reading the data much more often than every 2-3 seconds. When we discussed this in PM, I said you should take the setting out of the ini file, you said you had, and subsequently your readings were every 2-3 seconds as expected?

steve wrote:

JimDantin wrote:That is correct - I have it set back to "1"

I'm confused. Setting it to 1 in the ini file overrides the automatic value and effectively removes the effect, so I would expect it to be using a lot of CPU and re-reading the data much more often than every 2-3 seconds. When we discussed this in PM, I said you should take the setting out of the ini file, you said you had, and subsequently your readings were every 2-3 seconds as expected?

My bad - I HAD removed the line "VP2SleepInterval=1". I was remembering back a couple steps when we were testing. Sorry for the confusion I might have caused.

FYI, I have not seen a single error ever since I updated to 3.12. I'm curious how many users are suffering through the problem right now while we wait for Davis to release the update.

I'm experiencing the same issue but do not know anything about writing code. So just lurking and waiting for a solution.
However I don't seem to be having any adverse data results from the data input stopping. Just more of an annoyance of seeing the red Error indicator blinking.


[quote= I'm curious how many users are suffering through the problem right now while we wait for Davis to release the update.[/quote]

randy52644 wrote:I'm experiencing the same issue but do not know anything about writing code. So just lurking and waiting for a solution.

Hopefully Davis will be making the fixed firmware public soon.

However I don't seem to be having any adverse data results from the data input stopping.

You're missing out on data readings. For most things, it doesn't really matter much, but you may miss peak wind gusts, for example.

Just more of an annoyance of seeing the red Error indicator blinking.

You can turn it off by putting

ReportDataStoppedErrors=0

in the [Station] section of cumulus.ini

Another option which I used with the faulty firmware was selecting the option: Restart if data stopped option. Then the error "Led" does not appear anymore as well.

I'll give that a try.
Appears this thread went dry. Apparently no new solutions?

Vossenberg wrote:Another option which I used with the faulty firmware was selecting the option: Restart if data stopped option. Then the error "Led" does not appear anymore as well.

randy52644 wrote:Appears this thread went dry. Apparently no new solutions?

We're still waiting for some sort of response from Davis. I have sent multiple emails asking when they were going to release the new firmware on their website.