MESSAGE FORMAT (CONT’D)

BOBCAT Proprietary PGN (Cont’d)

CAN communication failure

•Detect CAN communication malfunction

•At system start

When EECU cannot receive necessary information via CAN-BUS for two seconds* after power-on start, it considers that the CAN communication failure occurred.

•After system start normally

When EECU cannot receive necessary information via CAN-BUS five times continuously, it is considers that the CAN communication failure occurred. (ex. period of five times: TSC1:10 x 5 ms, Y_ECR1:10 x 5 ms)

When EECU can receive necessary information via CAN-BUS for one time, it considers that the CAN communication has done normally.

•Start lock at CAN communication failure mode

When EECU cannot receive Y_ECR1 or Starter Prohibition (65308) via CAN-BUS for two seconds* after power-on start, EECU will allow to start engine according to discrete input signals. *1:starter

MESSAGE FORMAT (CONT’D)

BOBCAT Proprietary PGN (Cont’d)

•Engine speed control at CAN communication failure mode

If TSC1 or Y_ECR1 communication failure occurs, EECU will select a speed control mode as the table below.

•EECU shutdown at CAN communication failure condition

At CAN communication failure condition EECU doesn't execute the shutdown process, so log-data cannot be written in EEPROM (ex. Engine run time). There is a possibility that the new log-data is broken at power OFF, when EECU is writing the log-data in EEPROM temporarily.

There is no influence on driving the engine even if the new log-data has been broken.

Component ID check

When EECU is replaced, it has no way to check the actual engine type. Therefore we recommend that VECU should check Component_ID of EECU. IF Component_ID is different from original one, VECU should turn to the derate_mode. VECU can get vehicle manufacture specific component ID by VI Request, if VI has already written in EEPROM.

References

J1939/21 Data Link Layer

J1939/71 Vehicle Application Layer.

J1939/73 Application Layer - Diagnostics.

ISO 15765-1.3:2001[Road vehicles - Diagnostics on CAN - Part 1: General information]

ISO 15765-2.4:2002[Road vehicles - Diagnostics on CAN - Part 2: Network layer services]

ISO 15765-3.5:2002[Road vehicles - Diagnostics on CAN - Part 3: implementation of diagnostic services]

ISO 15765-4.3:2001[Road vehicles - Diagnostics on CAN - Part 4: Requirement for emission-related systems]

Appendix A: RECEIVE and SEND MESSAGE CAN ID SUMMARY

Appendix B: MESSAGE FORMAT(J1939-71,-73,-21)

Appendix C: MESSAGE FORMAT(BOBCAT Proprietary PGN)

Appendix D: 2G-ECO Governor Controller DTC Table