Megasquirt Bluetooth ini ambiguities

Connectivity Megasquirt
1

Hi,
by now I’m using Bluetooth as connection to my Megasquirt (MS3x).
Therefore I’m importing the MainController.ini from projectCfg.

When I change the UserAliases for example for the generic sensor inputs in the MainController.ini… RealDash doesn’t seem to care about those changes. They are always shown as sensor01… sensor02 and so on.

Therefore I have to change the name in RealDash. But there I’ve got two issues:

  1. When I want to change for example sensor03 to “Fuel Pressure” then RealDash says it is already in use. However it is nowhere in my MainController.ini.
    I also deleted all imported values in RealDash. For some reason it still generates “Engine/ECU Inputs: Fuel Pressure” by its own.
  2. Furthermore I can’t set the units in RealDash

In general I’m not really sure, where RealDash gets the channel infos.
For example it shows “ECU SPECIFIC: Spareportbit 0” under select inputs.
Which then Equals “PTT3” from Megasquirt.
But when I search the MainController.ini the “Spareportbit …” does not even exist. So where is RealDash taking the channel info/name from?

Also I’m missing the AFR target in RealDash.
Signal is listed in the Megasquirt MainController.ini
But after importing that file, the AFR target is not there in RealDash
Would be important for me to have this signal.

It is like RealDash is ignoring the .ini File and just using the basic “a 00 06” protocol. But don’t know why. Is there any “clean” ini File for Megasquirt available as alternative for the mainController.ini from Project Folder?

2

Thank you for reporting. It has been a long time since I last tested the Megasquirt connection. I will run some tests to see what is going on.

3

I did some tests on MS3 on serial connection. For me it seems to work as expected. As of how the ini file is used, here is some kind of a breakdown:

  • If no ini file is uploaded, the old data request of “a 00 06” is used.
  • From ini file, these sections are read:
    • [MegaTune]
      • the ‘signature’ is read from this section and later compared to signature sent by the ECU
    • [GaugeConfigurations]
      • This section is read to find units and conversions for the values.
    • [OutputChannels]
      • ‘ochGetCommand’ is read and stored. This is the command to send to ECU to request data block
      • ‘ochBlockSize’ is read and used as how many bytes are expected to have on data block.
      • Rest of the lines are read and stored the values and their offsets on data block. If value name cannot be matched to RealDash internal inputs, a custom input (ECU Specific) is created for that value.

Don’t know if this helps, but at least it seems to work as expected on my office MS3.