View Issue Details

IDProjectCategoryView StatusLast Update
000783710000-015: SafetySpecpublic2022-03-30 07:42
ReporterChristian Eitner Assigned ToChristian Eitner  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionopen 
Product Version1.05.00 
Target Version1.05.02 RC1 
Summary0007837: Inconsistency concerning SAPI.SafetyConsumerID in the UA Safety Specification
Description
  • as reported by Elke Hintze
  • "Table 26 - SAPI of SafetyConsumer" describes that SAPI.SafetyConsumerID is only read when a rising edge of Enable occurs.
  • However, in the SafetyConsumer state diagram, SAPI.SafetyConsumerID is read in every safety cycle (transition T16, i.e., every time a RequestSPDU is built). See Tables 32 and 34.
Additional Information
  • solution discussed in JWG meeting 2022-03-08
TagsNo tags attached.
Commit Version

Activities

Christian Eitner

2022-03-30 07:42

manager   ~0016483

  • solution accepted with draft version from 2022-03-22

Issue History

Date Modified Username Field Change
2022-03-08 14:22 Christian Eitner New Issue
2022-03-08 14:22 Christian Eitner Status new => assigned
2022-03-08 14:22 Christian Eitner Assigned To => Christian Eitner
2022-03-09 14:06 Christian Eitner Description Updated
2022-03-09 14:06 Christian Eitner Additional Information Updated
2022-03-30 07:42 Christian Eitner Status assigned => resolved
2022-03-30 07:42 Christian Eitner Target Version => 1.05
2022-03-30 07:42 Christian Eitner Note Added: 0016483
2022-03-30 07:42 Christian Eitner Status resolved => closed
2022-03-30 07:42 Christian Eitner Target Version 1.05 => 1.05.02 RC1