On 10/08/16 19:11, mwall wrote:
On Wednesday, August 10, 2016 at 9:49:32 AM UTC-4, Joep L. Blom wrote:
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".
so are you saying that 0.18rc1 does not report "Device or resource
busy", but still does not function?
what happens when you use te923.py version 0.18 through the 4 steps
enumerated in the previous email in this thread, i.e., diagnostics,
wee_device, weewxd directly, weewxd as daemon?
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.
good. that tells us that you do not have a hardware problem; the
problem is that usb protocol used by the te923 driver does not yet
match the protocol used by the tfa windows software.
Another thing is that with wee_device I can read the data of the
memory.
using which version of the te923 driver?
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.
the solution is to fix the te923 driver, not to apply more band-aids
that will encourage infection and eventual amputation.
m
--
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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
Matthew,
Thanks, Of course, band-aids are not the solution, maybe amputation or a
new joint (i got one in a finger 3 weeks ago).
But either I didn't get the driver correct (I have problems with github:
the only way is to copy the asci-text to a file) or something else is
wrong. I cannot find the driver as file on the page.
I used the te923.py version 018rc1 and that works ok but weewxd gives -
with v0.18rc1 - constantly read errors.
Here are 2 trials:
____________________
te923: driver version is 0.18rc1
Aug 10 21:37:15 kangoo weewx[4221]: te923: polling interval is 10
Aug 10 21:37:15 kangoo weewx[4221]: 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 10 21:37:15 kangoo weewx[4221]: te923: Found device on USB bus=001
device=012
Aug 10 21:37:16 kangoo weewx[4221]: te923: Failed attempt 1 of 5 to read
data: Bogus length during read: 128
Aug 10 21:37:20 kangoo weewx[4221]: te923: Failed attempt 2 of 5 to read
data: Timeout after 7 bytes
Aug 10 21:37:24 kangoo weewx[4221]: te923: Failed attempt 3 of 5 to read
data: Timeout after 14 bytes
Aug 10 21:37:28 kangoo weewx[4221]: te923: Failed attempt 4 of 5 to read
data: Timeout after 7 bytes
Aug 10 21:37:32 kangoo weewx[4221]: te923: Failed attempt 5 of 5 to read
data: Timeout after 14 bytes
Aug 10 21:37:35 kangoo weewx[4221]: engine: Unable to load driver: Read
failed after 5 tries
Aug 10 21:37:35 kangoo weewx[4221]: **** Exiting...
Aug 10 21:38:09 kangoo weewx[4264]: te923: driver version is 0.18rc1
Aug 10 21:38:09 kangoo weewx[4264]: te923: polling interval is 10
Aug 10 21:38:09 kangoo weewx[4264]: 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 10 21:38:09 kangoo weewx[4264]: te923: Found device on USB bus=001
device=012
Aug 10 21:38:10 kangoo weewx[4264]: te923: read: wrong number of bytes:
35 != 34
Aug 10 21:38:10 kangoo weewx[4264]: te923: Failed attempt 1 of 5 to read
data: Bad header byte: 0a != 5a
Aug 10 21:38:14 kangoo weewx[4264]: te923: Failed attempt 2 of 5 to read
data: Timeout after 7 bytes
Aug 10 21:38:18 kangoo weewx[4264]: te923: Failed attempt 3 of 5 to read
data: Timeout after 14 bytes
Aug 10 21:38:22 kangoo weewx[4264]: te923: Failed attempt 4 of 5 to read
data: Timeout after 14 bytes
Aug 10 21:38:26 kangoo weewx[4264]: te923: Failed attempt 5 of 5 to read
data: Timeout after 14 bytes
Aug 10 21:38:29 kangoo weewx[4264]: engine: Unable to load driver: Read
failed after 5 tries
Aug 10 21:38:29 kangoo weewx[4264]: **** Exiting...
_______________________________
The point is that in both trials at different points the read errors occur.
You see the driver version.
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.
