When adding a Brake Temperature Control to a page, is there some way to only add a single corner instead of all 4? I am only running a LF brake temp sensor because, IMHO, unless you have unlimited funds anything more is just redundant info.
Also, am I correct that there is no way to overwrite the built in ttc.TireTempXX arrays with a custom CAN input? Is there some other way to integrate with other Tire temp sensors that use a different BaseID offset than the ECUMaster one? Specifically, I want to use the Autosport Labs TireX; which can be configured to the same 16-channel, 255*C output as the ECUmaster but uses a 0x100 offset between sensors so none of the built in stuff works.
Being able to individually specify the BaseID for each Brake and Tire sensor in the ADU->Configuration->CANBus Setup would really make life a lot simpler.
Currently, there is no native option to display only one wheel temperature.
You can work around this by covering the unused graphic part with black squares.
We will consider adding a single bar graph for this data type.
The temperature cameras are hard-coded for optimization purposes. We are getting close to the limits of software resources in ADU, and adding configurations like this will use some of those resources. Considering it’s a feature to use competing products, we don’t have much incentive.
The best I can do for now is to give you a workaround. To do it, you must set CAN 2 to 1 Mbps and connect it to CAN 1. Now you can receive temperature sensor data on CAN 2 and export it to CAN 1 at different IDs.
Ok, that’s a bit disappointing but at least I know I have to find a work around. I’ll evaluate the resource consumption options between transposing the data into a new CAN message vs importing each element of the array into a different individual number and then stacking indicator boxes next to each other to make my own tire temp graph. If I’m doing it all manually then I can just put the TireX sensor into 4-zone mode and that will help save some space. I was just hoping to use the functions that are already compiled in and using up memory/cycles rather than have to spend precious custom resources to recreate them.