Jump to content

Simon

MVP 2014
  • Posts

    598
  • Joined

  • Last visited

  • Days Won

    36

Blog Comments posted by Simon

  1. I haven't done any relative comparison. However, the programmer who triggered this post has generously provided the following feedback:

    I found the amount of variables on the screen greatly effects the scan time, the page I was operating with a large amount of variables was making the cycle scan time slow to 4mS & when I changed screens (to one with only 4 variables) the scan time dropped to 1mS with no change to the plc code.

    This means that I can achieve my customers requested scan time of 1mS by just changing screens at the appropriate time with no issues.

    So the screen does affect scan time, but this suggests it relates more to the number of variables rather than the size of the screen. 4ms still looks pretty good for any general purpose PLC task.

  2. Hi Phil,

    Thanks for the post. This is of interest to me as I have come from a background of PC-based programming and it's always a brain-stretch to cross between that and PLC ladder logic.

    Whilst I generally agree with the usefulness of loops, my understanding of jumps in the Unitronics world is that they only jump forwards, not backwards. So the "jump back" actually causes the PLC to end the scan at the jump instruction and start the next scan at the jump label. So in the example of a loop, n interations would take n scans, and the other code in the program would not be executed during this time. If the code in the loop is short and the PLC is fast (like the V570) then this wil still execute reasonably well.

    This isn't confirmed knowledge, and the help file is not definitive on this point. A simple program could be used to test it, or if a Unitroics engineer is reading, it could be confirmed by revelation. Or maybe I am wrong all together...

×
×
  • Create New...