Kalmaker logging calculated VE

160 And 8192 Baud Aldl
Posts: 2326
Joined: Sun Aug 02, 2009 9:16 pm
Location: Bayside, Melbourne, Victoria

Kalmaker logging calculated VE

Postby VX L67 Getrag » Sun Jun 10, 2018 6:42 pm

I was just wondering if anyone knows the address for current VE for kalmaker map based software in the $A5 code so vt-vy L67(w55 to w96).

I found in the ose $11p code it's packet offset 0x22 so I used that & seems to lol about right but I just wanted to double check before I go tuning off those figures if there not correct.

Posts: 2326
Joined: Sun Aug 02, 2009 9:16 pm
Location: Bayside, Melbourne, Victoria

Re: Kalmaker logging calculated VE

Postby VX L67 Getrag » Wed Jul 04, 2018 11:26 pm

O.K. so I have been told from 1 of the moderators I "SHOULD" be able to figure it out, which I think I have but would like to have actual confirmation before I start basing my tune off the "POSSIBLE" what I know data log adreses...

So it looks like closed(or near closed TPS)is packet 22...

Then Main(non closed TPS) may be packet 26(which was MGC as now MAF is not being used it's now free) VE table may be packet 26?

Posts: 2326
Joined: Sun Aug 02, 2009 9:16 pm
Location: Bayside, Melbourne, Victoria

Re: Kalmaker logging calculated VE

Postby VX L67 Getrag » Sat Jul 07, 2018 4:34 pm

So it turns out the mgc data packet isn't correct for main VE table, so I have no idea without trying every single packet & see if it come close to what is commanded(but who knows if they're grabbing multiple areas for the 1 packet???).

Return to ALDL, OBDII Logging and Scanning

Who is online

Users browsing this forum: No registered users and 3 guests