Employee operating a Test Station using TestWork Automation Software

TestWork 10 CAN Safety

CAN messages can contain process-critical signals and thus need to be equipped with corresponding safety mechanisms. Due to that, CAN messages receive certain safety information ensuring the recognition of checksum verification and ensuring continuity monitoring of data reception.

Safety Measures - CAN Messages:

  • Checksum (ensuring checksum verification)
  • Message counter (ensuring continuitiy monitoring/order of messages)

Loss Detection

The TrueData-Gateway Controller supports loss detection for cyclically received messages. The parameterization of loss detection is carried out through an extended DBC file.

Components of loss detection are:

  • Processing a message-specific counter tag
  • The tag counts the failure of messages
  • The tag supports limit value alarming
  • Setting failure values to signals on a failed message
  • Parameterizing loss detection
  • Parameterizing loss detection through a DBC file

The operator can manually and automatically configure loss detection.

Checksum Verification

The TrueData-Gateway Controller supports checksum verification for all received messages. The parameterization of checksum verification is carried out through an extended DBC file.

Components of the check of checksum verification are:

  • Processing a message-specific counter tag
  • The tag counts the error with checksum verification
  • The tag supports limit value alarming
  • Sum counter that adds up all errors (_V2)
  • Setting failure values to signals on a corrupted message
  • Parameterizing the preinitialization of alarm limits
     

The operator can manually and automatically configure checksum verification.

Continuity Monitoring

The TrueData-Gateway Controller supports continuity monitoring for all received messages. For continuity monitoring, the received messages counter and its increment are evaluated. The parameterization of continuity monitoring is carried out through an extended DBC file.

Components of continuity monitoring are:

  • Processing a message-specific counter tag
    • The tag counts the error with continuity monitoring
    • The tag supports limit value alarming
    • Sum counter that adds up all errors (_V2)
  • Parameterizing continuity monitoring
  • Parameterizing the preinitialization of alarm limits
     

With continuity monitoring, no failure values are set as reaction. The operator can manually and automatically configure continuity monitoring.