Hello!
At least for AFR1 and AFR2(target id-s “0” and “1”) doesn’t work custom conversion formula. Always uses “V*1465.1”.
If you are using OBD2 connection, this could be that AFR values are in same cases actually calculated from Lambda1 and 2.
Thank you! Indeed, If I send correct lamda value(0.5-1.5) to id254(Lambda1), it’s automatically calculating AFR 1 channel.
Related problem( Android and iOS):
For OBD2 connection it doesn’t show PID 0111 anyway.
Althogh in OBD monitor reply works correctly:
Tried several string descriptions:
<command send="0111" replyLength="1" skipCount="2" targetId="93" conversion="V/2.55"></command> <!-- TPS -->
<command send="0111" replyLength="1" skipCount="2" targetId="42" conversion="V/2.55"></command> <!-- TPS -->
<command send="0111" replyLength="1" skipCount="2" name="myTPS" conversion="V/2.55"></command> <!-- TPS -->
<command send="0111" replyLength="1" skipCount="2" targetId="93" conversion="V"></command> <!-- TPS -->
Solved(partially). My device didn’t make a correct answer to mode1 “0100” request(avaliable PIDs mask). So, 0111 didn’t show there and RealDash didn’t ever ask this PID. May be it worth to ignore this mask if PID is in xml file.
But now working only custom name:
<command send="0111" replyLength="1" skipCount="2" name="myTPS" conversion="V/2.55"></command>
If I wanna use target ID42 (Throttle Position) it doesn’t show. Again some trick with calculated value?
We tried that some time back and it was a disaster. Many vehicles cause timeouts and hangups when requesting PIDs that are not supported.
Hello!
1.8.3:
Now this mapping(lambda → AFR) doesn’t work. Lambda works as expected, AFR always shows “28”. Mappings in settings are default.
Using RealDash CAN.
And OBD2 protocol totally broken with my own adapter(other apps works so as old RD). Log of OBD2 dialog mode1 is ok(request from RD, answer from my device), but dash shows nothing. OBD2 monitor works ok.
Wifi, tcp. RealDash CAN works.
Try on 1.8.4-beta2. It has a fix for OBD2 parsing without headers.