Russ
Guest
R
I am working on a AB PLC5/40. There is this subroutine I was working on that used one shots to (ons) as part of the rung to mov values to words (4 words). This happens twice.. the first time I added another branch and included a Latched bit (to signify that the values had been moved so I could start a On Timer (TON)... well.. when I was testing it out the bit didn't latch..
Each time I move (MOV) the data values (it happens twice) I put the 4 mov statements in the same rung.. could that have something to do with why the bit didn't latch? The values changed, but the timer didn't initiate its sequence.. and the only conditional for the timer is the latched bit...
Since I've taken out the one shot (ONS) and replaced it with an XIO (for the timer done bit value) it works fine. So now that rung is true until the timer (which is supposed to initiate once the data moves) finishes its sequence. The latched bit goes high just like it is supposed to....
But I still don't understand why it didn't go high for the one shot (ONS)...
hmmmmmm....
Thanks,
Russ
Each time I move (MOV) the data values (it happens twice) I put the 4 mov statements in the same rung.. could that have something to do with why the bit didn't latch? The values changed, but the timer didn't initiate its sequence.. and the only conditional for the timer is the latched bit...
Since I've taken out the one shot (ONS) and replaced it with an XIO (for the timer done bit value) it works fine. So now that rung is true until the timer (which is supposed to initiate once the data moves) finishes its sequence. The latched bit goes high just like it is supposed to....
But I still don't understand why it didn't go high for the one shot (ONS)...
hmmmmmm....
Thanks,
Russ