Program cycle

CX-One, CX programmer, NTST, Syswin ....
Post Reply
ghid
Posts: 10
Joined: Sat Apr 27, 2013 11:01 am

Program cycle

Post by ghid » Sun Oct 27, 2013 9:31 pm

Hi,

I know that in a program cycle, first are readed the inputs, in the order that are situated in the program, and then are actuated the outputs.

On the example bellow I have made a simulation , H10.0 will be high when 0.02 input will be set to high and just until at the end of the cycle ( DIFU ). When I have setted 0.02 input to high, H5.04 was ghanged to high. But why? because H10.0 should be high just until the end of the cycle, and H5.04 never should go high but it goes. Why? Because at the start of a new cycle the H10.0 shoul be low.

I don't understand this thing that first are readed the inputs in the written order and at the last of the cycle are actuated the output. Please enlight me.

Thank you.

Image

prushmere
Posts: 40
Joined: Fri May 07, 2010 8:44 am
Location: UK

Re: Program cycle

Post by prushmere » Mon Nov 18, 2013 10:26 am

The DIFU (a one-shot) output address will stay true for one FULL program scan. When rung 2 is processed H10.00 is still high, H10.00 is not set false until rung 3 is processed again.

Post Reply