7/11/2019 10:27 AM | |
Joined: 6/14/2019 Last visit: 8/7/2021 Posts: 30 Rating: (1) |
Hi Huggy_d1,
The steps I have followed are: 1. Create UDT "Valve_udt". [snip] (Note I made a small mistake here, the State.Command elements should be type INT, but it doesn't matter for this demonstration.) 2. Add UDT to library. [snip] 3. Create DB of type UDT: "Valve_01_db". [snip] 4. Create faceplate "Valve_faceplate" with property of type UDT. [snip] 5. Assign an animation to an element of the property. [snip] 6. Create new HMI tag "Valve_01". In the "PLC tag" field, type "Valve_01_db" then click SPACE then ENTER. This sets the type to the UDT type. [snip] 7. Create a screen and place an instance of the faceplate on the screen. In the Properties -> Interface tab, in the Dynamization field select "Valve_01". [snip] 8. The faceplate instance is now pointing directly to the UDT instance DB in the PLC. Proven by testing the animation by manipulating the online value of the DB element in the PLC. - 1 [snip] - 2 [snip] So, I have proven that it is possible to point faceplate instances on a screen to instance DBs in the PLC without the use of any unnecessary intermediate mapping array.
Regards, Angus AttachmentScreenshots.zip (114 Downloads) |
Last edited by: Angus_ at: 07/11/2019 10:28:00Last edited by: Jen_Moderator at: 07/11/2019 12:52:01Removed links and added files as an attachment. |
|
This contribution was helpful to1 thankful Users |
Follow us on