View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006321 | 10000-014: PubSub | Spec | public | 2020-12-21 15:55 | 2021-03-05 13:54 |
| Reporter | Liam Power | Assigned To | Matthias Damm | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0006321: DataSetClassId usage restrictions | ||||
| Description | In the case where a specific WriterGroup has multiple DataSetWriters, is it allowed that some of the DataSetWriters are writing DataSets whose DataSetMetaData has a DataSetClassId, and other DataSetWriters are writing DataSets whose DataSetMetaData has no DataSetClassId or a different DataSetClassId? If this is allowed we assume the DataSetMessages for each DataSetClassId must be segregated into their own dedicated NetworkMessages. Is this the case? | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
There is already a statement in the UADP message mapping that requires that only DataSetMessages with the same DataSetClassId are included in a NetworkMessage: Table 95 – UADP NetworkMessage But it makes sense to state it also for the configuration side: Added in Added in |
|
|
Agreed to changes in Virtual F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-12-21 15:55 | Liam Power | New Issue | |
| 2021-03-03 15:30 | Matthias Damm | Assigned To | => Matthias Damm |
| 2021-03-03 15:30 | Matthias Damm | Status | new => resolved |
| 2021-03-03 15:30 | Matthias Damm | Resolution | open => fixed |
| 2021-03-03 15:30 | Matthias Damm | Note Added: 0013930 | |
| 2021-03-05 13:54 | Jim Luth | Status | resolved => closed |
| 2021-03-05 13:54 | Jim Luth | Fixed in Version | => 1.05 |
| 2021-03-05 13:54 | Jim Luth | Note Added: 0013989 |
