ACC (Adaptive Cruise) Retrofit >> Underway, PSA

[rhill2901]

Even though it’s popping up as reserved, it should still be changing the correct bit for IRCM, but possibly not broadcasting it.
Can you post your current AlfaOBD backup file with that setting set to IRCM (this is the file that has a bunch of line items of numbers and letters that all start with 62)?
Do you have a canbus logger?

I have attached the backup file. Canbus logger? I don't think so. Is it needed? If so, any you recommend? I noticed there are also 3 other reserved settings you can select. How does it differeniate between them? Is it based off a number value thats held in a specific memory slot and not the actual verbage?

Sponsored

 

[Jimmy07]

I have attached the backup file. Canbus logger? I don't think so. Is it needed? If so, any you recommend? I noticed there are also 3 other reserved settings you can select. How does it differeniate between them? Is it based off a number value thats held in a specific memory slot and not the actual verbage?

In your backup file, the line item that starts with 620141 represents 2014 CBC Config I/O. Then followed by 8 bytes that represent all of the possible settings within 2014 cbc Config.

The bit that I have boxed in with red represents a group of 4 settings, with auto high beam location being one of them.
0 means that all 4 of those settings are set to “no”, or “none”.
So, as it stands with your backup file, Auto High Beam Location is currently not set to “IRCM”.
In AlfaOBD, what does your current BCM system ID show it being set to?

 

[rhill2901]

In your backup file, the line item that starts with 620141 represents 2014 CBC Config I/O. Then followed by 8 bytes that represent all of the possible settings within 2014 cbc Config.

The bit that I have boxed in with red represents a group of 4 settings, with auto high beam location being one of them.
0 means that all 4 of those settings are set to “no”, or “none”.
So, as it stands with your backup file, Auto High Beam Location is currently not set to “IRCM”.
In AlfaOBD, what does your current BCM system ID show it being set to?

My bad. I tried several settings on it in jscan and left it on as undefined. Use these files instead. I also including a bcm dump to show the settings. I have correctly selected ICRM, and alphaOBD is saying it is set for ICRM. However, JSCAN live data, and witech2 show it as reserved.

 

[Jimmy07]

My bad. I tried several settings on it in jscan and left it on as undefined. Use these files instead. I also including a bcm dump to show the settings. I have correctly selected ICRM, and alphaOBD is saying it is set for ICRM. However, JSCAN live data, and witech2 show it as reserved.

Ok. Your BCM dump shows location set to IRCM, but your backup file shows that it is still set to “none”. Your BCM dump also does not reveal two other related settings- auto high beam threshold on and off speed, and your backup file shows those being set at 0 km/h (example below).

So, this is what you can try:
Open up your backup file, and edit line item beginning 620141 so it reads:
62014170602040A0008045

Then use AlfaOBD to restore your BCM configuration to that new edited backup file.

 

[BringTheLightnin]

It seems my OCD and my curiosity have me retrofitting a bunch of stuff to my Gladiator (Paddle Shift Steering wheel, Selec-Trac, and now ACC).

There have been several posts questioning whether the adaptive cruise can be added after purchase. It seems it can. But it is definitely better to buy the Jeep with this option rather than retrofitting. My Gladiator is so modified that trading it for a new Gladiator just didn't make sense. I also enjoy a challenge and it has been fun to understand the Gladiator/Wrangler electronics systems.

I will update this post with additional findings, photos, and answers to questions regarding the swap. The main components required for the ACC swap are:

Required Components (~$1,600) (~$2,000) with price increases since the original post. Updated 01.22.23

• Camera/control module
• camera jumper harness
• ABS Module $250$370
  • Part# 68461644AC*
• ABS Controller ~ $150 $190
  • Part # 68438383AA*
• ACC Steering wheel switch

"Optional" components - These are not required for the ACC to function

• Heated windshield jumper harness
• heated windshield (specific to ACC)
  • ~$800

* Please confirm the part numbers are appropriate for your VIN, there are several versions of the components.


As I began installing components, I discovered numerous error codes which resulted in additional components (to comprise the list above). I do not have adaptive or standard cruise functioning currently. I have to calibrate the ACC ABS valves and the ACC system. I haven't discovered how to do this with either Jscan or ALFA OBD, I may need to use the Micropod with Witech 2.0.

While I don't have the system functioning, I remain confident it will soon be operational.

I realize this swap is not for most but I couldn't help but embark on the project as a challenge and opportunity to answer the feasibility question once and for all. The worst part is that I am running out of things to retrofit.


ACC module for reference

How much was the selec trac? Is there a post on it?

 

[rhill2901]

Ok. Your BCM dump shows location set to IRCM, but your backup file shows that it is still set to “none”. Your BCM dump also does not reveal two other related settings- auto high beam threshold on and off speed, and your backup file shows those being set at 0 km/h (example below).

So, this is what you can try:
Open up your backup file, and edit line item beginning 620141 so it reads:
62014170602040A0008045

Then use AlfaOBD to restore your BCM configuration to that new edited backup file.

Ok I changed the beam on and off thresholds are 25 and 20 respectively. I changed the line to read exactly that, and when I query in alphaobd, it says the state for the location as "undefined". I did another config save and verified that I have it correct as you specified.

I went for a quick drive to see if the CSM setting will stay selected, and it doesn't. I flipped the highbeams on just to verify and they come on, but no auto highbeams.

 

[Jimmy07]

Ok I changed the beam on and off thresholds are 25 and 20 respectively. I changed the line to read exactly that, and when I query in alphaobd, it says the state for the location as "undefined". I did another config save and verified that I have it correct as you specified.

I went for a quick drive to see if the CSM setting will stay selected, and it doesn't. I flipped the highbeams on just to verify and they come on, but no auto highbeams.

Can you post your new current BCM dump and backup files

 

[rhill2901]

Can you post your new current BCM dump and backup files

 

[Jimmy07]

I’ll have to flash a JL VIN to one of my bench BCMs this weekend to verify some things, but I’m guessing the issue is the 2019 JL BCM is not actually broadcasting those settings.

 

[rhill2901]

I’ll have to flash a JL VIN to one of my bench BCMs this weekend to verify some things, but I’m guessing the issue is the 2019 JL BCM is not actually broadcasting those settings.

I'm not confident that mopar ever intended it to work on a 2019 wrangler. Those who have late December 2019 wrangler JL have the auto highbeams. If anyone who has, or knows of anyone that has a 2019 jeep wrangler or even gladiator and has functional auto high beams, it would be very helpful to find out what BCM and DASM part numbers (or firmware versions) they are running. It is one of those parts that is preventing it to work. I'm suspecting its the bcm, but the bcm and dasm have different part numbers between 2019 and 2020. Maybe its both that have to be retrofitted.

If the 2019 BCM isn't broadcasting it, is it possible the firmware just doesn't include the instructions to handle auto highbeams and they haven't bothered to add it for some reason only mopar can share? My guess its the BCM. I've been looking over on the ram forums and others have attempted to swap newer bcm's with no or very limited success. I thought, well heck, just get a used one, put in the vin, (alphaOBD) and wallah. NOPE. The MCU has to be virgin to marry with the rfh module. Only way to truely test it is to swap a 2020 bcm and rfh thats already been married together, then marry the ecm to the pair. Then add a 2020 DASM. Just how much difference is there between a 2019 and 2020 bcm?

 

[Jimmy07]

I'm not confident that mopar ever intended it to work on a 2019 wrangler. Those who have late December 2019 wrangler JL have the auto highbeams. If anyone who has, or knows of anyone that has a 2019 jeep wrangler or even gladiator and has functional auto high beams, it would be very helpful to find out what BCM and DASM part numbers (or firmware versions) they are running. It is one of those parts that is preventing it to work. I'm suspecting its the bcm, but the bcm and dasm have different part numbers between 2019 and 2020. Maybe its both that have to be retrofitted.

If the 2019 BCM isn't broadcasting it, is it possible the firmware just doesn't include the instructions to handle auto highbeams and they haven't bothered to add it for some reason only mopar can share? My guess its the BCM. I've been looking over on the ram forums and others have attempted to swap newer bcm's with no or very limited success. I thought, well heck, just get a used one, put in the vin, (alphaOBD) and wallah. NOPE. The MCU has to be virgin to marry with the rfh module. Only way to truely test it is to swap a 2020 bcm and rfh thats already been married together, then marry the ecm to the pair. Then add a 2020 DASM. Just how much difference is there between a 2019 and 2020 bcm?

I finally had time to do some stuff on a bench BCM.
I flashed a used 2019 Ram BCM to a 2020 JL firmware (there is no 2019 JL flash file available, so I couldn’t try that).
One thing I discovered is that depending on the BCM variant, the byte location in 2014 CBC Config changes depending on the variant.
There is no way I can have you check your BCM variant with AlfaOBD, but when you get a chance, can you do the following:
- In your backup file, change that 620141 line item back to read 6201417060204080000000

- Restore your BCM to that new edited backup file

- use AlfaOBD to change the auto high beam location to “none”

- Create a new backup file and post it here

I am looking to see if this byte is the location of the auto high beam location setting on your BCM variant:

 

[rhill2901]

I finally had time to do some stuff on a bench BCM.
I flashed a used 2019 Ram BCM to a 2020 JL firmware (there is no 2019 JL flash file available, so I couldn’t try that).
One thing I discovered is that depending on the BCM variant, the byte location in 2014 CBC Config changes depending on the variant.
There is no way I can have you check your BCM variant with AlfaOBD, but when you get a chance, can you do the following:
- In your backup file, change that 620141 line item back to read 6201417060204080000000

- Restore your BCM to that new edited backup file

- use AlfaOBD to change the auto high beam location to “none”

- Create a new backup file and post it here

I am looking to see if this byte is the location of the auto high beam location setting on your BCM variant:

It changed the byte pair from 80 to 00 by putting the location to none.

Here are the results:

 

[Jimmy07]

It changed the byte pair from 80 to 00 by putting the location to none.

Here are the results:

Ok. If auto high beam never worked when that byte was reporting 80, then your BCM is most likely not capable of broadcasting it.
It might be easier for you to get a copy of CDA6 and a micropod II clone. With that, you can log the bus to verify that it isn’t broadcasting, and you can use it to flash your current BCM to a 2020 JL BCM firmware instead of replacing it. I have the 2020 JL BCM flash file.

 

[rhill2901]

Ok. If auto high beam never worked when that byte was reporting 80, then your BCM is most likely not capable of broadcasting it.
It might be easier for you to get a copy of CDA6 and a micropod II clone. With that, you can log the bus to verify that it isn’t broadcasting, and you can use it to flash your current BCM to a 2020 JL BCM firmware instead of replacing it. I have the 2020 JL BCM flash file.

I already ordered a 2020 bcm, so I will go ahead and try that first. Your suggestion is about 30 days out so the bcm will be here first lol. Also, I'm slightly concerned that what happens if the flash of the bcm fails, as in bricking it. Then I lost use of my jeep lol. Not that I depend on it though. So I'll give the bcm swap a try, if it works then others can use it as a solution. The BCM was about $260 delivered to me, so its not terribly expensive.

I have since went ahead and ordered the setup you suggested sent to me. It will take a while, but I'll give it a try once it arrives. I wanted to play with programming a ram 1500 ecm, so it will be a solution for another cause. I'll check back in and update as soon as I find something out.

 

[rhill2901]

So to bring others current, I was able to flash the BCM from 2019 jeep wrangler with no auto highbeams with the 2020 firmware. After the flash, I had to restore the configuration, and I used Alpha OBD to do it. Then with Alpha OBD, I set the Configuration as set to "YES". The flash apparantely makes it no. So now, on a 2019 Jeep Wrangler Sport with no options from the factory, I have auto high beams operational. So if you have ACC installed on a 2019 jeep wrangler/gladiator, it can be enabled. Oddly, I don't get a message to indicate that I've activated them though.... Work in progress.

On another note, I have a BCM that I ordered from a dealer that will eventually come in and I'm quite sure that install it will also accomplish the same result. Flashing it will be a whole lot cheaper if your able to find someone to bench flash it, otherwise, getting a new one is your other bet. Finding a dealer or someone else to adapt it to your car is another story.

Sponsored