A Variable may have a ValueRank = 0, -2 or -3. The spec defines these as:
ValueRank = 0: an array of any number of dimensions
ValueRank = -2: a scalar or an array of any number of dimensions
ValueRank = -3: a scalar or a 1 dimension array
If the existing value is NULL, then in all cases UAExpert will only allow entry of a scalar. For example, it allows a value of 123 to be written even if the value should be an array.
If the existing value is a scalar, then in all cases it will only allow entry of a scalar, even if the ValueRank supports arrays, such as -2. This occurs even if the ArrayDimensions attribute is set to a valid value, such as [2,3,4].
The expected behavior is for UAExpert to allow entry of all valid "shapes" (scalar, array, matrix) based on the ValueRank. For arrays, this includes a value of NULL or an empty array.
The UA Demo Server supports generic value ranks, but only under the "Dynamic\GenericValueRank" folder. Clients have write access to these, but the value is immediately overwritten by the server. There should be a "Static\GenericValueRank" folder so clients can verify they are writing correctly to the Node.
Problem writing values to Variables with generic value rank (0, -2, or -3)
Moderator: uaexpert
-
- Full Member
- Posts: 6
- Joined: 27 Jul 2020, 14:42
- Support Team
- Hero Member
- Posts: 3072
- Joined: 18 Mar 2011, 15:09
Re: Problem writing values to Variables with generic value rank (0, -2, or -3)
Hi,
there have been multiple changes to the widgeds that pop up for writing. Including changing the way the UaExperts tries to obtain the types and subtypes of objects that never delivered anything. There might be still some glitches, expecially for the optional parts. The goal is to guide the user as good as possible with the information we get out of the server.
We have added your request to the internal bug tracking system. The development team may contact you for more details.
there have been multiple changes to the widgeds that pop up for writing. Including changing the way the UaExperts tries to obtain the types and subtypes of objects that never delivered anything. There might be still some glitches, expecially for the optional parts. The goal is to guide the user as good as possible with the information we get out of the server.
We have added your request to the internal bug tracking system. The development team may contact you for more details.
Best regards
Unified Automation Support Team
Unified Automation Support Team