Glad it all worked! Posting your original hex numbers and modified numbers may be helpful for future reference by those modifying their temp gauge buffers.
I think because you have a high cluster, you may be able to code the LCM overheating warning gong to 115C like we did as well. However, you will need NCS Expert and NCS Dummy for this coding.
https://xoutpost.com/1150096-post81.html
So it seems as though we do have an alarm for overheating engine on the high clusters which would be a gong and a text message in the cluster coming from the LCM as per wpoll's advice. I looked at my trace file for my C22 LCM and found the following.
KUEHLMITTELTEMP = melden (reported)
(CHECK CONTROL FOR COOLANT TEMPERATURE)
KUEHLMITTELUEBERTEMP_CAN = activ
(CAN-BUS COOLANT OVERHEATING)
MOTOR_UEBERTEMP = 125_grad_celsius - 125 ºc (257 ºf)
with an option of 130_grad_celsius - 130 ºC (266 ºf)
(ENGINE OVERHEATING [TEMPERATURE_ºC=DATA])
So if MOTOR_UEBERTEMP are the alarm thresholds:
I will add another parameter to MOTOR_UEBERTEMP:
115_grad_celsius - 115 ºc (239 ºf)
Open up the LCM.Cxx file with NCS Dummy without loading any FSW_PSW files, go down to MOTOR_UEBERTEMP, right click it, and click "add parameter". Name it whatever you want, and under data put the hex value of the temp alarm you want. Then click on module -> update module.
You will be able to select that new parameter when coding the LCM now.
