valadm tomasyna naboth
Rodney Liuzzo
The element serves as a frame in which to display one or more already existing visualizations. You get a structured user interface. The size of the frame can be fixed or scaled. The display area of the referenced visualization then adapts itself to the frame size.
The position defines the location and size of the element in the visualization window. These are based on the Cartesian coordinate system. The origin is located at the upper left corner of the window. The positive horizontal x-axis runs to the right. The positive vertical y-axis runs downwards.
The properties contains character strings for labeling the element. The character string can also contain a placeholder with a format definition. In runtime mode, the placeholder is replaced by the current value in the specified format.
The properties contain IEC variables for controlling the position of the element dynamically. The reference point is the upper left corner of the element. In runtime mode, the entire element is moved.
Note: Specify a variable for the mouse events Tap or Toggle in the input configuration of the element. Only then is the placeholder set. If you configure a variable in both Toggle and Tap, then the variable specified in Tap is used.
The variable controls the switching of the referenced visualizations. This variable indexes one of the referenced frame visualizations and this is displayed in the frame. When the value of the variable changes, it switches to the recently indexed visualization.
Note: This variant of switching applies to the current client only, and therefore only on one display variant. That is the display variant where the value change was triggered (for example, by means of user input).
Function: The tab provides an editor for configuring the frame interface of the visualization opened below. This editor is used to define properties for the frame interface and then configure each in detail. If the visualization is referenced in a superordinate visualization with a frame, then the actual values can be configured there by means of the properties configured here, which act as transfer parameters. The frame with the referenced visualization then presents itself just like a visualization element and is supported by the same editors.
When a visualization with a frame interface is referenced by another visualization by means of a frame element, it brings with it the properties displayed here in the tree view. In the referencing visualization, it then presents itself like an ordinary visualization element: with properties categorized and arranged hierarchically. And with editors to help you specify the value with editors that match the data type.
The frame interface of Gauge hat the following properties as parameters: Scaling type, Value, Min, Max, Colors, Font, Image, and Label. In addition, the default Position, Center, Absolute movement, and State variables properties can be parameterized.
The CODESYS Group is the manufacturer of CODESYS, the leading hardware-independent IEC 61131-3 automation software for developing and engineering controller applications.
CODESYS is a registered trademark.
I want to change the registered visualisations of a frame by programm. Is this possible? And if so, how can I do this? Is the FrameManager a starting point for this? The documentation is a little sparse on these topics.
Auto It, great! I use the similar things to automate what can't be automated, but with codesys I didn't loose hope yet...
Digging into the problem, I was able to show visu in empty frame from debug mode. And so, I believe it is possible to do this from program (working on it now).
The other problem I see here is following, when we manually configure References for frame, codesys generates instaces for each visu in each frame, and puts them to the instance of parent visu, if we don't configure References, we can programmatically (i believe) switch frame to instanse of existing visu, but there would be only one instance of that visu. Then it would be hard or impossible to show different data in the same visu which is displayed in different frames (this is my goal).
Victor Kulikov hat geschrieben:
Marcel, it would be nice if I could use the type "TheNameOfMyVisu__vis" in declaration part of POU, I think it would solve my problem, but because of "__" it gets red and doesn't compile.
If you are a developer or close to them, is there any chance you could provide any docs on internal structure of visual entities and how do they interact with eachother and other parts of the program?
Imagine, I have 50 different types of entities, each entity is defined by FB and has corresponding visu.
I have hords of instances of such FBs, and I want to show about 16 visus attached to corresponding FBs on one screen. I don't want to configure 50+ references for each frame manually and want to do this programmatically.
When I open same visu in 2 frames and try to change color, or something in one frame, it changes simultaneously in both frames. This is because actually it is 2 views of the same instance of visu. The only way I see, is to create more instances... I see, codesys creates a TYPE for each visu, and names it like: "TheNameOfMyVisu__vis". I believe, if I could instantiate this type in GVL or some POU, I could use those different instances of visu in different frames and then attach different data through their VAR's.
The problem is I can't use "TheNameOfMyVisu__vis" type in geclaration. I suspect, the only problem here is "" in the name of type. It is somehow prohibited to write "" in both declaration and program parts of ST editor. Any word which contains "__" gets red in editor.
Visualizations can be nested at any depth by means of Frame . In order to use the Switch to any visualization frame selection type without any problems, a Frame must not contain more than 21 referenced visualizations.
In the case of the Frame element, you can freely program which of the visualizations is displayed at which time. One option is to use the switch frame variable of the Frame element, which automatically triggers a switch according to its value. You can also program additional controls which, after user input, trigger input actions that result in switching a visualization.
Now the Frame element references the three selected visualizations. The references (1) are listed in the References property in the element properties of the Frame element. In addition to the visualization name, the corresponding index value (2) is also displayed.
Note: You can open the dialog when you click the Configure button in the value field of the References property. See (3). You can influence the index by means of the visualization order in the Selected Visualizations list.
The visualization starts. One of the referenced visualizations is running in the frame. When you click an unselected option of the Radio Buttons element, the visualization switches the contents in the frame to the desired visualization.
In the main visualization, the Frame element displays one of the frame visualizations at runtime. The user can use buttons to control the display in the frame. The user input triggers the Switch frame visualization input action.
Note: You can open the dialog independently when you click the Configure button in the value field of the References property. See (3). You can influence the index by means of the visualization order in the Selected Visualizations list.
The visualization starts. One of the referenced visualizations is running in the frame. When you click one of the buttons, the visualization switches the contents in the frame to the respective visualization.
For the Tabs, the navigation of the referenced visualizations is provided automatically. The first of the referenced visualizations is in the foreground, while the others are hidden "behind it". The user can navigate between them by means of the tabs which are provided automatically.
Now the Tabs element references the three selected visualizations. The references (1) are listed in the References property in the element properties of the Frame element. In addition to the visualization name, the corresponding index value (2) is also displayed.
Note: You can open the dialog Frame Configuration dialog independently when you click the Configure button in the value field of the References property. See (3). You can influence the index by means of the visualization order in the Selected Visualizations list.
Hello,
i'm nearly done with my Webvisu for the shutters but a strange behavior appeared.
I'm using Frames to switch the different pages (Light,Shutters,Mainmenue,..)
When i switch from "Main" to "Light" it is a perfect fast transition.
But when i switch between the two shutter visu's a very short moment the Background is white.
Sorry, I can't explain any better.
Does anyone have a clue what i have done wrong?
I mean when i switch between two frames in the Visu. But the short moment of white background happens only when i'm using the Visu in a Browser (no matter which Browser) when i switch between the frames in the Codesys Programm (the Tab with the Visu when im online) it works perfekt.
Programming System is updated every 200ms only, so probably you can't See the white screen there. Browser normally update faster, depents to the settings of webvisu and tasks. Do you have a big picture as Background, that has to be downloaded from the Webserver, which is different from shutter to shutter? Whats your plc? A Raspberry Pi?
c01484d022