We have come across this in WinCC OA version 3.12 and in 3.14.
WARNING, 53, Illegal function call, DYNTEXT_VAR, operator
WARNING, 53, Illegal function call, DYNTEXT_VAR, operator
Search
- chris@blue-catalyst.co.uk
- Posts: 32
- Joined: Tue Jun 11, 2013 9:27 am
Re: WARNING, 53, Illegal function call, DYNTEXT_VAR, operator
I would like to know how to reproduce this error.
The error comes when the content of the cells in the table are of type DYNTEXT_VAR (dyn_string in CTRL), which can not be sorted since the "less than" operator is not implemented.
But how does your cells get a content of a dyn_string as value ?
In the std. AES, that should not happen. As you might know you can pass a dyn_string as a cell "value", but in this case the table assumes that the dyn_string contains 1:Value 2:backCol 3:foreCol and what is being sorted and stored as the value is just the value itself (the colors are stored differently).
Did you modify the AES or scripts thereof or is this the std. unmodified thingy ?
The error comes when the content of the cells in the table are of type DYNTEXT_VAR (dyn_string in CTRL), which can not be sorted since the "less than" operator is not implemented.
But how does your cells get a content of a dyn_string as value ?
In the std. AES, that should not happen. As you might know you can pass a dyn_string as a cell "value", but in this case the table assumes that the dyn_string contains 1:Value 2:backCol 3:foreCol and what is being sorted and stored as the value is just the value itself (the colors are stored differently).
Did you modify the AES or scripts thereof or is this the std. unmodified thingy ?
Re: WARNING, 53, Illegal function call, DYNTEXT_VAR, operator
Hello,
I've made a test with modified AES settings. The error did not occur and the dyn_string was displayed as string.
Why have you modified the format for this column?
What is needed to get this log message?
Best Regards
Leopold Knipp
Senior Support Specialist
I've made a test with modified AES settings. The error did not occur and the dyn_string was displayed as string.
Why have you modified the format for this column?
What is needed to get this log message?
Best Regards
Leopold Knipp
Senior Support Specialist
- chris@blue-catalyst.co.uk
- Posts: 32
- Joined: Tue Jun 11, 2013 9:27 am
Re: WARNING, 53, Illegal function call, DYNTEXT_VAR, operator
We have seen it when using two _add_values, we send in string values (not dyn_strings) into the _add_value_1 and _add_value_2 fields when the alarm triggers.
Re: WARNING, 53, Illegal function call, DYNTEXT_VAR, operator
Thanks Chris Fairless, I was just struggling with this problem also and '%s' solved the issue... Thanks!