View Issue Details

IDProjectCategoryView StatusLast Update
000955210000-015: SafetySpecpublic2024-06-12 11:04
ReporterChristian Eitner Assigned ToChristian Eitner  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionopen 
Product Version1.05.04 RC1 
Target Version1.05.04 RC1 
Summary0009552: Editorial Issues in 1.05.04 RC
Description

(1) red highlighting of "Structure" keyword in method signature definitions is unclear; it shows that the parameter types are abstract and need to be concretized before usage
(2) Table 23: missing blank after "document" in entry for SafetyConsumerID
(3) Figure 9: misalignment of SafetyConsumer in F-PLC
(4) Table 24 - SPI of the SafetyProvider: inconsistent usage of range "0 – 0xFFFFFFFF" (vs. "0x0 – 0xFFFFFFFF")
(5) Table 25 - SAPI of the SafetyConsumer: some terms in the first column are not in italics
(6) Table 26 - SPI of the SafetyConsumer: The wording explaining the SafetyProviderIDConfigured parameter is different from the SafetyBaseIDConfigured parameter.
(7) 6.3.4.3 Motivation for SAPI Operator Acknowledge (OperatorAckConsumer): last paragraph misses link to Subclause 6.3.4.5 Motivation for SPI SafetyOperatorAckNecessary
(8) Figure 16: availability of demand value "C" not noted at occurrence of second new MNR

Additional Information

(1) Removed unexplained bold red highlighting of method arguments OutSafetyData and OutNonSafetyData in signature descriptions for methods ReadSafetyData and ReadSafetyDiagnostics and added explanations that these are abstract types that have to be concretized for specific applications.
(2) Table 23: added missing blank after "document" in entry for SafetyConsumerID
(3) Figure 9: corrected misalignment of SafetyConsumer in F-PLC
(4) Table 24 - SPI of the SafetyProvider: adapted to consistent usage of range "0x0 – 0xFFFFFFFF" (vs. "0 – 0xFFFFFFFF")
(5) Table 25 - SAPI of the SafetyConsumer: uniformly formatted terms in first column in italics
(6) Table 26 - SPI of the SafetyConsumer: Harmonized the wording explaining the SafetyProviderIDConfigured parameter (using the wording from the SafetyBaseIDConfigured parameter)
(7) 6.3.4.3 Motivation for SAPI Operator Acknowledge (OperatorAckConsumer): added link to Subclause 6.3.4.5 Motivation for SPI SafetyOperatorAckNecessary to last paragraph
(8) Figure 16: noted availability of demand value "C" at occurrence of second new MNR

TagsNo tags attached.
Commit Version

Activities

Christian Eitner

2024-06-12 11:04

manager   ~0021313

Resolved in Draft 3 for RC R1.05.04.

Issue History

Date Modified Username Field Change
2024-05-15 09:28 Christian Eitner New Issue
2024-05-15 09:28 Christian Eitner Status new => assigned
2024-05-15 09:28 Christian Eitner Assigned To => Christian Eitner
2024-05-15 13:43 Christian Eitner Description Updated
2024-05-15 14:00 Christian Eitner Additional Information Updated
2024-05-15 14:03 Christian Eitner Description Updated
2024-05-15 14:03 Christian Eitner Additional Information Updated
2024-05-15 14:25 Christian Eitner Description Updated
2024-05-15 14:25 Christian Eitner Additional Information Updated
2024-05-22 13:20 Christian Eitner Description Updated
2024-05-22 13:20 Christian Eitner Additional Information Updated
2024-05-22 13:24 Christian Eitner Description Updated
2024-05-22 13:24 Christian Eitner Additional Information Updated
2024-05-22 13:39 Christian Eitner Description Updated
2024-05-22 13:39 Christian Eitner Additional Information Updated
2024-05-22 13:48 Christian Eitner Description Updated
2024-05-22 13:48 Christian Eitner Additional Information Updated
2024-06-11 11:31 Christian Eitner Description Updated
2024-06-11 11:31 Christian Eitner Additional Information Updated
2024-06-12 11:04 Christian Eitner Status assigned => closed
2024-06-12 11:04 Christian Eitner Note Added: 0021313