Dear Vince,
I believe you are right on the money with your last remark. Dead
software works as long as you have hardware, so I tried with cramming
weewx in router, and strange things happened.
Creating embedded firmware with Python inside for 24/7 task is
problematic at best. Low RAM, slow processor and so on is all hitting me
in the head. Check the capture, it runs with only 20MB of free RAM. I
have to move database out of RAM to USB stic/thumbdrive/disk.
By the way this router is only $17. ...not so important in grand scheme
of things.
There is no skin (generating) at all. Only CVS is rewritten to one file
(in RAM). There is no room/processor power for graphing. Even with such
"naked" weewx the processor routinely runs at more than 30%.
So, let me recap. Syncing archiving interval with WMR and WH stations on
5 minutes helped, and it works ok now. My friends are testing other
stations.
However, if moving database to USB disk does not help, there are only
two way out of this - using embedded device with more RAM, or clearing
measurement on VP periodically to prevent this in the first place. I am
not sure the first one will help, and latter feels bad on so many
levels. If router with more RAM does not help, Raspberry pi, here I come
fo VP stations.
Thanx!
Nick
On 22.5.2018. 19:43, vince wrote:
On Tuesday, May 22, 2018 at 5:27:23 AM UTC-7, Andrew Milner wrote:
As has been said many times in this forum comments like 'VP
struggles' do not tell us anything - we (and you) need to look at
the log, maybe run with debug enabled and so forth in order to
understand and more importantly see what is going on within weewx -
any error messages and so forth.
On a 60MB RAM system it is possible the computer simply is out of memory
and oddities are happening.
Turn off the CSV extension and see if that helps.
Alternately turn off WU and run only the CSV extension and see if 'that'
helps.
But ideally you'd have some data you could tell us about the ram/cpu
usage on the system.
You haven't shown us your custom weewx skin either. If that's too
complicated the computer will work too hard when the output is
generated. We have had numerous occcasions where people trying to run a
complicated skin makes the system unstable or unpredictable (my example
- running Saratoga templates on a 128MB RAM Seagate Dockstar (pogoplug)
here).
Ideally, set debug=1 and provide the syslog around the time(s) you see
whatever 'struggles' you are experiencing.
I still think the long-term solution is to just tell people to buy a
Raspberry Pi if they want to run weewx. You're talking well under $50
US and it is a very known quantity. You're doing all kinds of things
like writing custom firmware for embedded routers and trying to fit too
much stuff in too small a capacity computer. That's guaranteed pain.
Or just keep running (unsupported/dead) wview on your
(unsupported/hacked/legacy) old routers....
--
You received this message because you are subscribed to a topic in the
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/weewx-user/HXHjLqxOJxE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
weewx-user+unsubscr...@googlegroups.com
<mailto:weewx-user+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
