10/18/2022 3:15 PM | |
Joined: 9/10/2019 Last visit: 10/16/2023 Posts: 7 Rating: (0) |
Dear Forum Experts, I'm creating this topic in regards to APL scripts for the PIDConS faceplate, using PCS 7 V9.0 SP3 UC03. We are developing a custom faceplate based on the PIDConS and need to modify I/O objects in the 'limits' tab in faceplate "@PG_PIDConS_Limit". When the PIDConS block input "PV_AL_En" is set in the CFC the csoIOAnaAL object is set visible in OS runtime and invisible when PV_AL_En =0. I need to understand which script in the APL_ANALOG_OP_DISPLAY object "csoIOAnaAL" enables the propriety Display(Yes/No) of the object depending on the CFC Function Block input "PV_AL_En"? See attached file for details. Thank you.
AttachmentAPL_ANALOG_OP_DISPLAY.doc (314 Downloads) |
10/20/2022 7:03 AM | |
Joined: 3/14/2008 Last visit: 4/26/2024 Posts: 2066 Rating: (928)
|
Hi, In the APL_ANALOG_OP_DISPLAY is the following: Under Properties->Links there is an attribute called LinkTag1. Connected to that is Status2. Under the attribute there is another attribute called BitIndex1, which is set at a specific value. For AL its set to 12. So, this means that in the PIDConS block, Status2.Bit12 is checked. Bit12 means: "PV_AL_En OR Feature.Bit31". In the faceplate under Events->Links->LinkTag1 is a script on "Change". The script checks the value of Status.bit12 and if set to TRUE, the object is set visible. Please notice that LinkTag1 value is set default to -1 and tag: .Status2 is connected. What happens is that during opening of the faceplate, the value at LinkTag1 changes because it's default set to -1. This will trigger the Event on LinkTag1 where the script checks value Status.bit12. PS: There is a feature bit 31 which makes the limit visible regardless if AL_En is set. So you can view the value, however editing is not allowed. |
If I could help you, you can use the RATE button. Thank you. |
|
This contribution was helpful to2 thankful Users |
Follow us on