Deutz — 3.5 CAN STATUS

SERDIA MEASURED VALUES Phas e: The variable CanSetPointPhase (0 to 255, bytes) is sent via the ISO 9141 interface. This variable displays the time sequence of the setpoint value specification: ERROR INFORMATION/EVENT COUNTER: The EMR1 sends an error number CanErrorNumber (0 to 255, bytes) via the ISO 9141 interface specially for CAN bus errors. In SERDIA, these numbers are assigned a text, which is displayed in the window of the -CAN interface. TimeOut errors for receipt messages require special treatment. They are all reported with an error number of 100. To identify which message is causing a time-out error, SERDIA proceeds as follows:

CanRxObjActive displays, in bit mode, the active messages, i.e. the messages that have actually been received. CanConf_bits contains the configured receipt messages, in bit mode. 20-281 Code Text 0 0:Engine standstill, initialization 1 1:Engine standstill, phase 1, no CAN error 2 2:Engine standstill, phase 2, no CAN timeout error 3 3:Engibe start, ... until idling speed is recognized 4 4:Engine runs, wait for CAN setpoint 5 5:Engine runs, setpoint preset via CAN is allright 6 6:Engine runs, emergency op., setpoint preset via CAN failed 7 7:This phase doesn't exist Cod. Testo 0 0: No fault existing 1 1: Message request not received at controller object 15 2 2:

Invalid controller object 3 3:Engine start, ... until idling speed is recognized 4 4: CAN active, but no message activated 5 5: Diagnosis object not activated 6 6: Scan rate 0 in diagnosis message 7 7: Scan rate 0 in measure value telegram 8 8: preset engine speed config.6 does not match TSC2 activation 9 9: TSC1 activated, but ´Setpoint eng. speed´ not set to ´6´ 10 10: ´GovernConf=6´,neither TSC1 nor function shift is activated 11 11: ´GovernConf=6 & Setp.eng.speed=6´, but TSC1 is not activated 12 12:

TSC1 activated, but ´Governor config!=6´ 13 13:TSC1NotAct&FunctShiftAct&´GovernConf.!=6´=>´ShiftMGovernMode!=0´ 14 14:TSC1Act&FunctShiftAct&´GovernConf.=6´=>´ShiftMaskGovernMode!=0´ 100 100 Receipt message failed 101 101 Setpoint telegram failed w.eng.idle (repl. value) 102 102 Setpoint telegram missing w.eng.idle due to low battery voltage 103 103 Setpoint telegram missing after eng.start due to low battery 104 104 Setpoint telegram missing after eng.start, repl.value used 105 105 Setpoint telegram missing during eng.oper., repl.value used