This is the latest version... Thermostat initialization works fine (at least at my place).
The changes are:
<UL TYPE=SQUARE>
<LI>I found that the X10 packet received after a collision is NOT the packet which collided, as I first thought, but the next good packet. The previous version of the plugin would ignore this packet.
<LI>Also, the processing for X10 status was not working correctly, the acknowledge from the thermostat after a command was received (J Status On) was not being passed to the thermostat plugin.
<LI>I implemented the LynX-10 Xon/Xoff commands; when an Xoff is received, transmission of new packets stops until an Xon is received.
<LI>I've added the LynX-10 statistics to the options window, as well as the LynX-10 receive threshold adjustment. (This is the number of characters allowed in the LynX-10 input buffer before it drops CTS.) The LynX-10 statistics are uploaded when the window is opened.
<LI>All changed items in the options window take effect when 'OK' is clicked, except for baud rate change, which requires a restart.[/list]
The changes are:
<UL TYPE=SQUARE>
<LI>I found that the X10 packet received after a collision is NOT the packet which collided, as I first thought, but the next good packet. The previous version of the plugin would ignore this packet.
<LI>Also, the processing for X10 status was not working correctly, the acknowledge from the thermostat after a command was received (J Status On) was not being passed to the thermostat plugin.
<LI>I implemented the LynX-10 Xon/Xoff commands; when an Xoff is received, transmission of new packets stops until an Xon is received.
<LI>I've added the LynX-10 statistics to the options window, as well as the LynX-10 receive threshold adjustment. (This is the number of characters allowed in the LynX-10 input buffer before it drops CTS.) The LynX-10 statistics are uploaded when the window is opened.
<LI>All changed items in the options window take effect when 'OK' is clicked, except for baud rate change, which requires a restart.[/list]
Comment