ECU diagnostic CAN addresses: Difference between revisions

From BigJimny Wiki
Jump to navigation Jump to search
TPMS 0x798: add full 21 00 data block layout decoded from SZ Viewer capture; confirm B1A31 and voltage byte
Line 62: Line 62:
Reading the reply:
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.
* <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, probably tracks system voltage (about 11.7 V, unconfirmed).
* 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.
* Each wheel has a 10-byte record. Byte +6 of the record is the pressure; bar = raw x 0.01372.


Line 214: Line 214:
| <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. The code <code>9A 31</code> is probably the left front low pressure warning (inferred). The status byte was <code>20</code> in the full scan and <code>E0</code> in earlier captures (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>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 with ID, temperature-like value and pressure. The scan tool repeats it about twice a second (captured, decoded)
| <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. Speed and the warning lamp state may be here || –
|-
| 12–21 || K–T || – || Sensor record 1 || see record table below
|-
| 22–31 || U–AD || – || Sensor record 2 || see record table below
|-
| 32–41 || AE–AN || – || Sensor record 3 || see record table below
|-
| 42–51 || AO–AX || – || Sensor record 4 || see record table below
|-
| 52–71 || AY–BR || <code>00000000 4EAA09C9 4EAA0319 4EAA09C9 DD91B525</code> || Five 4-byte sensor ID slots. Probably a log of recently received sensors: in the deflation capture (example above) every filled slot held the left front ID (inferred) || –
|-
| 72–75 || BS–BV || <code>73 73 73 73</code> || One value per wheel: 1.58 bar (22.9 psi). Possibly the low-pressure warning threshold (inferred) || value × 0.0137 bar
|-
| 76–79 || BW–BZ || <code>7D 7D 7D 7D</code> || One value per wheel: 1.71 bar (24.8 psi). Possibly the threshold at which the warning clears (inferred) || value × 0.0137 bar
|-
| 80–83 || CA–CD || <code>00</code> ×4 || Unknown || –
|-
| 84–91 || CE–CL || <code>00 90 00 96 00 62 00 69</code> || Four 16-bit values (144, 150, 98, 105). All zero in the engine-off example above. Unknown; perhaps signal strength or reception counts || –
|-
| 92–101 || CM–CV || <code>00 30 33 33 02 01 80 17 00 00</code> || Unknown. Bytes 93–95 were <code>30 22 22</code> in the engine-off example || –
|}
Each sensor record is 10 bytes. Offsets are from the start of the record, as in the example at the top of the page.
{| 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 || value / 8: 1 = right front, 2 = left front, 3 = right rear, 4 = left rear || <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 || Acceleration (SZ Viewer label "TPS acceleration") || 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 battery status || <code>42</code> is shown as Normal. <code>49</code> in the engine-off example; other values not yet decoded || 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 car was stationary during the capture, so the acceleration values are probably held from each sensor's last transmission while moving. Unconfirmed.
* SZ Viewer also shows speed (0 km/h) and the low-pressure lamp (Off). Which bytes carry these is not known yet; a capture while driving with the lamp on should show them.
* SZ Viewer sends <code>21 00</code> every 0.12 to 0.15 s and <code>18 00 FF 00</code> about every 2 s, with flow control <code>30 00 00</code>.


== 0x79A Combination switch (lighting and turn) ==
== 0x79A Combination switch (lighting and turn) ==
Line 338: Line 402:
* 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 capture of the SZ Viewer app (TPMS tab, ELM327 v1.5 Bluetooth adapter) with a matching screenshot, 14 November 2026.


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

Revision as of 11:52, 14 November 2026

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

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

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

How to read this page

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

Example usage

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

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

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

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

Reading the reply:

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

Notes:

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

Device table

Request ID Reply ID Style Module Identification reply (first / second) How the module was identified
0x7E0 0x7E8 KWP ECM 33980-78R0 / 33980-78RC* Standard engine address
0x261 0x661 KWP ABS (inferred) 56100-77RA / 56100-78RF* Only brake module left by elimination
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

Two more addresses, 0x273 and 0x262, were probed by the scan tool and 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, so standard mode 01 PIDs should be available here, but none were captured.

Request Reply Meaning
3E 7E Tester present (captured)
1A 8E 5A 8E + ASCII 33980-78R0 ECU identification (captured)
1A 8A 5A 8A + ASCII 33980-78RC* ECU identification (captured)
18 00 FF 00 58 00 Read DTCs by status: none stored (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. Not confirmed.

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)

0x263 EPS controller

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

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

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

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)

0x274 Instrument cluster

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

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

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

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

0x798 TPMS controller

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

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

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

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

Sensor data block (21 00) layout

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

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

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

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

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

Notes:

  • The records are stored in sensor-ID order, not wheel order. Use byte +4 to find the wheel, especially after the tyres have been rotated.
  • SZ Viewer scales pressure by exactly 0.0137 bar per count (all four values match to three decimals). The 0.01372 used in the example above gives the same result to two decimals.
  • The car was stationary during the capture, so the acceleration values are probably held from each sensor's last transmission while moving. Unconfirmed.
  • SZ Viewer also shows speed (0 km/h) and the low-pressure lamp (Off). Which bytes carry these is not known yet; a capture while driving with the lamp on should show them.
  • SZ Viewer sends 21 00 every 0.12 to 0.15 s and 18 00 FF 00 about every 2 s, with flow control 30 00 00.

0x79A Combination switch (lighting and turn)

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

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

Request Reply Meaning
3E 7E Tester present (captured)
1A 8E 5A 8E + ASCII 37210-74PA ECU identification (captured)
1A 8A 5A 8A + ASCII 37210-74PE* ECU identification (captured)
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)

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)

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)

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 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). They are probably modules this car does not have, such as an automatic transmission or auto-levelling controller. This is a guess.

ELM327 notes

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

Sources

  • Owner PCAN-View captures of a Launch X431 CRP919 full health-check scan and rev counter sweep test, October 2026.
  • Suzuki Jimny parts catalogue 9900B-40312-004 (type 1, October 2021), figures 350A, 351A and 351B.
  • Labels on the TPMS controller and central gateway of the test car.
  • Owner PCAN-View capture of the SZ Viewer app (TPMS tab, ELM327 v1.5 Bluetooth adapter) with a matching screenshot, 14 November 2026.