weewx4 locks up Vantage2 console

[Steve Koone]

All-  The upgrade to weewx v4 isn't working here.  When I start up v4 it almost immediately sends the Vantage console into lock up with the letter 'R' in the lower right corner.

I'm reverting back to v3.92.

[Tom Keffer]

You're not giving us much information. How about a log? See the Wiki article Help! Posting to weewx-user for how to get a good log.

On Fri, May 1, 2020 at 6:55 AM Steve Koone <sko...@gmail.com> wrote:

All-  The upgrade to weewx v4 isn't working here.  When I start up v4 it almost immediately sends the Vantage console into lock up with the letter 'R' in the lower right corner.

I'm reverting back to v3.92.

--
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/e7679cae-b478-4469-92bc-8b79fe5876a3%40googlegroups.com.

[Steve Koone]

I don't know how to pull a log.

All I can tell you is this.  I'm using a pi2 w/ an FTDI USB to serial adapter.  Every time weewx starts, it locks up the Vantage console.

I have tried Deb 10 with python 2 and 3.

I have tried Deb 8 with python 2

I just tried Deb 9 with python 2.  Everything locks up communication to the Vantage2 console.  It never did this with 3.92 and earlier.  I have to pull the batteries in the Vantage2 console and hard reboot the thing.

I guarantee you I won't be the only one reporting this problem.

On Friday, May 1, 2020 at 10:22:10 AM UTC-4, Tom Keffer wrote:

You're not giving us much information. How about a log? See the Wiki article Help! Posting to weewx-user for how to get a good log.

On Fri, May 1, 2020 at 6:55 AM Steve Koone <sko...@gmail.com> wrote:

All-  The upgrade to weewx v4 isn't working here.  When I start up v4 it almost immediately sends the Vantage console into lock up with the letter 'R' in the lower right corner.

I'm reverting back to v3.92.

--
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...@googlegroups.com.

[Mike Doneske]

I using weewx4 with a Vantage 2 console as of 24 hours ago. It all works as expected... This is on a CentOS 8 system with a Vantage 2 Pro station

[Tom Keffer]

Unlikely. This driver has been around for a while. More likely it is a configuration problem on your end.

In any case, I simply cannot help you without the log. Instructions were included in my earlier post.

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/c0b9b4e0-6676-44b4-9272-bc6f1df39068%40googlegroups.com.

[Steve Koone]

Resolved:  After ten hours of fighting this mess, I finally found the solution to my issue.  Clear the memory in the console.

Issue this command at the terminal screen prompt:

wee_device --clear-memory

I tested this on two separate consoles both of which locked up the screen (frozen) and no keyboard response.  Issue the command even if the console is locked up.  After this, both consoles corrected themselves almost immediately and began working normally, and the software began reporting to CWOP as it always had in the past.

As for any logical explanation:  It seems the software sends some sort of command to the console when the software boots up.  Apparently the console doesn't like what it sees and it pukes.  The only way to fix it without clearing memory is to pull the batteries and restart from the beginning.  The software acts as if nothing is/was wrong.

I can confirm that I NEVER had this happen before and I've used weewx for years with no issues.  Yes I have had to occasionally clear the console memory for one reason or another but never to have the console completely lock up and be totally non-responsive.

Screw the log.  This is not to be diagnosed from some log.  This is a software / hardware conflict that should have been documented and highlighted to look at after a major software release such as this.  I've reinvented the wheel 14 times already today just to find this one fix.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/c0b9b4e0-6676-44b4-9272-bc6f1df39068%40googlegroups.com.

[Tom Keffer]

Screw the log.  This is not to be diagnosed from some log.  This is a software / hardware conflict that should have been documented and highlighted to look at after a major software release such as this.  I've reinvented the wheel 14 times already today just to find this one fix. 

Steve, you're encountering problems that no one else is having with a very mature driver. You can't make claims like this then dismiss a good-faith request for the log.

And, let me remind you this is an all-volunteer effort. No whining unless you offer to help.

-tk

[Tom Mitchell]

This was helpful to me. I have a VP2 console I have been having trouble with since 3.9 and this command resolved it. So at least for me, this is not about 4.0 as it is about my console.