On 08/08/16 14:31, J.L. Blom wrote:
On 08/08/16 00:29, mwall wrote:
On Sunday, August 7, 2016 at 6:16:55 PM UTC-4, Joep L. Blom wrote:
replying to myself:
This the result :
root@kangoo:/home/weewx/bin# ./wee_device
Using configuration file /home/weewx/weewx.conf
Using TE923 driver version 0.18rc5 (weewx.drivers.te923)
Traceback (most recent call last):
File "./wee_device", line 54, in <module>
main()
File "./wee_device", line 51, in main
device.configure(config_dict)
File "/home/weewx/bin/weewx/drivers/__init__.py", line 69, in
configure
self.do_options(options, parser, config_dict, prompt)
File "/home/weewx/bin/weewx/drivers/te923.py", line 767, in
do_options
with TE923Station() as station:
File "/home/weewx/bin/weewx/drivers/te923.py", line 1519, in
__enter__
self.open()
File "/home/weewx/bin/weewx/drivers/te923.py", line 1552, in open
self.read_memory_size()
File "/home/weewx/bin/weewx/drivers/te923.py", line 1734, in
read_memory_size
buf = self._read(0xfc)
File "/home/weewx/bin/weewx/drivers/te923.py", line 1704, in
_read
buf = self._raw_read(addr)
File "/home/weewx/bin/weewx/drivers/te923.py", line 1604, in
_raw_read
raise weewx.WeeWxIOError(e)
weewx.WeeWxIOError: Connection timed out
I can not see where the error comes from but surely something is
not OK.
(Thomas?)
Joep
the station shows up on the usb, but it is not responding.
the first thing the te923 driver does is to query the station to see
if it is a large or small memory model. in your case, that query fails.
most likely the firmware is wedged. did you try to power cycle the
station?
if you are loathe to lose the data in the logger (assuming there is
any, and assuming it is not corrupt), then you can try using the
te923 driver to do a raw dump of the station memory (see the options
you got when you did --help). you could also try using the latest
te923.py driver (version 0.18 - get it from the weewx repository on
github) instead of rc5. you could also try downloading and compiling
the te923tool software to see if it can read the station memory (if
it can, and the weewx driver cannot, that would be a useful data
point). however, if the weewx driver cannot even read the bytes that
indicate the memory size, chances are pretty good that nothing will
be able to read it.
this kind of usb lockup happens regularly on fine offset stations,
fairly frequently on acurite stations, but fairly rarely on hideki
(te923) stations.
m
Matthew,
Thanks for your elaborate answer. I need another weather station as
this one is gradually degrading. In April I changed the rechargeable
battery in the wind unit but since 2 weeks it doesn't send any signals
(the reason I changed the location of my logger). I will try your
useful suggestions this afternoon as I have to go in a few minutes. I
should see if I can repiar the wind unit (it's on a 10 m. mast) but I
can only use 1 hand (a minor operation puts it out of order for 6
weeks!) so I have to wait to do that and/or install a new system. I
tend to the Davis with only the units and a meteostick but I don't
know if the meteostick has a memory for data and for how long. I want
at least 4 days storage to prevent data gaps.
Matthew,
As usual you gave me something to work with. I used wee_device and it
works OK! I used the --history-since= tag and it read the full 7 days in
a local file.
THis means that wee_device can read the memory and also the current
values but weewx can not. (I tried it again and it still did nothing,
not even one entry in the log).
wee_device gave entries in the log as it reads a few times errors in
reading I often have (has that been solve in te923-rc5?).
Maybe you have some useful tips how I can proceed? I have debug=1 but
nothing happens. Only when I, after a reboot of the raspberry start
weewx (which is done automatically) then it gives the output I sent in
earlier mails.
Something has changed and apparently not in the logger or am I wrong??
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.
