Sim no J39 Data

Rhino

Member
Joined
Jul 12, 2014
Messages
5
Fluid Motion Model
C-248 C
Have a 2009 R25. Went to get underway this morning and had a fault code on the Smartcraft VesselView: "Sim no J39 Data", as well as a "NullReferenceException". Can't find either code or even a reference to them in the manual nor online. Long story short, while there's power available, unable to start the engine. Would greatly appreciate any assistance with this.
 
Two years ago several boats on our dock took lighting strikes (one in the slip next to our tug) and needless to say the voltage spikes played havoc with all boats on the dock to include ours. We lost all electronics from radar down through the engine and thruster systems. The ECM survived so we were able to start and move boat but no thrusters (lost control head). If I recall correctly one of the noted faults was SIM no J39 Data which is System Integration Module no J1939 Data. My SIM was replaced and calibrated and solved fault. The SIM replaced was located in Vessel Integration Panel (VIP) which on our R25 is mounted in the aft storage locker on starboard side. Not sure if this is what is causing your fault code but may be a start point to discuss with your local Cummins distributor. Even though SIMs are plug and play they have to be calibrated once installed.
 
Appreciate the insight on this. Once it stops raining I'll start troubleshooting there. So far all the fuses I've checked are good.
 
Once you have located the the Vessel Integration Panel you should find two circuit breakers on the front, one a 5 amp and the other a 10. Try a reset. The six fuse cluster located on top of the engine were all okay?
 
Well no joy with the reset, and all fuses on top of engine were good.
 
It turns out that a J39 is the descriptor for the plug that connects to the wiring harness that feeds the engine data to the SIM and ECM. Basically what happened was that the plug has snap connectors on both sides and one side had become disconnected from the engine. As a result, it would periodically make contact, the error would disappear, and this would allow the engine to start. Very simple fix, very frustrating to experience. Especially since I had checked all the wiring connections I could locate. Hopefully this can help someone else that may experience this.
 
This reminds me of the infamous 'wiggle test'. In my past professional life I had an intermittent issue happening in a very large computing system that had many inter-node connections. I had the worker bees check ALL connections and perform the 'wiggle test'. Eventually one connector was found to be causing the issue. 🙂 The lesson learned was to check every connection even if it appeared to be secure.
 
Back
Top