CDIAG INSITE & Controls — practice test
CDIAG tests whether you can use INSITE as a diagnostic instrument instead of a parts catalog - reading the ECM, the datalink, and the fault logic well enough to know what the tool is actually telling you. Techs fail it because they know the button clicks but not the why: they can pull a fault code and never explain what condition set it, or they can run a cylinder cutout without knowing what a passing result looks like. The test punishes anyone whose whole diagnostic process is 'read the code, replace the named part.'
Studying for CDIAG (INSITE & Controls)? Overhaul Prep has 120 verified CDIAG questions written to the current task list — in the same formats the real exam uses (direct, Technician A/B, EXCEPT and most-likely-cause). Every answer comes with a written explanation, so you learn why instead of memorising a letter.
What's on the CDIAG test
Weight sits heaviest on fault codes and diagnostic tests - active vs inactive codes, what condition triggers a code, and running and interpreting cylinder performance, injector response, and wiggle tests. Next is ECM parameters and features: customer vs OEM parameters, password levels, road speed and idle shutdown setup. Then calibration work - identifying the current cal, download rules, and what gets preserved. Datalink rounds it out: J1939 vs J1587, adapter setup, and no-communication troubleshooting. Trim and feature files show up in a small but reliable block.
High-yield CDIAG topics
The material that shows up year after year. If you're short on time, start here.
- Active vs inactive vs pending fault codes and what clearing actually does. Inactive codes carry the count and first/last occurrence timestamps and engine hours - that history is your diagnostic data, and wiping it before you read it is how techs lose the intermittent. Know that INSITE will not let you clear an active code, and that some codes stay latched until the keyswitch cycles even after the condition goes away. Expect questions about reading the code's trigger condition (the 'when set' logic) rather than the code number itself.
- The three-number fault identity: Cummins fault code, SPN/FMI, and the lamp/severity. Know the FMI meanings cold - 3 is voltage above normal/shorted high, 4 is voltage below normal/shorted low, 5 is current below normal/open circuit, 2 is erratic/intermittent/incorrect, 31 is condition exists. FMI 3 vs 4 on the same sensor is the single most common question shape on this test because it decides whether you're chasing a short to power or a short to ground, and that decision comes straight from unplugging the sensor and watching whether the code flips.
- Cylinder performance and injector-related tests. Know that the cylinder cutout/performance test needs the engine at operating temperature and steady idle to be valid, that results are compared cylinder to cylinder rather than against an absolute spec, and that a cylinder that shows little change when cut out is the weak one. Know why a bad injector, a burnt valve, and low compression all look similar on this test - and what the follow-up test is (injector response time, compression, or a manual crossover) to separate them.
- Parameters vs features vs trim files - these are three different things and the test will mix them. Customer parameters (road speed governor, idle shutdown, cruise, PTO) are adjustable in INSITE at the customer password level. Features are enabled/disabled and generally need OEM-level or a factory-authorized password. The trim file (ECM fueling calibration data specific to the engine) travels with the engine serial number, not the truck. Know what survives an ECM calibration download versus what you must save and restore, and that swapping an ECM without transferring the correct trim/parameters gives you a running engine with wrong fueling and bogus codes.
- Datalink layer knowledge: J1939 (250k CAN, twisted pair, 120-ohm terminators at each end, ~60 ohms measured across the bus key-off) vs J1587/J1708 (older, slower, 9-pin pins A/B vs F/G). No-communication troubleshooting order: adapter drivers and INSITE adapter selection first, then key-on power at pin A/B of the connector, then the datalink resistance/wiring, then the ECM. Know that a single missing terminator often still allows communication but produces intermittent dropouts - which is exactly the kind of 'it works on the bench, fails on the road' question they ask.
- Calibration download rules and when NOT to reflash. Know how to read the current cal ID/rev in INSITE, that you check the ECM code/cal against Cummins recommendations before assuming a reflash fixes anything, that battery voltage must be stable (a charger or good batteries - a dying battery mid-flash bricks the ECM), and that you never key-off mid-download. Also know that a calibration update is a fix for a known-issue code, not a shotgun for an electrical fault: reflashing does not repair a shorted harness.
Where techs lose points on CDIAG
Good technicians miss these — not from lack of skill, but because the question is built to catch them.
- The code names a component, so replace the component. A code that reads 'injector cylinder 3 circuit' means the ECM saw a fault on the circuit - which includes the harness, the connector at the valve cover, and the ECM driver, not just the injector. The test loves the answer 'replace the injector' as the wrong-but-obvious choice. The right answer is almost always the step that isolates the circuit: swap the injector connections to a known-good cylinder and see if the fault follows, or measure the circuit.
- Assuming an inactive code is a fixed problem. Inactive only means the condition is not present right now. A code with 40 occurrences that went inactive two engine hours ago is an active intermittent - that is your complaint. The look-alike wrong answer is 'clear inactive codes and return to customer.'
- Confusing FMI 3 and FMI 4 direction, and confusing an open circuit with a short. On most 5-volt sensors, unplugging the sensor drives the signal to reference voltage and sets the high-voltage code (FMI 3), while a signal-to-ground short sets FMI 4. That means a sensor code that changes from 4 to 3 when you unplug the sensor points at the sensor itself, and one that stays at 4 unplugged points at the harness shorted to ground. Techs invert this constantly and pick the wrong repair.
- Believing INSITE is the truth. INSITE shows you what the ECM believes based on the signals it receives. If the ECM has a bad ground or an out-of-cal reference voltage, every reading on your screen is wrong in a consistent, believable way. Questions where all the sensor values are 'a little off' across unrelated sensors are testing whether you go to power and ground at the ECM instead of chasing individual sensors.
A study plan that works for CDIAG
Roughly two weeks of real preparation, in the order that actually builds on itself.
- Days 1-4: Fault-code logic before anything else. Drill FMI meanings until they are reflex (2, 3, 4, 5, 7, 31), and for each of the common Cummins codes learn the trigger condition - what the ECM measured and against what threshold. Practice the sentence 'this code sets when ___' out loud for 25 codes. Do not memorize code-to-part mappings.
- Days 5-8: Live in INSITE. If you have shop access, open a real ECM and walk every menu - fault codes, monitor, parameters, features, tests, calibration. Run a cylinder performance test on a warm engine and read the result table until you can say which cylinder is weak and why. If you have no shop access, use INSITE's simulated/demo ECM and the help files - the menu structure and what each test requires are testable.
- Days 9-11: Parameters, features, trim, calibrations. Build one page: what changes at customer level, what needs OEM, what needs the trim file, what survives a cal download, what needs a keyswitch cycle. Then work the ECM-swap scenario end to end from memory, because it is the classic multi-step question.
- Days 12-14: Datalink and no-comm. Memorize J1939 vs J1587 speeds, wiring, pins, and terminator resistance values. Then walk the no-communication tree top to bottom twice. Finish with timed practice questions and re-read every one you missed until you can name the exact wrong assumption that made you miss it.
Sample CDIAG questions
Straight from the bank — answers highlighted, with the explanation underneath.
How does the INSITE service software physically communicate with a Cummins engine ECM?
- Through a Cummins INLINE datalink adapter (5/6/7) connected between the vehicle diagnostic connector and the PC
- Through a generic OBD-II Bluetooth dongle
- By tapping directly into the crankshaft position sensor
- Through a PACCAR ESA programming cable
In the Cummins SPN/FMI fault scheme, what does an FMI of 5 indicate?
- Voltage above normal, shorted high
- Current below normal or open circuit
- Mechanical system not responding
- Data erratic or intermittent
What value stored in the ECM uniquely identifies the engine and must match the calibration loaded into it?
- The vehicle VIN only
- The fleet password
- The Engine Serial Number (ESN)
- The DPF part number
Ready to pass CDIAG?
Get all 120 CDIAG questions plus timed full-length mock exams, a high-yield “must-know” filter, and readiness tracking that tells you when you're actually ready.
Start your 24-hour free trial