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]. For more options, visit https://groups.google.com/d/optout.
