Remote Diagnostic
Share your fault codes and operational context. We work through the diagnosis with you before any ECM ships — narrowing the underlying cause, identifying the resolution path, and saving you diagnostic time and unnecessary parts replacement.
- Same-day diagnostic conversation.
- No travel — no shipping needed for diagnosis.
- Fleet pattern recognition for recurring issues.
- 10,000+ ECMs across 38 countries.
- Fault code list (SPN/FMI or scan tool screenshot)
- Photos of dashboard warning lights
- Engine platform and approximate mileage
- Operational application and duty cycle
- When the issue started and recent service
Four Steps From Codes To Resolution
Share The Codes And Context
Send fault code screenshots from your scan tool, photos of the dashboard warning lights, or a description of what the truck is doing. Tell us what platform, what mileage, what application, and when the issue started.
Diagnostic Conversation
We walk through the code cluster and operational context. Most diagnostic patterns we encounter are ones we've seen many times — we typically narrow the underlying cause within a few minutes once the context is established.
Recommended Path
We tell you what we think is driving the issue, what the resolution options are, and what the trade-offs look like. Sometimes the answer is calibration work; sometimes it's hardware service; sometimes it's a combination.
Quote And Next Steps
If calibration work is the right path, we quote the scope and provide ship-in or remote programming instructions. If hardware service is needed first, we tell you what to address before calibration work makes sense.
Why Remote Diagnostic Works
Most diagnostic patterns we encounter on Cummins, Paccar, MaxxForce, Mack, Volvo, Cat, and Detroit diesel platforms are ones we've seen many times before. The fault code clusters, operational symptoms, and underlying causes follow recognizable patterns across the fleet population. Remote diagnostic works because we're not solving novel diagnostic puzzles for each customer — we're recognizing patterns and narrowing the underlying cause based on the operational context you describe.
A diagnostic conversation that takes a dealer service department hours of bay time often takes us minutes once the operational context is established. The dealer needs to physically attach diagnostic tooling, run through standard diagnostic procedures, and work toward identifying the issue from first principles. We work from recognizing the cluster pattern and asking the right operational questions to confirm the working hypothesis.
That diagnostic speed doesn't replace the value of dealer service for hardware diagnosis and repair — but it does mean we can typically identify whether dealer service is actually addressing the right issue, save you from unnecessary parts replacement, and narrow the calibration scope before any ECM ships for programming work.
When To Use Remote Diagnostic
Recurring Symptom Across A Fleet
Multiple trucks in the fleet showing similar fault codes, similar derate patterns, or similar operational issues. Fleet pattern recognition often surfaces causes that individual-truck diagnosis would miss — a calibration issue, an operational pattern, or fleet-wide aging at a predictable threshold.
Owner-Operator Specific Issue
A single truck with a recurring issue that standard service hasn't resolved. The diagnostic conversation typically saves substantial diagnostic time and avoids unnecessary parts replacement by narrowing the underlying cause from operational context.
Second Opinion Before Major Service
Before committing to engine rebuild, DPF replacement, or other major service, a diagnostic conversation often identifies whether the proposed service actually addresses the root cause. Misdiagnosed engine wear that's actually DPF backpressure, or vice versa, is more common than operators expect.
Pre-Programming Diagnostic
Before shipping an ECM for programming, we work through the operational context to confirm the calibration scope. The conversation often refines the scope based on actual operational patterns rather than the surface presentation alone.
Fleet Pattern Recognition
For fleet customers running multiple trucks across similar platforms or applications, remote diagnostic delivers an additional layer of value through fleet pattern recognition. Recurring fault code patterns across the fleet typically reflect common underlying issues — a calibration approach that doesn't match the operational duty cycle, fleet-wide aging at a predictable threshold, common fueling or service patterns that affect the broader fleet, or operational practices that compound across the fleet population.
Individual-truck diagnosis misses these patterns because each truck looks like its own diagnostic puzzle. Fleet-level analysis surfaces the common thread. For a fleet manager dealing with recurring derate events across 20 trucks, the operational economics of addressing the underlying pattern often far exceed the operational economics of treating each truck reactively.
Our fleet diagnostic conversations typically span the operational profile across the fleet, the mileage distribution, the application mix, recent service history fleet-wide, and the specific fault code patterns appearing across multiple trucks. The result is usually a calibration approach or operational recommendation that addresses the pattern fleet-wide rather than truck-by-truck.
What Remote Diagnostic Doesn't Replace
Remote diagnostic narrows the underlying cause and identifies the resolution path. It doesn't replace the hardware service that actual mechanical issues require. EGR cooler failures need hardware replacement; DPF substrates past ash service limit need cleaning or replacement; failing turbochargers, injectors, and engine wear need physical service. Our diagnostic work identifies what needs to happen and who needs to do it — the calibration work we do, the hardware service operators arrange separately.
For trucks where the right path is calibration work, we coordinate ship-in service (typical 2-3 day turnaround) or remote programming for compatible platforms. For trucks where hardware service is the right path, we point you toward the appropriate service category and confirm whether calibration work should follow or stand alone.
The diagnostic conversation is the value. Whether the resolution involves our calibration work, third-party hardware service, or both, the conversation typically saves substantial time and money compared to working through the diagnosis without it.
Patterns We Work Through Most Often
Start The Diagnostic Conversation
Same-day response. Share fault codes and operational context — we'll narrow the underlying cause and identify the resolution path. Available worldwide. NDAs available for confidential fleet work.