MHD teases N54 Antilag with the stock DME

[carabuser]

Is that second table defined?

Or can you make a screenshot of the values`?

I'm pretty certain there's a bug in the public XDF where the axis are swapped for the pre-control table so that's what it should look like if you are using the public XDF. You can fix it by changing the sort order from Row to Column since it's a square table.

The actual values look like this in when fixed:

Makes a lot more sense to have the wastegates closing at higher load and not at higher revs.

 

[corbanistan]

@Jake@MHD just noticed something weird going on, I've disabled 2F6C and 2FA3 codes however they're still appearing as shadow codes in MHD. Double checked my bin and they're definitely 00'd out.
Could MHD be overwriting disabled codes if aftermarket DPs is selected?

 

[JohnDaviz]

I'm pretty certain there's a bug in the public XDF where the axis are swapped for the pre-control table so that's what it should look like if you are using the public XDF. You can fix it by changing the sort order from Row to Column since it's a square table.

i looked into the "old" and v3 IKM XDF and can´t find that table. Please confirm. It is not defined in the public XDF right? Not that it is important.. but to figure out if i am blind or not.

 

[corbanistan]

i looked into the "old" and v3 IKM XDF and can´t find that table. Please confirm. It is not defined in the public XDF right? Not that it is important.. but to figure out if i am blind or not.

Never seen it in the XDFs but I've seen it in the DAMOS

 

[carabuser]

i looked into the "old" and v3 IKM XDF and can´t find that table. Please confirm. It is not defined in the public XDF right? Not that it is important.. but to figure out if i am blind or not.

Not in the XDF normally. But I was expecting you to copy the values into the normal pre-control table which is upside-down.

 

[corbanistan]

Not in the XDF normally. But I was expecting you to copy the values into the normal pre-control table which is upside-down.

Good catch with setting the table to "column". Makes sense. Surprised that hasn't been fixed yet.

 

[JohnDaviz]

I played with the table for the HP650s and mostly lowered the values in rpm areas below 3500rpm.
I guess most ppl never touch that table or questioned the axis? (i didn´t)

Quite excited how values around 4000-5000 rpm closer to the IKM values will feel.

 

[DCT_JAY]

After flashing this new update ive been getting this injector cutout code, anyone else ?

 

[corbanistan]

After flashing this new update ive been getting these codes, anyone else ?

I've been getting shadow codes for things I've disabled. Coding missing and exhaust flap.

 

[Jeffman]

I’ve started the process of converting my “legacy” home-brew custom FlexFuel bin to MHD+ using TunerPro and the new IJEOS XDF that includes all of the new MHD+ goodies for the N54. I may be approaching it the wrong way and am looking for a little guidance.

It seems incredibly laborious to copy and paste all of my tuning tables from my legacy FlexFuel custom bin to the new “IJEOS Base Map” bin which I can edit with the new XDF for IJEOS. Is there an easier way to do this?

Presently, I’ve opened my legacy Old FlexFuel.bin file into TunerPro with the new XDF loaded and saved that as “New FlexFuel.bin”. I’m checking each table and each toggle, and so far I only see a few glitchy tables (e.g., one or more of the Spool tables, IIRC) which I will manually change. I haven’t gotten to the MHD+ Tables yet - maybe later tonight.

Anybody convert their legacy custom MHD 2.0 bin to MHD+ (3.05) yet?

 

[MR-KRAKA]

I’ve started the process of converting my “legacy” home-brew custom FlexFuel bin to MHD+ using TunerPro and the new IJEOS XDF that includes all of the new MHD+ goodies for the N54. I may be approaching it the wrong way and am looking for a little guidance.

It seems incredibly laborious to copy and paste all of my tuning tables from my legacy FlexFuel custom bin to the new “IJEOS Base Map” bin which I can edit with the new XDF for IJEOS. Is there an easier way to do this?

Presently, I’ve opened my legacy Old FlexFuel.bin file into TunerPro with the new XDF loaded and saved that as “New FlexFuel.bin”. I’m checking each table and each toggle, and so far I only see a few glitchy tables (e.g., one or more of the Spool tables, IIRC) which I will manually change. I haven’t gotten to the MHD+ Tables yet - maybe later tonight.

Anybody convert their legacy custom MHD 2.0 bin to MHD+ (3.05) yet?

Use the compare bin function in TP and check the only defined items box. Select all you would like to convert->copy left to right.

 

[corbanistan]

I’ve started the process of converting my “legacy” home-brew custom FlexFuel bin to MHD+ using TunerPro and the new IJEOS XDF that includes all of the new MHD+ goodies for the N54. I may be approaching it the wrong way and am looking for a little guidance.

It seems incredibly laborious to copy and paste all of my tuning tables from my legacy FlexFuel custom bin to the new “IJEOS Base Map” bin which I can edit with the new XDF for IJEOS. Is there an easier way to do this?

Presently, I’ve opened my legacy Old FlexFuel.bin file into TunerPro with the new XDF loaded and saved that as “New FlexFuel.bin”. I’m checking each table and each toggle, and so far I only see a few glitchy tables (e.g., one or more of the Spool tables, IIRC) which I will manually change. I haven’t gotten to the MHD+ Tables yet - maybe later tonight.

Anybody convert their legacy custom MHD 2.0 bin to MHD+ (3.05) yet?

Yeah I have a custom XDF on GitHub with a ton of added tables for people to use, and to avoid any glitches I manually moved all custom tables to the new XDF and double checked addresses and such just in case.
MHD replaced some tables and whatnot in the actual BIN so I then, just to avoid issues, moved my tune over to an MHD 3.0+ base BIN manually. Only took me a few hours total. Just a lot of copy-paste-verify. Took the opportunity to make some changes I wanted to anyways.
Maybe there's a quicker way (above), but I didn't want to risk it. And I always learn something new when I dive into this stuff.

 

[Jeffman]

Use the compare bin function in TP and check the only defined items box. Select all you would like to convert->copy left to right.

Thank you. This is helpful.

 

[Jeffman]

@Jake@MHD I think I may have found a glitch in the new MHD+ XDF. My Legacy IJEOS XDF main Fuel (Spool) table was fairly compact:

But now the main Fuel (Spool) table in the new MHD+ XDF is much larger : how should we handle this? Or is there a glitch?

And also the Fuel (Start) table in the New MHD+ IJEOS XDF is bigger than the legacy table:

 

[corbanistan]

@Jake@MHD I think I may have found a glitch in the new MHD+ XDF. My Legacy IJEOS XDF main Fuel (Spool) table was fairly compact:
View attachment 71916
But now the main Fuel (Spool) table in the new MHD+ XDF is much larger : how should we handle this? Or is there a glitch?View attachment 71915


And also the Fuel (Start) table in the New MHD+ IJEOS XDF is bigger than the legacy table:
View attachment 71917

Is this after you converted? Something didn't convert correctly. That's why I did mine manually.

 

[Jeffman]

I was going through it manually. The dimensions of the main Fuel (Spool) tables are different. Assuming you also have IJEOS, what are the dimensions of your Fuel (Spool) table? Thanks.

 

[Jeffman]

Also, both of the Fuel (Spool) and Fuel (Start) tables in the IJEOS_MapSwitchBase.bin file are larger (16 rows x 12 columns) using the new IJEOS XDF:

But using the IJEOS XDF published in May, 2018 (which included the Flex Fuel tables I had been using), creates an 8x8 table for Fuel (Spool) and a 12 x 5 table for Fuel (Start):

And double checking, here is my legacy Fuel Start table, which is also 12x5:

 

[Jeffman]

I just checked the Fuel (Spool) and Fuel (Start) tables of the new I8AOS_MapSwitchBase.bin in the GitHub with the new I8AOS XDF. Interestingly, they are both larger like the IJEOS ones, but are also populated with values:

Maybe I downloaded the IJEOS tables incorrectly, so I'll take another look. Or adapt these I8AOS tables for my bin.

 

[RSL]

@Jake@MHD I think I may have found a glitch in the new MHD+ XDF. My Legacy IJEOS XDF main Fuel (Spool) table was fairly compact:
View attachment 71916
But now the main Fuel (Spool) table in the new MHD+ XDF is much larger : how should we handle this? Or is there a glitch?View attachment 71915


And also the Fuel (Start) table in the New MHD+ IJEOS XDF is bigger than the legacy table:
View attachment 71917

Not all tables cross or carry the same dimensions. Previously defined tables, like L2T 2, are replaced with 2-3 new tables in MHD+.

Everyone should be starting with a Mapswitch.bin, using the MHD+ XDF and copying tables to that from your old bin that actually still match. MapSwitch bins should have at least recognizable data or 0s populated in new tables to avoid confusion.

 

[Jeffman]

And now I see I indeed have erred in copying and pasting. Here are the tables as they appear using the IJEOS_MapSwitchBase.bin using the new IJEOS.xdf in TP:

(Thanks for listening!)