IS 250 PCS and DRCC (Dynamic Radar Cruise Control) Retrofit

[waquidvp]

After seeing a few examples of folks in the community attempting to retrofit PCS (Pre Crash System) + DRCC (Dynamic Radar Cruise Control), some successful and some not, I thought I give it a go on my 2015 IS 250 base model. After figuring out all the parts required, I started on the adventure of trying to get them. Here are all the parts that are required:

• Cruise Switch (84632-30020) + Wire (84633-76020) for DRCC
• Steering Controls (84250-53231-C0)
• Lexus Emblem for Radar (53141-48050)
• Radar (88210-53140) + Bolts (3x 90119-06782)
• Buzzer (86652-50010)
• Network Gateway ECU (89100-30221) + Bolts (2x 90159-50327)
• Driving Support ECU (88150-53052) + Wire (82143-24020) + Bolts (94151-80600)
• PCS Cancel Button (84770-50010)
• Engine Wire Harness with Radar Connector (82112-53340)

Most parts were available in the used market, mostly eBay. Some from within the UK and some from the US. The parts that proved to be more difficult to find were the Driving Support ECU and a matching Radar.

The Driving Support ECU part number that is required is 88150-53052, however from a quick Google search, the only place this part number appears are in parts catalog websites. Digging a bit deeper I first found it on sale in Vladivostok, on a Russian site called wiweb(blocked word). Here is the full link: https://www.wiweb(blocked word)/goods/elektronnyiy_blok_lexus_is250_8815053052_gse30_4gr_8815053052-198031S2997547103.html. I reached out to the seller however he wasn’t sure about how I would pay him and also how he would ship it to the UK with the current restrictions in place. After looking at the parts catalog, I found two other part numbers, one for an older part (88150-53051) used in a previous production batch (2013/06 - 2014/07), and one for a newer part (88150-53053) used in a later production batch (2015/08 - 2016/10). My vehicle was produced 2014/11 and the part I am looking for is from the 2014/07 - 2015/08 production batch. I thought I start looking for these parts in the hope of widening my chances, keeping in mind that these might not actually work in the end. I ended up finding these in Japan, on Yahoo auctions, and bought them through ZenMarket since Yahoo auctions is not available outside of Japan. At first, I found the newer part (88150-53053), and ordered it.

As I waited for the Driving Support ECU, I managed to get the rest of the parts. I fit the Network Gateway ECU, swapped the steering controls, changed the engine wire harness to the one with the radar connector,  the radar itself, swapped the emblem in front of the radar, and finally fit both the PCS cancel button and buzzer. The only thing now remaining was the Driving Support ECU. It’s worth mentioning that the new cruise switch, even though it’s the one for using with radar, works with standard cruise control.

Once the Driving Support ECU arrived, I plugged it in and hit my first issue. I got the following DTC: C1A0A - Front Radar Sensor Region Code Mismatch. Using Techstream, I found that the Radar had the country code set to NA (for North America) and the Driving Support ECU had the country code set to JPN (for Japan). This made sense since the Radar came from the US and the ECU from Japan, so then I ordered a Radar from Japan, again through ZenMarket.

After I got the Radar from Japan and replaced the US one, through Techstream, I used the initialisation utility on the Network Gateway ECU. After clearing all the previous DTC’s, started up everything and no errors. I can now see a cruise control tab in my instrument cluster and when using the cruise switch and the distance switch on the steering, everything seems to react accordingly. When turning on the cruise switch, I can also see “Radar Ready” in the instrument cluster. I went for a test drive, got the car to around 35 MPH and set the speed. For around 1 second, I see the set cruise speed in the cruise control tab but then get an error: “Check Cruise Control System”. Using Techstream, I get the following DTC: C1A52 - Driving Support ECU Communication Abnormal. I will try to record the exact behaviour and post a video soon. My first conclusion was that maybe since it’s a newer ECU, it’s not fully compatible with the rest of the system.

After resetting all the ECU (by disconnecting the negative Battery terminal for around 5 minutes) and trying again, I get the same DTC. Currently I have few theories, but no way to test them:

• Even though there is no region mismatch error being shown in Techstream, since all the other ECU’s, mainly the ECM and the multiplex ECU, in my car would be set to EU (Europe) I suspect that might still be problematic. This is hard to correct, since I can probably never get a Driving Support ECU with the correct part number and region.
• Since the ECU I tried is newer than the one needed and doesn’t match the exact part number, I thought I give the older ECU a try, this was in the market at the time on ZenMarket, so I went ahead and purchased it. Unfortunately that also leads to the same DTC.

Other examples from the community:

• 2011 GX 460 - https://www.clublexus.com/forums/gx-2nd-gen-2010-2023/921818-retrofit-oem-radar-cruise.html
• 2015 GS 350 https://www.clublexus.com/forums/gs-4th-gen-2013-2020/883922-pre-collision-system-retrofit.html
• 2008 GS 450h https://www.lexusownersclub.co.uk/forum/topic/131146-lexus-gs-450h-sport-radar-cruise-control-retrofit/

If anyone has any ideas or thoughts about how to go forward, feel free to respond to this thread.

DTC C1A52.pdf DTC C1A0A.pdf

[Linas.P]

Wow... that is massive undertaking, well done on that! Can't really help you with the issue, I would suspect maybe one of the units is slightly out by one number... and even if they are correct PN they may still refuse to communicate. 

I believe there should be second step of DTCs for radar in Techstrem which shows connectivity between modules, I just cant access it as my car does not have radar cruise... I would suspect something along the lines "module stopped communicating".

I was actually surprised when I discovered that wiring harness for Distance ECU is already there on my car as well. Was almost tempted to see how it would go retrofitting it. 

[waquidvp]

It would be quite straightforward if Lexus still sold the Driving Support ECU, since this is the only part that is very specific to the vehicle, the other parts are somewhat shared with other models, however after asking multiple suppliers, it’s been discontinued by the manufacturer and no one has any old stock.

And unfortunately, from the research I have done so far, I can’t find any cars from this production batch that has the PCS & DRCC option in the UK, so chances of it turning up at the breakers is near to zero.

[waquidvp]

Just to update this thread, I managed to find another project that seems to be experiencing the same issue. Haven't managed to get a response on if it was resolved. See their post: https://www.clublexus.com/forums/rx-3rd-gen-2010-2015/935954-lexus-rx450h-2009-cruise-radar-retrofit.html.

[waquidvp]

While writing up this post, it required me to review all the work I had done so far. I found that I was using the wrong Network Gateway ECU, I thought this could be the root cause, so I got the correct part, which was 89100-30160 instead of 89100-30221 which is from a newer production batch. However after trying it out, the same issue persists.

 

[waquidvp]

Another example of a project out in the wild, this time for a CT200H. No confirmation on if it was successful or not: https://www.clublexus.com/forums/ct-200h-model-2011-2017/928713-retrofit-radar-cruise-control-2.html.

[waquidvp]

I managed to get in touch with the CT200H owner, looks like that was a successful project.

With regards to my status, it seems like the PCS side of things are working. Yesterday I was surprised with the "BRAKE!" warning when I came a little close to someone at the lights. So the issue seems limited to the DRCC part.

[ganzoom]

On 9/18/2023 at 2:07 PM, waquidvp said:

From the research I have done so far, I can’t find any cars from this production batch that has the PCS & DRCC option in the UK, so chances of it turning up at the breakers is near to zero.

We wanted DRCC on our IS300H when we ordered the car new in 2015. When the dealer checked on pre-reg stock they couldn't find a single one with that option fitted, so we had to a new order from the factory.

Good luck, the rear radar for cross traffic when parking is really useful.

[SPC]

With some help from this thread and EEPROM programming I was able to add DRCC and PCS to my 2014 US spec. IS350 AWD. What finally worked was pulling the Driving Support ECU & Engine Control Module and virginizing them, which caused the car to think it has a new ECM.

Process to get the DSU to allow Radar Cruise (disconnect Battery before uninstalling DSU/ECU):

1. Backup ECM and DSU EEPROMs before doing anything. See these photos of the modules: https://imgur.com/a/jU8Jtjv

2. Write the semi-virgin data to the DSU EEPROM. (93LC66 16 bit) See this original and semi-virgin example data for writing. Don't delete the Region information or Part number information. Blank out the information like the example. (Different years and models may look nothing like this). (I'm not 100% sure if this whole step needed)

3. Write all 00's to the Engine Control Module EEPROM (93LC86 16bit)

4. Reinstall virginized ECM and DSU

5. Reconnect Battery. Initiate Immobilizer/ECM learn routine. (Jump Pin 4 and 13 on the OBD2/DLC, Ignition on for 30 minute, then off and start the car

6. Write VIN using Techstream to Engine Control Module (It will show a VIN not programmed DTC). Mine still shows the DTC after writing the VIN, but the check engine light is now off. I'm guess it will disappear eventually)

7. Test DRCC. All seemed to be working well matched leading vehicle speed and braking worked well. No DTC's after 30 min of driving. Radar aiming will likely be necessary to ensure it's properly tracking vehicles in front of you. DRCC should look like this one the instrument cluster: https://imgur.com/a/InCNkBt

Notes:  Be cautious with the ECM modification, there's always a chance of causing the car not to start if something goes wrong.

EEPROM Tools and Guides I used:

• CH341A EEPROM Programmer I used: https://www.amazon.com/dp/B07R5LPTYM?psc=1&ref=ppx_yo2ov_dt_b_product_details
• CH431A EEPROM Programmer modifications needed to support 93LCXX EEPROMSs: YouTube Instructions 
• EEPROM editing software I used: AsProgrammer_v2.1.0.13 (Windows driver included in the driver install folder): https://mega.nz/#!VMR0QQhL!wU4fYzCqjtHfXbD_tyOCRVnd3ahGgjprG_8RnVJ7N3o

Other good things to watch would be this YouTube video also showing modification of the programmer to work on 93LCXX EEPROMs used in Toyotas. The ECM and DSU both have a protective coating sprayed on the boards, so you may need to gently scrape the pins of the EEPROM for good contact with the programmer.

Please keep in mind that I'm not an engineer or an expert, just a hobbyist that enjoys working on cars. These modifications can have expensive/safety repercussions if something goes wrong. 

[waquidvp]

After following the above instructions, big shout out to @SPC, it works! I also found that you don't actually need to do any modifications to the DSU, only the ECM. It just means for who ever tries to attempt this, it's one less step.

The setup I have working is with a Radar and DSU that are both Japan spec, even though my car is EU spec. I am also using a newer DSU than the one which is spec'd for the car. I am using Part No. 88150-52053 instead of 88150-52052 (which I never could find anywhere). This confirms that, you can use a Radar and DSU which is a different spec from the rest of your car, the important thing is to keep the DSU and Radar the same region. This should be helpful for anyone who is trying to get parts but can't find them in their same region. I have found some of these parts are much cheaper in the US.

I will keep testing it and report back if there are any issues or DTC's that come up, but so far it's been clean. I am also fairly certain that I need to get the radar re-calibrated/re-aimed, even though it seems to be working without it for now.

I am also planning to do a full write up for whoever want's to attempt this in the future.