Page 2 of 3
Re: USB stop responding
Posted: Mon 27 Aug 2018 1:39 pm
by hillyjd
The diagnostic file I just posted has the error text in it, but I just checked my PWS webpage and updated weather data is being posted. It's not locked up. So I'm totally confused. I will continue to monitor the webpage and send an updated diagnostic file when the data actually freezes up.
r/
Jim
Re: USB stop responding
Posted: Mon 27 Aug 2018 3:01 pm
by hillyjd
Looks like it was just a timing thing. The data had gone stale in the last half hour, so it looked like it was still current when it wasn't.
r/
Jim
Re: USB stop responding
Posted: Thu 30 Aug 2018 9:02 am
by stef942
I set an auto reboot every 02 hours with crontab to solve the problem
Re: USB stop responding
Posted: Thu 30 Aug 2018 2:23 pm
by hillyjd
Can you show me how to do that? I'm not familiar with crontab.
r/
Jim
Re: USB stop responding
Posted: Thu 30 Aug 2018 4:28 pm
by stef942
i have followed tuto from Experimentor to install cumulus :
https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=16931
To make Cumulus run each time the Pi is rebooted (and force reboot in the early hours each day)
On the Pi, type:
On first run select the text editor you prefer (defaults to #2, nano)
Then add the following lines at the end of the file:
Code: Select all
# Start Cumulus as background task 30s after reboot (delay to allow WiFi to startup)
@reboot (sleep 30;cd /home/pi/CumulusMX;sudo mono CumulusMX.exe) &
# Reboot each day at 0258
58 02 * * * sudo reboot
If you want to access the Pi without Cumulus running, simply log in, then crontab –e, then add # before @reboot so that that line is ignored ‘commented out’. Then sudo reboot. Remove the # again for normal operation.
i just modified last 2 lines
Code: Select all
# Reboot every 2 hours
0 */2 * * * sudo reboot
Re: USB stop responding
Posted: Thu 30 Aug 2018 5:24 pm
by hillyjd
Thank you so much. I just went through the steps. I'm a Linux moron, so hopefully I got it correct.
r/
Jim
Re: USB stop responding
Posted: Sun 02 Sep 2018 3:29 pm
by theSwede
I am experiencing the same problem as stef942.
The symptoms are that the "now-page" looks like everything works fine but without updates. The "trend-page" shows that the reading has stopped.
See snap-shoot from temp screen. It stopped logging at 11:17:
data collection stop.jpg
As can be seen it started to work again after a "sudo reboot" of the pi at around 12:55.
Extracts from the log file around 11:17 where the logging stopped:
Code: Select all
2018-09-01 11:17:10.309 2018-09-01 11:17:10 Packet:D6 0D 1A 0B 01 09 12 FE 33 FF 33 87 03
2018-09-01 11:17:10.309 Baro packet received
2018-09-01 11:17:13.015 2018-09-01 11:17:13 Packet:D3 10 1A 0B 01 09 12 0C 0C 18 20 01 00 20 95 01
2018-09-01 11:17:13.015 Wind packet received
2018-09-01 11:17:14.826 2018-09-01 11:17:14 Packet:D7 10 1A 0B 01 09 12 00 CA 00 33 64 00 00 89 02
2018-09-01 11:17:14.826 Temp packet received
2018-09-01 11:17:15.072 2018-09-01 11:17:15 Packet:D9 08 00 20 01 00 02 01
2018-09-01 11:17:15.072 Status packet received
2018-09-01 11:17:18.072 Data read loop: The operation has timed-out.
2018-09-01 11:17:19.423 Sending heartbeat
2018-09-01 11:17:19.427 HISTORY_AVAILABLE_PACKET_TYPE
2018-09-01 11:17:19.428 Sending DA response
2018-09-01 11:17:22.428 Data read loop: The operation has timed-out.
2018-09-01 11:17:30.014 Data read loop: The operation has timed-out.
2018-09-01 11:17:33.014 Data read loop: The operation has timed-out.
2018-09-01 11:17:38.320 Data read loop: The operation has timed-out.
2018-09-01 11:17:44.012 Data read loop: The operation has timed-out.
2018-09-01 11:17:47.824 Data read loop: The operation has timed-out.
2018-09-01 11:17:49.423 Sending heartbeat
2018-09-01 11:17:52.427 Data read loop: The operation has timed-out.
2018-09-01 11:17:58.010 Data read loop: The operation has timed-out.
2018-09-01 11:18:01.010 Data read loop: The operation has timed-out.
2018-09-01 11:18:04.010 Data read loop: The operation has timed-out.
2018-09-01 11:18:07.820 Data read loop: The operation has timed-out.
2018-09-01 11:18:10.238 Data read loop: Array index is out of range.
2018-09-01 11:18:10.240 Data read loop: Array index is out of range.
2018-09-01 11:18:10.240 Data read loop: Array index is out of range.
2018-09-01 11:18:10.241 Data read loop: Array index is out of range.
2018-09-01 11:18:10.242 Data read loop: Array index is out of range.
2018-09-01 11:18:10.243 Data read loop: Array index is out of range.
See also attached complete log-file.
Re: USB stop responding
Posted: Sun 02 Sep 2018 4:23 pm
by steve
The station seems to have got a bit confused, it suddenly said that there was an archive packet available in the middle of 'live' running. It should only signal that when software hasn't previously been reading live data. It's possible that the response from Cumulus wasn't what it was expecting at that point, and possibly that caused it to start sulking and stop sending data. Just guessing, there is no official documentation available for this station.
Re: USB stop responding
Posted: Sun 02 Sep 2018 5:20 pm
by theSwede
Steve, thanks for a quick reply
After browsing around in the forum, it seems to be a quite common problem that the communication stops. Have you considered to make an automatic fix for the issue? According to the log it looks like CMX is detecting the problem but does nothing to come out of the situation.
I found a work-around in the posting
https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=15574 that I will try to apply.
Thanks for a very useful program, I have used for several years
Re: USB stop responding
Posted: Sun 02 Sep 2018 5:36 pm
by steve
In response to a 'history available' packet, Cumulus sends a 'DA' ("request historic data") packet, which is supposed to make the station send the history packet - according to the unofficial spec that I used to write the code -
https://www.bashewa.com/wmr200-protocol.php
It's not immediately obvious what else I can do. I bought a WMR200 so that I could write the code, and never hit this problem myself. I no longer have the WMR200 (or any other weather station for that matter) as I gave it away.
Re: USB stop responding
Posted: Sun 02 Sep 2018 8:03 pm
by theSwede
As a fix I ment a recovery action, not avoiding the interface anomality.
I see two levels of recovery actions that could maybe be implemented if you are still updating the program:
- - I don't know the interface at all towards WMR200 but maybe it could be possible to re-initialize the interface in the same way as during start-up of CMX?
- - Restart the entire CMX program. This is what I will try to accomplish with some scripts outside CMX
It could be that some users want to keep current behavior so it should maybe be under control of the CMX settings.
I first used Cumulus (V1) on a PC and I can't remember that I had these problems at all.
Then, a year or two ago, I changed to CMX running on a PC and started to see the problem now and then (about once a month) and my successful manual recovery was to terminate CMX and start it again
Lately I have changed to a RaspberryPi to host CMX and my feeling is that the problem is more frequent.
The biggest problem is that I have to monitor the data collection in order not to lose data. If CMX just stopped, then it will retrieve all info next time it starts up instead of emptying WMR200 from all data without storing it as it is now.
Re: USB stop responding
Posted: Sun 02 Sep 2018 8:56 pm
by steve
If I do any more updates, I'll have a look to see if there's anything I can do.
Re: USB stop responding
Posted: Mon 03 Sep 2018 7:03 am
by theSwede
Thanks!
Re: USB stop responding
Posted: Tue 04 Sep 2018 5:29 pm
by richard_newberry
We would be grateful of that wouldn't we people?
Steve is a legend with the CumulusMX. it's one great piece of software but he has had some bad luck recently so we'll have to sit on the fence for the update to come.
also sort out the libudev1 and mono problems out to.
Re: USB stop responding
Posted: Tue 04 Sep 2018 5:31 pm
by richard_newberry
If Steve wants to test it out on my machine more then happy for Steve to do it on mine.
Offers is there Steve.