Keep connector faces and pin numbers straight
Read a declared connector view, map a supplied rear-view record to the correct cavity, and reject an unsupported fault claim based on the wrong terminal.
The short version
- Connector ID, cavity number, viewing face and orientation belong together.
- Wire color can support identification but cannot replace the applicable pin map.
- A correct number attached to the wrong cavity is not usable evidence.
One connector, two views
Our original J1 connector has four numbered cavities and a latch shown at the top. One drawing looks into its mating face.
The supplied record photo looks at its wire-entry side. The same physical cavities appear in different left-right positions.
The exercise provides both labeled views. Do not use a general mirror rule instead of the actual manufacturer view on a real connector.
| Supplied material | Orientation |
|---|---|
| Drawing view | Mating face / latch up |
| Photo view | Wire entry / latch up |
| Required match | Same cavity, not same screen corner |
Read the cavity labels in the stated view
In the fictional mating-face view, the upper row is 1 then 2, left to right. The lower row is 3 then 4.
J1.1 is return, J1.2 is request, J1.3 is supply and J1.4 is reserved. Those assignments apply only to this original drawing.
A diagram may use a different numbering pattern or perspective. Find its viewing note, latch and cavity labels rather than assuming this pattern.
| Mating face, latch up | Cavity and function |
|---|---|
| Upper left | J1.1 return |
| Upper right | J1.2 request |
| Lower left | J1.3 supply |
| Lower right | J1.4 reserved |
Map the wire-entry photo explicitly
The supplied rear view labels its upper row 2 then 1, and its lower row 4 then 3. J1.2 is now at the upper left.
The previous note calls the rear upper-right cavity J1.2. Comparing the labeled views identifies that cavity as J1.1 instead.
Keep the original photo and add the corrected cavity identity. Do not rewrite the reading as though a different point was measured.
| Wire-entry side, latch up | Cavity and function |
|---|---|
| Upper left | J1.2 request |
| Upper right | J1.1 return |
| Lower left | J1.4 reserved |
| Lower right | J1.3 supply |
Follow the net beyond the plug
Sheet C1 calls J1.2 REQUEST and continues that net on sheet C2 at controller input IN-R. The repeated net name joins those drawing locations.
That cross-reference tells you where the intended path goes. It does not prove continuity through a harness or that a signal reached the controller.
The exercise provides a separate record at IN-R when that comparison is needed. Never turn a drawing connection into an invented measurement.
Re-read the old zero without inventing a fault
The earlier zero was recorded at rear upper right against B1 negative. That is the return cavity in this example.
A zero between the return cavity and its stated reference does not establish a missing request. The original number may be accurate while its label is wrong.
A new supplied record identifies rear upper left, J1.2, and reports 12.40 V to B1 negative during request on.
| Supplied record | Meaning |
|---|---|
| Earlier record | Rear upper right /0.00 V |
| Correct cavity | J1.1 return |
| New supplied request record | J1.2 /12.40 V |
| Conclusion | Old request claim unsupported |
Use color as supporting detail
Two wires in the supplied harness are white. The old note says white wire zero volts without a cavity number.
That description cannot distinguish return from request. Add connector identity, face, cavity, reference and operating state.
If a wire color conflicts with the applicable diagram, record the discrepancy. Do not silently relabel the pin or assume the harness was never changed.
| Supplied record | Meaning |
|---|---|
| Weak record | White wire / zero |
| Traceable record | J1.2, rear upper left |
| Reference | B1 negative |
| Condition | Request on |
Keep the same discipline on a motor pair
The related slide-polarity activity has two motor terminals. Its supplied drawing defines which pair and polarity correspond to each virtual command.
Identify both endpoints before interpreting the sign. A reversed meter reference and a reversed motor command are different events.
The connector case asks you to repair the record, not a real harness. Physical connector service remains a separate qualified task.
| Supplied record | Meaning |
|---|---|
| Motor activity | Name both terminals |
| Meter sign | Depends on lead order |
| Command | Depends on supplied control logic |
| Limit | No real connector work taught |
Make the test point repeatable
Carry connector ID, cavity, face and orientation into the test record, along with the selected reference and condition.
A drawing states intended connections. Measurements and observations establish what happened in the recorded condition.
When orientation or identity is missing, request it. A confident pin guess can corrupt an otherwise accurate reading.
Shop tip
Josh: Describe the face and latch position before you name the pin. Can another person point to the same cavity?
Where this comes from
- Cummins Onan HGJBB (Spec A-B) Operator Manual A031C171; Issue 8, December 2018; printed 9-10 (PDF 15-16), related literature and model identification; checked 2026-11-04. Scope: Identity and document-purpose example only; no generator service procedure or specification is taught. https://www.cummins.com/sites/default/files/rv-manuals/A031C171.pdf
- OMRON General Purpose Relays: Explanation of Terms; Undated live manufacturer page; no revision shown; HTML Contact Section, Contact Symbols, Make Contacts and Break Contacts; checked 2026-11-04. Scope: NO/NC terminology and the need to read the drawing convention; the fictional connector and circuit legend are Rigprobe originals. https://www.ia.omron.com/support/guide/36/explanation_of_terms.html
- Original Rigprobe teaching examples, 2026-11-04. Identifiers, diagrams, connector layouts, timings and readings are invented problem data, not OEM drawings, specifications or universal acceptance limits.
Try it on a service call
Put the lesson to work on a hands-on troubleshooting case.