Truck repair Truck computer diagnostics
Check-engine or stop-engine light on?
Nexgen reads and interprets the fault codes behind dash warning lamps on commercial trucks: check-engine and stop-engine lamps, module communication faults, and faults that set and clear on their own. A code points to a circuit or system, not always a failed part, so it is followed by testing. Diagnosis can often start where the truck is parked; photograph the dash, leave the codes alone and call.
Can I keep driving with the check-engine light on?
On most trucks a steady amber lamp with normal power and gauges means a fault has been logged that needs attention soon, not that the truck must stop. A red stop-engine lamp is different: get off the road where it is safe and shut down, because the engine is protecting itself and some will shut down on their own. A flashing lamp, or any lamp with power loss, low oil pressure, rising coolant temperature or a new noise, also means stop and call. Continuing to operate may risk further damage.
Example: the sweep stands for a scan tool reading the stored codes; the code says which system logged the fault, the inspection says why.
Call the nearest location.
Call now (204) 960-5390Injury, fire or danger: call 911 first. We take calls 24/7.
- Winnipeg (204) 960-5390
- Brandon (431) 279-4008
Problems we commonly inspect
- Amber check-engine lamp on
- The engine control module has logged a fault; the truck may drive normally or with reduced power.
- Red stop-engine lamp on
- A serious condition the engine is guarding against: low oil pressure, high coolant temperature and low coolant level are common triggers.
- Several unrelated lamps at once
- Engine, ABS, transmission and others lighting together, or gauges dropping out: often a data-link or module communication fault rather than several failures.
- A lamp that comes and goes
- A fault that sets and clears itself: the inactive code history is what shows when and how often.
- A code that did not lead to a fix
- A handheld reader or a telematics alert named a part, the part was replaced, and the lamp is back.
- Lamp on after recent work
- After a repair, a battery change or a jump-start: a connector not fully seated, a sensor left unplugged, or a voltage dip logged by a module.
Stop driving, or can it wait?
Stop and get help
- The red stop-engine lamp is on, or any lamp is flashing.
- A lamp together with low oil pressure, high coolant temperature or a low-coolant warning.
- A lamp with a sudden loss of power, knocking, heavy smoke or a burning smell.
- Several systems faulting together, including the ABS or the transmission.
May be safe to assess further
- A steady amber lamp with normal gauges, normal power and no new noise or smell.
- A lamp that came on once and went out, with the truck driving normally: still worth booking in while the history is fresh.
Continuing to operate may risk further damage or create a safety issue. When in doubt, stop where it is safe and call. Injury, fire or immediate danger: call 911 first.
What to do right now
- Photograph the dash with every warning lamp and message showing, before the key is turned off.
- Note whether each lamp is steady or flashing, amber or red, and what the truck was doing when it came on: climbing, idling, a cold start, or just after fuelling.
- Read the gauges you can see from the seat: coolant temperature, oil pressure, voltage and fuel.
- If the red stop-engine lamp is on, get fully off the road where it is safe and shut down.
- Call with the photos and what you noticed. If there is smoke, fire or anyone hurt, call 911 first.
What not to do
- Do not clear codes before they are recorded: when and how often a fault set is part of the evidence.
- Do not disconnect the batteries to make the lamps go out.
- Do not replace parts on the strength of a code alone.
- Do not drive on with a red stop-engine lamp to reach a destination.
- Do not unplug sensors or modules to see what changes.
When you call, have ready
- Photos of the dash with the lamps and any text messages showing.
- Any codes already read, written exactly as shown, including SPN and FMI numbers if the display gives them, and what read them.
- Whether each lamp is steady or flashing, and whether it has come and gone before.
- What the truck was doing: speed, load, grade, idling or cold start, and any change in power, noise or smoke.
- Make, model, engine and year, plus any recent repairs, battery work or jump-starts.
- Whether the truck is still running normally, running with reduced power, or shut down.
Not sure exactly where you are?
Your phone can find the spot and write the text for you.
Your text
Uses this phone’s location. Nothing is sent: copy it to paste in a message or read it out when you call.
What we check
Depending on the symptoms, the technician may check:
- Active and inactive fault codes in the engine and the other modules, with when and how often each one set
- Live data from the sensors behind the fault, compared with what the engine is actually doing
- The circuit behind a code: its power, ground, signal wire and connectors
- Data-link wiring, terminating resistors and the diagnostic connector when modules stop talking
- Module power and ground supplies, and battery voltage under load
- Snapshot data recorded at the moment a fault set, where the module keeps it
- Whether the fault can be made to repeat with the engine running or on a test drive
Common causes
Possibilities, not a diagnosis of your unit:
- A sensor, or its wiring, sending a reading the module treats as out of range
- A connector with corrosion, water inside or a loose pin
- Low or unstable voltage upsetting the modules, often after a battery or charging problem
- A damaged data-link wire or terminating resistor, setting communication codes in several modules
- A real mechanical fault that the sensor is correctly reporting
- An aftertreatment fault behind the lamp, often with reduced power
Roadside or shop?
Often done where the unit is
- Reading and recording codes and lamp history where the truck stopped
- Checking connectors, sensors and wiring that can be reached safely
- Judging from the codes and live data whether the fault is safe to drive on
Often better handled in a shop
- Faults that only appear under load and need a longer road test
- Intermittent faults that need the truck monitored over time
- Repairs where the code leads to a fault inside the engine or transmission
Every fault and every spot is different. Describe it on the call and we will tell you what can be done where the unit is.
How it works
Record first
Lamps, messages and every stored code are captured before anything is cleared or disconnected.
Read the history
Active against inactive, occurrence counts and the conditions when each code set show whether this is one fault or a pattern.
Test the circuit
The sensor, wiring and connector behind the code are tested, so the repair targets the cause, not the part the code names.
Repair, then clear
Codes are cleared only after the repair, and the truck is run to confirm the fault does not set again.
Where we work: Winnipeg, Highway 1 and Brandon
On the Trans-Canada Highway (Highway 1) near Brandon, Headingley or Winnipeg, a red stop-engine lamp means the next place you can get fully off the road, not the next exit you were aiming for. Photograph the dash before you shut down.
Roadside assistance and mobile truck and trailer repair 24/7 along the Trans-Canada Highway (Highway 1) between Winnipeg and Brandon, in both directions: Headingley, St. François Xavier, Elie, Oakville, Portage la Prairie, MacGregor, Austin, Sidney, Carberry and Douglas, and the yards and roads around them.
- 646 Pipeline Road, Winnipeg, MB R2P 2T7 (204) 960-5390
- 1601 Moreland Ave, Brandon, MB R7C 1A6 (431) 279-4008
Questions
- Should I clear the check-engine code?
- No, not before it has been recorded. When a code set, how often, and whether it is still active is what guides the diagnosis. Clearing it wipes that history, and the lamp comes back if the fault is still there.
- What is the difference between an active and an inactive code?
- An active code is happening now; an inactive code happened earlier and is stored. Inactive codes that set again and again usually point to an intermittent fault, often in wiring or a connector.
- Does a fault code tell you which part to replace?
- No. It tells you which circuit or system saw a problem. A sensor code can come from the sensor, its wiring, its connector or the condition it measures, which is why the circuit is tested before parts are replaced.
- Why are several warning lights on at once?
- Often a communication fault, not several failures. The modules share a data link, and damaged wiring, a bad connector or low voltage can make them lose contact and set codes together.
- Why has my truck lost power with a warning lamp on?
- It may be in a derate, protecting itself. On many trucks the cause is in the aftertreatment system, which our DEF, DPF and derate diagnostics page covers. Record the lamps and messages and call.