I suspect that adding temperature controller support to the remote sever is not
a quick "drop in a few lines of code" sort of thing. The current server
program is basically just reading bytes from the TCP connection and shipping
the out blindly to the Tbolt. It does no TSIP packet parsing, etc.
To add the temp control stuff, it would need to be able to parse some kind of
message from the Heather client program to control the fan/heater. The way
the temperature control program usually works is by pulse width modulating a
fan to mix cooler room air with the warmer air in a box (you can also do active
heating and/or cooling).
It uses the serial port modem control signals to do the PWM. The PWM is
calculated to millisecond values, but the actual output resolution depends
upon the system timer. Typically it runs around 10-20 msecs.
I suspect that trying to emulate the PWM via modem control signals over the net
would have problems. What would work better is for Heather to send a TSIP
message with the required PWM duty cycles. The server would have to parse that
message and do the PWM... not too much of a task.
An even better solution would be for the server to actually parse the TSIP
message from the Tbolt that has the temperature reading and for the server to
do the PID algorithm and temperature control PWM. The temp control code is not
that long or complicated. This method gets net delays, etc out of the
equation. It does add the complexity of how to configure the PID parameters on
the server.
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141665/direct/01/
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
