Scangauge X-Gauge Codes for Jul 21+ Models

[ptommo59 Senior Member Find all posts View Profile Close ptommo59]

Hopefully these will work on the new 2.8l 76 Series when I get mine.

I think most of the engine and trans codes will carry over with a few extra ones for the AdBlue SCR system and B1S4 on the EGTs to pickup post SCR Catalyst temp (to setup this one replicate the B1S3 post DPF info and change the 2 at the start of the RXD.to a 3)

[gunda Member Find all posts View Profile Close gunda]

A belated thank you to ptommo59 for doing all the work to establish these codes.

In the list posted nearly two years ago, there were multiple entries for transmission lockup status. I coded the first two and both seem to work. Why are there multiple entries and what is the difference between them? My MY21 Kakadu was built in May June 2021, FWIW.

[ptommo59 Senior Member Find all posts View Profile Close ptommo59]

Hi Gunda,

Thanks for the ack and yes was a bit of work to find the info above but a great learning exercise for me.

To answer your question:

I made two versions of the lock status code Status 1 uses the returned value 0 and 1 to indicate status, the Status 2 version changes the RXF to enable a special feature (2 in fifth position 046225160620) to switch 0 to read as OFF and 1 as ON in the SG2 display (Personal preference which one you prefer to see on screen).

There is also two different PID numbers used: The actual Toyota PID versions with TXD: 0700221620 and the obfuscated (offset) one with TXD: 0700221A80 provided by Scangauge which will only work on a Scangauge with firmware 4.42 or higher and not useable on any other brand products. (Info sent and received by the SG is the same for both PIDS just the published information and internal SG translation needs to be done for the second one).

You only need to pick any one of the four and it should work.

Phil

[gunda Member Find all posts View Profile Close gunda]

Thanks. If I had read the list more carefully I would have noticed the 0/1 vs off/on thing, but still puzzled over the duplicates.

[ptommo59 Senior Member Find all posts View Profile Close ptommo59]

I initially only had the Scangauge published versions but worked out they mask (obfuscate) the actual codes for the non OBDII standard Mode 01 PIDs (potentially to stop competitors reusing their published info, or for protection from Toyota Intellectual property breaches which could cause legal issues).

If you see any Toyota codes published by Scangauge with a C at the start of the RXF the TXD is not the actual code and has been offset. Doesn't affect Scangauge users but can't be converted and used by other brand products.

The list now also includes the actual Toyota codes I located/reverse engineered and have converted the commonly used ones to Torque Pro and Utra-Gauge formats..

[ptommo59 Senior Member Find all posts View Profile Close ptommo59]

A few extra codes for people to try which may be handy if you are having issues with ABS/VSC faults due to wheel speed sensor/s.

The sensor readings are available from the Skid Control (ABS/VSC) and 4WD ECUs. (I believe they work but haven't verified so any feedback of working or otherwise would be helpful)

ITEM	TXD	RXF	RXD	MTH	NAME	Unit	STATUS
FR Wheel Speed (ABS/VSC)	07B02103	046105030000	2808	014600FF0000	FRS	km/h	TBC
FL Wheel Speed (ABS/VSC)	07B02103	046105030000	3008	014600FF0000	FLS	km/h	TBC
RR Wheel Speed (ABS/VSC)	07B02103	046105030000	3808	014600FF0000	RRS	km/h	TBC
RL Wheel Speed (ABS/VSC)	07B02103	046105030000	4008	014600FF0000	RLS	km/h	TBC
Veh Speed (ABS/VSC)	07B02121	046105210000	2808	014600FF0000	SPD	km/h	TBC
FR Wheel Speed (4WD)	07412195	046105950000	2808	014800FF0000	FRS	km/h	TBC
FL Wheel Speed (4WD)	07412195	046105950000	3008	014800FF0000	FLS	km/h	TBC
RR Wheel Speed (4WD)	07412195	046105950000	3808	014800FF0000	RRS	km/h	TBC
RL Wheel Speed (4WD)	07412195	046105950000	4008	014800FF0000	RLS	km/h	TBC
Veh Speed (4WD)	07412195	046105950000	4808	014800FF0000	SPD	km/h	TBC

[ptommo59 Senior Member Find all posts View Profile Close ptommo59]

Deleted duplicate of last post

[GeeWhizz Senior Member Find all posts View Profile Close GeeWhizz]

ptommo59

Senior Member

Find all posts

View Profile

Close

ptommo59 I'm having trouble getting a valid Torque Converter Lock Up Status from my 2023 GXL. While I get a valid response from the ECU using 0700 221620, it never shows a change of state to 'locked'. The torque converter is definitely locking: the Torque Converter outlet temperature quickly matches the pan temperature when lockup occurs.

I have tried the alternative that you list (0700 221A80) but this always returns an error message, rather than a valid response. Edit: I've re-read this thread end to end and I saw that you had explained this previously. I'm not using a Scangauge, so I shouldn't be using this code ayway.

Any thoughts on why 700+221620 does not follow the lockup status?

From the appropriate logs:

14:30:16.913,TxU4@115200:'ATSH700<CR>', Cmd=208 (set header)
14:30:16.915,TxU4@115200:'221620<CR>', Cmd=228

Single response frame: 708 04 62 16 20 00 (response message never changes)
14:30:16.926,Header Matches obdUDSAddress
14:30:16.926,Gearbox: Torque Converter Status
14:30:16.926,0x621620,228,,TqConv_Locked=,0



15:54:39.913,TxU4@115200:'ATSH700<CR>', Cmd=208
15:54:39.915,TxU4@115200:'221A80<CR>', Cmd=228 (alternate command refer to edit, above)

Single response frame: 708 03 7F 22 31
Unrecognised UDS Response Frame

[ptommo59 Senior Member Find all posts View Profile Close ptommo59]

Sorry from looking at your command and response to 221620 everything looks normal (and yes 221A80 only works with a Scangauge as it converts value internally to 221620 before sending to ECM).

A few things worth noting ::

* The TC wont lock when the engine coolant and/or ATF pan temp is under 60 degrees to assist with warming up both.

* The TC will unlock when you take foot off throttle and/or coast downhill etc to reduce engine braking and with fuel cutoff help increase fuel economy.

* I think there is a slight delay between the lock and unlock occurring and the parameter updating as I think the ECM confirms matching amount of slip with the engine RPM and Trans Input Shaft Speeds.


So was your log example taken when those conditions existed?

Also how often are you requesting updates via sending the 221620 Command and are you getting a new valid reply every time?

One suggestion to save bombarding ECM with multiple requests, in UDS you can request several parameters at same time eg. if you want Trans Pan Temp, TC Temp, Current Gear, TC Lock Status to populate a screen you could alter your Command to:

ATSH700
221627162816211620

I believe the reply should come back 708 0D 62 16 27 XX 16 28 XX 16 21 XX 16 20 XX (because of length will be split over two frames).

So your decoder just needs to pick out the XX values from different positions for the individual gauges

You can also do same by using Service 2C to Dynamically Define the combination above under a single DID.

Hope that gives you a couple of ideas to work with.

[GeeWhizz Senior Member Find all posts View Profile Close GeeWhizz]

Thanks for your detailed response. I appreciate your insight into the way things are interrelated. I'll try your suggestions but I don't think they will provide a solution. I had wondered about ATF and coolant temperatures affecting lockups but my ATF temperature data shows that it is getting significantly warmer than 60C. I don't track coolant temperatures at the moment.

I sample Speed, RPM, Selected Gear and Lockup status every 3 seconds and Exhaust, Gearbox Temperatures every 12 seconds, so additional CAN bus loading should not be significant. As far as I can tell, I'm getting valid replies to Speed, Gear, Lockup and GBox Temperature 100% of the time.

To compare speed, gear selection and ATF temperatures, I downloaded the data from my "black box" trip recorder and quickly charted it in Excel. To describe the trip, after initial stuffing around, we set out with the caravan through metro Perth, climbing the Darling Scarp (TC temperature spike). Lunch break around the 6000th sample point. Red lines (RH Vertical Axis) are the selected gear (you can see where I forgot to put the box in 'S' mode!). LH Axis tracks speed (kmh) and temperature (degrees C). You can see that the PAN and TC outlet temperaures align for a substantial part of the journey, although you can see where the TC releases in hilly conditions. At no time** during the trip did the 221620 commands return data indicating a TC lockup.

** Edit: As noted later is this thread, I discovered the reason why I was not setecting a TC Lockup. The older CAN messages indicate Torque Converter lockup with bit #7 of a byte, while UDS uses bit #0

[RPP Senior Member Find all posts View Profile Close RPP]

2018 GXL with GVM upgrade. Has there been a software update in the last year or so?

Just completed my 3rd trip Adelaide-Kununurra via Stuart Hwy, down the CSR and back via the Nullabour highway (typically loaded to 3.3t). Been to the Kimberley and back 4 other times, never towed.
After the 1st trip was obliged to drive it like a manual on the hwy to avoid ATF temp > 120C. Typically ATF temp in the TC will be hi 90C to around 105C when in 4th. Set my scangauge to alert when ATF temp in the TC gets to 110C to signal me to drop to 4th/manual.

But on this year's trip the vehicle wanted to lock, and stay locked, in 5th/Drive, and occasionally 6th on the major highways. Rarely needed to drop into 4th to cool down the ATF. Overall fuel economy was significantly better than previous trips (12.7 vs high 13lt/100).

Anyway, just retired the Prado for a 2.8l 76 series. The 76's performance is substantially superior, ATF temps havent got over 90C yet and it takes off like a startled rabbit, locks and holds lock extremely well. Also comes with a GVM of 3.55t and twin locked from factory. Fuel economy isnt quite as good tho'.
Looking for the OBD codes to read the fuel tank level if anyone has that data.

[ptommo59 Senior Member Find all posts View Profile Close ptommo59]

RPP did you try the Main and Sub Tank codes in the list in this thread as I would think they may work if dual tank?

If yours has the single 130L tank try this code from the FJ Cruiser that may work

TXD: 07C0212C
RXF: 0461052C0000
RXD: 2808
MTH: 000100010000
Name: FLV

Edit: If those three codes give you nothing try replacing the two 2Cs in the x-gauge TXD and RXF above in turn with 21, 22, 23 , 24, 25, 26, 27, 28, 2B,2D, 2E, 2F and test to see if you get a response as pretty sure all the Combination Meter ECU Fuel Tank parameter variations sit in the 2121 to 212F block of codes.

[ptommo59 Senior Member Find all posts View Profile Close ptommo59]

GeeWhizz,
Stumped as it should work, so no certain why your logger is not picking up the state change or why the vehicle would not be reporting state correctly using that code.as works with SGs etc.
On yours you should get TC lockup in 3rd to 6th gear when at operating temps and tends to lock on mild acceleration or constant speed when holding a gear and unlocks during most gear shifts, when coasting/min throttle, or during heavier acceleration.

[RPP Senior Member Find all posts View Profile Close RPP]

RPP did you try the Main and Sub Tank codes in the list in this thread as I would think they may work if dual tank?

If yours has the single 130L tank try this code from the FJ Cruiser that may work

TXD: 07C0212C
RXF: 0461052C0000
RXD: 2808
MTH: 000100010000
Name: FLV

Edit: If those three codes give you nothing try replacing the two 2Cs in the x-gauge TXD and RXF above in turn with 21, 22, 23 , 24, 25, 26, 27, 28, 2B,2D, 2E, 2F and test to see if you get a response as pretty sure all the Combination Meter ECU Fuel Tank parameter variations sit in the 2121 to 212F block of codes.

Thanks ptommo59.
However both the Prado codes and that code come up no bueno on my 2.8l 76.

[ptommo59 Senior Member Find all posts View Profile Close ptommo59]

RPP try running through the other options mentioned in the Edit as pretty sure it will be one of them (try 2B, 2D,2E, 2F first and then backwards from 28 to 21 if no luck).
Edit: don't be concerned if the number is out as it may need a MTH tweek to get right scaling but first need to workout which one responds in that block so let me know what you get back.