So, I have everything working on my dash, but for some reason the MAP sensor is not reading in Realdash. Its populated in PClink.
The boost in RD is calculated from the MAP sensor input so im looking for anyhelp here.
So what I did was set in Realdash that Manifold absolute pressure is set from AN volt 1.
But what i get is 0.0. so I think i have to do some sort of gauge math to get the volt to a readable MAP signal?
What kind of a connection you are using? CAN?
I’m using CAN, using the can seeed studio analyzer.
On pclink im using transmit generic dash. I also used generic dash 2 same result.
On RD I’ve used short can and the other link option. Everything works except for the boost.
The gtrlink g4x transmits MAP on An Volt 1. I selected it as a stream on pclink as well. I really just want to have boost work. Kind of lost, I know link uses MGP and not sure if there’s some translation error going on.
Best,
First try the ‘Settings->Application->Debug->Debug Data View’ and analyse if you are receiving MAP value there. Once you verify that, we can make changes to the CAN connection XML for you to read the MAP properly.
What do you think 19787 stands for? Is it raw ADC value, which could be in 16 bits 3.31 volts?
Not sure what it means. It seems that the Short Can XML is different from Linux to windows. Can I get the windows XML? The linux xml file is reading the 19787 number. I cant seem to find it anywhere
It wouldn’t let me share the video, so i posted a YT link to it. The windows version is showing the correct MAP data, but still won’t show it on the gauge nor will it change the boost gauge. I’m assuming something needs to happen to change it to negative in. H.g but I’m not sure if this has been solved by someone else.
There is no differences in XMLs between OS versions of RealDash.
From your video I see that Manifold Absolute Pressure is negative. RealDash expects this value to be absolute pressure in kilopascals (kPA) - ~100 = atmospheric, 0 = total vacuum.
It seems like you have to offset your MAP value by +100?
Have you tried to configure your ECU to output Displaylink CAN data instead?
You can also modify the Link Short Datastream CAN XML file. Download it from here:
RealDash-extras/RealDash-CAN/XML-files/Link/link_ecu_short.xml at master · janimm/RealDash-extras
And modify line:
<value targetId="31" offset="2" length="2" conversion="V-100"></value> <!-- MAP -->
To
<value targetId="31" offset="2" length="2"></value> <!-- MAP -->
That did work. It is off my ~ 1 KPA, but not really a big issue. (100 on PCLink - 99 on Realdash. Boost is now calculating correctly and translates to PSI, confirmed with mechanical boost gauge.
I did have realdash force close on a test drive, I saw it had a connection error from dropping off wifi. I thought the app only needs to see the internet connection once every 30 days? I’ll see if its just a weird bug, I was testing something else so didn’t look too much into it. I started saving the log files automatically.
@realdashdev Any suggestions for GPS modules? I have bluetooth but I would rather have usb connected. I see as long as its NVME its supported. Does something like this work Amazon.com: VFAN USB GPS Receiver Antenna Gmouse for Laptop PC Car Marine Navigation Magnetic Base : Electronics
or am I asking for trouble with something this cheap?
Last question: Looking for support on implementing turn signals. I was going to use some spare AN Volt connections on my LinkG4x, but I’d be okay with an extra IO box to usb if its easier. Could I set up 3 connections on RD or would it cause issues.
Connections 1: CAN Seed Studio
Connections 2: GPS Module
Connections 3: IO expansion
Any NMEA compatible GPS module should work. We have been using QStarz 818XT for testing.
3 simultaneous connections should not be a problem, but if you have an option to read extra inputs with your ECU, you will get them to RealDash ‘for free’ with ECU data. So that would be the route I’d take.