|
West Central Missouri | Since you're issue is readily apparent upon startup, you don't have to wait until the spring to continue to diagnose this.
I have seen this before with a questionable ethernet connection, and I had one SC ecu once that failed to properly boot up. I had to connect it to a laptop and reflash the firmware through a web interface. It was flawless after that.
The most basic way to verify comms with the steering ECU is to go to diagnostics--> Display. See if the display has picked up an IP address on the "wired" port. If it has connectivity with the ECU on the ethernet port, it will list an address here (10.1.1.2 IIRC)
You could also export your vehicle profiles, swap the SteerCommand ECU with another tractor, import the appropriate profiles (minimal recalibration will be required), and then see if the problem follows an ECU (which would suggest hardware or other issue localized to that specific ECU) | |
|
InCommand not always recognizing SteerCommand
