How do you translate SAE J1939 fault codes without changing what a heavy-duty truck, bus, agricultural machine or industrial engine is reporting? The most important terms are PGN, SPN, FMI, DM1, diagnostic trouble code and source address. They look like compact technical abbreviations, but each answers a different question about a message, a measured parameter, a failure mode or the electronic controller responsible for reporting it.
Someone searching for J1939 SPN FMI translation may be reading a fleet diagnostic printout, a multilingual workshop manual, a telematics alert or a maintenance report. A sentence such as ‘engine sensor problem’ can be dangerously vague if the source actually distinguishes voltage above normal from voltage below normal, a data update-rate problem or an operator protection event. Accurate translation preserves that technical structure while explaining it in accessible language.
This guide shows how to localize SAE J1939 PGNs, SPNs, FMIs, DM1 and DM2 diagnostic messages, occurrence counts and warning-lamp labels without rewriting the underlying code. It also explains when a fault is active versus stored, why source-address context matters, and how to keep proprietary parameter definitions from being mistaken for universal codes. The aim is faithful technical reading, not remote fault diagnosis.
Did you know that one SPN can appear with different FMIs and therefore indicate different suspected failure conditions? The SPN generally points to the parameter, while the FMI provides the failure-mode information. A repair document that translates only the parameter name loses a piece of the original evidence. Equally, a message from one controller should not be casually attributed to every controller on the network.
The examples below are illustrative translation exercises. Do not use them as a vehicle-specific troubleshooting guide, a replacement for current licensed SAE publications or a basis for bypassing safety systems. OEM service information, diagnostic procedures and qualified technicians govern real maintenance decisions.
J1939 terminology, diagnostics and translation decisions
1. A PGN identifies a parameter group, not a broken component
A Parameter Group Number identifies a J1939 message’s parameter-group definition. It organizes how signals are represented and does not by itself indicate that a diagnostic trouble is active. In technical communication, a code is a pointer to a definition, not a synonym for a component. A useful translation preserves that pointer and supplies only the description justified by the standard or the vehicle manufacturer.
Translate the phrase ‘parameter group’ consistently and preserve the numerical PGN. When multiple messages share a family of related measurements, each PGN still has its own formal layout. Before release, verify the code tuple against its original diagnostic export, the vehicle model and the correct approved definition. Never change the numeric tuple merely because a localized label sounds better.
Example: ‘PGN 65226 / DM1’ refers to the active diagnostic message. A translator must not rewrite PGN as a diagnostic sensor number or mistake the message identity for the specific failed parameter. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
2. An SPN identifies a suspect parameter or reported signal
A Suspect Parameter Number is a standardized or potentially manufacturer-specific identifier associated with a parameter. In a fault code, it tells the reader which monitored quantity or subsystem the diagnostic record concerns. Think like a workshop reader comparing two printouts. Which controller spoke, which parameter was involved, what failure mode was identified and when? A translated field has passed if those answers remain reconstructable.
Keep SPN and its number intact. Translate the accompanying parameter name using verified technical terminology rather than a guessed everyday synonym. Some SPNs require an OEM definition. A reviewer should be able to copy the original PGN, SPN and FMI back into the authorised diagnostic system and obtain the same record. If not, the translation has broken traceability.
Example: ‘SPN ####’ in a service log should remain the precise numeric identifier. Do not invent a named sensor merely because a similar code appears in a generic Internet table. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
3. An FMI explains the failure-mode category
The Failure Mode Identifier characterizes how a reported parameter or condition is abnormal: examples include a high or low voltage, an out-of-range signal, missing information or another specified category. A compact label can hide several different layers: CAN transport, parameter definition, diagnostic interpretation and maintenance action. Explain the layers separately so a fluent paragraph does not flatten the evidence.
Preserve the FMI number and the precise approved description. A wrong failure-mode translation can redirect a technician from a possible open circuit to a different diagnostic route. Check whether the translated sentence asserts a failed part, a root cause or a completed repair when the source only describes a monitored signal. Those are different propositions.
Example: ‘SPN X FMI 3’ is not equivalent to ‘SPN X FMI 4’. Even if the SPN number is identical, the source distinguishes different failure modes. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
4. The DTC is a structured record, not one arbitrary number
A J1939 diagnostic trouble code contains multiple elements including SPN, FMI, occurrence count and a conversion-method field in its standard encoding. A display may flatten this into one human-readable line. Do not change a machine-readable code to suit the target language’s natural word order. Instead keep the numeric or hexadecimal token intact and translate the surrounding description.
Translate the components as components and preserve the code tuple. A label such as ‘error code 123’ is insufficient if it drops the FMI, controller or count required to interpret the record. When publishing a bilingual table, keep a separate column for the original diagnostic label. The target-language gloss can be longer, but should not obscure the machine-readable reference.
Example: ‘SPN 1234 FMI 5 OC 2’ should not be summarized as ‘1234 error’. The additional fields carry information needed by the authorised diagnostic workflow. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
5. DM1 means active diagnostic trouble information
Diagnostic Message 1 is used for current active faults and lamp-status information. It is typically broadcast while a relevant fault is active, with implementation-specific considerations and message changes. The goal is not to make the alert sound less alarming or more alarming. It is to convey the precise state and safety-relevant wording that the authorised source actually supplied.
Render ‘active’ as the status of the diagnostic record, not necessarily that a machine is moving or a malfunction is present at every millisecond. The timestamp and source controller matter. Where an operator instruction is involved, review its verb strength and conditions against the approved service or safety information. Do not substitute generic repair advice.
Example: ‘DM1 current faults at 09:14’. Keep the word current in that context; do not translate the entry as a permanent repair history. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
6. DM2 concerns previously active diagnostic trouble codes
DM2 is associated with previously active trouble codes that have been stored for retrieval. A stored diagnostic does not necessarily describe an active condition at the moment a mechanic reads it. When the original provides no OEM definition, an honest blank or unresolved flag is better than an impressive but unsupported expansion of the acronym.
Distinguish ‘previously active’, ‘stored’ and ‘current’ carefully. Never infer that a historic record means the fault was repaired; it may simply no longer meet the active condition. Review units, timestamps, number bases and source-controller identity. A simple formatting error can be as damaging as a vocabulary error.
Example: ‘DM2 records from last service interval’. The translation should not call them live alarms without a contemporaneous DM1 or other current evidence. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
7. Occurrence count is not a clock or severity score
The occurrence count field helps indicate a count of diagnostic occurrences as represented by the controller. It is not a duration in hours and does not independently establish how severe or dangerous a fault is. A text string that appears in diagnostic software may be translated twice: once by the software vendor and once in a fleet’s local dashboard. Keep a chain back to the source export where possible.
Preserve OC and its value; translate the count in the diagnostic context. If a service tool displays a related recurrence counter with a different definition, do not assume the two are interchangeable. Mark proprietary or unresolved descriptions clearly, with a query owner and source reference. Do not let a guessed meaning enter the terminology database as an accepted translation.
Example: ‘OC 5’ means the reported diagnostic occurrence count is five under that system’s rules. It does not mean five minutes or a 5/10 severity rating. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
8. Source address identifies which controller reported the message
J1939 uses source-address information in the extended CAN identifier. Multiple electronic control units may send diagnostic messages, so their source addresses are essential to attributing data correctly. Pay attention to the difference between a data record and an explanation of that record. A translator can add educational context while identifying that context as commentary rather than machine output.
Translate the ECU name where verified and preserve the source-address value. A telematics system that drops the address may merge messages from distinct controllers into one apparently coherent list. If the output will appear on a small dashboard, test truncation and line wrapping. ‘Not active’ must not lose ‘not’ when the interface narrows.
Example: ‘DM1 from source address 0x03’ should stay associated with that source. Do not automatically label every warning as ‘engine ECU’ if the network includes other systems. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
9. Priority and address fields are not human severity labels
The 29-bit identifier includes a priority field used in arbitration. Its technical communication role is separate from whether a fault is safety-critical or maintenance-relevant. Software and protocol versions determine what a label means. A glossary entry should cite its applicable source so a later editor does not generalize it to equipment for which it was never defined.
Translate ‘priority’ in a way that does not imply the operator should rank fault urgency simply by CAN arbitration priority. A diagnostic severity assessment uses other information. Distinguish error-state markers from extreme physical measurements. Present unavailable states as states, not fabricated numeric values.
Example: ‘CAN identifier priority 3’ is not the same as ‘third most urgent breakdown’. The number governs message handling, not a universal incident-severity scale. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
10. CAN identifiers and PGNs occupy related but different layers
A raw extended CAN identifier includes information from which a PGN and source address can be extracted. Decoding also depends on whether the message is destination-specific or broadcast and how its fields are defined. A serious quality review compares numeric fields, source addresses, status words and human instructions independently. Passing grammar alone is not enough when messages influence maintenance decisions.
Preserve both raw hexadecimal identifiers and any decoded PGN. They are not interchangeable textual names, and a translated report must not erase the original byte-level reference. Keep all source qualifiers—intermittent, previously active, requested, observed and estimated—attached to the field they qualify.
Example: ‘CAN ID 18FECA00 / PGN 65226’ links transport representation to a diagnostic message. Translate the surrounding explanation without altering the hex characters. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
11. The byte order and bit positions belong to the specification
Many J1939 parameter definitions include start positions, lengths, scaling and offsets. Swapping endianness or misreading bit positions can produce plausible but incorrect physical values. In technical communication, a code is a pointer to a definition, not a synonym for a component. A useful translation preserves that pointer and supplies only the description justified by the standard or the vehicle manufacturer.
Do not reformat bytes as prose. If the translation includes a decoding explanation, verify it against the exact parameter definition and version of the referenced standard. Before release, verify the code tuple against its original diagnostic export, the vehicle model and the correct approved definition. Never change the numeric tuple merely because a localized label sounds better.
Example: ‘raw bytes 01 FF 80’ is a byte sequence, not a decimal identifier. Spaces can improve legibility, but the order and data values must remain exact. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
12. Scaling and offset define the physical measurement
Raw values may require multiplying by a resolution and applying an offset to obtain the displayed physical quantity. The resulting number has units and sometimes special status values. Think like a workshop reader comparing two printouts. Which controller spoke, which parameter was involved, what failure mode was identified and when? A translated field has passed if those answers remain reconstructable.
Translate scale, offset and engineering unit together. A decoded engine temperature or speed is not simply the raw integer copied from a CAN frame. A reviewer should be able to copy the original PGN, SPN and FMI back into the authorised diagnostic system and obtain the same record. If not, the translation has broken traceability.
Example: ‘resolution 0.125 rpm/bit’ identifies a decoding coefficient. Omitting /bit changes the definition; presenting the raw number as revolutions per minute is another mistake. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
13. Not-available codes are data states, not real measurements
Specific bit patterns can represent unavailable or error states under a parameter definition. Rendering them as unusually high physical readings can create false alarms or misleading trend charts. A compact label can hide several different layers: CAN transport, parameter definition, diagnostic interpretation and maintenance action. Explain the layers separately so a fluent paragraph does not flatten the evidence.
Retain the state designation and avoid fabricating numeric measurements. A localized table should show blank or unavailable only according to its data-handling rules, not through an undocumented conversion. Check whether the translated sentence asserts a failed part, a root cause or a completed repair when the source only describes a monitored signal. Those are different propositions.
Example: ‘signal not available’ should not become ‘zero speed’ or a physically extreme temperature. Absence of a valid measurement is a different claim. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
14. Warning lamps convey operator-facing statuses
DM1 lamp indicators can include malfunction, red stop, amber warning and protect functions under relevant system definitions. The names and behavior should be cross-checked against the OEM display and safety instructions. Do not change a machine-readable code to suit the target language’s natural word order. Instead keep the numeric or hexadecimal token intact and translate the surrounding description.
Translate each lamp label with consistent, safety-conscious terminology. Do not substitute ‘maintenance due’ for ‘stop’ or assume color names alone capture the prescribed response. When publishing a bilingual table, keep a separate column for the original diagnostic label. The target-language gloss can be longer, but should not obscure the machine-readable reference.
Example: ‘Red Stop Lamp requested’ is not a casual suggestion to schedule service next week. The translation must retain the warning category and refer the actual response to the OEM manual. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
15. Active status and lamp illumination are related but distinct
A controller may report diagnostic records and lamp states as separate data fields. A diagnostic entry does not justify inventing a lamp indication that was not recorded. The goal is not to make the alert sound less alarming or more alarming. It is to convey the precise state and safety-relevant wording that the authorised source actually supplied.
Keep diagnostic state and operator display state in separate columns. An alarm monitoring dashboard may suppress, map or aggregate some messages, so source and derived display should remain distinguishable. Where an operator instruction is involved, review its verb strength and conditions against the approved service or safety information. Do not substitute generic repair advice.
Example: ‘DM1 active DTC listed; lamp state unavailable’ should not be translated as ‘red light flashing’. The lamp evidence was not supplied. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
16. Diagnostic timestamps require time-zone context
Telematics tools may record times in UTC while repair shops read local wall time. DST shifts, missing offsets and device-clock errors can confuse the chronology of active and stored faults. When the original provides no OEM definition, an honest blank or unresolved flag is better than an impressive but unsupported expansion of the acronym.
Keep timezone information and original timestamp precision. If a localized timestamp is calculated, label the conversion and preserve the original source value for audit. Review units, timestamps, number bases and source-controller identity. A simple formatting error can be as damaging as a vocabulary error.
Example: ‘2026-10-29T05:00:00Z’ is UTC. A translated maintenance log should not present it as 05:00 local workshop time without an actual conversion. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
17. Fault clearance is not the same as physical repair
A code can stop being active or be cleared from storage without proof that the underlying problem has been corrected. Different controllers may implement diagnostic aging or storage rules. A text string that appears in diagnostic software may be translated twice: once by the software vendor and once in a fleet’s local dashboard. Keep a chain back to the source export where possible.
Translate ‘inactive’, ‘cleared’, ‘resolved’ and ‘repaired’ distinctly. Those words represent different states or actions, and treating them as interchangeable can make a maintenance record falsely reassuring. Mark proprietary or unresolved descriptions clearly, with a query owner and source reference. Do not let a guessed meaning enter the terminology database as an accepted translation.
Example: ‘DTC cleared following test’ records an action. It does not, by itself, establish that a defective wire was replaced or that recurrence is impossible. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
18. Proprietary SPNs and OEM overlays need source ownership
Manufacturers may assign proprietary diagnostics or interpret standard parameter data in product-specific contexts. A generic table cannot establish every possible OEM message’s meaning. Pay attention to the difference between a data record and an explanation of that record. A translator can add educational context while identifying that context as commentary rather than machine output.
When a number is proprietary or unknown, mark its description as unresolved rather than substituting an online match for another make. Record the OEM model and software release. If the output will appear on a small dashboard, test truncation and line wrapping. ‘Not active’ must not lose ‘not’ when the interface narrows.
Example: ‘Manufacturer-specific SPN shown without definition’. A safe translation keeps the code and asks for the manufacturer’s service dictionary. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
19. A fleet dashboard’s wording may be an interpretation
Telematics systems often transform raw PGN/SPN/FMI data into short labels, severity badges and maintenance narratives. Those UI labels are useful but are not the raw wire-level message. Software and protocol versions determine what a label means. A glossary entry should cite its applicable source so a later editor does not generalize it to equipment for which it was never defined.
Translate the UI copy for clarity while retaining a path back to the original data. If a dashboard infers urgency, identify it as the system’s classification rather than a formal SAE parameter. Distinguish error-state markers from extreme physical measurements. Present unavailable states as states, not fabricated numeric values.
Example: ‘Check engine soon’ may be a derived product message. The precise diagnostic tuple should remain available to authorised technicians. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
20. Diagnostic trouble codes are not universal OBD-II P-codes
J1939 SPN/FMI representations differ from familiar passenger-car OBD-II codes such as P0xxx. Some tools display both, but translation must not turn one coding scheme into the other by analogy. A serious quality review compares numeric fields, source addresses, status words and human instructions independently. Passing grammar alone is not enough when messages influence maintenance decisions.
Keep the original code family visible. If the report includes an OEM cross-reference, treat it as a documented mapping rather than a direct word translation. Keep all source qualifiers—intermittent, previously active, requested, observed and estimated—attached to the field they qualify.
Example: ‘SPN/FMI record’ should not be renamed ‘P-code’ solely to make the interface recognizable to a car owner. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
21. Heavy vehicles may contain many network segments
A complex machine can have engine, transmission, aftertreatment, braking, body and implement controllers. Network gateways may bridge or filter messages between segments. In technical communication, a code is a pointer to a definition, not a synonym for a component. A useful translation preserves that pointer and supplies only the description justified by the standard or the vehicle manufacturer.
Translate gateway and controller names according to source system architecture. The absence of a message in one log does not prove the corresponding subsystem has no diagnostic record. Before release, verify the code tuple against its original diagnostic export, the vehicle model and the correct approved definition. Never change the numeric tuple merely because a localized label sounds better.
Example: ‘Gateway logs powertrain J1939 network’. Do not call it a comprehensive whole-vehicle inspection without evidence of all relevant networks. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
22. Aftertreatment diagnostics require exact subsystem naming
Engine exhaust aftertreatment can involve SCR, DPF, sensors, dosing and related controls. Similar English warning labels can conceal very different suspected components or failure conditions. Think like a workshop reader comparing two printouts. Which controller spoke, which parameter was involved, what failure mode was identified and when? A translated field has passed if those answers remain reconstructable.
Do not turn a structured SPN/FMI pair into a generic exhaust problem if the authorised definition is available. Preserve the relevant subsystem, parameter and failure mode separately. A reviewer should be able to copy the original PGN, SPN and FMI back into the authorised diagnostic system and obtain the same record. If not, the translation has broken traceability.
Example: ‘NOx sensor communication abnormal’ is different from ‘NOx emissions exceeded’. The words indicate distinct issues and must not be substituted. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
23. Protocol versions and data dictionaries are part of traceability
SAE publications and their digital annexes evolve. Diagnostic software may rely on specific parameter dictionaries and OEM extensions, so a translation can be misleading if it silently updates definitions. A compact label can hide several different layers: CAN transport, parameter definition, diagnostic interpretation and maintenance action. Explain the layers separately so a fluent paragraph does not flatten the evidence.
Record the standard edition, DBC version or vendor database reference when the source provides it. A newer public page should not silently overrule the version used by the actual equipment. Check whether the translated sentence asserts a failed part, a root cause or a completed repair when the source only describes a monitored signal. Those are different propositions.
Example: ‘Decoded using fleet diagnostic database version 6.2’. Preserve the version and avoid retrofitting another table’s interpretation without review. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
24. DM1 multi-packet handling can affect completeness
Diagnostic messages containing multiple trouble codes can exceed the data capacity of a single classic CAN frame and require transport-protocol handling. An incomplete capture may omit faults. Do not change a machine-readable code to suit the target language’s natural word order. Instead keep the numeric or hexadecimal token intact and translate the surrounding description.
When a log says partial, truncated or transport reassembly failed, translate that qualification rather than presenting an incomplete list as a complete diagnostic summary. When publishing a bilingual table, keep a separate column for the original diagnostic label. The target-language gloss can be longer, but should not obscure the machine-readable reference.
Example: ‘DM1 multi-packet frame loss, decode incomplete’. The correct user-facing output is an explicitly incomplete diagnostic view. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
25. A maintenance note needs the exact observed code
Technicians may translate a user’s symptom report, read the diagnostic snapshot and test a suspected fault. These are three separate records that should not be merged into one authoritative diagnosis. The goal is not to make the alert sound less alarming or more alarming. It is to convey the precise state and safety-relevant wording that the authorised source actually supplied.
Preserve symptom, observed DTC and action taken as distinct fields with timestamps. A bilingual workshop record gains clarity when the sequence of evidence is visible. Where an operator instruction is involved, review its verb strength and conditions against the approved service or safety information. Do not substitute generic repair advice.
Example: ‘Driver reports loss of power; tool reads SPN/FMI; technician inspects harness’. The initial report is not proof of the harness fault. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
26. Occurrence history needs a denominator and context
A count of diagnostic occurrences across a service interval may suggest recurrence, but no universal inference about frequency is possible without duration, sample window and controller rules. When the original provides no OEM definition, an honest blank or unresolved flag is better than an impressive but unsupported expansion of the acronym.
Translate terms such as ‘since last clear’, ‘active now’, ‘stored’ and ‘per trip’ exactly as used. A reader should know what time interval an indicator actually summarizes. Review units, timestamps, number bases and source-controller identity. A simple formatting error can be as damaging as a vocabulary error.
Example: ‘OC 7 since last reset’ is not ‘seven failures today’. The time-bounded qualification changes the interpretation. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
27. Numeric, hexadecimal and binary representations need separate labels
A PGN can appear in decimal and hexadecimal; a CAN ID often appears in hex. Those representations can be equivalent under a known conversion, but not if numbers are merely copied under different labels. A text string that appears in diagnostic software may be translated twice: once by the software vendor and once in a fleet’s local dashboard. Keep a chain back to the source export where possible.
Write decimal versus hexadecimal where necessary and protect leading zeros and prefix syntax. Never assume the target reader will recognize a base from typography alone. Mark proprietary or unresolved descriptions clearly, with a query owner and source reference. Do not let a guessed meaning enter the terminology database as an accepted translation.
Example: ‘PGN 65226 = 0xFECA’. Keep both labels and values as a checked representation, not two independent identifiers. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
28. Multilingual operator alerts must retain their instructions
Some diagnostics produce instructions to stop, reduce load, check a system or contact service. A translator must preserve imperative strength and conditions while avoiding invented repair guidance. Pay attention to the difference between a data record and an explanation of that record. A translator can add educational context while identifying that context as commentary rather than machine output.
The appropriate localized phrase follows the actual source manual and the product’s user-interface constraints. Literal translation can be too weak or too strong if it changes the safety action. If the output will appear on a small dashboard, test truncation and line wrapping. ‘Not active’ must not lose ‘not’ when the interface narrows.
Example: ‘Stop engine when safe and consult manual’ must not be shortened to ‘check engine’ or lengthened into an unverified service procedure. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
29. Missing or conflicting codes require a query
A blurry photograph might obscure FMI 3 versus FMI 8, or a spreadsheet could label an SPN differently from the source service software. Choosing one interpretation by intuition is not justified. Software and protocol versions determine what a label means. A glossary entry should cite its applicable source so a later editor does not generalize it to equipment for which it was never defined.
Record the contradiction and request the original diagnostic export or approved OEM reference. The translated report should not hide uncertainty behind polished prose. Distinguish error-state markers from extreme physical measurements. Present unavailable states as states, not fabricated numeric values.
Example: ‘FMI unreadable, appears 3 or 8’ belongs in a query log until a valid source is obtained. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
30. A translator should not become the repair authority
Faithful translation carries observed codes, approved definitions, chronology, warnings and the limits of the source. It does not certify that an engine is safe, identify a failed component without testing or authorise bypassing an interlock. A serious quality review compares numeric fields, source addresses, status words and human instructions independently. Passing grammar alone is not enough when messages influence maintenance decisions.
Document what was reported, who interpreted it and which maintenance instruction was used. This separation helps a workshop act responsibly across language boundaries. Keep all source qualifiers—intermittent, previously active, requested, observed and estimated—attached to the field they qualify.
Example: ‘Diagnostic summary translated from OEM software export’. That statement should not imply the translator performed hardware tests or approved the vehicle for release. The editorial decision is to preserve this exact layer of evidence without promoting it into a conclusion about repair, safety or the identity of a defective part. A multilingual reader should be able to recover the original diagnostic code and its documented meaning.
Eighteen field handover scenarios
Situation 1: A bus fleet receives an SPN/FMI alert
The transport manager’s summary names the SPN and the failure mode. The translation keeps both codes and sends the repair team to the model-specific service information, rather than diagnosing a sensor solely from a dashboard label. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 2: A workshop scans DM1 and DM2
Active and previously active records appear side by side. The bilingual report distinguishes them and retains the time of capture, so a reviewer does not treat every historic entry as a current fault. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 3: An OEM proprietary code is absent from a public table
The translator records the numeric code and asks for the manufacturer’s dictionary. Borrowing an appealing description from a different vehicle could produce a false repair instruction. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 4: Two ECUs emit the same diagnostic number
Source address determines which controller reported each entry. A combined dashboard can conceal that distinction, so the exported translation includes the source column. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 5: A lamp icon is red but no status data survive
The screenshot may not show whether the lamp was requested by the ECU or drawn by the app. The translated narrative describes the screenshot rather than inventing wire-level lamp status. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 6: A logger misses a multi-packet diagnostic message
The capture shows incomplete reassembly. A multilingual report says some diagnostic information may be missing, not that the machine had zero other faults. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 7: A code appears in hexadecimal and decimal
The service tool uses a hex PGN while a spreadsheet uses decimal. A checked conversion confirms they refer to the same number. A field label differentiates them so future users do not treat them as separate errors. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 8: A dealer asks for English-only fault text
The customer sees a local-language symptom but the support desk requires numeric SPN and FMI. The translator supplies the approved English descriptor and both numbers, preserving cross-language traceability. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 9: A stored code has been cleared
The maintenance log records clearance after testing. The translation says the record was cleared, without claiming that replacement parts were installed or no fault can recur. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 10: A driver reports a smell and loss of power
The driver’s observations, the ECU diagnostic and the technician’s later finding are separate evidence. A bilingual report retains that chronology instead of turning a human symptom into a verified ECU event. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 11: A dashboard groups unrelated fault categories
The application calls several issues ‘Powertrain attention required’. The exported translation should still preserve the underlying controller, SPN, FMI and lamp state where available. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 12: A fault count looks like a severity number
A display shows OC 12, which another language might mistake for risk level 12. The note explicitly identifies occurrence count and does not translate it as urgency or duration. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 13: The source contains a missing-value marker
A parameter bit pattern represents unavailable data. A target-language table should label it unavailable rather than showing a suspiciously large physical temperature or pressure. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 14: Maintenance staff compare different software versions
The old diagnostic application has a different text label for a proprietary SPN. The report records the source dictionary version and escalates the difference instead of silently harmonizing them. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 15: A remote team needs an operator warning
An operator-facing instruction should be translated from the vehicle’s authorised manual, not generated from a generic fault-code search. The same SPN/FMI can require context-specific safety procedures. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 16: A technician sends only a photograph
Glare obscures an FMI digit and the ECU name. The translator flags both missing fields and requests the raw diagnostic export rather than guessing from visual resemblance. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 17: A team compares intermittent alarms
Timestamp, source address, active/stored status and OC are needed to distinguish a recurring signal from multiple controllers’ reports. The translation should preserve those facets as separate columns. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
Situation 18: A repair order is closed
The repair status comes from the maintenance system, not from the J1939 frame alone. Translate ‘job completed’ as a workflow result and keep the diagnostic observations intact. The bilingual handover should document which parts came from the source export and which are explanatory commentary. That boundary prevents a helpful translation from becoming an unsupported diagnostic claim.
A practical technical-translation workflow
Obtain the raw diagnostic export if possible, not only a cropped screenshot. Preserve the ECU or source-address context, capture time, DM category, SPN, FMI, occurrence count and any lamp indicators. Identify the model, software version and relevant standard or OEM dictionary. Translate approved English descriptions into the target language, leaving identifiers unchanged. Where a code has no approved definition, use a visible unresolved status rather than guessing.
Run a two-pass review. A language reviewer checks readability, terminology and the strength of instructions; a data reviewer checks decimal/hex representation, number order, controller identity, fault status and timestamps. Then test the delivered format—PDF, spreadsheet, app string or printed repair record—to ensure that long labels have not been truncated and right-to-left scripts have not reordered numeric codes.
Keep three output layers: the exact source evidence, a faithful translation of the official description, and clearly marked educational explanation. This structure gives operators comprehensible language while preserving the technical record needed by engineers and service departments. If the source itself conflicts, request an authoritative clarification rather than editing the message to appear consistent.
Frequent questions
Can an SPN alone identify a failed part? Not reliably. It identifies a parameter or suspect area; the FMI and authorised diagnostic procedure add necessary context, and further testing may be required.
Is DM2 an active-fault report? DM2 is associated with previously active diagnostic codes. It should not be described as a live DM1 condition without corroborating evidence.
Is occurrence count a severity score? No. It represents a count in the diagnostic reporting scheme. Its relationship to timing or seriousness cannot be inferred without context.
Do two vehicles with the same SPN necessarily require the same repair? Not necessarily. Application, FMI, software version, controller and manufacturer-specific diagnostic procedures matter.
Can a translation include troubleshooting instructions? It can faithfully translate instructions that were actually supplied and approved. It should not invent new repair or safety instructions based only on a code label.
Further learning
This component-level J1939 guide belongs beside, not above, the general How English Works translation pathway and the protected Vocabulary Learning Hub.
Technical references: CSS Electronics on DM1 and the SPN/FMI/OC structure and the J1939 message and PGN tutorial. Use the applicable SAE J1939 publications and manufacturer documentation as the authoritative sources for actual code definitions.