ECU diagnostic CAN addresses: Difference between revisions

From BigJimny Wiki
Jump to navigation Jump to search
SZ Viewer DTC scan (14 Nov): ECM mode 01 supported PIDs, modes 03/07/0A, extra 1A/18 replies (VIN via 1A 90, not shown); 0x79A and 0x799 refusals; 25 more addresses with no reply
SZ Viewer tab captures (14 Nov): ECM 21 00 layout (incl. fuel level), BCM 21 08 (outside temp), EPS 21 08, SRS and 4WD 22 10 00 partial layouts, multi-PID mode 01, TPMS temp numbering
Line 140: Line 140:
|-
|-
| <code>18 00 00 00</code>, <code>18 00 40 00</code>, <code>18 00 80 00</code>, <code>18 00 C0 00</code>, <code>18 00 FF FF</code> || <code>7F 18 12</code> || Refused. SZ Viewer tries each of these in turn; only <code>18 00 FF 00</code> is accepted (captured)
| <code>18 00 00 00</code>, <code>18 00 40 00</code>, <code>18 00 80 00</code>, <code>18 00 C0 00</code>, <code>18 00 FF FF</code> || <code>7F 18 12</code> || Refused. SZ Viewer tries each of these in turn; only <code>18 00 FF 00</code> is accepted (captured)
|-
| <code>21 00</code> || <code>61 00</code> + 208 bytes (210 in total) || Live data block, layout below. SZ Viewer (Engine tab) repeats it about every 0.4 s (captured, partly decoded)
|-
| <code>21 50</code>, <code>21 51</code>, <code>21 52</code>, <code>21 53</code>, <code>21 55</code>, <code>21 70</code>, <code>21 71</code>, <code>21 90</code> || <code>7F 21 12</code> || Refused: local ID not supported. SZ Viewer tries each once when the Engine tab opens (captured)
|}
|}
=== ECM data block (21 00) layout ===
Decoded from a PCAN-View capture taken while the SZ Viewer app (Engine tab) was polling the ECM on 14 November 2026, engine idling with a few blips of the throttle, car stationary. ''Matches SZ Viewer'' means the formula reproduces the value on the SZ Viewer screen from that capture. Everything else is inferred.
Byte numbers count from the <code>61</code> at the start of the reply (byte 0). The ''letter'' column is the variable name for Torque Pro and Car Scanner custom PIDs, where A is the first byte after <code>61 00</code> (A = byte 2). Bytes not listed were <code>FF</code> (unused) or did not change.
{| class="wikitable"
! Byte !! Letter !! Example (hex) !! Meaning !! Formula !! Status
|-
| 2–5 || A–D || <code>00 07 E1 80</code> || Monitor status, the same four bytes as OBD PID 01 || – || Matches SZ Viewer (OBD-II tab)
|-
| 17 || P || <code>02</code> || Fuel system status: <code>02</code> = closed loop || – || Matches SZ Viewer ("Closed loop (Sensor)")
|-
| 19 || R || <code>81</code> || Short-term fuel trim || (R − 128) / 1.28 % (0.781 %) || Matches SZ Viewer
|-
| 20 || S || <code>77</code> || Long-term fuel trim || (S − 128) / 1.28 % (−7.031 %) || Matches SZ Viewer
|-
| 23 || V || <code>79</code> || Total fuel trim. Not exactly the sum of the two trims above || (V − 128) / 1.28 % (−5.469 %) || Matches SZ Viewer
|-
| 25–26 || X–Y || <code>09 59</code> || Injection time || (X × 256 + Y) / 1000 ms (2.393 ms) || Matches SZ Viewer
|-
| 29 || AB || <code>87</code> || Ignition advance || AB / 2 − 64 degrees (3.5°), the same formula as OBD PID 0E || Matches SZ Viewer
|-
| 36 || AI || <code>37</code> || Rises from 54 to 70 when the throttle is opened. Perhaps engine load || – || Inferred
|-
| 37–38 || AJ–AK || <code>0C A0</code> || Engine speed || (AJ × 256 + AK) / 4 rpm || Matches SZ Viewer
|-
| 42 || AO || <code>00</code> || Vehicle speed || AO km/h || Matches SZ Viewer (0 km/h only)
|-
| 43 || AP || <code>1E</code> || Intake manifold absolute pressure || AP kPa (30 kPa) || Matches SZ Viewer
|-
| 44 || AQ || <code>63</code> || Coolant temperature || AQ − 40 °C (59 °C) || Matches SZ Viewer
|-
| 45 || AR || <code>34</code> || Intake air temperature || AR − 40 °C (12 °C) || Matches SZ Viewer
|-
| 46 || AS || <code>64</code> || Barometric pressure || AS kPa (100 kPa = 750 mmHg). SZ Viewer's "Rel. pressure" (−0.7 bar) is MAP minus this value || Matches SZ Viewer
|-
| 60 || BI || <code>2A</code> || Rises from 41 to 57 when the throttle is opened. Unknown || – || –
|-
| 66 || BM || <code>08</code> || Throttle position || BM / 2.55 % (3.137 %). Byte 67 carries the same value || Matches SZ Viewer
|-
| 76 || BW || <code>1A</code> || Upstream oxygen sensor (sensor 1) || BW × 0.005 V (0.13 V), the same scaling as OBD PID 14 || Matches SZ Viewer
|-
| 77 || BX || <code>98</code> || Downstream oxygen sensor (sensor 2) || BX × 0.005 V (0.76 V) || Matches SZ Viewer
|-
| 99–100 || CT–CU || <code>38 B0</code> || Battery (control module) voltage || (CT × 256 + CU) / 1000 V (14.512 V), the same value as OBD PID 42 || Matches SZ Viewer
|-
| 101 || CV || <code>D6</code> || Fuel tank level || CV / 2.55 % (83.922 %) || Matches SZ Viewer
|-
| 105 || CZ || <code>56</code> || Rises from 85 to 134 when the throttle is opened. Unknown || – || –
|-
| 113 || DH || <code>2D</code> || Battery temperature || DH − 40 °C (4 °C on the temperature tab) || Matches SZ Viewer
|}
Notes:
* The fuel tank level (byte 101) is not available as a standard OBD PID on this car (PID 2F is not supported), so this block is the only known source for it.
* SZ Viewer also shows "Injector: 0.97 min/hour". No byte has been matched to it; it may be calculated from the injection time and engine speed.
* SZ Viewer requests this block with flow control <code>30 00 08</code> (8 ms between frames). The first request of a session used <code>30 00 00</code> and also worked.


=== Standard OBD (mode 01) PIDs supported ===
=== Standard OBD (mode 01) PIDs supported ===
Line 159: Line 221:
|}
|}


Not supported, so not available to OBD apps through standard PIDs: mass air flow (10; the engine works from MAP), fuel tank level (2F), ambient air temperature (46), engine oil temperature (5C) and odometer (A6).
Not supported, so not available to OBD apps through standard PIDs: mass air flow (10; the engine works from MAP), fuel tank level (2F), ambient air temperature (46), engine oil temperature (5C) and odometer (A6). The fuel level and outside temperature can be read from the [[#ECM data block (21 00) layout|ECM]] and [[#BCM data block (21 08) layout|BCM]] data blocks instead.
 
The ECM accepts up to six PIDs in one request. SZ Viewer's OBD-II tab polls with <code>01 01 03 04 05 06 07</code>, <code>01 0B 0C 0D 0E 0F 11</code>, <code>01 13 14 15 1C 1F 21</code>, <code>01 2E 30 31 33 42 43</code>, <code>01 45 47 49 4A 4C 5E</code> and <code>01 9D</code>, and gets every value back in a single (multi-frame) reply, for example <code>41 0B 24 0C 0C C6 0D 00 0E 86 0F 34 11 23</code> (captured).


Other standard requests in the same scan:
Other standard requests in the same scan:
Line 244: Line 308:
|-
|-
| <code>18 00 FF 00</code> || <code>58 00</code> || DTCs: none stored (captured)
| <code>18 00 FF 00</code> || <code>58 00</code> || DTCs: none stored (captured)
|-
| <code>21 08</code> || <code>61 08</code> + 40 bytes (42 in total) || Live data block, partly decoded below. Polled continuously by SZ Viewer's PS tab (captured)
|}
|}
=== EPS data block (21 08) layout ===
Decoded from a PCAN-View capture of the SZ Viewer PS tab on 14 November 2026, engine idling, wheel not turned. Byte numbers count from the <code>61</code> (byte 0); letter A = byte 2.
Example reply: <code>61 08 7F 9D FF FF 00 0F DD 7C CD 80 80 81 00 00 00 C8 26 FF 13 FF 10 04 C1 13 80 33 33 FF FF 00 45 FF FF FF FF 00 00 5E 4D 44</code>
{| class="wikitable"
! Byte !! Letter !! Example (hex) !! Meaning !! Formula !! Status
|-
| 9 || H || <code>7C</code> || Varied between 112 and 124 during the capture. Unknown || – || –
|-
| 10 || I || <code>CD</code> || Battery voltage || I × 0.07 V (14.35 V) || Matches SZ Viewer
|-
| 13 || L || <code>81</code> || Changed between <code>81</code> and <code>82</code>. Perhaps the control torque (0.061 Nm on the screen) || – || Inferred
|-
| 18 || Q || <code>27</code> || Engine speed || Q × 20 rpm (780 rpm) || Matches SZ Viewer
|}
The screen also shows sensor supply 4.984 V, main and sub torque 0.002 Nm, motor currents 0 A and motor drive voltages 0.968 V. None of these has been matched to a byte yet; a capture while turning the wheel should show the torque and current bytes.


== 0x271 Body control module ==
== 0x271 Body control module ==
Line 260: Line 344:
|-
|-
| <code>18 00 FF 00</code> || <code>58 00</code> || DTCs: none stored (captured)
| <code>18 00 FF 00</code> || <code>58 00</code> || DTCs: none stored (captured)
|-
| <code>21 08</code> || <code>61 08</code> + 100 bytes (102 in total) || Live data block, partly decoded below. SZ Viewer's BCM tab repeats it about every 0.13 s (captured)
|}
=== BCM data block (21 08) layout ===
Decoded from a PCAN-View capture of the SZ Viewer BCM tab on 14 November 2026, engine idling, car stationary. Byte numbers count from the <code>61</code> (byte 0); letter A = byte 2.
{| class="wikitable"
! Byte !! Letter !! Example (hex) !! Meaning !! Formula !! Status
|-
| 2 || A || <code>32</code> || Outside air temperature || A − 40 °C (10 °C). Also shown on SZ Viewer's temperature tab (9 °C, <code>31</code>, a few minutes earlier) || Matches SZ Viewer
|-
| 3 || B || <code>B9</code> || Battery voltage || B × 0.078 V (14.43 V) || Matches SZ Viewer
|-
| 6 || E || <code>D2</code> || Auto light sensor voltage || E × 5 / 255 V (4.118 V) || Matches SZ Viewer
|-
| 7 || F || <code>28</code> || Varied between 40 and 43. Unknown || – || –
|-
| 22 || U || <code>00</code> || Vehicle speed || U km/h || Inferred (0 km/h only)
|-
| 23–24 || V–W || <code>0C 94</code> || Engine speed || (V × 256 + W) / 4 rpm (805 rpm) || Matches SZ Viewer
|-
| 12, 26–60 || – || <code>80</code>, <code>33 00 FF 45 C0</code>, <code>08</code>, <code>02 00 E1 FF FF 02 80 00 02 32 87 00 00 10 FF 01 FF 04 A5 20 00</code> || Probably the switch states shown on the BCM tab (doors, lights, key, seat belt, parking brake, A/C, wipers and so on). They did not change during the capture, so the bits are not yet mapped || – || –
|}
|}
The outside temperature is not available as a standard OBD PID on this car (PID 46 is not supported), so this block is the only known source for it. To map the switch bits, capture the BCM tab while operating one switch at a time.


== 0x274 Instrument cluster ==
== 0x274 Instrument cluster ==
Line 364: Line 472:
* The acceleration at +7 is the centripetal acceleration of the rotating wheel, so it rises with wheel speed. The module compares each sensor's rotation signal with the ABS wheel-speed signals to work out which sensor is on which wheel, and stores the result as the position code at +4. That is why the records are kept in sensor-ID order with the position as a separate field.
* The acceleration at +7 is the centripetal acceleration of the rotating wheel, so it rises with wheel speed. The module compares each sensor's rotation signal with the ABS wheel-speed signals to work out which sensor is on which wheel, and stores the result as the position code at +4. That is why the records are kept in sensor-ID order with the position as a separate field.
* The car was stationary during the capture, so the +7 values are held from each sensor's last transmission while moving. Each sensor transmits on its own schedule, so the four values were taken at different speeds as the car slowed: with the valve at about 0.19 m radius and a tyre rolling radius of about 0.37 m, 28 g / 26.5 g / 10.5 g / 6.5 g correspond to roughly 50 / 48 / 30 / 24 km/h, which supports the ÷ 2 scaling (estimate).
* The car was stationary during the capture, so the +7 values are held from each sensor's last transmission while moving. Each sensor transmits on its own schedule, so the four values were taken at different speeds as the car slowed: with the valve at about 0.19 m radius and a tyre rolling radius of about 0.37 m, 28 g / 26.5 g / 10.5 g / 6.5 g correspond to roughly 50 / 48 / 30 / 24 km/h, which supports the ÷ 2 scaling (estimate).
* SZ Viewer's temperature (°C) tab lists the TPMS temperatures as "Air temperature #1" to "#4" in record order, not wheel order (10 / 9 / 9 / 10 °C in the capture, matching records 1 to 4).
* SZ Viewer also shows speed (0 km/h) and the low-pressure lamp (Off). Which bytes carry these is not known yet; a capture while driving with the lamp on should show them.
* SZ Viewer also shows speed (0 km/h) and the low-pressure lamp (Off). Which bytes carry these is not known yet; a capture while driving with the lamp on should show them.
* SZ Viewer sends <code>21 00</code> every 0.12 to 0.15 s and <code>18 00 FF 00</code> about every 2 s, with flow control <code>30 00 00</code>.
* SZ Viewer sends <code>21 00</code> every 0.12 to 0.15 s and <code>18 00 FF 00</code> about every 2 s, with flow control <code>30 00 00</code>.
Line 415: Line 524:
|-
|-
| <code>19 02 FF</code> || <code>59 02 4B</code> || DTCs by status mask: none stored (captured)
| <code>19 02 FF</code> || <code>59 02 4B</code> || DTCs by status mask: none stored (captured)
|-
| <code>22 10 00</code> || <code>62 10 00</code> + 60 bytes (63 in total) || Live data, partly decoded below. Polled continuously by SZ Viewer's SRS tab (captured)
|}
=== SRS data (22 10 00) layout ===
Decoded from a PCAN-View capture of the SZ Viewer SRS tab on 14 November 2026, engine idling. Byte numbers count from the <code>62</code> (byte 0). For a UDS reply the app letter A is the first byte after <code>62 10 00</code>, so A = byte 3.
Example reply: <code>62 10 00 FF 04 AF BE FF FF FF FF FF FF 1A FF FF FF FF FF FF FF FF FF 02 60 FF FF 4F 80 07 E0 CC 00 19 17 FF FF 17 16 FF…</code>
{| class="wikitable"
! Byte !! Letter !! Example (hex) !! Meaning !! Formula !! Status
|-
| 4 || B || <code>04</code> || Number of squib channels || B (4) || Matches SZ Viewer
|-
| 5 || C || <code>AF</code> || Battery voltage || C × 21 / 255 V (14.412 V) || Matches SZ Viewer
|-
| 6 || D || <code>BE</code> || Back-up (energy reserve) voltage || About D × 0.167 V (31.8 V). The exact scale is not known || Close to SZ Viewer (31.816 V)
|-
| 33 || AE || <code>19</code> || Driver airbag squib resistance || AE / 10 Ω (2.5 Ω) || Matches SZ Viewer
|-
| 34 || AF || <code>17</code> || Passenger airbag squib resistance || AF / 10 Ω (2.3 Ω) || Matches SZ Viewer
|-
| 37 || AI || <code>17</code> || Driver pretensioner squib resistance || AI / 10 Ω (2.3 Ω) || Matches SZ Viewer
|-
| 38 || AJ || <code>16</code> || Passenger pretensioner squib resistance || AJ / 10 Ω (2.2 Ω) || Matches SZ Viewer
|}
|}


Line 435: Line 569:
|-
|-
| <code>19 02 FF</code> || <code>59 02 4B</code> || DTCs by status mask: none stored (captured)
| <code>19 02 FF</code> || <code>59 02 4B</code> || DTCs by status mask: none stored (captured)
|-
| <code>22 10 00</code> || <code>62 10 00</code> + 30 bytes (33 in total) || Live data, partly decoded below. SZ Viewer's 4WD tab repeats it about every 0.08 s (captured)
|}
=== 4WD data (22 10 00) layout ===
Decoded from a PCAN-View capture of the SZ Viewer 4WD tab on 14 November 2026, engine idling, 2H selected. Byte numbers count from the <code>62</code> (byte 0); app letter A = byte 3.
Example reply: <code>62 10 00 90 FF 00 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 01 80 10 01 FF 04 FF FF FF 11</code>
{| class="wikitable"
! Byte !! Letter !! Example (hex) !! Meaning !! Formula !! Status
|-
| 3 || A || <code>90</code> || Battery voltage || A / 10 V (14.4 V) || Matches SZ Viewer
|-
| 5 || C || <code>00</code> || Vehicle speed || C km/h || Inferred (0 km/h only)
|-
| 6, 23–26, 28, 32 || – || <code>00</code>, <code>01 80 10 01</code>, <code>04</code>, <code>11</code> || Probably the switch states shown on the 4WD tab (4WD, 4WD-L, vacuum, VSV1, VSV2, ignition, transmission type). They did not change during the capture || – || –
|}
|}
A capture while shifting between 2H, 4H and 4L should show which bits carry the 4WD and 4WD-L switches.
The scan tool tried the KWP-style <code>3E</code> first and fell back to the UDS form <code>3E 00</code>.
The scan tool tried the KWP-style <code>3E</code> first and fell back to the UDS form <code>3E 00</code>.


Line 506: Line 658:
* Owner PCAN-View captures of the SZ Viewer app (TPMS and ABS/ESP tabs, ELM327 v1.5 Bluetooth adapter) with matching screenshots, 14 November 2026.
* Owner PCAN-View captures of the SZ Viewer app (TPMS and ABS/ESP tabs, ELM327 v1.5 Bluetooth adapter) with matching screenshots, 14 November 2026.
* Owner PCAN-View capture of an SZ Viewer full DTC scan (two passes), 14 November 2026.
* Owner PCAN-View capture of an SZ Viewer full DTC scan (two passes), 14 November 2026.
* Owner PCAN-View captures of the SZ Viewer temperature, OBD-II, Engine, 4WD, BCM, PS and SRS tabs with matching screenshots, 14 November 2026.


[[Category:Electrical - gen4]]
[[Category:Electrical - gen4]]

Revision as of 17:38, 14 November 2026

Support this project: The information on this page is free, but it took a lot of work to gather, test and write up. If it has been useful to you, you can say thanks with a donation at buymeacoffee.com/bigjimny.

Suzuki Jimny JB74 - CAN bus devices and the commands they answer

Status: work in progress. This page lists every module that answered on the OBD socket (DLC) of one RHD UK-market 2021 Jimny, its request and reply CAN IDs, and the diagnostic commands seen so far. Many sections are short because only identification and fault-code requests have been captured. See OBD2 Diagnostics reading project for how the captures were made and for the TPMS data in detail.

How to read this page

  • All IDs are 11-bit CAN IDs on the OBD socket (pins 6 and 14, 500 kbit/s). The "request ID" is the header a tool sends to; the "reply ID" is where the module answers.
  • Commands are shown as the payload bytes in hex, without the ISO-TP length byte. Replies longer than 7 bytes are sent as several frames; the tables show them reassembled.
  • KWP-style modules use services such as 1A (read ECU identification) and 18 (read DTCs by status). UDS-style modules use 22 (read data by identifier) and 19 (read DTCs).
  • The reply ID is not always the request ID plus 8: the engine is +0x08, the 0x261 to 0x274 group is +0x400, and all others are +0x10.
  • Identification strings are ASCII Suzuki part numbers. The first one in each module (1A 8E or 22 F1 01) has no trailing character; the second (1A 8A or 22 F1 88) ends in *. They do not always equal the number printed on the module's label.
  • Commands marked captured were seen in a trace. Nothing here has been sent to a module by us except the TPMS requests.

Example usage

This example reads the TPMS controller (request ID 0x798) with an ELM327 adapter in a terminal app. Use a terminal that sends a carriage return (CR) at the end of each line, with the ignition on. Send the commands one at a time and wait for OK after each.

Command Purpose
ATZ Reset the adapter (prints the adapter version, not OK)
ATSP6 Use protocol 6: ISO 15765-4, 11-bit CAN, 500 kbit/s
ATSH798 Send requests to the TPMS controller (see device table above)
ATS0 No spaces in the reply (stops one clone adapter overflowing its buffer)
ATL0 No line feeds in the reply
ATFCSH798 Send flow-control frames to 0x798 (see device table above)
ATFCSD300000 Flow-control data 30 00 00: continue, send all frames, no delay
ATFCSM1 Use the custom flow-control header and data above
2100 Request the sensor data block (service 0x21, identifier 0x00) ( see device specific tables below)

Example reply (generic ELM327 clone, ignition on, engine off):

2100
066
0:610075010000
1:0000000000004E
2:AA094310397901
3:4900DD91B52520
4:3B880149004EAA
5:0319183C830249
6:004EAA09C9083C
7:83024900000000
8:004EAA09434EAA
9:09434EAA09434E
A:AA094373737373
B:7D7D7D7D000000
C:00000000000000
D:00000030222202
E:01801700000000

Reading the reply:

  • 066 is the total length in hex: 0x66 = 102 bytes. The lines 0: to E: carry those bytes in order.
  • The data starts 61 00 (positive reply to 21 00). The next byte, 75 = 117, is the module supply voltage in tenths of a volt: 11.7 V (confirmed against SZ Viewer, see #Sensor data block (21 00) layout).
  • Each wheel has a 10-byte record. Byte +6 of the record is the pressure; bar = raw x 0.01372.
Wheel Record (hex) Byte +6 Raw Pressure
Front left 4E AA 09 43 10 39 79 01 49 00 79 121 1.66 bar
Rear left DD 91 B5 25 20 3B 88 01 49 00 88 136 1.87 bar
Rear right 4E AA 03 19 18 3C 83 02 49 00 83 131 1.80 bar
Front right 4E AA 09 C9 08 3C 83 02 49 00 83 131 1.80 bar

Notes:

  • The sensor IDs, and the byte values, are from one car. Your IDs will differ, and the values change with pressure and temperature.
  • ATSH and the ATFC settings last until the adapter is reset (ATZ) or loses power, so send them again after either.
  • Without the ATFC lines, the clone adapter used here returned only the first line (610075010000).
  • If the terminal prints NO DATA, check the ignition is on, that no other app is connected to the adapter, and that ATSH798 was sent after the last reset.

Device table

Request ID Reply ID Style Module Identification reply (first / second) How the module was identified
0x7E0 0x7E8 KWP ECM 33980-78R0 / 33980-78RC* Standard engine address
0x261 0x661 KWP ABS (inferred) 56100-77RA / 56100-78RF* Only brake module left by elimination; SZ Viewer reads it under its ABS/ESP tab (inferred)
0x263 0x663 KWP EPS controller 38720-77R0 / 38720-77R0* Parts catalogue (38720-77R01)
0x271 0x671 KWP Body control module 36775-77R0 / 36775-77RC* Parts catalogue (36775-77RC2 to RC4)
0x274 0x674 KWP Instrument cluster 34100-78R0 / 34110-78RD* Rev counter sweep test
0x798 0x7A8 KWP TPMS controller 37160-61M0 / 37120-78R0* Label (Model No. P61M0) and parts catalogue
0x79A 0x7AA KWP Combination switch (lighting and turn) 37210-74PA / 37210-74PE* Parts catalogue (37210-74PE2)
0x778 0x788 KWP Dual sensor brake support (inferred) 33990-52R0 / 33990-78R8* By elimination
0x793 0x7A3 UDS Airbag (SRS) controller 38910-77R0 / 38910-78RC* Parts catalogue (38910-78RC0)
0x772 0x782 UDS 4WD shift controller 38885-77R0 / 38885-78R0* Parts catalogue (38885-78R01)
0x799 0x7A9 UDS E-call controller 38960-78RA / 38960-78RA* Parts catalogue (38960-78RA0, RA1)
0x751 0x761 UDS Central gateway 33580-79R0 / 33580-78R0* Label (33580-79R01) and parts catalogue

The Launch and SZ Viewer scans also probed 27 more addresses that did not answer.

The names marked "inferred" are guesses from elimination and part-number series, not confirmed by a label or test.

0x7E0 ECM

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x7E0, reply 0x7E8. This is the standard OBD engine address. It is the only module that answers standard OBD requests sent to the functional address 0x7DF (see below).

Request Reply Meaning
3E 7E Tester present (captured)
3E 01 7F 3E 12 Refused: sub-function not supported (captured)
1A 8E 5A 8E + ASCII 33980-78R0 ECU identification (captured)
1A 8A 5A 8A + ASCII 33980-78RC* ECU identification (captured)
1A 90 5A 90 + 17 ASCII characters The car's VIN (captured; not reproduced here)
1A 9E 5A 9E + ASCII 10SW030025 Unknown identification string, perhaps a software or calibration number (captured; meaning inferred)
1A 87, 1A 88, 1A 9C, 1A 9D 7F 1A 12 Refused: identifier not supported (captured)
18 00 FF 00 58 00 Read DTCs by status: none stored (captured)
18 00 00 00, 18 00 40 00, 18 00 80 00, 18 00 C0 00, 18 00 FF FF 7F 18 12 Refused. SZ Viewer tries each of these in turn; only 18 00 FF 00 is accepted (captured)
21 00 61 00 + 208 bytes (210 in total) Live data block, layout below. SZ Viewer (Engine tab) repeats it about every 0.4 s (captured, partly decoded)
21 50, 21 51, 21 52, 21 53, 21 55, 21 70, 21 71, 21 90 7F 21 12 Refused: local ID not supported. SZ Viewer tries each once when the Engine tab opens (captured)

ECM data block (21 00) layout

Decoded from a PCAN-View capture taken while the SZ Viewer app (Engine tab) was polling the ECM on 14 November 2026, engine idling with a few blips of the throttle, car stationary. Matches SZ Viewer means the formula reproduces the value on the SZ Viewer screen from that capture. Everything else is inferred.

Byte numbers count from the 61 at the start of the reply (byte 0). The letter column is the variable name for Torque Pro and Car Scanner custom PIDs, where A is the first byte after 61 00 (A = byte 2). Bytes not listed were FF (unused) or did not change.

Byte Letter Example (hex) Meaning Formula Status
2–5 A–D 00 07 E1 80 Monitor status, the same four bytes as OBD PID 01 – Matches SZ Viewer (OBD-II tab)
17 P 02 Fuel system status: 02 = closed loop – Matches SZ Viewer ("Closed loop (Sensor)")
19 R 81 Short-term fuel trim (R − 128) / 1.28 % (0.781 %) Matches SZ Viewer
20 S 77 Long-term fuel trim (S − 128) / 1.28 % (−7.031 %) Matches SZ Viewer
23 V 79 Total fuel trim. Not exactly the sum of the two trims above (V − 128) / 1.28 % (−5.469 %) Matches SZ Viewer
25–26 X–Y 09 59 Injection time (X × 256 + Y) / 1000 ms (2.393 ms) Matches SZ Viewer
29 AB 87 Ignition advance AB / 2 − 64 degrees (3.5°), the same formula as OBD PID 0E Matches SZ Viewer
36 AI 37 Rises from 54 to 70 when the throttle is opened. Perhaps engine load – Inferred
37–38 AJ–AK 0C A0 Engine speed (AJ × 256 + AK) / 4 rpm Matches SZ Viewer
42 AO 00 Vehicle speed AO km/h Matches SZ Viewer (0 km/h only)
43 AP 1E Intake manifold absolute pressure AP kPa (30 kPa) Matches SZ Viewer
44 AQ 63 Coolant temperature AQ − 40 °C (59 °C) Matches SZ Viewer
45 AR 34 Intake air temperature AR − 40 °C (12 °C) Matches SZ Viewer
46 AS 64 Barometric pressure AS kPa (100 kPa = 750 mmHg). SZ Viewer's "Rel. pressure" (−0.7 bar) is MAP minus this value Matches SZ Viewer
60 BI 2A Rises from 41 to 57 when the throttle is opened. Unknown – –
66 BM 08 Throttle position BM / 2.55 % (3.137 %). Byte 67 carries the same value Matches SZ Viewer
76 BW 1A Upstream oxygen sensor (sensor 1) BW × 0.005 V (0.13 V), the same scaling as OBD PID 14 Matches SZ Viewer
77 BX 98 Downstream oxygen sensor (sensor 2) BX × 0.005 V (0.76 V) Matches SZ Viewer
99–100 CT–CU 38 B0 Battery (control module) voltage (CT × 256 + CU) / 1000 V (14.512 V), the same value as OBD PID 42 Matches SZ Viewer
101 CV D6 Fuel tank level CV / 2.55 % (83.922 %) Matches SZ Viewer
105 CZ 56 Rises from 85 to 134 when the throttle is opened. Unknown – –
113 DH 2D Battery temperature DH − 40 °C (4 °C on the temperature tab) Matches SZ Viewer

Notes:

  • The fuel tank level (byte 101) is not available as a standard OBD PID on this car (PID 2F is not supported), so this block is the only known source for it.
  • SZ Viewer also shows "Injector: 0.97 min/hour". No byte has been matched to it; it may be calculated from the injection time and engine speed.
  • SZ Viewer requests this block with flow control 30 00 08 (8 ms between frames). The first request of a session used 30 00 00 and also worked.

Standard OBD (mode 01) PIDs supported

Captured from an SZ Viewer scan on 14 November 2026, engine idling. SZ Viewer sends the standard requests to the functional address 0x7DF and the ECM answers on 0x7E8; no other module answered. A single request (01 00 20 40 60 80 A0) asks for all six "PIDs supported" bitmaps at once.

Range Bitmap reply PIDs supported
01–20 BE 3E B8 13 01 monitor status, 03 fuel system status, 04 calculated load, 05 coolant temperature, 06 short-term fuel trim, 07 long-term fuel trim, 0B intake manifold pressure (MAP), 0C engine speed, 0D vehicle speed, 0E timing advance, 0F intake air temperature, 11 throttle position, 13 oxygen sensors present, 14 and 15 oxygen sensors (bank 1, sensors 1 and 2), 1C OBD standard, 1F run time since engine start
21–40 80 05 A0 01 21 distance with MIL on, 2E commanded evaporative purge, 30 warm-ups since codes cleared, 31 distance since codes cleared, 33 barometric pressure
41–60 6A D0 00 05 42 control module voltage, 43 absolute load, 45 relative throttle position, 47 absolute throttle position B, 49 and 4A accelerator pedal positions D and E, 4C commanded throttle actuator, 5E engine fuel rate
61–80 00 00 00 01 None (only the bit that points to the next range)
81–A0 00 00 00 08 9D engine fuel rate

Not supported, so not available to OBD apps through standard PIDs: mass air flow (10; the engine works from MAP), fuel tank level (2F), ambient air temperature (46), engine oil temperature (5C) and odometer (A6). The fuel level and outside temperature can be read from the ECM and BCM data blocks instead.

The ECM accepts up to six PIDs in one request. SZ Viewer's OBD-II tab polls with 01 01 03 04 05 06 07, 01 0B 0C 0D 0E 0F 11, 01 13 14 15 1C 1F 21, 01 2E 30 31 33 42 43, 01 45 47 49 4A 4C 5E and 01 9D, and gets every value back in a single (multi-frame) reply, for example 41 0B 24 0C 0C C6 0D 00 0E 86 0F 34 11 23 (captured).

Other standard requests in the same scan:

Request (to 0x7DF) Reply (from 0x7E8) Meaning
03 43 00 Stored emission-related DTCs: none (captured)
07 47 00 Pending DTCs: none (captured)
0A No reply Permanent DTCs. Sent 16 times per scan with no answer, so probably not supported (captured)

0x261 ABS (inferred)

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x261, reply 0x661. The name is inferred: this is the only brake module left in the scan report after the others were matched, and 56100 looks like a brake part-number series. The SZ Viewer app reads this module under its ABS/ESP tab and shows the same two part numbers, which supports the name (inferred).

Request Reply Meaning
3E 7E Tester present (captured)
1A 8E 5A 8E + ASCII 56100-77RA ECU identification (captured)
1A 8A 5A 8A + ASCII 56100-78RF* ECU identification (captured)
18 00 FF 00 58 00 DTCs: none stored (captured). SZ Viewer repeats it about every 1.4 s and shows "OK, no DTCs"
21 00 61 00 + 50 bytes (52 in total) Live data block, layout below. SZ Viewer repeats it every 70 to 120 ms (captured, partly decoded)

ABS data block (21 00) layout

Decoded from a PCAN-View capture taken while the SZ Viewer app (ABS/ESP tab) was polling the module on 14 November 2026, engine idling, car stationary. Matches SZ Viewer means the formula reproduces the value on the SZ Viewer screen from that capture; it has not been checked under other conditions. Everything else is inferred.

Byte numbers count from the 61 at the start of the reply (byte 0). The letter column is the variable name for Torque Pro and Car Scanner custom PIDs, where A is the first byte after 61 00 (A = byte 2).

Byte Letter Example (hex) Meaning Formula Status
0–1 – 61 00 Positive reply to 21 00 – –
2–12 A–K 00 ×11 Probably the four wheel speeds (all 0 km/h on the screen). Whether they are single bytes or 16-bit values is not known – Inferred
13 L 80 One of longitudinal acceleration, lateral G or yaw rate (all 0 on the screen), centred on 128 – Inferred
14 M B9 Battery voltage M × 20 / 255 V (185 = 14.51 V). Dipped to A8 (13.2 V) and recovered during the capture Matches SZ Viewer
15 N 2E Pump motor voltage N × 20 / 255 V (46 = 3.608 V). Alternates between 2E and 2F Matches SZ Viewer
16 O 79 Steering angle offset (O − 128) / 2 degrees (121 = −3.5°) Matches SZ Viewer
17–18 P–Q FF FF Probably master cylinder pressure: −1 as a signed 16-bit value, × 0.1 = −0.1 MPa as shown on the screen. Could also be a single signed byte ((P × 256 + Q) − 65536) × 0.1 MPa (guess) Inferred
19 R 13 Unknown – –
20 S 80 One of longitudinal acceleration, lateral G or yaw rate, centred on 128 – Inferred
21 T 80 One of longitudinal acceleration, lateral G or yaw rate, centred on 128 – Inferred
22–23 U–V 00 FF Unknown – –
24–25 W–X 0C 74 Engine speed (W × 256 + X) / 4 rpm (3188 = 797 rpm), the same formula as OBD PID 0C. Changes on every reply with the idle (about 775 to 831 rpm) Matches SZ Viewer
26–51 Y–AX 00 A2 FF FF FF FF A9 FF FF FF FF FF FF FF 40 00 0E 00 40 00 80 03 00 53 FF FF Unknown; did not change during the capture. Probably status flags or unused channels – –

Notes:

  • SZ Viewer shows a second "Pump motor voltage" of 3.698 V. No byte in the reply matches it with the same scaling (2F would give 3.686 V), so where it comes from is not known.
  • The wheel speeds, the acceleration, lateral G and yaw channels, and the master cylinder pressure need a capture while driving (and one with the brake pedal pressed) to confirm.
  • Before polling the ABS, SZ Viewer sent one tester-present (3E) to 0x7E1 and got no reply. 0x7E1 is the usual address for a separate transmission ECU (the slot after the engine at 0x7E0). The test car has a manual gearbox and no automatic transmission controller; its only transmission-related controller is the 4WD shift controller at 0x772, so nothing is fitted at 0x7E1. SZ Viewer, which also has an AT/CVT tab, appears to check the address and move on.

0x263 EPS controller

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x263, reply 0x663. Matches parts catalogue entry 38720-77R01 (EPS controller).

Request Reply Meaning
3E 7E Tester present (captured)
1A 8E 5A 8E + ASCII 38720-77R0 ECU identification (captured)
1A 8A 5A 8A + ASCII 38720-77R0* ECU identification (captured)
18 00 FF 00 58 00 DTCs: none stored (captured)
21 08 61 08 + 40 bytes (42 in total) Live data block, partly decoded below. Polled continuously by SZ Viewer's PS tab (captured)

EPS data block (21 08) layout

Decoded from a PCAN-View capture of the SZ Viewer PS tab on 14 November 2026, engine idling, wheel not turned. Byte numbers count from the 61 (byte 0); letter A = byte 2.

Example reply: 61 08 7F 9D FF FF 00 0F DD 7C CD 80 80 81 00 00 00 C8 26 FF 13 FF 10 04 C1 13 80 33 33 FF FF 00 45 FF FF FF FF 00 00 5E 4D 44

Byte Letter Example (hex) Meaning Formula Status
9 H 7C Varied between 112 and 124 during the capture. Unknown – –
10 I CD Battery voltage I × 0.07 V (14.35 V) Matches SZ Viewer
13 L 81 Changed between 81 and 82. Perhaps the control torque (0.061 Nm on the screen) – Inferred
18 Q 27 Engine speed Q × 20 rpm (780 rpm) Matches SZ Viewer

The screen also shows sensor supply 4.984 V, main and sub torque 0.002 Nm, motor currents 0 A and motor drive voltages 0.968 V. None of these has been matched to a byte yet; a capture while turning the wheel should show the torque and current bytes.

0x271 Body control module

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x271, reply 0x671. Matches parts catalogue entries 36775-77RC2 to RC4 (body control module, RHD).

Request Reply Meaning
3E 7E Tester present (captured)
1A 8E 5A 8E + ASCII 36775-77R0 ECU identification (captured)
1A 8A 5A 8A + ASCII 36775-77RC* ECU identification (captured)
18 00 FF 00 58 00 DTCs: none stored (captured)
21 08 61 08 + 100 bytes (102 in total) Live data block, partly decoded below. SZ Viewer's BCM tab repeats it about every 0.13 s (captured)

BCM data block (21 08) layout

Decoded from a PCAN-View capture of the SZ Viewer BCM tab on 14 November 2026, engine idling, car stationary. Byte numbers count from the 61 (byte 0); letter A = byte 2.

Byte Letter Example (hex) Meaning Formula Status
2 A 32 Outside air temperature A − 40 °C (10 °C). Also shown on SZ Viewer's temperature tab (9 °C, 31, a few minutes earlier) Matches SZ Viewer
3 B B9 Battery voltage B × 0.078 V (14.43 V) Matches SZ Viewer
6 E D2 Auto light sensor voltage E × 5 / 255 V (4.118 V) Matches SZ Viewer
7 F 28 Varied between 40 and 43. Unknown – –
22 U 00 Vehicle speed U km/h Inferred (0 km/h only)
23–24 V–W 0C 94 Engine speed (V × 256 + W) / 4 rpm (805 rpm) Matches SZ Viewer
12, 26–60 – 80, 33 00 FF 45 C0, 08, 02 00 E1 FF FF 02 80 00 02 32 87 00 00 10 FF 01 FF 04 A5 20 00 Probably the switch states shown on the BCM tab (doors, lights, key, seat belt, parking brake, A/C, wipers and so on). They did not change during the capture, so the bits are not yet mapped – –

The outside temperature is not available as a standard OBD PID on this car (PID 46 is not supported), so this block is the only known source for it. To map the switch bits, capture the BCM tab while operating one switch at a time.

0x274 Instrument cluster

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x274, reply 0x674. Confirmed by the rev counter sweep test.

Request Reply Meaning
3E or 3E 00 7E Tester present, about every 2.15 s during the sweep test (captured)
1A 8E 5A 8E + ASCII 34100-78R0 ECU identification (captured)
1A 8A 5A 8A + ASCII 34110-78RD* (last byte of the reply is 06) ECU identification (captured)
18 00 FF 00 58 00 DTCs: none stored (captured)
30 01 07 80 40 00 00 70 01 07 Starts the rev counter sweep (service 0x30, local ID 01, "short-term adjustment"). The cluster then sweeps up and down by itself (captured)
30 01 07 80 00 00 00 7F 30 22 Refused ("conditions not correct"). Possibly a stop request sent after the sweep had finished (captured)

The meaning of the four control bytes (80 40 00 00) is not known. Other output tests (gauges, warning lights) have not been captured.

0x798 TPMS controller

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x798, reply 0x7A8. The label on the module reads 37160-78R00, "BASE ASSY-TPMS", Model No. P61M0 (Continental A2C13930301, 433.92 MHz). The full data layout, calibration and app setups are on OBD2 Diagnostics reading project.

Request Reply Meaning
3E 7E Tester present (captured)
1A 8E 5A 8E + ASCII 37160-61M0 ECU identification; matches Model No. P61M0 on the label (captured)
1A 8A 5A 8A + ASCII 37120-78R0* ECU identification (captured)
18 00 FF 00 58 00 (no codes) or 58 01 9A 31 20 (one code) DTCs by status. 9A 31 is B1A31, "Left front tire pressure low" (confirmed by SZ Viewer). SZ Viewer shows status 20 as History (stored, not current); E0 was seen in earlier captures (captured)
21 00 61 00 + 100 bytes Sensor data block: module supply voltage and four sensor records (ID, wheel position, temperature, pressure, acceleration, battery status). Layout below. The Launch tool repeats it about twice a second, SZ Viewer every 0.12 to 0.15 s (captured, decoded)

ELM327 setup that works for 21 00: ATSH798, ATS0, ATL0, ATFCSH798, ATFCSD300000, ATFCSM1, then 2100.

Sensor data block (21 00) layout

Decoded from a PCAN-View capture taken while the SZ Viewer app (TPMS tab) was polling the module on 14 November 2026, engine running, car stationary. Each decoded value below was checked against the SZ Viewer screen at the same moment.

Byte numbers count from the 61 at the start of the reply (byte 0). The letter column is the variable name for Torque Pro and Car Scanner custom PIDs, where A is the first byte after 61 00 (A = byte 2).

Byte Letter Example (hex) Meaning Formula
0–1 – 61 00 Positive reply to 21 00 –
2 A 8E Module supply voltage A / 10 V (14.2 V). It dipped to 82 (13.0 V) and recovered during the capture; SZ Viewer showed 13.3 V (85) at that moment
3 B 01 Unknown –
4–11 C–J 00 ×8 Unknown, all zero so far. Speed and the warning lamp state may be here –
12–21 K–T – Sensor record 1 see record table below
22–31 U–AD – Sensor record 2 see record table below
32–41 AE–AN – Sensor record 3 see record table below
42–51 AO–AX – Sensor record 4 see record table below
52–71 AY–BR 00000000 4EAA09C9 4EAA0319 4EAA09C9 DD91B525 Five 4-byte sensor ID slots. Probably a log of recently received sensors: in the deflation capture (example above) every filled slot held the left front ID (inferred) –
72–75 BS–BV 73 73 73 73 One value per wheel: 1.58 bar (22.9 psi). Possibly the low-pressure warning threshold (inferred) value × 0.0137 bar
76–79 BW–BZ 7D 7D 7D 7D One value per wheel: 1.71 bar (24.8 psi). Possibly the threshold at which the warning clears (inferred) value × 0.0137 bar
80–83 CA–CD 00 ×4 Unknown –
84–91 CE–CL 00 90 00 96 00 62 00 69 Four 16-bit values (144, 150, 98, 105). All zero in the engine-off example above. Unknown; perhaps signal strength or reception counts –
92–101 CM–CV 00 30 33 33 02 01 80 17 00 00 Unknown. Bytes 93–95 were 30 22 22 in the engine-off example –

Each sensor record is 10 bytes. Offsets are from the start of the record, as in the example at the top of the page.

Offset Letters (records 1 / 2 / 3 / 4) Meaning Formula Check against SZ Viewer (records 1 / 2 / 3 / 4)
+0 to +3 K–N / U–X / AE–AH / AO–AR Sensor ID 4 bytes, hex 4EAA0943 / DD91B525 / 4EAA0319 / 4EAA09C9
+4 O / Y / AI / AS Wheel position, as learned by the module's auto-location (see notes) value / 8: 1 = right front, 2 = left front, 3 = right rear, 4 = left rear 10 left front / 20 left rear / 18 right rear / 08 right front
+5 P / Z / AJ / AT Air temperature value − 50 °C 3C 10 °C / 3B 9 °C / 3B 9 °C / 3C 10 °C
+6 Q / AA / AK / AU Air pressure value × 0.0137 bar (× 1.37 kPa, × 0.1987 psi) 89 1.877 / 89 1.877 / 85 1.822 / 87 1.850 bar
+7 R / AB / AL / AV Rotational (centripetal) acceleration measured by the sensor (SZ Viewer label "TPS acceleration"). Used with the ABS wheel speeds to locate each sensor on its wheel. Held from the sensor's last transmission, so not zero when parked value / 2 g 38 28 g / 35 26.5 g / 15 10.5 g / 0D 6.5 g
+8 S / AC / AM / AW Sensor battery status 42 is shown as Normal. 49 in the engine-off example; other values not yet decoded all 42, Normal
+9 T / AD / AN / AX Unknown – all 00

Notes:

  • The records are stored in sensor-ID order, not wheel order. Use byte +4 to find the wheel, especially after the tyres have been rotated.
  • SZ Viewer scales pressure by exactly 0.0137 bar per count (all four values match to three decimals). The 0.01372 used in the example above gives the same result to two decimals.
  • The acceleration at +7 is the centripetal acceleration of the rotating wheel, so it rises with wheel speed. The module compares each sensor's rotation signal with the ABS wheel-speed signals to work out which sensor is on which wheel, and stores the result as the position code at +4. That is why the records are kept in sensor-ID order with the position as a separate field.
  • The car was stationary during the capture, so the +7 values are held from each sensor's last transmission while moving. Each sensor transmits on its own schedule, so the four values were taken at different speeds as the car slowed: with the valve at about 0.19 m radius and a tyre rolling radius of about 0.37 m, 28 g / 26.5 g / 10.5 g / 6.5 g correspond to roughly 50 / 48 / 30 / 24 km/h, which supports the ÷ 2 scaling (estimate).
  • SZ Viewer's temperature (°C) tab lists the TPMS temperatures as "Air temperature #1" to "#4" in record order, not wheel order (10 / 9 / 9 / 10 °C in the capture, matching records 1 to 4).
  • SZ Viewer also shows speed (0 km/h) and the low-pressure lamp (Off). Which bytes carry these is not known yet; a capture while driving with the lamp on should show them.
  • SZ Viewer sends 21 00 every 0.12 to 0.15 s and 18 00 FF 00 about every 2 s, with flow control 30 00 00.

0x79A Combination switch (lighting and turn)

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x79A, reply 0x7AA. Matches parts catalogue entry 37210-74PE2 (switch assembly, lighting and turn, RHD).

Request Reply Meaning
3E 7E Tester present (captured)
1A 8E 5A 8E + ASCII 37210-74PA ECU identification (captured)
1A 8A 5A 8A + ASCII 37210-74PE* ECU identification (captured)
1A 90, 1A 8D, 1A 99, 1A 98 7F 1A 12 Refused: identifier not supported. Tried by SZ Viewer (captured)
18 00 FF 00 58 00 DTCs: none stored (captured)

0x778 Dual sensor brake support (inferred)

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x778, reply 0x788. The name is inferred by elimination (the scan report's last unassigned module). Not confirmed.

Request Reply Meaning
3E 7E Tester present (captured)
1A 8E 5A 8E + ASCII 33990-52R0 ECU identification (captured)
1A 8A 5A 8A + ASCII 33990-78R8* ECU identification (captured)
18 00 FF 00 58 00 DTCs: none stored (captured)

0x793 Airbag (SRS) controller

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x793, reply 0x7A3. Matches parts catalogue entry 38910-78RC0 (airbag controller, VAN).

Request Reply Meaning
3E 00 7E 00 Tester present (captured)
22 F1 01 62 F1 01 + ASCII 38910-77R0 Identification (captured)
22 F1 88 62 F1 88 + ASCII 38910-78RC* Identification (captured)
19 02 FF 59 02 4B DTCs by status mask: none stored (captured)
22 10 00 62 10 00 + 60 bytes (63 in total) Live data, partly decoded below. Polled continuously by SZ Viewer's SRS tab (captured)

SRS data (22 10 00) layout

Decoded from a PCAN-View capture of the SZ Viewer SRS tab on 14 November 2026, engine idling. Byte numbers count from the 62 (byte 0). For a UDS reply the app letter A is the first byte after 62 10 00, so A = byte 3.

Example reply: 62 10 00 FF 04 AF BE FF FF FF FF FF FF 1A FF FF FF FF FF FF FF FF FF 02 60 FF FF 4F 80 07 E0 CC 00 19 17 FF FF 17 16 FF…

Byte Letter Example (hex) Meaning Formula Status
4 B 04 Number of squib channels B (4) Matches SZ Viewer
5 C AF Battery voltage C × 21 / 255 V (14.412 V) Matches SZ Viewer
6 D BE Back-up (energy reserve) voltage About D × 0.167 V (31.8 V). The exact scale is not known Close to SZ Viewer (31.816 V)
33 AE 19 Driver airbag squib resistance AE / 10 Ω (2.5 Ω) Matches SZ Viewer
34 AF 17 Passenger airbag squib resistance AF / 10 Ω (2.3 Ω) Matches SZ Viewer
37 AI 17 Driver pretensioner squib resistance AI / 10 Ω (2.3 Ω) Matches SZ Viewer
38 AJ 16 Passenger pretensioner squib resistance AJ / 10 Ω (2.2 Ω) Matches SZ Viewer

0x772 4WD shift controller

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x772, reply 0x782. Matches parts catalogue entry 38885-78R01 (4WD shift controller).

Request Reply Meaning
3E 7F 3E 13 Refused: incorrect message length. Sent four times by the scan tool (captured)
3E 01 7F 3E 12 Refused: sub-function not supported. Sent four times (captured)
3E 00 7E 00 Tester present (captured)
22 F1 01 62 F1 01 + ASCII 38885-77R0 Identification (captured)
22 F1 88 62 F1 88 + ASCII 38885-78R0* Identification (captured)
19 02 FF 59 02 4B DTCs by status mask: none stored (captured)
22 10 00 62 10 00 + 30 bytes (33 in total) Live data, partly decoded below. SZ Viewer's 4WD tab repeats it about every 0.08 s (captured)

4WD data (22 10 00) layout

Decoded from a PCAN-View capture of the SZ Viewer 4WD tab on 14 November 2026, engine idling, 2H selected. Byte numbers count from the 62 (byte 0); app letter A = byte 3.

Example reply: 62 10 00 90 FF 00 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 01 80 10 01 FF 04 FF FF FF 11

Byte Letter Example (hex) Meaning Formula Status
3 A 90 Battery voltage A / 10 V (14.4 V) Matches SZ Viewer
5 C 00 Vehicle speed C km/h Inferred (0 km/h only)
6, 23–26, 28, 32 – 00, 01 80 10 01, 04, 11 Probably the switch states shown on the 4WD tab (4WD, 4WD-L, vacuum, VSV1, VSV2, ignition, transmission type). They did not change during the capture – –

A capture while shifting between 2H, 4H and 4L should show which bits carry the 4WD and 4WD-L switches. The scan tool tried the KWP-style 3E first and fell back to the UDS form 3E 00.

0x799 E-call controller

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x799, reply 0x7A9. Matches parts catalogue entries 38960-78RA0 and RA1 (E-call controller).

Request Reply Meaning
3E 7F 3E 13 Refused: incorrect message length. Sent four times (captured)
3E 01 7F 3E 12 Refused: sub-function not supported. Sent four times (captured)
3E 00 7E 00 Tester present (captured)
22 F1 01 62 F1 01 + ASCII 38960-78RA Identification (captured)
22 F1 88 62 F1 88 + ASCII 38960-78RA* Identification (captured)
19 02 FF 59 02 4B 92 4E 00 02 One stored code record: 92 4E 00, status 02. The Launch report does not list it and its meaning is not known (captured)
1A 8A, 1A 8E, 1A 8D, 1A 90, 1A 91, 1A 98, 1A 99, 1A 9A 7F 1A 11 Refused: service not supported. Sent by SZ Viewer (captured)
18 00 00 00, 18 00 40 00, 18 00 80 00, 18 00 C0 00, 18 00 FF 00, 18 00 FF FF 7F 18 11 Refused: service not supported. Sent by SZ Viewer (captured)

SZ Viewer talks to this module with KWP-style requests (3E, 1A, 18), which it refuses, so SZ Viewer cannot read its identification or fault codes and does not show the 92 4E 00 record. Only the UDS requests above work. SZ Viewer did not send 19 02 FF, so its scan does not show whether that record is still stored.

0x751 Central gateway

Models: JB74 (2018+, tested on 2021) — untested on: JB64, JC74, JB43

Request 0x751, reply 0x761. The label on the module reads 33580-79R01.

Request Reply Meaning
3E 00 7E 00 Tester present (captured)
22 F1 01 62 F1 01 + ASCII 33580-79R0 Identification (captured)
22 F1 88 62 F1 88 + ASCII 33580-78R0* Identification (captured)
19 02 FF 59 02 4B DTCs by status mask: none stored (captured)

The gateway sits between the OBD socket and the vehicle CAN bus. Whether it forwards requests to the other modules unchanged is not confirmed.

Addresses probed with no reply

The Launch scan tool sent tester-present (3E) about eight times each to 0x273 and 0x262 and received nothing from the expected reply IDs (0x673 and 0x662).

The SZ Viewer scan of 14 November 2026 probed 0x262 and 0x273 too, and also sent tester-present (3E, 3E 00 or 3E 01) to the addresses below. None of them answered, in either of two full passes:

Range Addresses with no reply
0x2xx 0x241, 0x242, 0x243, 0x262, 0x264, 0x265, 0x272, 0x273, 0x275, 0x276, 0x277
0x7xx 0x715, 0x716, 0x750, 0x776, 0x777, 0x779, 0x77A, 0x784, 0x79B, 0x79C
0x7Ex 0x7E1, 0x7E3, 0x7E4, 0x7E5, 0x7E6, 0x7EA

These are probably modules that SZ Viewer knows from other Suzuki models and this car does not have, such as an automatic transmission (0x7E1, see the ABS notes) or an auto-levelling controller. Which module each address belongs to is a guess.

ELM327 notes

  • Only 0x798 has been tested with an ELM327. For other modules, set ATSH to the request ID and ATFCSH to the same ID, and you may need ATCRA with the reply ID, because the reply is not always the request ID plus 8. This is untested.
  • Replies from the 0x7xx modules are multi-frame for the identification strings, so the flow-control settings from the TPMS section probably apply there too. Untested.
  • Do not send output-control commands (service 30 and similar) from a head-unit app while driving.

Sources

  • Owner PCAN-View captures of a Launch X431 CRP919 full health-check scan and rev counter sweep test, October 2026.
  • Suzuki Jimny parts catalogue 9900B-40312-004 (type 1, October 2021), figures 350A, 351A and 351B.
  • Labels on the TPMS controller and central gateway of the test car.
  • Owner PCAN-View captures of the SZ Viewer app (TPMS and ABS/ESP tabs, ELM327 v1.5 Bluetooth adapter) with matching screenshots, 14 November 2026.
  • Owner PCAN-View capture of an SZ Viewer full DTC scan (two passes), 14 November 2026.
  • Owner PCAN-View captures of the SZ Viewer temperature, OBD-II, Engine, 4WD, BCM, PS and SRS tabs with matching screenshots, 14 November 2026.