Linking of variables in control builder to graphics by lateBoundpropertyreference
I have 1600 varibales in control module and none of them have any object or faceplates.We need to indicate there status on screen by on/off status by changing color of a indicator.Now this work has to be done for each and every variable.Can i use lateBoundpropertyreference for this .If i can How?
I can combine 32 variables in a DINT variable and split them in my graphic display , and then i can copy paste whole graphic diplay and just change source DINT variable by reference tool,which will do most of my work and reduce amount of time.That option works for me.
Still i would like to know if late bound propertyreference option could work in this situation.
I would not use late binding if early is available. Late = slow.
Use late only when ref is unavailable at build stage, and then in limited amounts to not cause too much slowdown in callup performance.
I can't tell if typing & testing paths into LateBoundPropertyRef() calls will be faster than selecting them as early bound by browsing/editing.
User's guide and PG2 examples should be able to tell you how to get late binding to work.
No. late binding does not work that way.
To use display data from a Control Module Type ( or from any other type, like a function block ) you can either ....
- create your own graphic aspects or faceplates on the Object Type. This is a re-usable solution and is the recommended way.
- after you create an instance of your control module you can use the data directly in your graphics. You have to do this manually every time you use the control module in your code.
Late Binding is something quite different. Late Binding is used when a graphic aspect on an Object Type needs to get data from another object. Say you create a graphic aspect for a Tank Unit in your object type structure, but want to show some data from the feed pump in another Unit. The problem is your Tank Type can never know where the feed Pump actually exists untill the application is built. Late Binding allows your Tank Unit graphic to search for the actual Pump after the application code is created.
Try to avoid "packing" data just for your display. It is extra work for you and makes the graphic harder to understand by the next programmer. Allways try to display graphic data in the same form that it is used in your application program.