Multiple Active Fault Codes Detected by ADE

Common Symptoms

• Platform LCD scrolls 9999 or displays 9999-14 instead of a single SPN/FMI code
• Machine may refuse to lift, drive, or both depending on which underlying codes are active
• Ground control panel shows one or more amber or red fault indicator lights
• Functions that normally work from the platform controls feel sluggish or stop mid-cycle
• ADE controller cycles through multiple fault entries faster than you can read them
• Machine powers up but immediately limits motion or goes into a safe-hold state
• Resetting the key switch clears the display temporarily but faults return within seconds

Probable Causes (Ranked by Likelihood)

• Two or more independent SPN/FMI codes active simultaneously, overflowing the single-code display and triggering the 9999 summary indicator Very Likely
• CAN network communication fault causing cascading secondary codes across TCON, GCON, and ADE modules Very Likely
• Low or unstable battery or chassis voltage causing multiple sensor and module faults to set at once Likely
• Ground connection corrosion or loose chassis ground strap creating erratic voltage references across multiple ECU nodes Likely
• Failed or intermittently failing ADE controller producing spurious DTC entries that do not correspond to real hardware faults Possible
• Recent software update or controller parameter mismatch between TCON and GCON that has not been resolved by EZcal calibration Possible
• Water or contaminant intrusion into the ADE connector or ground control enclosure corrupting multiple sensor signals Less Likely

Step-by-Step Diagnostic Procedure

1. Connect the JLG Analyzer software via the data link connector at the ground controls before doing anything else. The platform LCD cannot display the full DTC list when 9999 is showing. You need the Analyzer to pull every active and stored SPN/FMI code so you know what you are actually dealing with.

2. Write down every code the Analyzer returns. Sort them by severity. Codes with FMI 12 (bad device), FMI 5 (open circuit), or FMI 6 (short to ground) on a power or CAN-related SPN usually explain the others. Fix those first.

3. Check battery voltage at the main battery terminals with the machine keyed ON. You want 12.4 V or higher on a 12 V system, or 24.4 V or higher on a 24 V system. Voltage below those thresholds can set five or six unrelated codes all at once.

4. Inspect every main chassis ground strap, the ground from the battery negative to the frame, and the ground from the frame to the ADE controller enclosure. Clean any white or green corrosion with a wire brush and retorque the connections. A bad ground is one of the most common triggers for a 9999 summary code.

5. Inspect the CAN network wiring harness from the ADE controller to the TCON and GCON. Look for pinched, chafed, or melted insulation, especially near the turntable rotation point and the base of the boom. A single broken CAN wire will pull down the whole network and generate codes on every node.

6. After fixing any wiring or voltage issues, clear all stored codes using the JLG Analyzer and cycle the key switch. Let the machine sit powered up for two full minutes without operating it. If 9999 reappears, reconnect the Analyzer to see which codes came back. This tells you which root fault survives the repair.

7. If the Analyzer shows codes pointing to a specific sensor or actuator (for example, a platform load sensor or a boom angle sensor), isolate that component and swap or bench-test it before condemning the ADE controller itself.

8. If the Analyzer shows no real hardware faults but 9999 keeps returning, and a software or firmware mismatch is suspected, contact JLG technical support for a controller parameter file matched to your serial number. Loading a mismatched parameter file via EZcal can generate phantom fault floods that the 9999 summary is designed to flag.

Frequently Asked Questions