View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010329 | 10000-003: Address Space | Spec | public | 2025-05-14 05:58 | 2025-09-25 12:03 |
| Reporter | Hock, Christian | Assigned To | Jeff Harding | ||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Target Version | 1.05.06 | Fixed in Version | 1.05.06 | ||
| Summary | 0010329: Asking for an optional Property 'MinArrayLength' | ||||
| Description | Today, the optional ‘MaxArrayLength’ property can be applied to DataVariables to specify the size of the values (already in the NodeSet). Some systems (especially older ones) are not able to handle the OPC UA way from ‘0’ length to ‘MaxArrayLength’. This means that the ‘MaxArrayLength’ is also the ‘MinArrayLength’ that makes e.g. a write operation successful. It would be good to be able to reflect this in the NodeSet in a standardized way. | ||||
| Tags | No tags attached. | ||||
| Commit Version | 1.05.06 RC1 | ||||
| Fix Due Date | 2025-06-01 | ||||
| has duplicate | 0010501 | closed | Jeff Harding | 10000-005: Information Model | Question about MinArrayLength |
|
|
Added new Optional Property MinArrayLength to ServerCapabilitiesType. |
|
|
Agreed to changes in Virtual F2F. |
|
|
Wolfgang (RC Review comment): Matthias: We should move this to Part 3 and add the property to the Variable node class |
|
|
It was the intention to have this on the DataVariable 'https://reference.opcfoundation.org/Core/Part3/v105/docs/5.6.4'. |
|
|
This was incorrectly assigned to Part 5. Now moved to Part 3 to add a Property to the Variable Node class. |
|
|
The intention is to allow the Server to define an array of fixed size that a Client can't change that size. |
|
|
Added new Variable NodeClass optional property 'FixedSizeArray'. |
|
|
Agreed to changes edited in F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-14 05:58 | Hock, Christian | New Issue | |
| 2025-05-20 15:22 | Jim Luth | Assigned To | => Jeff Harding |
| 2025-05-20 15:22 | Jim Luth | Status | new => assigned |
| 2025-05-20 15:22 | Jim Luth | Commit Version | => 1.05.06 RC1 |
| 2025-05-20 15:22 | Jim Luth | Fix Due Date | => 2025-06-01 |
| 2025-05-29 19:03 | Jeff Harding | Status | assigned => resolved |
| 2025-05-29 19:03 | Jeff Harding | Resolution | open => fixed |
| 2025-05-29 19:03 | Jeff Harding | Fixed in Version | => 1.05.06 RC1 |
| 2025-05-29 19:03 | Jeff Harding | Note Added: 0022808 | |
| 2025-06-05 17:18 | Jim Luth | Status | resolved => closed |
| 2025-06-05 17:18 | Jim Luth | Note Added: 0022972 | |
| 2025-09-16 14:18 | Matthias Damm | Status | closed => feedback |
| 2025-09-16 14:18 | Matthias Damm | Resolution | fixed => reopened |
| 2025-09-16 14:18 | Matthias Damm | Note Added: 0023296 | |
| 2025-09-17 15:29 | Hock, Christian | Note Added: 0023298 | |
| 2025-09-17 15:29 | Hock, Christian | Status | feedback => assigned |
| 2025-09-24 07:13 | Jeff Harding | Project | 10000-005: Information Model => 10000-003: Address Space |
| 2025-09-24 07:14 | Jeff Harding | Note Added: 0023337 | |
| 2025-09-24 07:16 | Jeff Harding | Note Added: 0023338 | |
| 2025-09-25 08:25 | Jeff Harding | Status | assigned => resolved |
| 2025-09-25 08:25 | Jeff Harding | Note Added: 0023352 | |
| 2025-09-25 08:26 | Jeff Harding | Relationship added | related to 0010501 |
| 2025-09-25 08:28 | Jeff Harding | Relationship replaced | has duplicate 0010501 |
| 2025-09-25 12:03 | Jim Luth | Status | resolved => closed |
| 2025-09-25 12:03 | Jim Luth | Fixed in Version | 1.05.06 RC1 => 1.05.06 |
| 2025-09-25 12:03 | Jim Luth | Note Added: 0023360 |