Lexus RX400h Custom PIDs

I do not have any PIDs for RX400h, most likely it has to be built from scratch.

Firstly, the user need to identify which protocol it is using. By looking at the DLC3 connector, which are the pins have connection. e.g. pin 4, 5, 16, 6, 14 and possibly 7. Since RX400h was introduced after Gen2, I guess CAN must be one of them. Alternatively, user can also use any terminal program and type AT DP to display the protocol detected by ELM327.

Next, we need to find out the physical address of the ECUs. For CAN, 7E0 is typically for ECM and 7E2 is typically for HV ECU in hybrid.

After finding the address, we can inquire the ECUs for the PID Map. Using the TEST PID in Torque, send 2100, 2120, 2140,..., 21E0 to get the map.

With the map, using TEST PID again to send the valid PID to get the response. After this point, it is a challenge to get the correct scaling and offset for the response and it is pretty much guesswork and observations.

Vincent

 

Vincent, I'm gona guess that your guess is not right
although it was called a 2006 - our 400h was manufactured in 2005 around july. all that to say the 400h was introduced during the early / mid run of the Gen II Prius and not after. The Gen II ran all the way to 2009. It's pretty much the same deal, but for the larger traction pack, and the option of all-wheel drive, which btw our model has.

.

 

The Gen II was introduced in 2003 model year 2004 and your 400h was introduced 2 years later, that is why I said after. When people talk about what date a car was introduced, they usually refer to their launch date, not the EOL date or the stop production date, no?

Vincent

 

I don't know. maybe it's just me. I'd guess that production that overlapped during about 2/3 of of the run, would be considered the same run . . . rather than the next generation's run. That just goes to show you what I know. 1 thing is for certain there are a ton of 400h's out on the road. I see them everyday. They do share the same type of multi function display (resolution) as the gen II prius . . . as well as the dvd map data base and reader. .. and another identical elements.

SGH-I717R ? 2

 

Hi USBseawolf,
Was any progress made on getting the RX400H PID data?
Have an RX400h here if that helps...

I been using PriiDash and a clone ELM327 but am getting buffer overrun when in ATM logging mode.

regards,

 

I'm using TorQue Pro with the PRIUS PIDs loaded and most seem to be work the same when connect to RX400h

 

There is also a PID scanner in TorQue but seems to get slower and slower untill it hangs and then termintaes

 

GenII & USBseaWolfs GenII Metric PIDs ( although some Temp are F not C )

When i do the PID 2100 Test i notice the response changes periodically ... ( is it normal or a quirk of my clone BT em327 adapter)

There should be additional PIDs for the AWD mode..

The 7e3 Battery ECU reports the extra HV modules ( need to add more PIDS for these V and IR of the extras)
and the higher module voltage reports fine)

The Rx400/Harrier came out in 2005 so it stands to reason its based on GenII technology enhanced for higher power. Same MFD and Nav also.
Can EV-Mode be invoked from the CAN Bus ?? or only from hardware EV button ? ( RX400 (2007) did not have the EV-Mode button installed)

 

ID DLC Data Period Count Comment
020 3 00 00 07 13 82237
022 8 01 FF 01 FA 00 00 00 25 13 82235
023 7 02 02 02 05 00 00 35 13 82236
025 8 00 DF 00 01 78 78 78 75 13 82238
036 5 1E 00 00 00 59 8 121144
03C 7 04 00 52 00 10 00 A9 8 121148
0A2 8 A0 00 00 00 00 20 00 6A 13 82237
0B0 8 00 00 00 00 11 00 00 C9 13 82237
0B2 8 00 00 00 00 11 00 00 CB 13 82235
0B4 8 00 00 00 00 00 00 00 BC 13 82236
120 8 00 00 00 00 10 20 05 5E 17 60573
122 5 CC 00 00 00 F4 17 60573
230 7 00 00 00 01 00 00 3A 25 41118
244 8 18 88 00 00 00 00 00 EE 25 42139
262 4 00 05 00 6D 21 49670
2C6 5 00 00 00 00 CD 34 31265
320 3 00 00 26 52 20559
340 7 00 00 00 00 00 00 4A 52 20621
3CF 5 10 09 19 00 09 142 7568
420 8 00 01 FF D2 00 00 00 FE 1082 989
423 1 00 1091 985
4C1 8 01 00 08 01 00 00 00 00 985 1090
4C3 8 03 00 06 00 00 00 00 00 1004 1066
4C6 8 07 00 01 00 00 00 00 00 1040 1035
4C7 8 08 00 01 00 00 00 00 00 1051 1022
4C8 8 09 00 08 03 00 00 00 00 1059 1013
4CD 8 0E 00 01 03 00 00 00 00 1118 960
4CE 8 0F 00 01 03 00 00 00 00 1125 954
4D0 8 10 00 20 04 00 00 00 00 1136 946
520 3 A4 01 6C 1299 127
521 2 23 00 323 3311
526 3 24 00 00 540 1984
527 4 25 01 FA 00 1083 991
528 4 25 00 00 00 540 1986
529 7 28 00 00 85 00 00 00 1082 994
52C 2 23 A9 1083 992
53F 6 57 01 44 CC 80 60 10830 100
540 4 25 80 00 00 1082 992
553 7 58 49 4E 80 00 00 09 10847 100
554 7 58 57 4B 92 41 58 4D 10848 100
56A 3 54 30 00 1083 985
56D 4 65 65 80 7F 1084 993
57F 7 68 00 10 00 00 00 00 1083 995
591 5 26 80 20 00 00 326 3292
5B2 4 25 00 04 00 5408 198
5B6 4 65 45 00 00 1084 992
5C8 4 25 00 00 00 1082 998
5CC 3 24 01 E2 277 3875
5D4 3 24 00 00 1083 1000
5EC 7 28 00 00 00 00 98 72 540 1986
5ED 6 67 08 00 FF 00 00 1061 994
5F8 2 23 40 1082 993
5FC 8 69 40 20 00 00 00 00 00 5442 198
602 2 03 00 55230 17

 

File attached of RX400h CAN pids active

 

Attached file show the actual responses fro RX400h to PID MAP requests fro 7e0 and 7e2.
7e3 is not responding to requests but Torque Pro does display 7e3 PID data intermittently
from the battery ECU ....
( These PID maps were traced with CANhacker V2 ( http://www.canhack.de ) using CANusb from Lawicel

 

I think you did not set the Header. By default, Torque will use 7DF if you did not set the Header. 7DF is functional request so any ECUs that are required to response will reply. You get responses from 7E0 and 7E2 that is why it changes when either ECU reply. You need to use physical addressing by changing the Header to 7E0, 7E2 or 7E3. In this mode, only the physically addressed ECU will reply.

You got responses from Torque because it set the Header before sending the request.

I've decoded your PID Map and added the supported PIDs in the Comment column. You can use the Testing PID function to get me the responses and I 'll try to compile a list for RX400h.

Vincent

 

Hopefully this will not be highjacking too badly. We just got a '06 Highlander Hybrid which I understand is the same platform as the RX400h. I also recently got Torque and am having fun learning how to use it. usbseawolf's GenII PIDs seem to work (haven't checked every one) and I would also like to be able to add the extra battery stuff. So I spent some time in the garage and offer the results here in case they can help. I certainly can't do much more than provide these numbers ;-) File selector wouldn't show me csv that's why these have a txt extension.

HiHy_Test2_result.txt is the result of logging the Test2.csv file. This returns decimal values (usb's method?) so I just grabbed 1 line for each header. I added lines to test 7E3 but those results appear to be the same as 7E2. However, the raw 7E3 log data was variable for several lines (seconds) before settling into the 7E2 pattern. The lines for 7E0 and 7E2 were completely stable. Not sure if any of that is pertinent, or even if it was done correctly.

For HiHy_7E2_test_pids_screencap.txt I made a test.csv file of the supported PIDs then used my phone to test each PID and wrote the responses back to the file. I just added enough columns to hold each result (max was 9). The phone is 2.3 so this was screencap the old-fashioned way That's why I started with just 7E2 but can do others if necessary. On my setup, Torquescan also was able to find the ones up to 2160, and there was nothing found using the 7E3 header.

 

Puzzles me why can get the Battery ECU PIDs from the RX400h at times but can not see this in the logging hardware ... Could this be because the CRC formula is different and so the packet request and/or responses are being discarded most of the time?


Definitely Did have the Headers set to the relevant 7E0, 7E2 and 7E3

 

The headers were SET to 7e0, 7e2, 7e3 as appropriate. TEST PID gave no response to 7e3 Headers, Torque real time display occasionally but does Not update regularly as it should and does in the PRIUS )

Files attached above were from CANhacker log software NOT Torque

Torque Pro TEST PID get no response if header set 7E3 ( works fine if header set to 7E0 or 7E2 ) but Torque REAL TIME Display does eventually capture the 7E3 PIDs and display the 7E3 data . Also CANhacker see NO 7E3 responses.

Thanks for the PID maps Will do some more testing ....

 

The key Battery ECU and hv ECU ID codes are unfortunately missing from this list ... these were the codes used for spoofing battery SOC and EV mode in 2004 PRIUS PHEV upgrades , Now not appearing in this scan code list captured from the OBDII connector port.
Not good news.... more work required for a PHEV upgrade to work