Renewable Energy and Sustainability Forum
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Anyone wishing to register as a new member on the forum is strongly recommended to use a "proper" email address. Following continuous spam/hack attempts on the forum, "disposable" email addresses like Gmail, Yahoo and Hotmail tend to be viewed with suspicion, and the application rejected if there is any doubt whatsoever
Recent Articles: Navitron Partners With Solax to Help Create A More Sustainable Future | Navitron Calls for Increased Carbon Footprint Reduction In Light of Earth Overshoot Day | A plea from The David School - Issue 18
   Home   Help Search Login Register  
Pages: [1]   Go Down
Author Topic: TDC3-e Protocol Document  (Read 6905 times)
Offline Offline

Posts: 29

« on: September 10, 2016, 06:36:43 PM »

Long time since I've been here. Does anyone have the Sorel Protocol document used for the TDC3-e or know where I can download it? I've just needed to amend my automation software and I have no idea where I got my information from to extract the data from the TDC3-e. Probably from the big thread on the TDC3 started by Ivan. But it refers to a protocol document which I would like to get my hands on.

Anyway this might also be of interest as I see a number of other threads regarding the TDC3-e.

I have a TDC3-e and it seems I'm experiencing what other people have experienced and that is lock ups. What seems to happen is that I assume the Sorel part of the device locks up for ever. The Lantronix - the Xport03 seems to work fine and even sending the RS command to reboot the device doesn't clear the issue. Presumably this reboot is just  the Lantronix bit. So anyone who can't read data you might need to power it off and on which might not be straight forward. Fortunately my whole solar system runs from a 13 amp mains socket so I switch it off ans on and it works. Whilst this lock up happened once every month(ish) it now happens once or twice a day. Not very good for home automation and data logging (why do so many problems like this occur in so many devices. Just cr*p testing).

Anyway I write my own software so my solution is to use an X10 (Actually PLBus) device to power off for a few seconds before powering on. I have a Java program that queries all my devices from one wire devices to X10s ,cameras, burglar alarm etc so I simply amended it and plugged a spare x10 device in.

So now my software runs for weeks (perhaps months or years) without issue..until we have a power cut.

Pages: [1]   Go Up
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines
SMFAds for Free Forums
Simple Audio Video Embedder
Valid XHTML 1.0! Valid CSS!