I tried tvm's solution in SP16 which comes with stateless visualizations (whatever that means in detail). So, the referenced data will be updated in each cycle. Only problem now is that the MeterInterface:= AllMeters[SelectedMeter]; has to be called at each cycle whether the SelectedMeter value changed or not, because somewhere the old value of MeterInterface gets written back to it. I guess somewhere in the codesys visaulization code the value of the initial value of MeterInterface is stored and...
I tried tvm's solution this in SP16 which comes with stateless visualizations (whatever that means in detail). So, the referenced data will be updated in each cycle. Only problem now is that the MeterInterface:= AllMeters[SelectedMeter]; has to be called at each cycle whether the SelectedMeter value changed or not, because somewhere the old value of MeterInterface gets written back to it. I guess somewhere in the codesys visaulization code the value of the initial value of MeterInterface is stored...
I tried tvm's solution this in SP16 which comes with stateless visualizations (whatever that means in detail). So, the referenced data will be updated in each cycle. Only problem now is that the MeterInterface:= AllMeters[SelectedMeter]; has to be called at each cycle whether the SelectedMeter value changed or not, because somewhere the old value of MeterInterface gets written back to it. I guess somewhere in the codesys visaulization code the value of the initial value od MeterInterface is stored...
I tried tvm's solution this in SP16 which comes with stateless visualizations (whatever that means in detail). So, the referenced data will be updated in each cycle. Only problem now is that the MeterInterface:= AllMeters[SelectedMeter]; has to be called at each cycle whether the SelectedMeter value changed or not, because somewhere the old value of MeterInterface gets written back to is. I guess somewhere in the codesys visaulization code the value of the initial value od MeterInterface is stored...
Now, four years later... Is it now possible? I do need exactly this functionality - change the visualization reference at runtime by programm code.
Now, four years later... Is it now possible? I do need exactly this functionality - change the visualization reference at runtime.
I created a simple function block for a green lamp and red lamp: FUNCTION_BLOCK GreenLamp VAR LampActive : BOOL; END_VAR (Red lamp is the same, just the different name) And I created a visualization with just one lamp called "GreenLamp" and another one called "RedLamp" with the following interface configuration: VAR_IN_OUT Data : GreenLamp; END_VAR (Red lamp is the same, just the different type name) In my main program I instantiated two instances of the green and one instance of the red lamp: PROGRAM...
Lets say I have a navigation bar with three buttons where I want to change to a different visualization when the user clicks on one of the buttons. Each button/visualization could represent a settings visualization where the user can modify machine parameters. As I want to use object oriented programming I created different visualizations for each machine type. In the interface editor of each visualization I defined a VAR_IN_OUT custom variable with the custom data type of the machine like: Machine...