The circuit that matters
One 5V feed. The rest of the sheet goes quiet.
PCM C175B pin 24 sends 5 volts on GY/RD. That is the job. Signal and ground stay drawn so you still see the diagram — they just are not this test.
How Sparkr works
One path from fault to proof.
What the technician does, what Sparkr recommends, how a result changes the assessment, and how the technician verifies the outcome. The product page explains what is in the workflow. This page shows how a case moves.
-
01
Connect
The technician connects Sparkr Link. The case is attached to this vehicle. Link reads generic powertrain OBD-II, not ABS, SRS, body modules, or circuit voltage.
-
02
Scan
Available data comes into one workspace: VIN, powertrain codes, freeze frame, standard live data, and the customer’s complaint.
-
03
Diagnose
Sparkr evaluates that evidence and recommends a next diagnostic test, with the reason visible. The technician decides whether to run it.
-
04
Test
The technician performs the check with the right tool — a meter, a scope, a swap, or a procedure from service information — and records what happened.
-
05
Prove
Sparkr updates the assessment from that result. If the cause is still open, it recommends the next check. The technician confirms the cause.
-
06
Verify
After the repair, the technician checks the vehicle again so the case does not close on an assumption.
-
07
Learn
The completed case can stay on file so a later similar complaint can be compared with what was already confirmed. A stored case is not a promise the next job will be faster.
Example diagnostic journey
An example case, from the complaint to a confirmed cause.
Illustrative sequence. Clock times such as 0:12, 0:28, and 1:52 mark the order of this drawing. They are not a recorded diagnostic and not a measured shop time. Voltage in the example is a technician meter reading, not data from Sparkr Link.
Repair order
2016 F-150 3.5 EcoBoost
0:00
example sequence
1:52 · cause locked
-
0:00
Connect
Example sequence, not a timed job. Sparkr Link is connected. VIN, powertrain codes, freeze frame, and standard live data are available.
-
0:12
Scan
P0107 and P0122 are both active in this example. The truck stalls at idle and sometimes will not restart. MAP was already replaced.
-
0:28
Diagnose
Two sensors failed together. A technician-entered meter reading shows the 5V reference at 1.1V. That voltage is not a Sparkr Link reading. Check the shared reference before replacing either sensor.
-
1:10
Test
Unplug MAP and measure the 5V reference with a meter. If it returns near 5V, the short in this example is on the MAP branch.
-
1:52
Prove and verify
In this illustration the reference recovers with MAP unplugged and a chafe is found on the harness. Repair the loom, then confirm the reading and the stall with the technician’s own checks.
Electrical diagnostics
Don’t hand me the whole sheet. Tell me where to put the meter.
Conceptual example. This drawing shows one circuit a technician might measure with a meter. It is not the vehicle’s service diagram, and Sparkr Link does not read these voltages.
- The example highlights one circuit. The rest of the sheet is muted.
- A pin, splice, or chafe can be selected to see what a meter might show and what that would mean.
- In this story a 5V reference short can make more than one sensor look failed. Confirm that with a meter and the service information before replacing a part.
Conceptual example
2016 F-150 · MAP 5V reference
Junior · tap to explain
Tap the splice
S108 splits the rail to MAP and throttle.
If either branch shorts to metal, the computer often kills the whole 5V. Both sensors look dead. Unplug MAP first. If throttle 5V comes back, the short is on the MAP side of the splice.
The fault on the graph
Harness chafe to chassis — not a bad MAP.
After S108 the MAP 5V wire is worn through to metal. That short is why the rail is dead. Do not replace the sensor. Do not condemn the PCM. Repair the harness.
Measure here
MAP C102 pin 3 · key on, engine off
In this example a meter should see about 5V on this pin. The illustration shows 0.1V. That voltage is a technician measurement, not a reading from Sparkr Link. Confirm the wire and the repair against the vehicle’s service information.
The difference is the path after the code.
Traditional workflow
CODE
List of possible causes
Technician figures everything else out
The scan tool stops at data. Service info stops at possibilities. The proof still lives in one technician’s head.
Sparkr
CODE
CONTEXT
NEXT CHECK
TEST
RESULT
UPDATED ASSESSMENT
CONFIRMED CAUSE
VERIFICATION
CASE ON FILE
The code is the start of a connected loop. Context, tests, and verification stay in the same system until the fault is proven and the repair is checked.
FAQ
Questions about the path from fault to proof.
The workflow is the product. These are the questions technicians and shop owners usually ask after seeing it.
01 Does Sparkr replace the technician?
No. The technician still makes the call. Sparkr keeps the evidence, the next test, and the proof in one path so the diagnosis does not live only in someone’s head.
02 Does this replace my scan tool or service information?
No. Sparkr Link reads generic powertrain OBD-II: VIN, stored, pending, and permanent codes, freeze frame, and standard live data. Keep a bidirectional OEM scan tool for programming and for modules Sparkr Link does not read, including ABS and SRS. Keep service information for procedures and specifications. Sparkr recommends the next check and keeps the result on the case. It does not replace a multimeter, an oscilloscope, or that service information.
03 What does the technician actually do in the workflow?
Connect the vehicle, confirm the complaint, run the recommended test, and record what happened. Sparkr updates the assessment and names a next check when the result does not confirm the cause. The technician still performs the test and still decides when the cause is confirmed.
04 What if the first test doesn’t prove the cause?
The result is recorded. Sparkr updates the hypothesis and recommends the next branch until a root cause is proven. The case does not jump to parts on a guess.
05 How is this different from looking up a code?
A code is often the effect, not the cause. Scan data tells you what the vehicle is reporting. Sparkr helps the technician decide what evidence to gather next, interpret the result, and move the diagnosis forward. The technician still confirms the cause.
06 Do I need Sparkr Link?
The workflow starts with Sparkr Link connected to the vehicle — VIN, codes, freeze-frame, and live data. It is not a bidirectional OEM scan tool.
07 Is this for master technicians?
Yes. Master techs do not have a knowledge problem. They have a time problem. They already know a code lookup is a gimmick. What they need is less time on the hard car — live data off this vehicle, competing causes with the reasoning shown, a next test with the expected result named, and proof in the case so they are not the shop’s search engine. It does not replace the master. Less experienced techs can follow that same path instead of stopping the bay for a hallway question.
08 Are the times on this page guaranteed?
No. Clock times such as 0:12, 0:28, and 1:52 are sequence markers in an illustration. They are not a recorded job and not a measured shop time.
Next step
See Sparkr work through a diagnostic case.
Tell us about your shop and we’ll contact you to arrange a demonstration.