Hmmmmm....
I was just playing around with the simulator in PicoSoft. I wrote a quick little program for a 2 furnace setup that
should have worked...
| T_STAT_1 INHIBIT
|---] [---------]/[-------+-----(SET) FURNACE_1
| |
| +-----(SET) INHIBIT
| T-STAT_1
|---]/[-------------------------(RST) FURNACE_1
|
| T-STAT_2 INHIBIT
|---] [---------]/[-------+-----(SET) FURNACE_2
| |
| +-----(SET) INHIBIT
| T-STAT_2
|---]/[-------------------------(RST) FURNACE_2
|
| INHIBIT +--------+
|---] [-------------------------| TIM_1 |
| | 5 Sec. |
| +--------+
| TIM_1
|---] [-------------------------(RST) INHIBIT
If you turn on T-STAT_1, the INHIBIT turns on and the timer starts timing. While the timer's running, turning on T-STAT_2 won't start FURNACE_2 because INHIBIT is on.
Okay, that seems to work as expected. BUT...
If, while the timer's timing, you turn off T-STAT_1, then turn on BOTH T-STATs,
BOTH FURNACEs turn on once the timer expires!...
It seems that the status of INHIBIT is
NOT updated immediately. The status only seems to update on the
FOLLOWING scan!
Is this just the simulator, or does the Pico operate this way? Did I overlook something?...
Attached is a copy of the program if any one wants to investigate.
beerchug
-Eric