Welcome to the Cumulus Support forum.

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024

Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

Pocket PWS and Readings

Topics about the Beta trials up to Build 3043, the last build by Cumulus's founder Steve Loft. It was by this time way out of Beta but Steve wanted to keep it that way until he made a decision on his and Cumulus's future.

Moderator: mcrossley

Locked
txweather
Posts: 36
Joined: Sun 03 Jan 2016 10:27 pm
Weather Station: Davis Vantage Vue
Operating System: Raspbian
Location: Spring, TX
Contact:
Contact txweather

Re: Pocket PWS and Readings

Post by txweather »

txweather wrote:
steve wrote:If you still have data logging on, the diags file might be interesting.
Steve,

It died today.

Logs are attached.
It dieg again.
Hopefully we caught it thsi time and it looks like we did... :)
You do not have the required permissions to view the files attached to this post.
Top
User avatar
steve
Cumulus Author
Posts: 26701
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:
Contact steve

Re: Pocket PWS and Readings

Post by steve »

While receiving a set of LOOP packets, it stopped being sent any data after packet 37 of 50:

2016-01-10 19:44:03.638 Data 37: 4C-4F-4F-14-00-76-04-2E-76-1A-03-26-B2-01-00-01-35-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-40-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-00-00-14-01-B4-12-00-00-00-00-00-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-24-03-06-09-CE-02-CB-06-0A-0D-0D-D7
2016-01-10 19:44:23.467 !!! loop data not received

Then, when it tried to wake the connection up again, it got no response:

2016-01-10 19:44:47.481 Wake VP
2016-01-10 19:44:47.483 Sending newline
2016-01-10 19:44:49.485 ch1 = 0xFFFFFFFF
2016-01-10 19:44:49.487 ch2 = 0xFFFFFFFF
2016-01-10 19:44:49.489 Sending newline
2016-01-10 19:44:51.491 ch1 = 0xFFFFFFFF
2016-01-10 19:44:51.493 ch2 = 0xFFFFFFFF
2016-01-10 19:44:51.495 Sending newline
2016-01-10 19:44:53.497 ch1 = 0xFFFFFFFF
2016-01-10 19:44:53.498 ch2 = 0xFFFFFFFF
2016-01-10 19:44:53.500 *** Not woken

Nothing it did after that produced a response of any kind.
Steve
Top
txweather
Posts: 36
Joined: Sun 03 Jan 2016 10:27 pm
Weather Station: Davis Vantage Vue
Operating System: Raspbian
Location: Spring, TX
Contact:
Contact txweather

Re: Pocket PWS and Readings

Post by txweather »

steve wrote:While receiving a set of LOOP packets, it stopped being sent any data after packet 37 of 50:

2016-01-10 19:44:03.638 Data 37: 4C-4F-4F-14-00-76-04-2E-76-1A-03-26-B2-01-00-01-35-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-40-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-00-00-14-01-B4-12-00-00-00-00-00-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-24-03-06-09-CE-02-CB-06-0A-0D-0D-D7
2016-01-10 19:44:23.467 !!! loop data not received

Then, when it tried to wake the connection up again, it got no response:

2016-01-10 19:44:47.481 Wake VP
2016-01-10 19:44:47.483 Sending newline
2016-01-10 19:44:49.485 ch1 = 0xFFFFFFFF
2016-01-10 19:44:49.487 ch2 = 0xFFFFFFFF
2016-01-10 19:44:49.489 Sending newline
2016-01-10 19:44:51.491 ch1 = 0xFFFFFFFF
2016-01-10 19:44:51.493 ch2 = 0xFFFFFFFF
2016-01-10 19:44:51.495 Sending newline
2016-01-10 19:44:53.497 ch1 = 0xFFFFFFFF
2016-01-10 19:44:53.498 ch2 = 0xFFFFFFFF
2016-01-10 19:44:53.500 *** Not woken

Nothing it did after that produced a response of any kind.
Steve,

Thanks for your reply.

What does that exactly mean?
MX keeps dying on me and I cant figure out why... :(
Top
freddie
Posts: 2473
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 22.04 LXC
Location: Alcaston, Shropshire, UK
Contact:
Contact freddie

Re: Pocket PWS and Readings

Post by freddie »

txweather wrote:
steve wrote:While receiving a set of LOOP packets, it stopped being sent any data after packet 37 of 50:

2016-01-10 19:44:03.638 Data 37: 4C-4F-4F-14-00-76-04-2E-76-1A-03-26-B2-01-00-01-35-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-40-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-00-00-14-01-B4-12-00-00-00-00-00-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-24-03-06-09-CE-02-CB-06-0A-0D-0D-D7
2016-01-10 19:44:23.467 !!! loop data not received

Then, when it tried to wake the connection up again, it got no response:

2016-01-10 19:44:47.481 Wake VP
2016-01-10 19:44:47.483 Sending newline
2016-01-10 19:44:49.485 ch1 = 0xFFFFFFFF
2016-01-10 19:44:49.487 ch2 = 0xFFFFFFFF
2016-01-10 19:44:49.489 Sending newline
2016-01-10 19:44:51.491 ch1 = 0xFFFFFFFF
2016-01-10 19:44:51.493 ch2 = 0xFFFFFFFF
2016-01-10 19:44:51.495 Sending newline
2016-01-10 19:44:53.497 ch1 = 0xFFFFFFFF
2016-01-10 19:44:53.498 ch2 = 0xFFFFFFFF
2016-01-10 19:44:53.500 *** Not woken

Nothing it did after that produced a response of any kind.
Steve,

Thanks for your reply.

What does that exactly mean?
MX keeps dying on me and I cant figure out why... :(
It means that MX is losing contact with your weather station. Something is causing it to be unavailable - possibly noise/interference with your USB connection.
Freddie
Image
Top
Locked

Return to “CumulusMX Beta (releases up to b3043 ONLY)”