Data logger going to die?

[Mauro De Lauretis]

Good morning

I'm running WeeWX 4.5.1 on a RPi connected to a Davis console.

Everything works well, but I get this error messages every 10 minutes:

Apr 26 10:15:09 raspberrypi weewx[15755] ERROR weewx.drivers.vantage: LOOP try #1; error: LOOP buffer failed CRC check

Apr 26 10:15:09 raspberrypi weewx[15755] ERROR weewx.drivers.vantage: LOOP try #2; error: LOOP buffer failed CRC check

Apr 26 10:15:09 raspberrypi weewx[15755] ERROR weewx.drivers.vantage: LOOP try #3; error: LOOP buffer failed CRC check

Apr 26 10:15:09 raspberrypi weewx[15755] ERROR weewx.drivers.vantage: LOOP try #4; error: LOOP buffer failed CRC check

Apr 26 10:15:09 raspberrypi weewx[15755] ERROR weewx.drivers.vantage: LOOP max tries (4) exceeded.

Apr 26 10:15:09 raspberrypi weewx[15755] INFO weewx.engine: Main loop exiting. Shutting engine down.

Apr 26 10:15:09 raspberrypi weewx[15755] INFO weewx.engine: Shutting down StdReport thread

Apr 26 10:15:29 raspberrypi weewx[15755] ERROR weewx.engine: Unable to shut down StdReport thread

Apr 26 10:15:29 raspberrypi weewx[15755] DEBUG weewx.restx: Shut down PWSWeather thread.

Apr 26 10:15:29 raspberrypi weewx[15755] DEBUG weewx.restx: Shut down Wunderground-PWS thread.

Apr 26 10:15:29 raspberrypi weewx[15755] DEBUG weewx.restx: Shut down StationRegistry thread.

Apr 26 10:15:29 raspberrypi weewx[15755] CRITICAL __main__: Caught WeeWxIOError: Max tries exceeded while getting LOOP data.

After getting that messages, the logger works fine and updates the LOOP Data.

Is this a signal that the logger is going to damage?

Thank you

Mauro

[Tom Keffer]

Your logger is probably fine. 

Does this happen often?

What kind of logger? Serial or USB port? 

Have you installed ferrite coils?

Try reseating the logger. Just remove it, then reinstall it.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/106a3989-3437-469f-a558-bb58572f0959n%40googlegroups.com.

[Mauro De Lauretis]

Hello Tom,

thank you for reply.

It happens every 10 minutes interval, but I said in the post before LOOP data gets received anyway after one minute waiting.

It's a third part logger serial to usb and I don't have installed ferrite coils on it.

I will try reseating it.

Mauro

[Tom Keffer]

If I understand correctly, you have a serial port, which you connect to your computer via a serial-to-usb converter. Is that correct?

If so, serial-to-usb converters are notoriously unreliable. Try a different one.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ad804c31-09f8-4fd6-8046-9e0bdb05dbcdn%40googlegroups.com.

[Mauro De Lauretis]

I think so, it's a converter like this:

https://www.eurowebcamsite.com/it/e-shop/stazioni-di-rilevamento-meteo/datalogger-davis-usb-detail

[Tom Keffer]

Now I understand. You have a 3rd party USB logger. I am not familiar with it.

You will have to ask the manufacturer about the problem.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/6fdfd09d-7042-4938-8ade-e1ae97a3961en%40googlegroups.com.

[Mauro De Lauretis]

Yes, I mentioned that it's a 3rd party logger. Maybe you didn't see it :-)

I get the error by reseating the logger too, but thank you anyway Tom!

[Tom Keffer]

No, you said you had "a third part logger serial to usb". I assumed that meant you had a third party serial to usb converter. However, no serial port is involved.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/744cca77-3727-4015-9573-4937c5bf9150n%40googlegroups.com.

[Mauro De Lauretis]

Then I was definitely wrong by explaining. My fault ;-)

Thank you Tom and have a nice day!

[Mauro De Lauretis]

Tom, it's me again.

I've contacted the manufacturer of the data logger and he's pretty sure the errors could depend on the driver (vantage.py).

My WeeWX runs on weather34-skin. Do you think the problem could be provided by this skin itself too?

Would be grateful for a feedback.

Thanks

Mauro

Il giorno lunedì 26 aprile 2021 alle 14:42:40 UTC+2 tke...@gmail.com ha scritto:

[Tom Keffer]

No, the skin is not the problem. It involves only the database, not the driver.

Somehow the packets are not passing the CRC test. I can think of only three possible failure modes: (1) the wrong value is being calculated by the logger, (2) the driver is reading the number incorrectly, or (3) the driver is calculating the check incorrectly. I say it's #1.  What does he think the failure mode is?

It is only natural that the manufacturer is trying to shift the blame, but there are thousands of WeeWX installations around the world that are running the code successfully. His is a new product. Why is he so confident that the problem is not on his end?

If you are willing, I can send you an instrumented version of vantage.py that would show us what is in the buffer. But, you have to be comfortable with copying it into the correct position.

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/86a284ea-ce1d-41d9-865b-b7e75078fa1fn%40googlegroups.com.

[Mauro De Lauretis]

He says that I would be the first case for failures on his logger that nobody else have. N

No more explaining about it. 

I am comfortable with my RPi and the folders of WeeWX.

We can check this out.

Mauro

[Tom Keffer]

On Mon, Apr 26, 2021 at 9:47 AM Mauro De Lauretis <mauro.de...@gmail.com> wrote:

He says that I would be the first case for failures on his logger that nobody else have.

I'm sure he would, but how many does he have in the field?

The attached version of vantage.py will log the buffer in the case of a CRC error. Then we can see what is happening. 

-tk

[Mauro De Lauretis]

I really don't know, but it doesn't matter anymore.

Before I change the version of vantage.py I have to integrate some information.

On my Weewx.conf I had enabled both Season and Standard report, as well the Weather34 together with the highcharts (this without realizing it). 

Apart from Weather34, I'm using the old Standard report to upload via FTP some weather data with a local forecast association.

I've tried disabling all skins to see what would happen and I noticed that I don't receive any CRC error in the syslog.

Afterwards, I've restarted Weewx enabling the only Weather34 skin and the result is the same. No CRC errors!

This makes me think that the different skins create a kind of interference between them.

I could check it better by running the Simulator driver. What do you think?

Mauro

[Tom Keffer]

The skins interact through the database, not the driver. 

However, I suppose it is possible that with so many skins enabled that your RPi was overloaded. This would somehow lead to USB read errors. Not very plausible, but I guess it is possible.

Anyway, glad to hear that things are working now.

--

You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4467dad6-2cce-4502-9d86-dc98b2938b56n%40googlegroups.com.

[Mauro De Lauretis]

Could it be that my RPi has a memory leak or crashes because of different python versions?

By running “python —version”, it shows my python  2.7 as default, but I’ve installed WeeWX using python3 command line.

At the moment I have the only Weather34 skin enabled. 

My fear is that as soon as I activate StandardReport and FTP,  the CRC errors are there again.

I’m glad too that is working now, even not like I really want that he acts.

Thank you for your patience and help, Tom.

Mauro

[vince]

On Tuesday, April 27, 2021 at 4:24:37 AM UTC-7 Mauro De Lauretis wrote:

Could it be that my RPi has a memory leak or crashes because of different python versions?

By running “python —version”, it shows my python  2.7 as default, but I’ve installed WeeWX using python3 command line.

You have to specify 'python3 --version' to see which version of python3 weewx is using.

Your pi has both python versions installed, one python2 (the default called 'python' for legacy reasons), plus one python3 (which you need to call as 'python3' explicitly.

You didn't mention which model pi you are running, but if you're on anything weaker than a pi3 you can pretty easily get into the situation where the reports take too long to run 'especially' if you have a slow or failing SD card.   You can see how long things take to run in your syslog.   Likely not an issue if you're on a pi4 but it is possible...

[Mauro De Lauretis]

Hi Vince

Thank you for your feedback.

My RPi is pretty old (ver. 2 B+) with only 512 Mb RAM memory.

Since I thought my issue belongs to a memory leak too, I decided to buy the new Pi 4 with 4 Gb RAM memory.

This should solve my problems.

Mauro

[Tom Keffer]

Unless you are running many complex skins, which you are not, WeeWX can easily run on an RPi 2. Here's an RPi B+, which is even less capable, that has been running continuously for over 6 years.

I guess I don't understand what problem you are trying to solve. The machine is running as expected, without CRC errors. What is left?

-tk

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dd467d4e-ac4f-4ddf-8374-8618c3ee64b7n%40googlegroups.com.

[Mauro De Lauretis]

Nothing left Tom, the second question was more for feedback if my RPi could have memory leaks or python problems. :-)

In any case I would have bought a new RPi , because I want to dedicate the current one to another project.

Thank you so much your efforts and your brillant daily assistance.

Mauro