Realdash ignore some "conversion"

General
1

pippeueba.xml (4.9 KB)

This is my XML.

I have sent the DEBUG file.

All the values ​​are read and displayed but it does not perform the conversions no matter what you enter.

“0142” skipCount=“12” name=“Voltaje” units=“V” conversion=“V/100”>

This one is ignored, I have been able to modify it in realdash by setting the scale to 0.001

“2203CA” skipCount=“50” name=“IAT2” conversion=“V-40”>

This DOES work

“2203e8” skipCount=“410” name=“OAR” conversion=“(signed(A)*256+B)/16384”>

This worked and no longer shows the corrected value without having touched anything.

“222813” header=“atsh726” skipCount=“0” targetId=“240” units=“BAR” conversion=“(((256A)+B)/3+22/3)/100">
“222814” header=“atsh726” skipCount=“0” name=“rftp” units=“BAR” conversion="(((256A)+B)/3+22/3)0.145">
“222815” header=“atsh726” skipCount=“77” name=“lrtp” units=“BAR” conversion="((A256+B)/3+22/3)/100”>
“222816” header=“atsh726” skipCount=“77” name=“rrtp” units=“BAR” conversion=“256*A+B”>

With these four I have tried different things, formulas, name, etc… realdash ignores it and shows the uncorrected value.

The rest of the original PIDs work correctly.

2

@Darkitu not sure of the precise cause, but have you tried removing all the units=“BAR” etc. attributes

3

I remove units and clear “imports values” in the “units and values” sections.

There were hundreds, I guess they have accumulated while testing. I think they might create conflict.

I’ll try.

4

I have made progress. Realdash does not recognize any formula in PID added with A,B format.

I have managed to get it to recognize the TPMS formulas with B0,B1.

The problem is that it does not recognize “V” in any added PID either.

IAT2 does not recognize me as “V-40”

5

@Darkitu I think you need to use conversionABC= to use the A,B format, I have attached a link to guidance on the OBD2 xml format https://github.com/janimm/RealDash-extras/blob/master/OBD2/README.md

6

OMG! TY!!!

I read the information several times and got confused. In my head I thought that the ABC to B0 B1 B2 conversion was automatic, I didn’t notice the conversionABC command.

Everything works except one thing:

command send=“2203e8” skipCount=“410” name=“Octanaje” conversion=“(signed(B0)*256+B1)/16384”>

It should return a value of -1 but with this formula it is about 46000.

I have managed to do this with this formula of 3 but I can’t get the correct value.

command send=“2203e8” skipCount=“410” name=“Octanaje” conversion=“(B0*256+B1)/16384”>

SIGNED(A) , signed(A) , Signed(A) – treat byte as signed (-128 … 127)

1 Like
7

RealDash has no ‘signed’ function in conversion, instead use signed=“true” attribute in command.

<command send="2203e8" skipCount="410" name="OAR" signed="true" conversion="V/16384"/>
9

I can’t get the signed=true command to work. But it’s not something that worries me.

Now i have another problem, i’ll send you the log… The coolant value is lost after a short time. Everything else works fine and that sensor has not been modified in the XML.

base12.xml (2.5 KB)

10

It happened also to me on the last RD update. Battery Voltage never works anymore (it works in obd Link app and also in RD with default Mitsubishi mut). Atf temp (custom PID) works then it doesn’t, without understanding why and when. I think also maf or map might be doing the same sometimes they work sometimes they don’t. The XML worked for the last 4 years without issues. Using obd Link sx on usb.
What has changed during last update (maybe 2 updates as I was out of the country and maybe I updated directly over one version)?
Thank you!
No rpm no speed MUT 29.09.2020 MAP header.xml (5.1 KB)

11

Now that you mention it, I updated the app two days ago and that’s when it stopped working shortly after connecting.

12

Also the standard coolant temperature is intermittently working, like you said. So battery voltage never works, coolant temperature it works sometimes but only for few seconds, ATF temp, custom PID, the same, it works sometimes for few seconds. Everything worked before the last update.
Maybe this should be moved to bugs.
I hope Jani can fix this or let us know what we need to change in the XML.
Thank you!

13

After 30km (about 20 minutes) it has lost the coolant signal. It doesn’t appear in debug or anything.

14

There was some changes in OBD2 connection for 2.4.8. Send a debug log for analysis:

How to send a debug log - General / Frequently Asked Questions - RealDash Forum

15

Sent debug now, also with some details over email

1 Like
16

Do we know anything? Would it be possible to have the previous version to test?

17

We are working on a fix. This issue is related using custom headers in OBD2 connection.

18

The new version has broken everything for me. My XML doesn’t work at all. Only the headers work. If I want the rest to work, I have to remove them.

I can use 2.4.7?

Edit: I found 2.4.6 and now work…

19

If you want to help, send a debug log on latest version:

How to send a debug log - General / Frequently Asked Questions - RealDash Forum