Mode Parameter Type Actual Field

Hello,

I was testing some logic and wanted to be able to simulate switching modes.  Instead of implementing the corresponding analog control function block, I just used a parameter of type Mode.  I was experimenting with confirming a mode, and wanted to use the "Actual" field, but it is always blank.  I've tried using both input and output parameters, and they both have blank "Actual" fields.  I read a post about exposing the mode parameter of a Device Control (DC) block as an output and then the "Actual" field is populated.  I have not tried that, because I was hoping to just use a parameter.  I did try wiring an input parameter to an output parameter, but both parameters still have a blank "Actual" field.  Why is the "Actual" field not populating, and/or what is the best method to test Mode.Target versus Mode.Actual?

Thanks.

  • Using the parameter by itself will not populate the Actual field when you change the Target, but you can use a Calc or Act block to write to the Actual field.

    For example, if the parameter is named MODE:

    '^/MODE.ACTUAL' := CAS;

    Or

    '^/MODE.ACTUAL' := '^/MODE.TARGET;'
  • Here are the numeric values for the modes. These were driven by foundation fieldbus specification and note that IMAN and LO aren't valid Target modes

    Mode - Target - Actual
    OOS - 1 - 1
    IMAN - n/a - 2
    LO - n/a - 4
    MAN - 8 - 8
    AUTO - 16 - 16
    CAS - 48 - 32
    RCAS - 80 - 64
    ROUT - 144 - 128

  • In reply to KeithStThomas:

    Ah. For testing purposes this will work nicely, because I will have control over when the MODE.ACTUAL changes. This can be good to simulate problems with equipment not making the TARGET, and making sure my logic/graphics can handle those problems. Thank you.
  • In reply to Matt Stoner:

    Thank you. This is good to know.