BRACKET 4769750 - Caterpillar

Illustration 1 g03344337
Simplified schematic of ethernet connectivity between autonomy ECMsThis diagnostic code is active when the #1 autonomy electronic control module (ECM) cannot communicate with the #5 autonomy ECM for more than 5 seconds. Ensure that task stalled (EID 9958) and task crashed (9959) are not active while troubleshooting. If one or both events are active, follow the appropriate event procedures first. Ensure that the diagnostic code is active at the time of troubleshooting. Check for other active diagnostics and troubleshoot all other codes before starting this procedure.Test Step 1. PING THE #2 AUTONOMY ECM FROM THE MACHINE CAB.
Using a laptop computer, connect to the onboard truck network and ping test the #5 autonomy ECM.Results:
OK - The ping test is successful. Proceed to Test Step 4.
NOT OK - The ping test to the #5 autonomy ECM was unsuccessful. Proceed to Test Step 2.Test Step 2. CONNECT DIRECTLY TO SWITCH #2 IN THE AUTONOMY CABINET.
Using a laptop computer, connect to switch #2 and ping test the #5 autonomy ECM.Results:
OK - The ping test is successful.Repair: If ping tests were successful only after connecting to switch #2 directly, there is most likely a problem between switch #2, switch #4, and the cab ethernet port. This issue is not triggering this diagnostic code, but should be addressed further to ensure proper operation of the system. Proceed to Test Step 5.
NOT OK - The ping test was unsuccessful.Repair: Check the ethernet cable between the #2 switch and #5 autonomy ECM. If an ethernet cable is damaged, replace or repair the cable as necessary. Check port #5 for active lights showing communications. Proceed to Test Step 3.Test Step 3. CHECK SWITCH #2.
Check switch #2 for proper operation.Results:
OK - Switch is operating properly.Repair: Check communications lights on the switch. Check the switch using the laptop and web browser interface. Reset using the button on the internet browser window. If the web browser does not work, the switch has a serial port for communications.Verify that the diagnostic is no longer active.STOP
NOT OK - Switch is NOT operating properly.Repair: Repair or replace the switch as necessary.STOPTest Step 4. CHECK THAT THE AUTONOMY PROCESS ARE RUNNING.
Using PCM remote, verify all the autonomy processes are running.Results:
OK - All processes are running properly. Proceed to Test Step 5.
NOT OK - All processes are NOT running properly.Repair: All processes need to be running in order to troubleshoot this diagnostic code further, Restart the truck and allow for proper startup time. Check the status of the diagnostic code before restarting this step and continuing.STOPTest Step 5. CHECK FOR PROCESS ERROR CODES.
Check for a eid 9958 autonomy process stalled or a eid 9959 autonomy process crashed event code.Results:
OK - The event codes are NOT active or present.Repair: It is possible that the diagnostic code was caused by an intermittent problem or connection. Ensure that all related connectors are properly installed, connected, and free of corrosion.STOP
NOT OK - One or both of the event codes are present and active.Repair: The cid 3728 fmi 09