Hi,
In hindsight "the rs232 connection was lost" could have been descriptive of both events... ie, red (broken) connection icon on otmonitor or no msgs appearing in the log. Whilst trying to get this thing stable i'm working on a script to enter the data from PS=1 into mysql. Ofcourse when a PS=1 has been issued, no further communication comes from the gateway until a next command is issued. A pitfall i might have fallen into maybe once or twice.
That being said, the GW=R should have worked first time.
I wasn't aware TI defaulted to 1.. From the description on the website i'd think it defaults to 0.
The error01's started immediately after powercycling the usb port, so the connection to the gw was restored at that point and it accepted commands. However it issued error01's teh entire time. Not knowing what caused them led me to powercycle the GW (because GW=R didn't yield a working GW in my view as the error01's were still present), and then the boiler for the same reason. It the time i wasn't aware of the TI= settings..
Changing the Ref voltage would have been one of the later things i did, certainly after GW=R and even powercycling the gw.
The gateway is built without the max232 and connected directly to a rs232/usb converter which in turn is connected to a tp-link 702 which is in client bridge mode to my main wifi router. Powercycling the usb port on the tplink is accomplished by issuing: "
Code: Select all
echo 0 >/sys/class/gpio/gpio8/value && sleep 5 && echo 1 >/sys/class/gpio/gpio8/value && sleep 5"
on it.
I'll just leave it running for now, and i'll hold off on my dev'ing as not to interfere with the setup. I do really hope it's not the dallas (code) causing it, because love the outside temp on the thermostat
I could rig a direct connection to the gw with a netbook i have... Next time it all stops again, i'll hook that up.