Hi, loving RealDash! I have it connected to my kprov4 over bluetooth, and any issues I have have been connection related coming from the ECU and not RealDash. There is one issue that I’m unsure of, my calculated boost value doesn’t read above 11.3PSI, and I tried watching the MAP value with a calculation to convert it to PSI, and it still doesn’t read above 11.3 (177kpa?). I poured over the settings to make sure I wouldn’t be wasting time making this post, I don’t believe it’s any of my settings on the kpro or the RealDash config. I understand if it’s a limitation of the kprov4 connection over Bluetooth, but I haven’t seen a Topic covering it, so I just wanted to reach out to see if this might be a known issue/limitation. I tried to get a datalog on my way into work today but I need to actually bring my tablet inside to get wifi to sync it, I can try to get it and add it here if that helps. Thanks!
It is possible that your gauge displaying the boost is capped at 177kpa. To check:
- Enter edit mode
- Select your boost gauge
- Go to Input & Values
- Check the gauge range if it is capped
You can also use Debug Data View from ‘Settings->Application->Debug’ as those values are raw without capping.
Thanks @realdashdev I did recheck the gauge range of both the calculated boost and MAP and both are well above 11.3psi and 178kpa respectively. This morning I watched the debug values as you instructed while I did a pull and I saw the MAP under the engine tab not go over 178, and Calculated boost under calculated values didn’t go over 11. Sounds like hondata is probably not sending map over 178, just weird that it’s such a specific number right? Not like a cap that would make sense on a data transmission like 255 or 256.
Also I synced the datalogs from the other day where I did some pulls and you can see it cap at 11.3 psi, but I can’t upload them here because it says I can’t upload .msl files, not sure if you can see them on my account from your end. Either way I understand if our hands are tied.
Yes, seems like issue is in the sending end. Could not find anything from RealDash source code that would cap the MAP to 178.