OSEK_DIRECT_NM.ppt

OSEK DIRECT NM NM Services The essential task of NM is to ensure the safety and the reliability of a communication network for ECUs. ? Initialization of ECU resources, e.g. network interface. ? Start-up of network ? Providing network configuration ? Management of different mechanisms for node monitoring ? Detecting, processing and signaling of operating states for network and node ? Reading and setting of network- and node-specific parameters ? Coordination of global operation modes (e.g. network wide sleep mode) ? Support of diagnosis NM Messages Alive message: 1) Start phase: If an ECU wants to communicate via CAN or detect a communication request from another ECU, it sends an alive message to register to the logical ring. 2) Normal operation: If the ECU detects, that it was skipped, then it sends an alive message to register to the logical ring again. 3) Failure: If the ECU detects a failure of another ECU (no ring message received within T[max]) then it sends an alive message to start the logical ring again. Ring message: During normal operation all ECUs are sending a ring message according to OSEK/VDX NM standard. Limp home message: In the error case the ECU switch to Limp Home. NM States NMOff NM is shut off NMOn NM is switched on NMShutDown Selective shut off of NM entity NMOn: NMInit NM initialization NMAwake Active state of the NM NMBusSleep NM is in sleep mode NMActive NM communication enabled NMPassive NM communication disabled NMAwake: NMReset The operability of the own node is determined NMNormal Processing of direct node monitoring NMLimpHome Handling of failure in own node NM Protocol Data Unit NM address field - source Id - destination Id NM control field - OpCode NM data field (optional) - application specific data NMPDU --- CAN MSG Timing NM Nodes NM Communication