Honda Civic RS 1.5 Turbo - 2023 11th Gen

General
21

@realdashdev i hace made some more changes to ECT and IAT, B - 40 works but i am not getting the same tenps as Torque (which i assume is more accurate.
I think it has to B1 or B2, not sure which is the first one. Tried B1-40 for both but the temps are varying somewhat relevant. I think i should try B2 -40 to see if its consistent. Any idea which is the first byte b1 or b2? As my engine give 2 readings IAT 1 and 2 and ECT1 and 2.

Apart from this that day i got low fuel notification in realdash but still the fuel level is not shown, any suggestions on that?

I will upload the new XML of ECT and IAT are fixed by changing the B value.

22

By default RealDash uses calculated fuel level. You can reset the calculated fuel level from quick settings. Open the top menu and press the gear icon on lower right corner of the screen to access the quick settings.

23

@realdashdev i am trying to explore knock control and knock retard PID.
The pid i have explored are 222662 and 22224f.
The response i amm getting from these 2 are following;
18DAF1101039622662280033
18DAF110217160070000000O
18DAF110223F000000000000
18DAF1102300000000000000
18DAF1102401010000002800
18DAF11025610001000000AA
18DAF1102600606F00000000
18DAF1102700000000000051
18DAF1102800005555555555

And

18DAF1101039622663000000
18DAF110210O00O000000000
1 8DAF1102200000001000000
18DAF1102300000000000000
1 8DAF1102400000000000000
1 8DAF11025000O00O0000000
1 8DAF11026000O0000000000
18DAF1102700000000000000

24

What information would you need to identify what these responses are and how to interpret them, and in formula which variable could be used and what formula for knock control percentage and what for sensor volts

25

I would like to help, but it takes quite a long time to analyze the data. Also, to reverse engineer the data, I would immediately go with CAN connection instead of OBD2. Much easier and faster to reverse engineer.

But, basic principle is, you send 222662 and get reply:

18DAF1101039622662280033
18DAF1102171600700000000
18DAF110223F000000000000
18DAF1102300000000000000
18DAF1102401010000002800
18DAF11025610001000000AA
18DAF1102600606F00000000
18DAF1102700000000000051
18DAF1102800005555555555

First you find 622662 as that indicates valid reply for pid 222662. That is on first line.

Then you see that this is a multiline response, frame ordering is in bytes 10,21,22,23 … 28.

Actual response data is read:

  • read bytes after 622662
  • read each line after identifier 2X.
  • this will give you data:
280033
7160070000000O
3F000000000000
00000000000000
01010000002800
610001000000AA
00606F00000000
00000000000051
00005555555555

Your values (and probably some others) are hidden somewhere on this data set. To reverse engineer where, it requires live data and hours, if not days of work.