Matthew, Thank you for your effort! It's still kinda weird though, and I'm still stuck.
As for the wiring: First I checked the modular cable with a network tester I have. All 6 pins are connected (but in reverse order on the other end, as is the color scheme in the RJ25 connector.) I looked inside the modulair to db9 converter. Inside only three wires are connected, to pin 2, 3 and 5. I had a look at the table here: http://www.peetbros.com/shop/custom.aspx?recid=6 It seems my pinout follows the DB-9 to TNC column. I don't quite understand what is meant by the difference between DB-9 to computer and DB9 to TNC colums, to be honest. Input and output are reversed, but why is it different for a terminal node controller? Peet Bros seems to sell the same item for both purposes: http://www.peetbros.com/shop/item.aspx?itemid=64 However I connected everything again, and ran your version 0.17 directly. On screen no output is shown, and in the logs only: ultimeter: open serial port /dev/ttyS0 as before. No mentioning of write timeouts. Then I pulled the modular cable out of the DB9 plug, while the python script was still running and to my surprise this showed up: 1484485968.77 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 this is just a part of it. Afterwards it showed only timestamps again: 1484486084.15 1484486087.15 1484486090.15 1484486093.16 So to put it all together, The time stamps are coming from the script itself I assume, as they show up when the station isn't even connected. When disconnecting the display from my computer, some buffer seems to be dumped or something. There may some wiring problem? should I follow the DB9 to computer scheme? (sounds logical). Op zaterdag 14 januari 2017 15:54:36 UTC+1 schreef mwall: > > just for fun, try ultimeter-0.17rc1.py > > it has write timeouts, so if the driver is unable to write (but able to > read) this should be reflected in the log > > > -- 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.
