Hello Community,
I am using VIMII to pass datasets from a third-party PLC to DeltaV via the Modbus TCP/IP. Each of the many solenoid valves with their limit switches has three states - passed as three bits: open/closed, failed to open, and failed to close. Each bit is configured as a class-based DI_SOFT_52 DeltaV PCSD module.
Now, I would like to add the valve dynamo on the process graphic, but am uneasy about which dynamo would accomplish the task. When selecting an available dynamo from the library, I can only specify one path/name, i.e. the DI_SOFT_52 module for the open/closed state. I am contemplating stacking three dynamos on top of each other and configuring each of the three animations in such way that only the active state would be visible. However, that seems crude. Can anyone suggest a more elegant solution to this?
I would suggest (EDC if v13):
Otherwise you will have to do like you indicated or create a custom dynamo for your inputs (which scares most people to death :D).
In reply to Matt Stoner:
In reply to dmitriy sagadiev:
I built a PCSD discrete valve control module based on the _V11_IP_SOFT_52 in ver. 11.3.1 following the guidelines above. Please refer to the attached control studio capture. However, all modules in this class are in MODBAD alarms with undefined field values and “unresolved reference” MSTATUS.
I routed the close/open (0/1) bit via EXT_IN_D1. The CAS_IN_D parameter of the DC_CTRL function block outputs the UNDEFINED 255. I reckon that the operating parameter REQ_SP writes 255 to the DC_CTRL module and causing problems.
In SIMULATE, state of the module changes from 0 = CLOSED to 1 = OPEN; however, when I force the bit via EXT_IN_D1 to 0 (normally closed), the PV_D is UNDEFINED and when EXT_IN_D1 equals 1, PV_D is CLOSED. In both cases OUT_D is zero.
I would be very happy to gather your input on the subject if you have time to review.
The MODBAD is being caused by the Unresolved Reference(s). These can be found by going to Diagnostics, finding the module (Controller Assigned/Assigned Modules/Module), right click and select Display Unresolved References. Fix those issues and MODBAD should go away.
The EXT_IN_D1 issue is because the DC1/STATE_MASKS parameter is configured to have 2 inputs and you only have 1 close limit switch. Change the 2nd Column for the inputs to be don't care (Grey out check box). If EXT_IN_D1 isn't a close limit switch you will need to change Column 1 to be open limit switch (See below).
Thank you Matt. You are a rockstar! The unresolved messages happened to be two alarms I disabled: BYPASS_ON and INTERLOCK_ALM. I couldn't removed the two from the module in DeltaV Explorer, but successfully deleted them in Control Studio.