PeterW
Member
Not used proworx for awhile and just trying to reacquaint myself with its little oddities.
I'm working with an existing system which has multiple segments scheduled, all set to continuous, but only the first few actually contain code.
I was a little confused why this was done and then realised that the number of segments scheduled matched the number of drops for I/O points.
So every Drop has a segment scheduled where it is the Drop in and drop out. Even where the drop point only has input cards, its included on drop in and drop out.
I'm sure this is not needed as I thought (from past history) that the I/O is updated at the start and end of the program, just like most other PLC's. I thought the drop in and drop out fields in the schedular were if you needed to specifically update a drop during the program, and then it could be different on the in and out depending on where the inputs and outputs are located.
In most cases I thought the drop in and drop out would be left blank....
Am I correct or am I going crazy? .... Both are possible.
I'm working with an existing system which has multiple segments scheduled, all set to continuous, but only the first few actually contain code.
I was a little confused why this was done and then realised that the number of segments scheduled matched the number of drops for I/O points.
So every Drop has a segment scheduled where it is the Drop in and drop out. Even where the drop point only has input cards, its included on drop in and drop out.
I'm sure this is not needed as I thought (from past history) that the I/O is updated at the start and end of the program, just like most other PLC's. I thought the drop in and drop out fields in the schedular were if you needed to specifically update a drop during the program, and then it could be different on the in and out depending on where the inputs and outputs are located.
In most cases I thought the drop in and drop out would be left blank....
Am I correct or am I going crazy? .... Both are possible.