On 08/08/16 18:01, mwall wrote:
On Monday, August 8, 2016 at 11:43:25 AM UTC-4, Joep L. Blom wrote:
matthew,
Continuing... Weewxd from the commandline works OK, all data are
read.
the deamon weewx, however won't start.
if you get one behavior when you run weewxd directly but a different
behavior when you run weewxd as a daemon, then the problem is in your
daemon and/or operating system configuration.
I reset the debug switch (storage
is sparse on the PI) but now I have again the gap of approx. 15
minutes
but I haven't found where I can download te923.py version 0.18 or
do I
have to download the latest version but that is of March this year
and
is yhe one I use.
slow down, tiger. changing the value of debug should not affect the
driver behavior. if it does, there is a bug somewhere.
if you are experiencing a 15 minute gap then you are not using the
latest driver, or even 0.18rc5
the latest driver is version 0.18 and is in the weewx repository at
github:
https://github.com/weewx/weewx/blob/master/bin/weewx/drivers/te923.py
as of 16:55 UTC on 08aug2016, the driver version is 0.18 (and has been
for 17 days).
using anything other than 0.18 is a waste of your time and my time
(unless a different version proves a regression in 0.18).
m
Matthew,
I had other business to attend to but I have now had time to test further.
The error I showed in my latest mail is definitively a problem in de
driver. I have used te923py version rc0.18r1 and that didn't give the
error "Device or resource busy".
I have other problems mostly the fact that it encounters the
error:"te923: Failed attempt 1 of 5 to read data: Bad header byte: 00 !=
5a".
The strange thing is that the original TFA software (Windows) reads the
memory without a problem. I can also see that at 5 minutes interval the
stored data span 10 days.
Another thing is that with wee_device I can read the data of the memory.
I can store the data in temporary files but I wonder if there is a
simple script to translate these data or import them directly in the
database.
Another thing I have found is that removing power and batteries doesn't
destroy the internal database.
However due to the fact that weewx (or weewxd) won't read the station I
think the only solution is to store the data from the memory regularly
as that can be done.
(why weewxd will not read the data is a mystery for me).
Joep
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
