SRT Performance Pages (2015-2016) - UConnect ReCoding Thoughts

[rayzazoo]

It's been several years trying to figure this out but I was able to finally track down the issue with the Performance Pages Gauge 2 Dashboard swap.

I'd like to get folks thoughts and help on how we can

(1) get Dodge to send out a patch update -or-
(2) figure how we can do it ourselves.

I've got the coding problem figured out. The challenge is getting the UConnect software repackaged properly so the car will authenticate/take the update.

UConnect Versions
18.45.01 - September 24, 2019
17.43.01 - January 12, 2018
17.11.07 - April 5, 2017

--- This is when the Hellcat SRT Performance Pages Gauge 2 readings between I/C Coolant and Intake Air Temp swapped ---

16.16.13 - April 13, 2016
15.17.05 - April 24, 2015

Issue (2015-2016 Hellcats)
UConnect 17.11.07 introduced a change in how the Performance Pages resolved sensor data. The updated code mapped the Performance Pages’ temperature gauges to incorrect sensor URLs (e.g., "LTR_Coolant" and "IntkAirTempIntrClr") referenced in the I/C Coolant and Intake Air Temperature Dashboard Views, resulting in a mismatch between the displayed labels and the underlying CAN signals.

The instrument cluster was unaffected because it continued to reference the correct CAN sensor IDs. This is why cluster readings for I/C Coolant Temp and Intake Air Temp remained correct, while the Performance Pages began showing cross-mapped or inverted values starting in 17.11.07 and all later releases.



Potential Fix
Dodge needs to patch the Performance Pages App for 2015-2016 Hellcats with the following corrections to Gauges 2 Dashboard files.

File Location:
UConnect 18.45.01 version > swdl.upd > secondary.iso > usr > share > xlets > kim_packages > KIM18 > xlets > 7DEC7834-535D-47B5-BD33-695477EDCD57 > prog > jars > GSkills_MY15_LSeries_v02.01.01_FIT.jar

Current in 18.45.01
IntakeAirTempDashboardView.class -> IntakeAirTempICSensorModel.getInstance()
CoolantTempICDashBoardView.class -> CoolantTempICSensorModel.getInstance()

Software Patch Needed (2015-2016 Hellcats only)
IntakeAirTempDashboardView.class -> CoolantTempICSensorModel.getInstance()
CoolantTempICDashBoardView.class -> IntakeAirTempICSensorModel.getInstance()

This is because the current CoolantTemplCSensorModel references "LTR_Coolant" and IntakeAirTempICSensorModel references "IntkAirTempIntrClr". When the wiring was changed from MAF to IAT sensor in 2017, the signal referenced by "LTR_Coolant" is now the post-intercooler charge air temperature, and the signal referenced by "IntkAirTempIntrClr" is the coolant temperature flowing through the low-temp coolant circuit and intercooler pump.

 

[DGatzby]

Amazing, a Dodge engineer did not have the time during the covid time-out to fix that. Good work Ray, hope they are reading us.

 

[BULL]

Subscribed and bookmarked

 

[ACMAVRO]

Would love to get this fixed. Nice work!

 

[covidcommander]

Nice work. Ur Mr Uconnect.

 

[2ndgen]

Now maybe see if you can figure out why the unit setting for the boost gauge is ignored--it always displays in in. hg.

 

[rayzazoo]

Now maybe see if you can figure out why the unit setting for the boost gauge is ignored--it always displays in in. hg.

The gauge is a dual mode gauge. It shows in/HG, which is a measure of vacuum (low pressure) until this goes to zero then it changes to showing boost pressure in PSI.

Is this not the case anymore?

 

[2ndgen]

The gauge is a dual mode gauge. It shows in/HG, which is a measure of vacuum (low pressure) until this goes to zero then it changes to showing boost pressure in PSI.

Is this not the case anymore?

Oh, hrm. I dunno. I never watch it while on the throttle--I'm watching the road--so I only really get a look at it while idling, stopped at a light. So maybe it's switching units when I'm at WOT...?

 

[MikeD1]

Well, this vindicates what I thought (and told Dodge + uconnect multiple times) - the problem is a simple mapping issue & involves 2 lines of code max !!

Have to believe they knew it as well, but for whatever reason, refused to 'fix' it in any of the releases since the error was 1st introduced.

There was a lot of bitching when it 1st happened + the usual avoidance tactic of Dodge & uconnect finger pointing on who was to blame. On several occasions I chased the problem thru Dodge CS as high as I could take it with zero answers or (obviously) results. I could understand them not making a release just to fix that error, but there is simply no excuse for it not being corrected in any of the subsequent releases. While it's not a critical error, I cringe every time I look at it and it's been annoying AF since it started.

As far as I know that 18.45.01 is the last release that will be issued for these cars as they are now discontinued & 10 years old. So unless there is some slick way to hack into the software & manually patch it, I doubt we'll ever be able to make Dodge/uconnect fix it.