how to open controller performance application ?

Iwant to see system expansion data including :Control expansion  ,Comm expansion ,Memory Expansion 

which is show inside controller performance application where can i open this?

4 Replies

  • In DeltaV Diagnostics, please right click on the controller in question and click on "Time Utilization Chart" and in the Controller Performance window that pops up click on the System Expansion tab.
  • In reply to Rune Reppenhagen:

    I have one question how is possible to integrate the parameters from this Time utilization Chart from any controller through the deltav Operate ,is ther any way to create a datalink to this parameters sucha as control expansion ,comm expansion and memory expasion?

    indeed ,is there any way to do that ?

  • In reply to ManuelEscobedo:

    V12.3 and V13.3 hotfixes are available for SX, SZ, and SQ controllers to expose the expansion parameters. The parameters can then be accessed via External Reference or Calc block and subsequently historized or displayed to the operator. Refer to KBA AP-0900-0129 or your Local Business Partner for further information.
  • The parameter paths to these values are:
    - NODENAME/CONTROL_EXPSN
    - NODENAME/COMMS_EXPSN
    - NODENAME/MEM_EXPSN

    The KBA mentions these values must be read by a module before they can be historized. This is because DeltaV Explorer does not recognize these runtime diagnostic parameters, so you cannot add them to a controller's History collection (but you can add the PERF_INDEX. The KBA does not mention that these parameters can only be read from a workstation, The parameters can be referenced by a module assigned to the controller or to a workstation.  You can also place these in a datalink in a faceplate, Detail display or process graphic. If you want to historize them, you have to build a module assigned to an App Station.

    If you do build a diagnostic module, its no big deal to simply assign these to the HIstorian App Station, and then you can configure any parameter to be historized. I'd say this is better than having a local module in the controller and another in an App station for those parameters the controller cannot read. There is no real advantage to running a diagnostic module in the controller.


    When I tested this earlier, I had a typo in my $ref path in the module assigned to a controller.  This was pointed out by a colleague in Austin.  (Thanks).  Good news is you can have this in a module assigned to the controller or a workstation. 

    Andre Dicaire