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
Mathew,
Thanks for the speedy reply. I have the new driver and it works, but now
I have another error:
_______________________________
ug 8 22:26:51 kangoo weewx[10905]: engine: Initializing weewx version 3.5.0
Aug 8 22:26:51 kangoo weewx[10905]: engine: Using Python 2.7.9
(default, Mar 8 2015, 00:52:26) #012[GCC 4.9.2]
Aug 8 22:26:51 kangoo weewx[10905]: engine: Platform
Linux-4.4.13-v7+-armv7l-with-debian-8.0
Aug 8 22:26:51 kangoo weewx[10905]: engine: Using configuration file
/home/weewx/weewx.conf
Aug 8 22:26:51 kangoo weewx[10905]: engine: Loading station type TE923
(weewx.drivers.te923)
Aug 8 22:26:51 kangoo weewx[10905]: te923: driver version is 0.18
Aug 8 22:26:51 kangoo weewx[10905]: te923: polling interval is 10
Aug 8 22:26:51 kangoo weewx[10905]: te923: observation map is {'bat_1':
'outBatteryStatus', 'bat_3': 'extraBatteryStatus2', 'bat_2':
'extraBatteryStatus1', 'bat_5': 'extraBatteryStatus4', 'bat_4':
'extraBatteryStatus3', 'bat_wind': 'windBatteryStatus', 't_in':
'inTemp', 'link_rain': 'rainLinkStatus', 't_5': 'extraTemp4', 'h_in':
'inHumidity', 'h_4': 'extraHumid3', 'h_5': 'extraHumid4', 'h_2':
'extraHumid1', 'h_3': 'extraHumid3', 'h_1': 'outHumidity', 't_2':
'extraTemp1', 'link_2': 'extraLinkStatus1', 'link_uv': 'uvLinkStatus',
'link_wind': 'windLinkStatus', 'uv': 'UV', 'bat_uv': 'uvBatteryStatus',
'link_5': 'extraLinkStatus4', 'bat_rain': 'rainBatteryStatus', 'link_3':
'extraLinkStatus2', 't_3': 'extraTemp2', 'link_1': 'outLinkStatus',
't_1': 'outTemp', 't_4': 'extraTemp3', 'link_4': 'extraLinkStatus3'}
Aug 8 22:26:51 kangoo weewx[10905]: te923: Found device on USB bus=001
device=008
Aug 8 22:26:52 kangoo weewx[10905]: te923: Failed attempt 1 of 5 to
read data: error sending control message: Device or resource busy
Aug 8 22:26:55 kangoo weewx[10905]: te923: Failed attempt 2 of 5 to
read data: error sending control message: Device or resource busy
Aug 8 22:26:58 kangoo weewx[10905]: te923: Failed attempt 3 of 5 to
read data: error sending control message: Device or resource busy
Aug 8 22:27:01 kangoo weewx[10905]: te923: Failed attempt 4 of 5 to
read data: error sending control message: Device or resource busy
Aug 8 22:27:04 kangoo weewx[10905]: te923: Failed attempt 5 of 5 to
read data: error sending control message: Device or resource busy
Aug 8 22:27:07 kangoo weewx[10905]: engine: Unable to load driver: Read
failed after 5 tries
Aug 8 22:27:07 kangoo weewx[10905]: **** Exiting...
____________________________________________
Device or resource busy but there is no other weewx process running (as
seen with ps -ef|grep weewx) so I don't know what process is hampering
me or should I restart the pi and is there some - to me unknown -
process that's in the way.
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.
