Performance Pages on 2022 Limited 12 inch UC5

[Jimmy07]

I can't comment on them being irrelevant, but it doesn't set all of them to know.

This is my before
View attachment 175984

This is after
View attachment 175985

All of the settings in ECUConfig 18 are settings that are communicated to the telematics box. If there is no telematics box present, it really doesn’t matter what they are all set to, but they would normally all be set to “no” (for example, like they are in a 2021 that has UC4 with no telematics box).

 

[Thefloridalife]

2018 radio has cell card inside the radio, no separate telematics box

I have the instructions on removing the cell card from the radio, but after that I don’t know which wires to reconnect and which ones to leave disconnected?

 

[Darksteel165]

I have the instructions on removing the cell card from the radio, but after that I don’t know which wires to reconnect and which ones to leave disconnected?

If there is no cell card, it wouldn't matter what wires you put back.
A phone with no sim card can't make calls.

 

[billybaloneey]

With the telematics box removed location and altitude at the bottom of the off-road pages doesn’t work. Is there a way to remove the cell service from the box so that it can stay connected in the vehicle, minus the antennas?


Sent from my iPhone using Tapatalk

Even before I removed the telematics box in my truck...and when I occasionally had the performance pages and the off road pages, the location and altitude values at the bottom of the page were not correct...after removing the telematics box the off road page location and altitude are still wrong. I have no problems with any GPS/Nav apps otherwise.

 

[Thefloridalife]

If there is no cell card, it wouldn't matter what wires you put back.
A phone with no sim card can't make calls.

I’m trying to avoid Ram from being able to connect to the truck.

 

[Jimmy07]

but it doesn't set all of them to know.

When I say “they get set to no”, obviously I mean the user would make the changes with alfaobd, not that they “automatically” get set to no by the act of removing the TBM.

 

[Thefloridalife]

When I say “they get set to no”, obviously I mean the user would make the changes with alfaobd, not that they “automatically” get set to no by the act of removing the TBM.

I don’t know why my phone keeps not attacking pics to my posts. I’m not sure which ones I keep hooked up, and which ones I leave disconnected to keep am/fm, Sirius XM, and GPS?

 

[Jimmy07]

I don’t know why my phone keeps not attacking pics to my posts. I’m not sure which ones I keep hooked up, and which ones I leave disconnected to keep am/fm, Sirius XM, and GPS?

White is am/fm, mustard is SXM/GPS, red is backup camera. Magenta and pink are cellular. Disconnecting the antenna plugs on that radio will not stop OTA and connectivity.

 

[Stoopalini]

Great information in this thread, thanks to all who have done the heavy lifting!

I joined to see if you kind folks might be able to help solve an issue us Durango R/T Tow & Go owners seem to be facing.

For background, the Durango R/T Tow & Go (TnG for short) is essentially a Durango SRT 392, except it has the 5.7L Hemi instead of the 6.4L ... and the TnG retains the R/T's 3.09 diff gear ratio. Everything else is SRT though, including the AWD system, the electronic suspension, transfer case, brake setup, rear diff with eLSD, etc ... So it has all of the SRT component modules.

The TnG comes from the factory with perf pages and drive modes, but unlike the SRT, the TnG uses hard buttons for drive mode selection. The TnG does not get the uConnect's SRT dashboard drive mode screens nor the race options though. Thus, we don't have the custom drive mode. Or better stated, we have no way to access the custom drive mode.

Here is what the TnG's OEM center stack panel looks like with the Track, Sport, Tow and Snow drive mode buttons:



We've successfully enabled the uConnect Drive Mode screens as well as Race Options using AlfaOBD without any EVIC errors by simply setting "Vehicle is an SRT" to "Yes". I believe we don't get any errors because the TnG has all the SRT modules present and thus the ABS and FCW errors don't occur for us like they do on a standard Durango R/T.

Swapping in an SRT 392 or Hellcat center stack panel replaces the TnG drive mode hard buttons with an SRT and Launch button instead. With "Vehcile is an SRT" set to "Yes", the SRT button functions as expected and provides a shortcut to the uConnect drive modes screen. The Launch button doesn't function by default because "Launch" is disabled in the engine PCM. Something which HP Tuners could resolve.

Here's a pic of the Hellcat/SRT controls:



When doing this, everything works for a while but then (as you've also noticed in the RAMs) the dashboard tabs for Drive Modes and Race Options disappear and it reverts to only having perf pages; but ... and this may be different in the RAMS ... we can still access the drive modes and race options screens through widget shortcuts or by going to the Apps listing.

So reading this thread, I think a bypass of the Telematics box will likely stop the tabs from disappearing from the SRT Dashboard and I'm grateful for the efforts put in here to come to that solution I've ordered the antennae bypass cable from Amazon to give it a try, as I do want to keep SXM and GPS functional.

The issue we're now trying to resolve is an attempt to keep the OEM TnG panel in place and have the drive mode hard buttons function.

What's interesting is ... if we set "Vehicle is an SRT" to yes, then cycle the power ... we get the drive mode screens; but the TnG drive mode hard buttons then cease to function. But if we then go into Alfa and set "Vehicle is an SRT" back to "No", but do not do a reboot or start the engine ... then the drive mode hard buttons start working again along with still having the uConnect drive mode screens. Everything works together in this state.

This is perfect and what we'd like to keep ... but unfortunately, as soon as you start the engine or do a power cycle, the Drive Mode uConnect screens disappear since the BCM now has "Vehicle is an SRT" set back to "No".

My thought is the Android OS is most likely the culprit here but I've no experience with getting into the OS on these radios.

If I could set "Vehicle is an SRT" to Yes", but somehow keep the TnG hard mode buttons functional ... then great! Or ... if I can get everything working, then set "Vehicle is an SRT" back to "No", but somehow keep the Android OS from removing the Drive Mode and Race Options tabs from the dashboard, then that would seem to work as well.



So ... any ideas on how to approach this given all the advanced knowledge about the UC5 system in here? Is there a way to retain the tabs in the "Dashboard" even when "Vehicle is an SRT" is set back to "No"?

 

[Jimmy07]

Great information in this thread, thanks to all who have done the heavy lifting!

I joined to see if you kind folks might be able to help solve an issue us Durango R/T Tow & Go owners seem to be facing.

For background, the Durango R/T Tow & Go (TnG for short) is essentially a Durango SRT 392, except it has the 5.7L Hemi instead of the 6.4L ... and the TnG retains the R/T's 3.09 diff gear ratio. Everything else is SRT though, including the AWD system, the electronic suspension, transfer case, brake setup, rear diff with eLSD, etc ... So it has all of the SRT component modules.

The TnG comes from the factory with perf pages and drive modes, but unlike the SRT, the TnG uses hard buttons for drive mode selection. The TnG does not get the uConnect's SRT dashboard drive mode screens nor the race options though. Thus, we don't have the custom drive mode. Or better stated, we have no way to access the custom drive mode.

Here is what the TnG's OEM center stack panel looks like with the Track, Sport, Tow and Snow drive mode buttons:

View attachment 176161

We've successfully enabled the uConnect Drive Mode screens as well as Race Options using AlfaOBD without any EVIC errors by simply setting "Vehicle is an SRT" to "Yes". I believe we don't get any errors because the TnG has all the SRT modules present and thus the ABS and FCW errors don't occur for us like they do on a standard Durango R/T.

Swapping in an SRT 392 or Hellcat center stack panel replaces the TnG drive mode hard buttons with an SRT and Launch button instead. With "Vehcile is an SRT" set to "Yes", the SRT button functions as expected and provides a shortcut to the uConnect drive modes screen. The Launch button doesn't function by default because "Launch" is disabled in the engine PCM. Something which HP Tuners could resolve.

Here's a pic of the Hellcat/SRT controls:

View attachment 176163

When doing this, everything works for a while but then (as you've also noticed in the RAMs) the dashboard tabs for Drive Modes and Race Options disappear and it reverts to only having perf pages; but ... and this may be different in the RAMS ... we can still access the drive modes and race options screens through widget shortcuts or by going to the Apps listing.

So reading this thread, I think a bypass of the Telematics box will likely stop the tabs from disappearing from the SRT Dashboard and I'm grateful for the efforts put in here to come to that solution I've ordered the antennae bypass cable from Amazon to give it a try, as I do want to keep SXM and GPS functional.

The issue we're now trying to resolve is an attempt to keep the OEM TnG panel in place and have the drive mode hard buttons function.

What's interesting is ... if we set "Vehicle is an SRT" to yes, then cycle the power ... we get the drive mode screens; but the TnG drive mode hard buttons then cease to function. But if we then go into Alfa and set "Vehicle is an SRT" back to "No", but do not do a reboot or start the engine ... then the drive mode hard buttons start working again along with still having the uConnect drive mode screens. Everything works together in this state.

This is perfect and what we'd like to keep ... but unfortunately, as soon as you start the engine or do a power cycle, the Drive Mode uConnect screens disappear since the BCM now has "Vehicle is an SRT" set back to "No".

My thought is the Android OS is most likely the culprit here but I've no experience with getting into the OS on these radios.

If I could set "Vehicle is an SRT" to Yes", but somehow keep the TnG hard mode buttons functional ... then great! Or ... if I can get everything working, then set "Vehicle is an SRT" back to "No", but somehow keep the Android OS from removing the Drive Mode and Race Options tabs from the dashboard, then that would seem to work as well.

View attachment 176164

So ... any ideas on how to approach this given all the advanced knowledge about the UC5 system in here? Is there a way to retain the tabs in the "Dashboard" even when "Vehicle is an SRT" is set back to "No"?

Vehicle is an srt is a vehicle configuration setting, so all of the modules on the vehicle have to be “in agreement” with the settings. That’s why the TnG controls won’t function when they are being told that the vehicle is an srt, because that center stack module is specifically looking for the message for vehicle is not an srt.
The only way you’ll be able to use the TnG hard controls while having vehicle is an srt set to yes is to put a canbus shield in between the IHS bus and the integrated center stack, and have the vehicle is not an srt message spoofed directly to the integrated center stack.

 

[Stoopalini]

Vehicle is an srt is a vehicle configuration setting, so all of the modules on the vehicle have to be “in agreement” with the settings. That’s why the TnG controls won’t function when they are being told that the vehicle is an srt, because that center stack module is specifically looking for the message for vehicle is not an srt.
The only way you’ll be able to use the TnG hard controls while having vehicle is an srt set to yes is to put a canbus shield in between the IHS bus and the integrated center stack, and have the vehicle is not an srt message spoofed directly to the integrated center stack.

Interesting ... My thought was the CANBUS messages being sent by the TnG drive mode buttons were being ignored by either the BCM or UC5, or some other component in the chain. I didn't think to consider a CANBUS message was being sent to the control panel which was disabling them or preventing them from sending out a message when actuated.

I may need to invest in a snooping solution to be able to see what's being sent in various conditions. Thanks for the input.

I'm experienced in building things like Arduino, ESP8266, ESP32, etc ... I assume I can construct a canbus shield from something like this. Or ... is there a packaged product already available to do something like this?

 

[Jimmy07]

Interesting ... My thought was the CANBUS messages being sent by the TnG drive mode buttons were being ignored by either the BCM or UC5, or some other component in the chain. I didn't think to consider a CANBUS message was being sent to the control panel which was disabling them or preventing them from sending out a message when actuated.

I may need to invest in a snooping solution to be able to see what's being sent in various conditions. Thanks for the input.

I'm experienced in building things like Arduino, ESP8266, ESP32, etc ... I assume I can construct a canbus shield from something like this. Or ... is there a packaged product already available to do something like this?

Yeah, the way I’m seeing it is, the state of that setting alone is what causes the hard buttons to function, or not, from the way you’re describing it. So, I would think if you can set that setting to yes with alfaobd, but tell only the integrated center stack that setting is set to no, everything should work together.

This is what I use to spoof CustSetMenu 3 settings to the radio so I can get factory turn signal cameras and front park assist activated camera working:

Arduino-Based ECU Development Board With Dual CAN Bus Interface

Leverage the power of an ARM Cortex M3 32-bit processing capability in combination with a dual CAN Bus interface to create a CAN Bus or SAE J1939 application.

copperhilltech.com

I’m not too savvy on implementing the code (I have someone that helps me with that), but if you send me your current backup file with vehicle is an srt set to no, I can tell you what message ID, byte, and bits need to be spoofed to the ICS so it sees that setting as no.

 

[Stoopalini]

Yeah, the way I’m seeing it is, the state of that setting alone is what causes the hard buttons to function, or not, from the way you’re describing it. So, I would think if you can set that setting to yes with alfaobd, but tell only the integrated center stack that setting is set to no, everything should work together.

This is what I use to spoof CustSetMenu 3 settings to the radio so I can get factory turn signal cameras and front park assist activated camera working:

Arduino-Based ECU Development Board With Dual CAN Bus Interface

Leverage the power of an ARM Cortex M3 32-bit processing capability in combination with a dual CAN Bus interface to create a CAN Bus or SAE J1939 application.

copperhilltech.com

I’m not too savvy on implementing the code (I have someone that helps me with that), but if you send me your current backup file with vehicle is an srt set to no, I can tell you what message ID, byte, and bits need to be spoofed to the ICS so it sees that setting as no.

That would be great, thanks! I can't seem to attach a TXT file, so I shared it from my DropBox: https://www.dropbox.com/scl/fi/8d8c...-BIN.txt?rlkey=l17poiiu9nczpl295qyvnbx33&dl=1

That's a backup file from a 2021 Durango R/T TnG with "Vehicle is an SRT" set to "No". Let me know if the link doesn't work for some reason.

Thinking through this, I assume a dual CAN bus capable micrprocessor would be required hence the Arduino based ECU Dev board you linked. Thanks again.

The connector is 8 pins but only 5 are populated:




So intercepting the IHS(-) and IHS(+) lines with two interfaces would be something like the following:



I won't muddy up this thread with details specific to implementation for this Durango challenge, but I do appreciate your help and input ... thanks! Knowing what to look for in identifying "Vehicle is an SRT" vs "Vehicle is not an SRT" will be extremely helpful.

 

[Jimmy07]

That would be great, thanks! I can't seem to attach a TXT file, so I shared it from my DropBox: https://www.dropbox.com/scl/fi/8d8c...-BIN.txt?rlkey=l17poiiu9nczpl295qyvnbx33&dl=1

That's a backup file from a 2021 Durango R/T TnG with "Vehicle is an SRT" set to "No". Let me know if the link doesn't work for some reason.

Thinking through this, I assume a dual CAN bus capable micrprocessor would be required hence the Arduino based ECU Dev board you linked. Thanks again.

The connector is 8 pins but only 5 are populated:

View attachment 176181


So intercepting the IHS(-) and IHS(+) lines with two interfaces would be something like the following:

View attachment 176180

I won't muddy up this thread with details specific to implementation for this Durango challenge, but I do appreciate your help and input ... thanks! Knowing what to look for in identifying "Vehicle is an SRT" vs "Vehicle is not an SRT" will be extremely helpful.

That’s not quite how it gets hooked up, I’ll send you a PM.

 

[akostaac]

I got my performance and off road pages in my evic and the 12” screen thanks to Jimmy. I know they will probably take them down but in my case I upgraded my 2022 Uconnect 5 non nav to the 12” so I’m not sure if they even can see what I got since the truck did not come with it. It’s been 3 days and they still there. Very valuable info on performance pages for sure. I also upgraded my Uc5 via usb to 25.47 before making my changes(adding pages) with Alfaobd. The weird part about is I still have connected services for safety but I’m not paying a subscription. I will update if anything

 

[akostaac]

Well, Ram did strike my pages out on the 4th day I decided to call Ram connect services and cancel all my trials for privacy reasons. They canceled my account and told me no communication will go back and forth from my truck since they don’t have permission. I will update you guys if my pages still working after at least a week otherwise I’ll take the TBM out.

 

[Darksteel165]

Well, Ram did strike my pages out on the 4th day I decided to call Ram connect services and cancel all my trials for privacy reasons. They canceled my account and told me no communication will go back and forth from my truck since they don’t have permission. I will update you guys if my pages still working after at least a week otherwise I’ll take the TMB out.

TBM, not TMB.
And they will still pull info from your truck even without your permission. there is no opt out.

 

[akostaac]

TBM, not TMB.
And they will still pull info from your truck even without your permission. there is no opt out.

Fixed the typo and I will update you guys if it happens. Don’t really want to remove all that crap if I don’t have to. Time will tell and normally I will find out quickly

 

[Sigfla]

I am curious how his works with adding a trailer brake controller. You can enable its function via alpha or JScan but you must factory reboot the radio to get the trailer tow app and gauges widget. Ram will then remove them via the telematics box eventually. If you add the sales code to your vin at the dealer will that avoid the issue of losing the app and widget? I programmed my truck for cargo lights and didn’t add them to my sales code vin but they still work. Certain features must be tied into telematics while others aren’t. Personally I hate buying a car monitored by big brother. I didn’t agree to it to this extent and frankly my next truck may just be an older classic without all this garbage. I can aftermarket add pretty much anything and it be more reliable than this!!

 

[Pejcinoski]

Here is how I managed to get 4 new Performance pages...see the link below to the post I made showing screen shots of the new pages/apps I was able to get...and keep for a short while...till RAM Connect remotely removed them via a connection to the telematics box. I have a 2022 RAM 1500 Lone Star 5.7 Hemi, with a 12" Uconnect 5 radio/screen.

Using AlfaOBD, all of the following Car Configuration Changes need to be set to Yes: (there is no need to back any of these changes out at any point...they do not cause any alarms, electrical or mechanical issues if left with a value of Yes)
(I issued all of the AlfaOBD changes with the vehicle in the RUN ignition switch...not the truck running...just in the RUN position...it is actually not necessary to have the truck in the RUN position but doing so allows you to see some of the alarms that will pop up on the EVIC and Uconnect 5 screen)

VehConfig 1: Performance Pages Present : Yes
VehConfig 3: Vehicle is an SRT: Yes
VehConfig 3: Sport Mode Present: Yes
VehConfig 2; Drive mode feature configuration: Yes
VehConfig 2: Memory Drive Mode Sub-Feature Configuration: Yes
VehConfig 2: ESC Drive Mode Sub-Feature Configuration: Yes
VehConfig 2: ECM Drive Mode Sub-Feature Configuration: Yes
VehConfig 2: Configuration For Performance & Gear Shift Indication : (set this one to: Performance and gear shift indication)
VehConfig 5; Off-Road Pages Present: Yes
VehConfig 8 Off-road Mode Present: Yes
ECUConfig 3: Radio Apps Present: Yes
VehConfig 2: Off road Capable: Yes

1) Now here is where the magic happens:
Issue the following change after all of the above have been changed:
VehConfig 1: Vehicle Line: (set the value to) LD-Charger
Then get out of AlfOBD and wait about 5-10 mins

2) After the 5-10 min wait...place the truck back in the RUN position and you'll probably see the following alarms displayed in the EVIC (dash cluster screen): Service Air Bag System, Service Anti Lock Brake System, Service Electronic Stability System and Service Trailer Brake System (if you have the trailer brake option)...and on the Uconnect 5 screen you will get a message that says: SOS Call Unavailable.

3) From here go over to your Uconnect 5 screen...at the bottom right you will see the soft switch for the: Vehicle, then Settings at the top right. Press it...scroll down the menu at the bottom till you find: Reset...press it...then look for the: Factory Reset...press it. This will reset your Uconnect 5 screen...you will lose your music presets, and any driver profile icons you might have set up. Wait for the Uconnect 5 screen to completely reset...takes about 1 minute...then turn the ignition switch off and go do something for about 5-10 mins. While you are waiting the 4 new Performance apps are being created and loaded onto the apps page.

4) Now because your RAM truck is not a Charger...place the truck back in the RUN position and issue the one final AlfaOBD parameter change: VehConfig 1: Vehicle Line: set the value back to: DT-RAM 1500. After the Vehicle Line command is issued back to a DT-RAM 1500, all of the alarms mentioned in the EVIC and the Uconnect 5 screen will clear.

For my truck the Off Road app is always the first to appear in the Apps list...and followed a little later by the other 3 Performance apps...keep checking the Apps page...they will eventually show up shortly after the Off Road app.

Until the telematics work around...bypass...is resolved/solved you will most likely lose the 4 new Performance apps when RAM Connect services detects and deletes them from your Uconnect 5 Apps page....if you are stubborn like me all you have to do is repeat steps 1), 2), 3) and 4) and the apps will come back again.
Below is a link to a post I made over on the AlfaOBD thread a few weeks back showing screen shots of the new Performance page menus...and screen shots from some of the actual apps themselves.

AlfaOBD

They never worked on my 2020 Built to Serve either. Speed didn't mater. Even sitting still it just showed dashes instead of numbers 2019 Rebel here. More of a novelty at this point. Might just get rid of them haha

5thgenrams.com

I’ve done all of the changes as your write up and I get bunch of errors faults including service 4wd?

I’d there any fix so we can clear all the errors??

Thank you