View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007683 | Compliance Test Tool (CTT) Unified Architecture | 1 - Script Issue | public | 2022-01-31 13:42 | 2022-08-04 15:13 |
| Reporter | Jonas Green | Assigned To | Paul Hunkar | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | won't fix | ||
| Product Version | 1.04.09.398 | ||||
| Summary | 0007683: ByteString length limitation in the application | ||||
| Description | In our device the data type ByteString is mapped to a type of the application named octet. In our application an array of octet maps to an array of ByteString on OPC UA. But an array of octet can only have a single element per array index. The application definition is not possible to change. When running CTT we have experienced problem with this as CTT tries to write an array of bytestrings where each bytestring has a length >1. An example is "Monitored Item Services - Monitor Value Change - 029" which writes 14 elements per array index. Is it valid to have a such narrow limitation as max 1 element in a ByteString or is the CTT expectation that a ByteString should handle 14 elements invalid? | ||||
| Tags | No tags attached. | ||||
| Files Affected | |||||
|
|
We are trying to understand your issue. The OPC UA specification has a very specific definition of a Byte and a ByteString, it sounds like you have a different definition of a byteString, but we are not sure we understand your definition? The OPC definition is fixed. Are you actually asking for a new DataType Octet? that has different properties? |
|
|
No explanation of what is being desired - so nothing to do |
|
|
Agreed in CMP call - issue closed |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-01-31 13:42 | Jonas Green | New Issue | |
| 2022-02-03 16:28 | Paul Hunkar | Assigned To | => Paul Hunkar |
| 2022-02-03 16:28 | Paul Hunkar | Status | new => feedback |
| 2022-02-03 16:28 | Paul Hunkar | Note Added: 0015912 | |
| 2022-08-04 15:12 | Paul Hunkar | Status | feedback => resolved |
| 2022-08-04 15:12 | Paul Hunkar | Resolution | open => won't fix |
| 2022-08-04 15:12 | Paul Hunkar | Note Added: 0017285 | |
| 2022-08-04 15:13 | Paul Hunkar | Status | resolved => closed |
| 2022-08-04 15:13 | Paul Hunkar | Note Added: 0017286 |