Adding adaptive cruise

[blbrown]

I'll let you know in a couple of weeks once they try the Calibration on mine. I have a 2020 2500 and a used DASM supposedly from a 2020 with 12000 miles, so hopefully no mismatch.

Took into dealership yesterday and was told the Tech followed the instructions I gave them, to go into Plant mode, clear all DTCs and the run the calibration. I was told after the tech completed the calibration it still said ACC not available . Was told after awhile the errors went away. Was hoping all worked,only to find out they had flashed the BCM back to stock. Spent a couple hours when I got home reprogramming all my add-ons. Blind Spot, TTPMS, Bed Lights, Auto Wipers, Cargo Camera. Haven't tried Auto Highbeam or ACC yet.
I'm retired and on a fixed budget, which I've exceeded for the month so I think I'll leave ACC off for now until I see someone else thats had success.

 

[mattjackson86]

@jrf your DASM seems broken in someway. Not sure what’s going on. I’d be curious if that module has been that way since you installed it or what, no way to know. But it’s not responding so unless your wiring harness isn’t correct (don’t see why that would be) id say it’s a bad DASM. It was new though huh?

@blbrown we seem to be in a similar spot. We need to compare notes and see what makes us unique. Do you have the small 3.5” screen instrument cluster or the larger 7” cluster? I have a base tradesman that I am adding this too.

 

[blbrown]

7

@jrf your DASM seems broken in someway. Not sure what’s going on. I’d be curious if that module has been that way since you installed it or what, no way to know. But it’s not responding so unless your wiring harness isn’t correct (don’t see why that would be) id say it’s a bad DASM. It was new though huh?

@blbrown we seem to be in a similar spot. We need to compare notes and see what makes us unique. Do you have the small 3.5” screen instrument cluster or the larger 7” cluster? I have a base tradesman that I am adding this too."

I have the 7" cluster, used DASM out of same year, model 2500. It beeps when I press the ACC button on the steering wheel prior to making the program changes with AlfaOBD and if I unplug it it says Trailer Break needs service

 

[blbrown]

@Jimmy07
Is it possible that both these settings need to be enabled?

 

[jrf]

@jrf your DASM seems broken in someway. Not sure what’s going on. I’d be curious if that module has been that way since you installed it or what, no way to know. But it’s not responding so unless your wiring harness isn’t correct (don’t see why that would be) id say it’s a bad DASM. It was new though huh?

It has not always been that way. It responded on my initial and 2nd trip to the dealer and he was able to calibrate it twice. I know because I was in the truck the 2nd time. I watched it go through calibration. After calibration he cleared the DTCs but it still came back and said "ACC not available" or something (I'd have to go back to my notes). Now however it's acting as if it can't communicate. I too suspect the DASM but it is new. It is also a newer 2022 model. Wish I had a used one to at least try.

 

[Jimmy07]

@Jimmy07
Is it possible that both these settings need to be enabled?
View attachment 56981

P/T Chassis Net: ACC Adaptive Cruise Control definitely does not get enabled.
P/T Chassis Net is the list of all of the modules that are present on the truck that are on the Canbus C network, and there is no such ACC module for Ram trucks, only the DASM.

 

[Jimmy07]

I haven’t had any time to do anything lately, but I’m trying to make time to look into all this, specifically the bits that AlfaOBD is changing for the ACC settings.
I’ve gone over this thread, and made a timeline of this being installed on HD Rams.

Feb 15:
@TXJosh - successfully installed on a 2022 with new 2022 DASM

Feb 24:
Verified on my truck that used 2022, 2021, and 2020 DASM can be calibrated back and forth between 2021 and 2022 BCMs being installed in my truck. ACC settings originally configured last year using AlfaOBD.

Feb 25:
Sold used 2021 DASM to @nsuth for 2020 truck. Have not heard back of this install was successful.

***March 31- AlfaOBD update available to include MY2023 PowerNet body computer support ***

April 18:
Sold used 2020 DASM to @catronro for 2020 truck. Have not heard back if this install was successful.

April 24:
@jrf - unsuccessful with new 2022 DASM on 2021 truck.

May 4:
@mattjackson86 - unsuccessful with new?(verify) 2022 DASM on 2022 truck.

@blbrown - unsuccessful with used (verify year) DASM on 2020 truck.

I’m not sure if something got broke in AlfaOBD with the 3/31/23 update, but that’s what I’m going to look at when I get a chance.
I have @jrf and @mattjackson86 backup files and BCM system ID.
@blbrown can you send me your current backup file and BCM system ID?

 

[mattjackson86]

Correct, new 2022 DASM on a 2022 truck.

 

[blbrown]

Looks like I don't know how to send the log file. How do I get a copy to you?
And sorry for being dumb, but how do I get the system id?

 

[mattjackson86]

Looks like I don't know how to send the log file. How do I get a copy to you?
And sorry for being dumb, but how do I get the system id?

This may help:

I use the windows app so it’s different than the android app which I assume your using. Hope video helps. Basically @Jimmy07 is looking for your log files and the system id is really just a dump of all the configuration parameters and values as they are set.

FYI @Jimmy07 i have a 7” 2021 gas evic on its way to me to install. Slim shot but see if that changes anything for my issue.

 

[mattjackson86]

@Jimmy07 7” Evic cluster installed. No change but I can see the extra icons and error messages now. I confirmed the Current VIN on the new cluster is my VIN while the Original VIN is indeed the original vin.

Everything in AlfaOBD has been configured for about a week (all DASM, acc, and fwc paramters) and driven many miles to see if that made any difference. Obviously it didn’t

 

[blbrown]

@Jimmy07 7” Evic cluster installed. No change but I can see the extra icons and error messages now.

Everything in AlfaOBD has been configured for about a week (all DASM, acc, and fwc paramters) and driven many miles to see if that made any difference. Obviously it didn’t

Looks exactly like mine

 

[blbrown]

Looks exactly like mine

When you first start your truck and press the adaptive cruise button on the steering wheel do you get a beep tone, I think from the DASM?
Also do you have auto highbeam now? My auto high beam is working better than it ever has, so I know the DASM is talking.

 

[mattjackson86]

Auto high beam works great. So yes DASM works fine in and of itself. I know the system is complaining of the vechicle configuration mismatch in the DASM (WiTech tells me) but that doesn’t mean it’s broken. Just misconfigured, and the default response to a misconfig according to the documentation is to disable FCW and ACC. So on one hand the truck is actually working exactly as intended. We just need to correct the misconfig, which means finding it in first place. So it’s not a physical issue it seems at all for you and I at least.

Power up the car, it beeps. And those lights show. One message saying FCW unavailable. Push the old cruise control button the “cruise control canceled” pops up and the “cruise control unavailable” message gets added to the list. Press the ACC button and “ACC unavailable” displays with same message now also shown.

an AlfaOBD issue with its latest update would make sense and it’s just not configuring it all like it says it is. Timeline Jimmy spelled out would also concur with that. But we will need Jimmy to dig into this for us as I think we are at a dead end. But I do hope it’s “just” a reconfigure in AlfaOBD of some sort when the time comes. Don’t believe anything is actually broken.

Message page images attached

 

[blbrown]

Auto high beam works great. So yes DASM works fine in and of itself. I know the system is complaining of the vechicle configuration mismatch in the DASM (WiTech tells me) but that doesn’t mean it’s broken. Just misconfigured, and the default response to a misconfig according to the documentation is to disable FCW and ACC. So on one hand the truck is actually working exactly as intended. We just need to correct the misconfig, which means finding it in first place. So it’s not a physical issue it seems at all for you and I at least.

Power up the car, it beeps. And those lights show. One message saying FCW unavailable. Push the old cruise control button the “cruise control canceled” pops up and the “cruise control unavailable” message gets added to the list. Press the ACC button and “ACC unavailable” displays with same message now also shown.

an AlfaOBD issue with its latest update would make sense and it’s just not configuring it all like it says it is. Timeline Jimmy spelled out would also concur with that. But we will need Jimmy to dig into this for us as I think we are at a dead end. But I do hope it’s “just” a reconfigure in AlfaOBD of some sort when the time comes. Don’t believe anything is actually broken.

Message page images attached

My symptoms are exactly the same as you have described, which I feel is a good thing.

 

[blbrown]

Your using a new DASM correct?

 

[mattjackson86]

Mine was brand new. I don’t see used or new being an issue so long as the Enter Plant Mode was run in WiTech by the dealer to reconfigure it to your vin.

Considering your auto high beams is working I’d rule out any DASM physical issue and id even say that the dealer must have done the Enter Plant Mode correctly for you otherwise I don’t think auto high beam would work at all. I think we sit in the same boat with some other config issue elsewhere.

 

[blbrown]

Auto high beam works great. So yes DASM works fine in and of itself. I know the system is complaining of the vechicle configuration mismatch in the DASM (WiTech tells me) but that doesn’t mean it’s broken. Just misconfigured, and the default response to a misconfig according to the documentation is to disable FCW and ACC. So on one hand the truck is actually working exactly as intended. We just need to correct the misconfig, which means finding it in first place. So it’s not a physical issue it seems at all for you and I at least.

Power up the car, it beeps. And those lights show. One message saying FCW unavailable. Push the old cruise control button the “cruise control canceled” pops up and the “cruise control unavailable” message gets added to the list. Press the ACC button and “ACC unavailable” displays with same message now also shown.

an AlfaOBD issue with its latest update would make sense and it’s just not configuring it all like it says it is. Timeline Jimmy spelled out would also concur with that. But we will need Jimmy to dig into this for us as I think we are at a dead end. But I do hope it’s “just” a reconfigure in AlfaOBD of some sort when the time comes. Don’t believe anything is actually broken.

Message page images attached

You must have a huge fuel capacity, 1999 Range.

 

[mattjackson86]

it’s just due to the new cluster while it relearns.

 

[blbrown]

One thing I've noticed is that after programming per the instructions, when I go into settings Foward Collision Warning is off and if you try to select Warning or Warning with active Braking you get settings not saved. The same is true for Foward Collision Sensitivity, but after a day it allows me to set the Sensitivity.