Fast vs. Very, Very Fast

Code Samples and Tips
2

I would like to think about this a bit, but in my typical fashion, I’m going to answer with a spur of the moment gut feeling first :-]

  1. Don’t do any timing assessments while in PAC Control debug. (I note your not really doing this, but want to make it clear).

  2. Pac Term comm loop time is worth keeping an eye on.

  3. Look in PAC Manager → Inspect. Scroll down almost to the bottom and look for:
    0xFFFF F030 0140 Analog & High Density Digital Scanner 10.340 msec/scan
    0xFFFF F030 0144 4-Channel Digital Scanner 6.387 msec/scan
    But don’t get hung up on these times, in other words, don’t take them as ‘law’, like the pac term comm loop time, they are part of the story, not THE story.

  4. Read my post here; Off delay on DI - #30 by Beno Consider using this code in one or more of your loops or chart (I don’t know the structure of your chart(s), so cant advise the best place to put that code, but you will soon figure out the loop times you want to monitor).

  5. Add delays in your chart - EVERY loop through each part of each chart should have a delay. Adding delays speeds things up. In your case, the delays can be anything from 1 to 10msec, but be sure and have them.

  6. Try and isolate the PAC and touch screen from the rest of your network traffic. (Think broadcast packet isolation).

  7. Read this slowly. Scan time explained - old forum post

  8. If you are brave, and your application has need for it, consider off loading some ‘Event Reaction’ code from your charts to the I/O.

1 Like