Controller performance metrics: parameters to trend and examine, what are most critical?

While looking into why a several EMs on a SX controller aren't running at the configured scan rate, fell into a rabbit hole.

In the past, have trended controller parameters such as HPCTONTIME.CV, COMM/AWSNT.CV, and FRETIM to get perspective.

Of more recent times, Diagnostics' Performance Index Parameter ostensibly aggregates the most salient metric parameters into a single value from 1 to 5. 

This SX controller has 50% of modules running above configured scan rate and yet FRETIME, H, M, and LPCTONTIME all at 100% - and yet Performance Index Parameter = 4 (Good)

How does one reconcile these metrics and yet consequential module scan time slippage?

1 Reply

  • Newer controller software went away from FRETIM and use CONTROL_INDEX and some other individual parameters:
    COMMS_EXPSN - Communication Expansion
    CONTROL_EXPSN - Control Expansion
    MEM_EXPSN - Memory Expansion

    These can be trended to help evaluate a little bit but this sounds like a problem and you should log a call if modules are slipping but the %On Time isn't saying they are slipping...