ECU diagnostic CAN addresses: Difference between revisions
| (17 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
* Identification strings are ASCII Suzuki part numbers. The first one in each module (<code>1A 8E</code> or <code>22 F1 01</code>) has no trailing character; the second (<code>1A 8A</code> or <code>22 F1 88</code>) ends in <code>*</code>. They do not always equal the number printed on the module's label. | * Identification strings are ASCII Suzuki part numbers. The first one in each module (<code>1A 8E</code> or <code>22 F1 01</code>) has no trailing character; the second (<code>1A 8A</code> or <code>22 F1 88</code>) ends in <code>*</code>. 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. | * 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 <code>OK</code> after each. | |||
{| class="wikitable" | |||
! Command !! Purpose | |||
|- | |||
| <code>ATZ</code> || Reset the adapter (prints the adapter version, not OK) | |||
|- | |||
| <code>ATSP6</code> || Use protocol 6: ISO 15765-4, 11-bit CAN, 500 kbit/s | |||
|- | |||
| <code>ATSH798</code> || Send requests to the TPMS controller ('''see device table above''') | |||
|- | |||
| <code>ATS0</code> || No spaces in the reply (stops one clone adapter overflowing its buffer) | |||
|- | |||
| <code>ATL0</code> || No line feeds in the reply | |||
|- | |||
| <code>ATFCSH798</code> || Send flow-control frames to 0x798 ('''see device table above''') | |||
|- | |||
| <code>ATFCSD300000</code> || Flow-control data <code>30 00 00</code>: continue, send all frames, no delay | |||
|- | |||
| <code>ATFCSM1</code> || Use the custom flow-control header and data above | |||
|- | |||
| <code>2100</code> || Request the sensor data block (service 0x21, identifier 0x00) ( '''see device specific tables below''') | |||
|} | |||
Example reply (generic ELM327 clone, ignition on, engine off): | |||
<pre> | |||
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 | |||
</pre> | |||
Reading the reply: | |||
* <code>066</code> is the total length in hex: 0x66 = 102 bytes. The lines <code>0:</code> to <code>E:</code> carry those bytes in order. | |||
* The data starts <code>61 00</code> (positive reply to <code>21 00</code>). The next byte, <code>75</code> = 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. | |||
{| class="wikitable" | |||
! Wheel !! Record (hex) !! Byte +6 !! Raw !! Pressure | |||
|- | |||
| Front left || <code>4E AA 09 43 10 39 79 01 49 00</code> || <code>79</code> || 121 || 1.66 bar | |||
|- | |||
| Rear left || <code>DD 91 B5 25 20 3B 88 01 49 00</code> || <code>88</code> || 136 || 1.87 bar | |||
|- | |||
| Rear right || <code>4E AA 03 19 18 3C 83 02 49 00</code> || <code>83</code> || 131 || 1.80 bar | |||
|- | |||
| Front right || <code>4E AA 09 C9 08 3C 83 02 49 00</code> || <code>83</code> || 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. | |||
* <code>ATSH</code> and the <code>ATFC</code> settings last until the adapter is reset (<code>ATZ</code>) or loses power, so send them again after either. | |||
* Without the <code>ATFC</code> lines, the clone adapter used here returned only the first line (<code>610075010000</code>). | |||
* If the terminal prints <code>NO DATA</code>, check the ignition is on, that no other app is connected to the adapter, and that <code>ATSH798</code> was sent after the last reset. | |||
== Device table == | == Device table == | ||
| Line 21: | Line 89: | ||
| [[#0x7E0 ECM|0x7E0]] || 0x7E8 || KWP || ECM || 33980-78R0 / 33980-78RC* || Standard engine address | | [[#0x7E0 ECM|0x7E0]] || 0x7E8 || KWP || ECM || 33980-78R0 / 33980-78RC* || Standard engine address | ||
|- | |- | ||
| [[#0x261 ABS (inferred)|0x261]] || 0x661 || KWP || ABS (inferred) || 56100-77RA / 56100-78RF* || Only brake module left by elimination | | [[#0x261 ABS (inferred)|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 EPS controller|0x263]] || 0x663 || KWP || EPS controller || 38720-77R0 / 38720-77R0* || Parts catalogue (38720-77R01) | | [[#0x263 EPS controller|0x263]] || 0x663 || KWP || EPS controller || 38720-77R0 / 38720-77R0* || Parts catalogue (38720-77R01) | ||
| Line 44: | Line 112: | ||
|} | |} | ||
The Launch and SZ Viewer scans also probed [[#Addresses probed with no reply|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. | The names marked "inferred" are guesses from elimination and part-number series, not confirmed by a label or test. | ||
| Line 51: | Line 119: | ||
{{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | {{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | ||
Request <code>0x7E0</code>, reply <code>0x7E8</code>. This is the standard OBD engine address | Request <code>0x7E0</code>, reply <code>0x7E8</code>. This is the standard OBD engine address. It is the only module that answers standard OBD requests sent to the functional address <code>0x7DF</code> (see [[#Standard OBD (mode 01) PIDs supported|below]]). | ||
{| class="wikitable" | {| class="wikitable" | ||
! Request !! Reply !! Meaning | ! Request !! Reply !! Meaning | ||
|- | |- | ||
| <code>3E</code> || <code>7E</code> || Tester present (captured) | | <code>3E</code> || <code>7E</code> || Tester present (captured) | ||
|- | |||
| <code>3E 01</code> || <code>7F 3E 12</code> || Refused: sub-function not supported (captured) | |||
|- | |- | ||
| <code>1A 8E</code> || <code>5A 8E</code> + ASCII <code>33980-78R0</code> || ECU identification (captured) | | <code>1A 8E</code> || <code>5A 8E</code> + ASCII <code>33980-78R0</code> || ECU identification (captured) | ||
|- | |- | ||
| <code>1A 8A</code> || <code>5A 8A</code> + ASCII <code>33980-78RC*</code> || ECU identification (captured) | | <code>1A 8A</code> || <code>5A 8A</code> + ASCII <code>33980-78RC*</code> || ECU identification (captured) | ||
|- | |||
| <code>1A 90</code> || <code>5A 90</code> + 17 ASCII characters || The car's VIN (captured; not reproduced here) | |||
|- | |||
| <code>1A 9E</code> || <code>5A 9E</code> + ASCII <code>10SW030025</code> || Unknown identification string, perhaps a software or calibration number (captured; meaning inferred) | |||
|- | |||
| <code>1A 87</code>, <code>1A 88</code>, <code>1A 9C</code>, <code>1A 9D</code> || <code>7F 1A 12</code> || Refused: identifier not supported (captured) | |||
|- | |- | ||
| <code>18 00 FF 00</code> || <code>58 00</code> || Read DTCs by status: none stored (captured) | | <code>18 00 FF 00</code> || <code>58 00</code> || Read DTCs by status: none stored (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 === | |||
Captured from an SZ Viewer scan on 14 November 2026, engine idling. SZ Viewer sends the standard requests to the functional address <code>0x7DF</code> and the ECM answers on <code>0x7E8</code>; no other module answered. A single request (<code>01 00 20 40 60 80 A0</code>) asks for all six "PIDs supported" bitmaps at once. | |||
{| class="wikitable" | |||
! Range !! Bitmap reply !! PIDs supported | |||
|- | |||
| 01–20 || <code>BE 3E B8 13</code> || 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 || <code>80 05 A0 01</code> || 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 || <code>6A D0 00 05</code> || 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 || <code>00 00 00 01</code> || None (only the bit that points to the next range) | |||
|- | |||
| 81–A0 || <code>00 00 00 08</code> || 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 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: | |||
{| class="wikitable" | |||
! Request (to 0x7DF) !! Reply (from 0x7E8) !! Meaning | |||
|- | |||
| <code>03</code> || <code>43 00</code> || Stored emission-related DTCs: none (captured) | |||
|- | |||
| <code>07</code> || <code>47 00</code> || Pending DTCs: none (captured) | |||
|- | |||
| <code>0A</code> || No reply || Permanent DTCs. Sent 16 times per scan with no answer, so probably not supported (captured) | |||
|} | |} | ||
| Line 67: | Line 239: | ||
{{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | {{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | ||
Request <code>0x261</code>, reply <code>0x661</code>. 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. | Request <code>0x261</code>, reply <code>0x661</code>. 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). The driving capture of 15 November 2026 shows wheel speeds, yaw rate, steering angle and brake pressure in its data block, which confirms it is the ABS/ESP module. | ||
{| class="wikitable" | {| class="wikitable" | ||
! Request !! Reply !! Meaning | ! Request !! Reply !! Meaning | ||
| Line 77: | Line 249: | ||
| <code>1A 8A</code> || <code>5A 8A</code> + ASCII <code>56100-78RF*</code> || ECU identification (captured) | | <code>1A 8A</code> || <code>5A 8A</code> + ASCII <code>56100-78RF*</code> || ECU identification (captured) | ||
|- | |- | ||
| <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). SZ Viewer repeats it about every 1.4 s and shows "OK, no DTCs" | ||
|- | |||
| <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 once when the ABS/ESP tab opens; only <code>18 00 FF 00</code> is accepted (captured) | |||
|- | |||
| <code>21 00</code> || <code>61 00</code> + 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 PCAN-View captures of the SZ Viewer app (ABS/ESP tab): one on 14 November 2026 with the engine idling and the car stationary, and three on 15 November 2026. The 15 November captures were an 8-minute drive, a parked capture with the steering turned to each lock and the brake pressed lightly and hard, and a 7-minute drive with a roundabout, left and right turns and three sharp stops (the last with the ABS cutting in). The last two were made alongside Android screen recordings of SZ Viewer. ''Matches SZ Viewer'' means the formula reproduces the value on the SZ Viewer screen at the same moment. ''Fits the drive'' means the byte behaved as expected while driving; the scale is not confirmed. 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). | |||
{| class="wikitable" | |||
! Byte !! Letter !! Example (hex) !! Meaning !! Formula !! Status | |||
|- | |||
| 0–1 || – || <code>61 00</code> || Positive reply to <code>21 00</code> || – || – | |||
|- | |||
| 2–8 || A–G || <code>00</code> ×7 || Unknown. Stayed at zero for the whole drive || – || – | |||
|- | |||
| 9 || H || <code>00</code> || Wheel speed, front right || H km/h || Matches SZ Viewer | |||
|- | |||
| 10 || I || <code>00</code> || Wheel speed, front left || I km/h || Matches SZ Viewer | |||
|- | |||
| 11 || J || <code>00</code> || Wheel speed, rear right || J km/h || Matches SZ Viewer | |||
|- | |||
| 12 || K || <code>00</code> || Wheel speed, rear left || K km/h || Matches SZ Viewer | |||
|- | |||
| 13 || L || <code>80</code> || Longitudinal acceleration ("Acceleration"), centred on 128. Negative when braking (−36 = −0.72 G in a sharp stop) || (L − 128) × 0.02 G || Matches SZ Viewer | |||
|- | |||
| 14 || M || <code>B9</code> || Battery voltage || M × 20 / 255 V (185 = 14.51 V). Dipped to <code>A8</code> (13.2 V) and recovered during the capture || Matches SZ Viewer | |||
|- | |||
| 15 || N || <code>2E</code> || Pump motor voltage. SZ Viewer shows it twice: the first line is N × 20 / 255 and the second line is the same byte × 20.5 / 255 (46 = 3.608 V and 3.698 V; 175 = 13.725 V and 14.069 V). Alternates between <code>2E</code> and <code>2F</code>. Rises to battery voltage for a second or two during the ABS pump self-check just after moving off, and after an ABS stop || N × 20 / 255 V || Matches SZ Viewer | |||
|- | |||
| 16 || O || <code>79</code> || Steering angle offset || (O − 128) / 2 degrees (121 = −3.5°) || Matches SZ Viewer | |||
|- | |||
| 17–18 || P–Q || <code>FF FF</code> || Unknown. Stayed <code>FF FF</code> for the whole drive, including braking, so this is not the brake pressure || – || – | |||
|- | |||
| 19 || R || <code>13</code> || Master cylinder pressure. 19 or 20 at rest; about 64 for a light press and 109 for a hard press with the car parked || (R − 20) / 10 MPa (64 = 4.4 MPa, 108 = 8.8 MPa) || Matches SZ Viewer | |||
|- | |||
| 20 || S || <code>80</code> || Lateral acceleration ("G sensor (lateral)"), centred on 128. Positive in a right turn || (S − 128) × 0.02 G || Matches SZ Viewer | |||
|- | |||
| 21–22 || T–U || <code>80 00</code> || Yaw rate, a 16-bit value centred on 32768. Positive in a right turn || ((T × 256 + U) − 32768) × 0.05 °/s (712 = 35.6 °/s) || Matches SZ Viewer | |||
|- | |||
| 23 || V || <code>FF</code> || Unknown || – || – | |||
|- | |||
| 24–25 || W–X || <code>0C 74</code> || 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–27 || Y–Z || <code>00 A2</code> || Steering angle, signed 16-bit. Negative is left, positive is right: −759 at full left lock and +704 at full right lock with the car parked, a span of 1463 counts. The steering wheel turns 4 times lock to lock (1440°), so one count is 1° (0.98° measured). SZ Viewer does not display it || (Y × 256 + Z), minus 65536 if Y ≥ 128, in degrees || Direction confirmed; scale from the lock-to-lock count | |||
|- | |||
| 28–40 || AA–AM || <code>FF FF FF FF A9 FF FF FF FF FF FF FF 40</code> || Unknown; did not change || – || – | |||
|- | |||
| 41 || AN || <code>00</code> || Status flags. Bit 3 (<code>08</code>) is set while the brake pedal is pressed. Bit 6 (<code>40</code>) was set only while manoeuvring at 0 to 2 km/h at the start of the drive, so it may be reverse gear (inferred) || – || Confirmed (bit 3) | |||
|- | |||
| 42 || AO || <code>0E</code> || Status flags. Bit 0 is set together with the brake bit in byte 41 (<code>0E</code> becomes <code>0F</code>) || – || Confirmed | |||
|- | |||
| 43 || AP || <code>00</code> || Bit 0 (<code>01</code>) came on when the ABS cut in (one wheel slowing much faster than the others in a hard stop) and stayed on until the car had stopped (inferred) || – || Fits the drive | |||
|- | |||
| 44 || AQ || <code>40</code> || Status flag (<code>40</code> or <code>00</code>). With the car parked it was clear only while the steering was within about ±10 counts of straight ahead; while driving it also changed during hard stops. Meaning not certain || – || – | |||
|- | |||
| 45 || AR || <code>00</code> || Braking flags. <code>50</code> (bits 4 and 6) during every hard stop (about −0.6 G or more). The low bits and bit 7 were added while a wheel was slipping, for example <code>51</code> and <code>D5</code> when the front right wheel dropped to 1 km/h and the ABS cut in. Which bit belongs to which wheel is not certain (inferred) || – || Fits the drive | |||
|- | |||
| 46–51 || AS–AX || <code>80 03 00 53 FF FF</code> || Unknown; did not change || – || – | |||
|} | |} | ||
== 0x263 EPS controller == | Notes: | ||
* The wheel speeds, acceleration, lateral G, yaw rate and brake pressure were checked against Android screen recordings of SZ Viewer made alongside the 15 November captures. For example, in a tight right turn the screen showed 8 / 11 / 7 / 10 km/h (front right, front left, rear right, rear left), 35.6 °/s and 0.16 G, and bytes 9–12 read 8, 11, 7 and 10 with yaw 712 and lateral 136. In a sharp stop it showed −0.72 G, 7.8 MPa and the rear left wheel at 19 km/h against 22 for the others. | |||
* The steering direction comes from a parked capture that followed a set order (full left lock, then full right lock) and from a drive that started with a left turn at a roundabout. Both gave negative values for left. | |||
* SZ Viewer shows the steering angle offset (−3.5°, byte 16) but not the steering angle itself. The scale of bytes 26–27 comes from counting the turns of the steering wheel from lock to lock (4 turns). | |||
* On the test car, straight ahead reads between about −36° and +9° rather than 0°. A lift kit has been fitted and the steering was only centred by eye afterwards; the steering centre had not been reset since. The centre appears to be held by the [[#0x263 EPS controller|EPS controller]] (bytes 2–3 of its data block), which learns it over time and can be reset with a diagnostic tool; it was reset with a Launch X431 on 15 November 2026. Whether the ABS reading is centred after the reset has not been checked yet. | |||
* Before polling the ABS, SZ Viewer sent one tester-present (<code>3E</code>) to <code>0x7E1</code> 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 [[#0x772 4WD shift controller|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 (Power Steering) == | |||
{{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | {{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | ||
| Line 94: | Line 334: | ||
|- | |- | ||
| <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) | |||
|- | |||
| <code>30 E0 07 80 80</code>, then <code>30 03 08 80 80</code>, then <code>30 E0 07 00 80</code> || <code>70 E0 07</code>, <code>70 03 08</code>, <code>70 E0 07</code> || Steering angle (centre) reset, sent by the Launch X431 CRP919. KWP service 30 is input/output control by local identifier; 07 is a short-term adjustment and 08 a long-term (stored) adjustment. Probably: enter centre-learning mode, store the current wheel position as centre, leave the mode (inferred). Afterwards bytes 2–3 of the data block read <code>80 00</code>. Both of the Launch's "steering angle reset" menu items send the same three requests (captured) | |||
|} | |} | ||
=== EPS data block (21 08) layout === | |||
Decoded from two PCAN-View captures of the SZ Viewer PS tab: one on 14 November 2026 with the engine idling and the wheel not turned, and one on 15 November 2026 during a 2-minute drive (up to 42 km/h) that ended with parking manoeuvres at full assist. 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 | |||
|- | |||
| 2–3 || A–B || <code>7F 9D</code> || Stored steering centre offset, centred on <code>8000</code>. It does not change as the wheel is turned, even at full lock. The Suzuki manual says the module corrects the centre by itself over time from the average steering position; on the test car it was −99 on 14 November and −94 on 15 November without any reset. The Launch steering angle reset (see the request table) sets it to exactly <code>80 00</code> || (A × 256 + B) − 32768 (unit not known) || Captured | |||
|- | |||
| 9 || H || <code>7C</code> || Battery voltage. Dips by 1 to 2 V while the motor is assisting hard || H × 30 / 255 V (122 = 14.353 V, 107 = 12.588 V) || Matches SZ Viewer | |||
|- | |||
| 10 || I || <code>CD</code> || Sensor power supply || I × 6.2 / 255 V (205 = 4.984 V, 206 = 5.009 V) || Matches SZ Viewer | |||
|- | |||
| 11 || J || <code>80</code> || Sensor (main) torque, centred on 128 (range 61 to 193 on the drive). Negative when turning one way, positive the other || (J − 128) × 0.153 Nm (91 = −5.665 Nm, 68 = −9.19 Nm) || Matches SZ Viewer | |||
|- | |||
| 12 || K || <code>80</code> || Sensor (sub) torque, the mirror image of byte 11 (J + K is always about 256) || (K − 128) × 0.153 Nm (165 = 5.668 Nm) || Matches SZ Viewer | |||
|- | |||
| 13 || L || <code>81</code> || Control (assist) torque, about twice the sensor torque, clipped at 2 and 255 || (L − 128) × 0.06125 Nm (40 = −5.39 Nm, 2 = −7.717 Nm) || Matches SZ Viewer | |||
|- | |||
| 14 || M || <code>00</code> || Target motor current. Up to 160 (32 A) at full assist. Always positive, whichever way the wheel is turned || M × 0.2 A || Matches SZ Viewer | |||
|- | |||
| 15 || N || <code>00</code> || Measured motor current. Follows byte 14 || N × 0.2 A || Matches SZ Viewer | |||
|- | |||
| 16 || O || <code>00</code> || Vehicle speed || O km/h (up to 42) || Fits the drive | |||
|- | |||
| 18 || Q || <code>27</code> || Engine speed || Q × 20 rpm (780 rpm) || Matches SZ Viewer | |||
|- | |||
| 27 || Z || <code>33</code> || Motor drive voltage (+). Rises when assisting one way || Z × 0.117 − 5.0 V (51 = 0.968 V, 43 = 0.032 V, 98 = 6.47 V) || Matches SZ Viewer | |||
|- | |||
| 28 || AA || <code>33</code> || Motor drive voltage (−). Rises when assisting the other way || AA × 0.117 − 5.0 V (151 = 12.67 V) || Matches SZ Viewer | |||
|- | |||
| 31–32 || AD–AE || <code>00 45</code> || Changed all the time while driving (byte 31 from 0 to 163). Unknown || – || – | |||
|} | |||
The scales were checked against an Android screen recording of SZ Viewer made alongside a parked and low-speed capture on 15 November 2026 (wheel turned to each lock, quick left-right turns, then a short drive). Main and sub torque read 0.002 Nm on the screen with bytes 11 and 12 both at 128, so SZ Viewer adds a tiny offset; it makes no practical difference. Before 15 November this table listed byte 10 as battery voltage (× 0.07 V) and bytes 27–28 as × 0.019 V; both were wrong. | |||
== 0x271 Body control module == | == 0x271 Body control module == | ||
| Line 110: | Line 390: | ||
|- | |- | ||
| <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 || Fits the drive of 15 November 2026 (0 to 52 km/h) | |||
|- | |||
| 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 146: | Line 450: | ||
| <code>1A 8A</code> || <code>5A 8A</code> + ASCII <code>37120-78R0*</code> || ECU identification (captured) | | <code>1A 8A</code> || <code>5A 8A</code> + ASCII <code>37120-78R0*</code> || ECU identification (captured) | ||
|- | |- | ||
| <code>18 00 FF 00</code> || <code>58 00</code> (no codes) or <code>58 01 9A 31 20</code> (one code) || DTCs by status. | | <code>18 00 FF 00</code> || <code>58 00</code> (no codes) or <code>58 01 9A 31 20</code> (one code) || DTCs by status. <code>9A 31</code> is B1A31, "Left front tire pressure low" (confirmed by SZ Viewer). SZ Viewer shows status <code>20</code> as ''History'' (stored, not current); <code>E0</code> was seen in earlier captures (captured) | ||
|- | |- | ||
| <code>21 00</code> || <code>61 00</code> + 100 bytes || Sensor data block: four sensor records | | <code>21 00</code> || <code>61 00</code> + 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 <code>21 00</code>: <code>ATSH798</code>, <code>ATS0</code>, <code>ATL0</code>, <code>ATFCSH798</code>, <code>ATFCSD300000</code>, <code>ATFCSM1</code>, then <code>2100</code>. | ELM327 setup that works for <code>21 00</code>: <code>ATSH798</code>, <code>ATS0</code>, <code>ATL0</code>, <code>ATFCSH798</code>, <code>ATFCSD300000</code>, <code>ATFCSM1</code>, then <code>2100</code>. | ||
=== 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 <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). | |||
{| class="wikitable" | |||
! Byte !! Letter !! Example (hex) !! Meaning !! Formula | |||
|- | |||
| 0–1 || – || <code>61 00</code> || Positive reply to <code>21 00</code> || – | |||
|- | |||
| 2 || A || <code>8E</code> || Module supply voltage || A / 10 V (14.2 V). It dipped to <code>82</code> (13.0 V) and recovered during the capture; SZ Viewer showed 13.3 V (<code>85</code>) at that moment | |||
|- | |||
| 3 || B || <code>01</code> || Unknown || – | |||
|- | |||
| 4–11 || C–J || <code>00</code> ×8 || Unknown, all zero so far || – | |||
|- | |||
| 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 || <code>00000000 4EAA09C9 4EAA0319 4EAA09C9 DD91B525</code> || Log of received sensor IDs. The first slot (52–55) has always been zero; 56–59 holds the most recently received sensor, then the older ones. While driving, the newest ID changed every time one of the four records was updated. In the deflation capture (example above) every filled slot held the left front ID || 4 bytes per slot, hex | |||
|- | |||
| 72–75 || BS–BV || <code>73 73 73 73</code> || Low-pressure warning threshold for each wheel, in wheel-position order (right front, left front, right rear, left rear). Temperature-compensated: each value changes when that wheel's record brings a new temperature (inferred) || value × 0.0137 bar (<code>73</code> = 1.58 bar, 22.9 psi) | |||
|- | |||
| 76–79 || BW–BZ || <code>7D 7D 7D 7D</code> || A second threshold per wheel, in the same order and also temperature-compensated. Possibly the pressure at which the warning clears (inferred) || value × 0.0137 bar (<code>7D</code> = 1.71 bar, 24.8 psi) | |||
|- | |||
| 80–81 || CA–CB || <code>00 00</code> || Unknown || – | |||
|- | |||
| 82–83 || CC–CD || <code>00 00</code> || Vehicle speed. Byte 83 is <code>00</code> or <code>80</code> (a half step). Matched the SZ Viewer "Speed" line on 48 readings in a row during a drive || (CC × 256 + CD) / 128 km/h, or simply CC × 2 to the nearest 2 km/h | |||
|- | |||
| 84–91 || CE–CL || <code>00 90 00 96 00 62 00 69</code> || Four 16-bit counters. While driving they rose by about 290 per second at 25 to 30 mph and wrapped round at 32768, in two closely matched pairs (84–87 and 88–91). Probably ABS wheel-rotation pulse counts, which the module needs for auto-location (inferred) || – | |||
|- | |||
| 92 || CM || <code>00</code> || Low tyre pressure warning lamp. Bit 7 (<code>80</code>) is set while the lamp is on. It came on in the same reply in which the left front pressure fell from 1.603 to 1.507 bar, below that wheel's threshold in byte 73 (1.603 bar), and SZ Viewer changed from "Off" to "On / Blinking" at the same moment || bit 7: 1 = lamp on | |||
|- | |||
| 93–101 || CN–CV || <code>30 33 33 02 01 80 17 00 00</code> || Unknown. Bytes 94–95 were <code>22 22</code> in the engine-off example and <code>44 43</code> at the start of the drive, settling to <code>33 33</code> as the tyres cooled. Byte 96 changed from <code>02</code> to <code>12</code> once the car was moving. Byte 94 also changed from <code>34</code> to <code>24</code> when the first pressure drop was reported in the deflation capture || – | |||
|} | |||
Each sensor record is 10 bytes. Offsets are from the start of the record, as in the example at the top of the page. | |||
{| class="wikitable" | |||
! 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 in the top five bits, as learned by the module's auto-location (see notes). The bottom three bits are status flags: bit 2 was set on each sensor's first transmission after moving off and bit 0 a little later (<code>10</code> → <code>14</code> → <code>15</code>) || INT(value / 8): 1 = right front, 2 = left front, 3 = right rear, 4 = left rear. Plain value / 8 is wrong once the car has moved || <code>10</code> left front / <code>20</code> left rear / <code>18</code> right rear / <code>08</code> right front | |||
|- | |||
| +5 || P / Z / AJ / AT || Air temperature || value − 50 °C || <code>3C</code> 10 °C / <code>3B</code> 9 °C / <code>3B</code> 9 °C / <code>3C</code> 10 °C | |||
|- | |||
| +6 || Q / AA / AK / AU || Air pressure || value × 0.0137 bar (× 1.37 kPa, × 0.1987 psi) || <code>89</code> 1.877 / <code>89</code> 1.877 / <code>85</code> 1.822 / <code>87</code> 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 || <code>38</code> 28 g / <code>35</code> 26.5 g / <code>15</code> 10.5 g / <code>0D</code> 6.5 g | |||
|- | |||
| +8 || S / AC / AM / AW || Sensor status, shown by SZ Viewer as battery status || <code>42</code> is shown as Normal. <code>49</code> in the engine-off example and <code>4C</code> in data held from parking; each sensor changed to <code>42</code> on its first transmission while moving, and one sent <code>82</code> once. While the left front tyre was being deflated it sent <code>4A</code> (bit 3 set), which looks like the sensor's pressure-drop alert mode. Probably a sensor mode or frame type as well as the battery state (inferred) || all <code>42</code>, Normal | |||
|- | |||
| +9 || T / AD / AN / AX || Unknown || – || all <code>00</code> | |||
|} | |||
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). | |||
* Driving capture (15 November 2026, about 3 minutes, up to about 40 mph): the highest +7 value was <code>51</code> (40.5 g). At 40 mph a valve at about 0.19 m radius sees roughly 45 g, so this supports the ÷ 2 scaling. Each sensor sent a new record roughly every 10 to 30 seconds while driving. | |||
* Temperatures fell from 16–19 °C (held from an earlier drive) to 7–8 °C during the drive, and the pressures fell with them (for example <code>90</code> to <code>80</code>, 1.97 to 1.75 bar). The thresholds in bytes 72–79 dropped at the same moments: <code>77</code> to <code>73</code> (1.63 to 1.58 bar) for a fall from 18 °C to 7 °C, which is what the gas law predicts for a cold-pressure threshold. | |||
* 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 and the low-pressure lamp. Both were found with a capture on 15 November 2026 alongside an Android screen recording: the left front tyre was let down while parked (1.877 to 1.48 bar) until the lamp came on, and the car was then driven for about 7 minutes with the lamp on. The speed is bytes 82–83 and the lamp is byte 92 bit 7 (see the table). The lamp came on below the threshold in byte 73 (the left front wheel's threshold), which supports the reading of bytes 72–75 as the low-pressure thresholds. | |||
* 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>. | |||
== 0x79A Combination switch (lighting and turn) == | == 0x79A Combination switch (lighting and turn) == | ||
| Line 164: | Line 540: | ||
|- | |- | ||
| <code>1A 8A</code> || <code>5A 8A</code> + ASCII <code>37210-74PE*</code> || ECU identification (captured) | | <code>1A 8A</code> || <code>5A 8A</code> + ASCII <code>37210-74PE*</code> || ECU identification (captured) | ||
|- | |||
| <code>1A 90</code>, <code>1A 8D</code>, <code>1A 99</code>, <code>1A 98</code> || <code>7F 1A 12</code> || Refused: identifier not supported. Tried by SZ Viewer (captured) | |||
|- | |- | ||
| <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) | ||
| Line 185: | Line 563: | ||
== 0x793 Airbag (SRS) controller == | == 0x793 Airbag (SRS) controller == | ||
{{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | |||
Request <code>0x793</code>, reply <code>0x7A3</code>. Matches parts catalogue entry 38910-78RC0 (airbag controller, VAN). | Request <code>0x793</code>, reply <code>0x7A3</code>. Matches parts catalogue entry 38910-78RC0 (airbag controller, VAN). | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 196: | Line 576: | ||
|- | |- | ||
| <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 | |||
|} | |} | ||
== 0x772 4WD shift controller == | == 0x772 4WD shift controller == | ||
{{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | |||
Request <code>0x772</code>, reply <code>0x782</code>. Matches parts catalogue entry 38885-78R01 (4WD shift controller). | Request <code>0x772</code>, reply <code>0x782</code>. Matches parts catalogue entry 38885-78R01 (4WD shift controller). | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 214: | Line 621: | ||
|- | |- | ||
| <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>. | ||
== 0x799 E-call controller == | == 0x799 E-call controller == | ||
{{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | |||
Request <code>0x799</code>, reply <code>0x7A9</code>. Matches parts catalogue entries 38960-78RA0 and RA1 (E-call controller). | Request <code>0x799</code>, reply <code>0x7A9</code>. Matches parts catalogue entries 38960-78RA0 and RA1 (E-call controller). | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 233: | Line 660: | ||
|- | |- | ||
| <code>19 02 FF</code> || <code>59 02 4B 92 4E 00 02</code> || One stored code record: <code>92 4E 00</code>, status <code>02</code>. The Launch report does not list it and its meaning is not known (captured) | | <code>19 02 FF</code> || <code>59 02 4B 92 4E 00 02</code> || One stored code record: <code>92 4E 00</code>, status <code>02</code>. The Launch report does not list it and its meaning is not known (captured) | ||
|- | |||
| <code>1A 8A</code>, <code>1A 8E</code>, <code>1A 8D</code>, <code>1A 90</code>, <code>1A 91</code>, <code>1A 98</code>, <code>1A 99</code>, <code>1A 9A</code> || <code>7F 1A 11</code> || Refused: service not supported. Sent by SZ Viewer (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 00</code>, <code>18 00 FF FF</code> || <code>7F 18 11</code> || Refused: service not supported. Sent by SZ Viewer (captured) | |||
|} | |} | ||
SZ Viewer talks to this module with KWP-style requests (<code>3E</code>, <code>1A</code>, <code>18</code>), which it refuses, so SZ Viewer cannot read its identification or fault codes and does not show the <code>92 4E 00</code> record. Only the UDS requests above work. SZ Viewer did not send <code>19 02 FF</code>, so its scan does not show whether that record is still stored. | |||
== 0x751 Central gateway == | == 0x751 Central gateway == | ||
{{Models|JB74 (2018+, tested on 2021)|untested=JB64, JC74, JB43}} | |||
Request <code>0x751</code>, reply <code>0x761</code>. The label on the module reads 33580-79R01. | Request <code>0x751</code>, reply <code>0x761</code>. The label on the module reads 33580-79R01. | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 251: | Line 685: | ||
== Addresses probed with no reply == | == Addresses probed with no reply == | ||
The scan tool sent tester-present (<code>3E</code>) about eight times each to <code>0x273</code> and <code>0x262</code> and received nothing from the expected reply IDs (<code>0x673</code> and <code>0x662</code>). | The Launch scan tool sent tester-present (<code>3E</code>) about eight times each to <code>0x273</code> and <code>0x262</code> and received nothing from the expected reply IDs (<code>0x673</code> and <code>0x662</code>). | ||
The SZ Viewer scan of 14 November 2026 probed 0x262 and 0x273 too, and also sent tester-present (<code>3E</code>, <code>3E 00</code> or <code>3E 01</code>) to the addresses below. None of them answered, in either of two full passes: | |||
{| class="wikitable" | |||
! 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 [[#0x261 ABS (inferred)|ABS notes]]) or an auto-levelling controller. Which module each address belongs to is a guess. | |||
== ELM327 notes == | == ELM327 notes == | ||
| Line 262: | Line 708: | ||
* Suzuki Jimny parts catalogue 9900B-40312-004 (type 1, October 2021), figures 350A, 351A and 351B. | * 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. | * 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. | |||
* Owner PCAN-View captures of the SZ Viewer ABS/ESP, PS and TPMS tabs while driving, 15 November 2026. | |||
* Owner PCAN-View captures of the SZ Viewer ABS/ESP, PS and TPMS tabs with matching Android screen recordings (parked steering and braking, a drive with ABS stops, power steering at full assist, and a TPMS deflation and drive with the lamp on), 15 November 2026. | |||
* Owner PCAN-View captures of the Launch X431 CRP919 steering angle reset (EPS), 15 November 2026. | |||
[[Category:Electrical - gen4]] | [[Category:Electrical - gen4]] | ||
Latest revision as of 16:53, 15 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) and18(read DTCs by status). UDS-style modules use22(read data by identifier) and19(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 8Eor22 F1 01) has no trailing character; the second (1A 8Aor22 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:
066is the total length in hex: 0x66 = 102 bytes. The lines0:toE:carry those bytes in order.- The data starts
61 00(positive reply to21 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.
ATSHand theATFCsettings last until the adapter is reset (ATZ) or loses power, so send them again after either.- Without the
ATFClines, 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 thatATSH798was 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 used30 00 00and 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). The driving capture of 15 November 2026 shows wheel speeds, yaw rate, steering angle and brake pressure in its data block, which confirms it is the ABS/ESP module.
| 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" |
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 once when the ABS/ESP tab opens; only 18 00 FF 00 is accepted (captured)
|
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 PCAN-View captures of the SZ Viewer app (ABS/ESP tab): one on 14 November 2026 with the engine idling and the car stationary, and three on 15 November 2026. The 15 November captures were an 8-minute drive, a parked capture with the steering turned to each lock and the brake pressed lightly and hard, and a 7-minute drive with a roundabout, left and right turns and three sharp stops (the last with the ABS cutting in). The last two were made alongside Android screen recordings of SZ Viewer. Matches SZ Viewer means the formula reproduces the value on the SZ Viewer screen at the same moment. Fits the drive means the byte behaved as expected while driving; the scale is not confirmed. 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–8 | A–G | 00 ×7 |
Unknown. Stayed at zero for the whole drive | – | – |
| 9 | H | 00 |
Wheel speed, front right | H km/h | Matches SZ Viewer |
| 10 | I | 00 |
Wheel speed, front left | I km/h | Matches SZ Viewer |
| 11 | J | 00 |
Wheel speed, rear right | J km/h | Matches SZ Viewer |
| 12 | K | 00 |
Wheel speed, rear left | K km/h | Matches SZ Viewer |
| 13 | L | 80 |
Longitudinal acceleration ("Acceleration"), centred on 128. Negative when braking (−36 = −0.72 G in a sharp stop) | (L − 128) × 0.02 G | Matches SZ Viewer |
| 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. SZ Viewer shows it twice: the first line is N × 20 / 255 and the second line is the same byte × 20.5 / 255 (46 = 3.608 V and 3.698 V; 175 = 13.725 V and 14.069 V). Alternates between 2E and 2F. Rises to battery voltage for a second or two during the ABS pump self-check just after moving off, and after an ABS stop |
N × 20 / 255 V | 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 |
Unknown. Stayed FF FF for the whole drive, including braking, so this is not the brake pressure |
– | – |
| 19 | R | 13 |
Master cylinder pressure. 19 or 20 at rest; about 64 for a light press and 109 for a hard press with the car parked | (R − 20) / 10 MPa (64 = 4.4 MPa, 108 = 8.8 MPa) | Matches SZ Viewer |
| 20 | S | 80 |
Lateral acceleration ("G sensor (lateral)"), centred on 128. Positive in a right turn | (S − 128) × 0.02 G | Matches SZ Viewer |
| 21–22 | T–U | 80 00 |
Yaw rate, a 16-bit value centred on 32768. Positive in a right turn | ((T × 256 + U) − 32768) × 0.05 °/s (712 = 35.6 °/s) | Matches SZ Viewer |
| 23 | V | 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–27 | Y–Z | 00 A2 |
Steering angle, signed 16-bit. Negative is left, positive is right: −759 at full left lock and +704 at full right lock with the car parked, a span of 1463 counts. The steering wheel turns 4 times lock to lock (1440°), so one count is 1° (0.98° measured). SZ Viewer does not display it | (Y × 256 + Z), minus 65536 if Y ≥ 128, in degrees | Direction confirmed; scale from the lock-to-lock count |
| 28–40 | AA–AM | FF FF FF FF A9 FF FF FF FF FF FF FF 40 |
Unknown; did not change | – | – |
| 41 | AN | 00 |
Status flags. Bit 3 (08) is set while the brake pedal is pressed. Bit 6 (40) was set only while manoeuvring at 0 to 2 km/h at the start of the drive, so it may be reverse gear (inferred) |
– | Confirmed (bit 3) |
| 42 | AO | 0E |
Status flags. Bit 0 is set together with the brake bit in byte 41 (0E becomes 0F) |
– | Confirmed |
| 43 | AP | 00 |
Bit 0 (01) came on when the ABS cut in (one wheel slowing much faster than the others in a hard stop) and stayed on until the car had stopped (inferred) |
– | Fits the drive |
| 44 | AQ | 40 |
Status flag (40 or 00). With the car parked it was clear only while the steering was within about ±10 counts of straight ahead; while driving it also changed during hard stops. Meaning not certain |
– | – |
| 45 | AR | 00 |
Braking flags. 50 (bits 4 and 6) during every hard stop (about −0.6 G or more). The low bits and bit 7 were added while a wheel was slipping, for example 51 and D5 when the front right wheel dropped to 1 km/h and the ABS cut in. Which bit belongs to which wheel is not certain (inferred) |
– | Fits the drive |
| 46–51 | AS–AX | 80 03 00 53 FF FF |
Unknown; did not change | – | – |
Notes:
- The wheel speeds, acceleration, lateral G, yaw rate and brake pressure were checked against Android screen recordings of SZ Viewer made alongside the 15 November captures. For example, in a tight right turn the screen showed 8 / 11 / 7 / 10 km/h (front right, front left, rear right, rear left), 35.6 °/s and 0.16 G, and bytes 9–12 read 8, 11, 7 and 10 with yaw 712 and lateral 136. In a sharp stop it showed −0.72 G, 7.8 MPa and the rear left wheel at 19 km/h against 22 for the others.
- The steering direction comes from a parked capture that followed a set order (full left lock, then full right lock) and from a drive that started with a left turn at a roundabout. Both gave negative values for left.
- SZ Viewer shows the steering angle offset (−3.5°, byte 16) but not the steering angle itself. The scale of bytes 26–27 comes from counting the turns of the steering wheel from lock to lock (4 turns).
- On the test car, straight ahead reads between about −36° and +9° rather than 0°. A lift kit has been fitted and the steering was only centred by eye afterwards; the steering centre had not been reset since. The centre appears to be held by the EPS controller (bytes 2–3 of its data block), which learns it over time and can be reset with a diagnostic tool; it was reset with a Launch X431 on 15 November 2026. Whether the ABS reading is centred after the reset has not been checked yet.
- Before polling the ABS, SZ Viewer sent one tester-present (
3E) to0x7E1and 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 (Power Steering)
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) |
30 E0 07 80 80, then 30 03 08 80 80, then 30 E0 07 00 80 |
70 E0 07, 70 03 08, 70 E0 07 |
Steering angle (centre) reset, sent by the Launch X431 CRP919. KWP service 30 is input/output control by local identifier; 07 is a short-term adjustment and 08 a long-term (stored) adjustment. Probably: enter centre-learning mode, store the current wheel position as centre, leave the mode (inferred). Afterwards bytes 2–3 of the data block read 80 00. Both of the Launch's "steering angle reset" menu items send the same three requests (captured)
|
EPS data block (21 08) layout
Decoded from two PCAN-View captures of the SZ Viewer PS tab: one on 14 November 2026 with the engine idling and the wheel not turned, and one on 15 November 2026 during a 2-minute drive (up to 42 km/h) that ended with parking manoeuvres at full assist. 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 |
|---|---|---|---|---|---|
| 2–3 | A–B | 7F 9D |
Stored steering centre offset, centred on 8000. It does not change as the wheel is turned, even at full lock. The Suzuki manual says the module corrects the centre by itself over time from the average steering position; on the test car it was −99 on 14 November and −94 on 15 November without any reset. The Launch steering angle reset (see the request table) sets it to exactly 80 00 |
(A × 256 + B) − 32768 (unit not known) | Captured |
| 9 | H | 7C |
Battery voltage. Dips by 1 to 2 V while the motor is assisting hard | H × 30 / 255 V (122 = 14.353 V, 107 = 12.588 V) | Matches SZ Viewer |
| 10 | I | CD |
Sensor power supply | I × 6.2 / 255 V (205 = 4.984 V, 206 = 5.009 V) | Matches SZ Viewer |
| 11 | J | 80 |
Sensor (main) torque, centred on 128 (range 61 to 193 on the drive). Negative when turning one way, positive the other | (J − 128) × 0.153 Nm (91 = −5.665 Nm, 68 = −9.19 Nm) | Matches SZ Viewer |
| 12 | K | 80 |
Sensor (sub) torque, the mirror image of byte 11 (J + K is always about 256) | (K − 128) × 0.153 Nm (165 = 5.668 Nm) | Matches SZ Viewer |
| 13 | L | 81 |
Control (assist) torque, about twice the sensor torque, clipped at 2 and 255 | (L − 128) × 0.06125 Nm (40 = −5.39 Nm, 2 = −7.717 Nm) | Matches SZ Viewer |
| 14 | M | 00 |
Target motor current. Up to 160 (32 A) at full assist. Always positive, whichever way the wheel is turned | M × 0.2 A | Matches SZ Viewer |
| 15 | N | 00 |
Measured motor current. Follows byte 14 | N × 0.2 A | Matches SZ Viewer |
| 16 | O | 00 |
Vehicle speed | O km/h (up to 42) | Fits the drive |
| 18 | Q | 27 |
Engine speed | Q × 20 rpm (780 rpm) | Matches SZ Viewer |
| 27 | Z | 33 |
Motor drive voltage (+). Rises when assisting one way | Z × 0.117 − 5.0 V (51 = 0.968 V, 43 = 0.032 V, 98 = 6.47 V) | Matches SZ Viewer |
| 28 | AA | 33 |
Motor drive voltage (−). Rises when assisting the other way | AA × 0.117 − 5.0 V (151 = 12.67 V) | Matches SZ Viewer |
| 31–32 | AD–AE | 00 45 |
Changed all the time while driving (byte 31 from 0 to 163). Unknown | – | – |
The scales were checked against an Android screen recording of SZ Viewer made alongside a parked and low-speed capture on 15 November 2026 (wheel turned to each lock, quick left-right turns, then a short drive). Main and sub torque read 0.002 Nm on the screen with bytes 11 and 12 both at 128, so SZ Viewer adds a tiny offset; it makes no practical difference. Before 15 November this table listed byte 10 as battery voltage (× 0.07 V) and bytes 27–28 as × 0.019 V; both were wrong.
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 | Fits the drive of 15 November 2026 (0 to 52 km/h) |
| 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 | – |
| 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 |
Log of received sensor IDs. The first slot (52–55) has always been zero; 56–59 holds the most recently received sensor, then the older ones. While driving, the newest ID changed every time one of the four records was updated. In the deflation capture (example above) every filled slot held the left front ID | 4 bytes per slot, hex |
| 72–75 | BS–BV | 73 73 73 73 |
Low-pressure warning threshold for each wheel, in wheel-position order (right front, left front, right rear, left rear). Temperature-compensated: each value changes when that wheel's record brings a new temperature (inferred) | value × 0.0137 bar (73 = 1.58 bar, 22.9 psi)
|
| 76–79 | BW–BZ | 7D 7D 7D 7D |
A second threshold per wheel, in the same order and also temperature-compensated. Possibly the pressure at which the warning clears (inferred) | value × 0.0137 bar (7D = 1.71 bar, 24.8 psi)
|
| 80–81 | CA–CB | 00 00 |
Unknown | – |
| 82–83 | CC–CD | 00 00 |
Vehicle speed. Byte 83 is 00 or 80 (a half step). Matched the SZ Viewer "Speed" line on 48 readings in a row during a drive |
(CC × 256 + CD) / 128 km/h, or simply CC × 2 to the nearest 2 km/h |
| 84–91 | CE–CL | 00 90 00 96 00 62 00 69 |
Four 16-bit counters. While driving they rose by about 290 per second at 25 to 30 mph and wrapped round at 32768, in two closely matched pairs (84–87 and 88–91). Probably ABS wheel-rotation pulse counts, which the module needs for auto-location (inferred) | – |
| 92 | CM | 00 |
Low tyre pressure warning lamp. Bit 7 (80) is set while the lamp is on. It came on in the same reply in which the left front pressure fell from 1.603 to 1.507 bar, below that wheel's threshold in byte 73 (1.603 bar), and SZ Viewer changed from "Off" to "On / Blinking" at the same moment |
bit 7: 1 = lamp on |
| 93–101 | CN–CV | 30 33 33 02 01 80 17 00 00 |
Unknown. Bytes 94–95 were 22 22 in the engine-off example and 44 43 at the start of the drive, settling to 33 33 as the tyres cooled. Byte 96 changed from 02 to 12 once the car was moving. Byte 94 also changed from 34 to 24 when the first pressure drop was reported in the deflation capture |
– |
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 in the top five bits, as learned by the module's auto-location (see notes). The bottom three bits are status flags: bit 2 was set on each sensor's first transmission after moving off and bit 0 a little later (10 → 14 → 15) |
INT(value / 8): 1 = right front, 2 = left front, 3 = right rear, 4 = left rear. Plain value / 8 is wrong once the car has moved | 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 status, shown by SZ Viewer as battery status | 42 is shown as Normal. 49 in the engine-off example and 4C in data held from parking; each sensor changed to 42 on its first transmission while moving, and one sent 82 once. While the left front tyre was being deflated it sent 4A (bit 3 set), which looks like the sensor's pressure-drop alert mode. Probably a sensor mode or frame type as well as the battery state (inferred) |
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).
- Driving capture (15 November 2026, about 3 minutes, up to about 40 mph): the highest +7 value was
51(40.5 g). At 40 mph a valve at about 0.19 m radius sees roughly 45 g, so this supports the ÷ 2 scaling. Each sensor sent a new record roughly every 10 to 30 seconds while driving. - Temperatures fell from 16–19 °C (held from an earlier drive) to 7–8 °C during the drive, and the pressures fell with them (for example
90to80, 1.97 to 1.75 bar). The thresholds in bytes 72–79 dropped at the same moments:77to73(1.63 to 1.58 bar) for a fall from 18 °C to 7 °C, which is what the gas law predicts for a cold-pressure threshold. - 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 and the low-pressure lamp. Both were found with a capture on 15 November 2026 alongside an Android screen recording: the left front tyre was let down while parked (1.877 to 1.48 bar) until the lamp came on, and the car was then driven for about 7 minutes with the lamp on. The speed is bytes 82–83 and the lamp is byte 92 bit 7 (see the table). The lamp came on below the threshold in byte 73 (the left front wheel's threshold), which supports the reading of bytes 72–75 as the low-pressure thresholds.
- SZ Viewer sends
21 00every 0.12 to 0.15 s and18 00 FF 00about every 2 s, with flow control30 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
0x798has been tested with an ELM327. For other modules, setATSHto the request ID andATFCSHto the same ID, and you may needATCRAwith 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
30and 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.
- Owner PCAN-View captures of the SZ Viewer ABS/ESP, PS and TPMS tabs while driving, 15 November 2026.
- Owner PCAN-View captures of the SZ Viewer ABS/ESP, PS and TPMS tabs with matching Android screen recordings (parked steering and braking, a drive with ABS stops, power steering at full assist, and a TPMS deflation and drive with the lamp on), 15 November 2026.
- Owner PCAN-View captures of the Launch X431 CRP919 steering angle reset (EPS), 15 November 2026.