Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
This is working very well, but now i would like to make another dialog which uses multiple motor DUT's, the problem is only the first variable declared after {attribute 'VAR_IN_OUT_AS_POINTER'} is being treated as such...
the other variables are not updated cyclically.
I tried to put {attribute 'VAR_IN_OUT_AS_POINTER'} before each variable declaration but then the visualization runtime crashes as soon as i open the popup (dialog).
Is there a solution to this problem? Is it possible at all?
Hello all,
In a WebVisu i am using a dialog as motor popup with the MTR_HMI DUT as VAR_IN_OUT using {attribute 'VAR_IN_OUT_AS_POINTER'}.
as described here: https://content.helpme-codesys.com/en/CODESYS%20Visualization/_visu_pragma_var_in_out_as_pointer.html
This is working very well, but now i would like to make another dialog which uses multiple motor DUT's, the problem is only the first variable declared after {attribute 'VAR_IN_OUT_AS_POINTER'} is being treated as such...
the other variables are not updated cyclically.
I tried to put {attribute 'VAR_IN_OUT_AS_POINTER'} before each variable declaration but then the visualization runtime crashes as soon as i open the popup (dialog).
Is there a solution to this problem? Is it possible at all?
Thanks!
System Config:
- RevolutionPi controller with Codesys Runtime Package 4.4.0.0 (Multicore)
- Codesys V3.5 SP18 + (64-bit)
- Codesys Visualization 4.1.0.0
Issue is gone!
after a Build -> Clean all and controller power cycle, the runtime is not crashing anymore.
Everything works fine when putting {attribute 'VAR_IN_OUT_AS_POINTER'} before each variable declaration
(see Example2 in previous post)
BR,
Rinie