I have my realdash connected to my Maxxecu via Bluetooth and I can’t get Coolant Pressure and Fuel pressure to display. They are Analog input on my CAN device. Both device have the Destination set in Maxx and these data are showing on my Maxx Dashboard and Mtune.
So as a workaround I also tried to display the raw voltage of the CAN Analog input but even this will stay at 0.
What is strange is the Oil Pressure gauge is working, and this sensor is also conected to my CAN device.
Just some more test I did today;
In my Maxxecu I changed the Destination of my Fuel Pressure input to Oil Pressure, and the fuel pressure displayed as Oil Pressure on Realdash. I did the same test with coolant pressure set to oil pressure as the destination and it had the same behavior.
I then tried to display raw voltage of my Can analog input (all of them) and gauge was resting at 0.
If you look under Settings>Units & Values > Input Mapping, I believe the Realdash default oil pressure is simulated, which might explain why you are seeing a value for this
Oh, could have been! But I already went thru this setting and changed the input to the ECU. As of right now oil pressure display as it should and is 1:1 what I see on my Ecu.
I had a quick look at maxxecu xml file and see oil pressure is set at targetId151 so would align with RealDash values, but fuel and coolant pressure and not mapped by default into RealDash parameters; looks like your analog inputs need to be aligned in the xml file to RealDash targetId
How can I know the frame id and target Id of the 2 parameter I am trying to display?
TargetIds are listed here
https://realdash.net/manuals/targetid.php
202 for Fuel Pressure, but there is not one for Coolant Pressure, just Temp.
I suggest using the CAN monitor to see how your analog inputs align with frames
Found this CAN table on the maxxecu website and see frame id locations for Fuel Pressure 1 and Coolant Pressure
https://www.maxxecu.com/webhelp/can-default_maxxecu_protocol.html
Good points. One thing to note is that it was stated that MaxxECU is connected via Bluetooth. The MaxxECU Bluetooth connection is a proprietary custom protocol for MaxxECU and basically has nothing to do with CAN output. I’m not sure how these custom values are transmitted over MaxxECU Bluetooth, but it could be that RealDash is not reading all of them.
I would suggest that you use an ‘actual’ CAN connection with MaxxECU. That way you can easily configure the custom CAN data from MTune.
I think my only option so far as I’m not a programmer, is to send the coolant pressure and fuel pressure sensor to another “destination” in my ecu. By using an already mapped destination with data that are transferred to Realdash, I might be able to trick realdash by displaying other data.
Any plan to integrate these missing connection? Since there were all available to choose from in Realdash I kinda assumed that they were already mapped.
I’m working through the exact same issue right now using Bluetooth connection through Maxxecu. I have a DCT transmission and I need to find a way to make the RealDash show DCT gear before it’s really useful.
I was thinking the same thing as far as mapping to a different parameter that RealDash reads.
Is it possible to use a usertable output? I’m not seeing that option either.
It should be easy to do with User table under advanced, just delete the X axis and set the Y axis to your DCT gear position switch. The trick is under “Use as analog input function” select one that is already mapped into RealDash, might have to fiddle around until you find an empty spot you can use.
This way at least the display on Mtune won’t be showing your DCT gear under another sensor data since you only remapped the position switch to another analog input and left the original signal unaltered.
Did you try getting the pull up table for the sensor from the manufacturer of those sensors then making the the realdash table.
All of these sensor are already properly calibrated on the ECU but the data is not transferred over to Realdash. I am using User Table and I mapped EGT 1 to EGT with the sensor that I had no data on realdash, works like a charm now (until I actually need my EGT data).
When working on this relatively complex project, I would recommend switching to CAN connection. It is easier to configure on MTune and is very fast.
In our DEATHFISH 2 demo car we actually use both. CAN for data transmit and Bluetooth only for MaxxECU Bluetooth button support.