Evo8 ECU in a 1G DSM in the works!
MAF size isn't as much of my concern as is the scaling. Ideally, if someone was to install a 2G MAF inline with their evo8 MAF on their evo, and had a way to log the 2G maf, it could be mapped out perfectly. Trouble is....no one is going to go thru the trouble lol. Can you even see the MAF size and scaling in the 2G roms??? I haven't seen a DSMlink v3 ECU setup yet so I dont know what parameters are visible to the general public.
MAF size isn't as much of my concern as is the scaling. Ideally, if someone was to install a 2G MAF inline with their evo8 MAF on their evo, and had a way to log the 2G maf, it could be mapped out perfectly. Trouble is....no one is going to go thru the trouble lol. Can you even see the MAF size and scaling in the 2G roms??? I haven't seen a DSMlink v3 ECU setup yet so I dont know what parameters are visible to the general public.
http://www.dsmtuners.com/forums/tuni...shing-faq.html
Download the 2055011 ROM and DEF.
All the MAF Scaling, Smoothing, Adder, etc, have been found.
The DSMLink 95 ECU and DSM 98 and 99 Flashable ECUs are totally different programming wise. Use maps from the 98/99 they are similar to the EVOs.
Edit:
The end of post #1, I have how to install a EVO MAF in a 2G ECU. You could do the opposite for a 2G MAF in a EVO ECU
Last edited by Ceddy; Jul 27, 2009 at 09:35 PM.
Sorry, I didn't remember. I have the scalings taken directly from an Evo I ROM. The MAF adder is different though, so you have to compensate for that in the MAF scaling table itself.
It would be good if someone smarter than me could find the MAF adder for an 8 ROM so we wouldn't have to copensate in the MAF scaling table.
It would be good if someone smarter than me could find the MAF adder for an 8 ROM so we wouldn't have to copensate in the MAF scaling table.
Last edited by wreckleford; Jul 28, 2009 at 07:40 AM.
Check out ->
http://www.dsmtuners.com/forums/tuni...shing-faq.html
Download the 2055011 ROM and DEF.
All the MAF Scaling, Smoothing, Adder, etc, have been found.
The DSMLink 95 ECU and DSM 98 and 99 Flashable ECUs are totally different programming wise. Use maps from the 98/99 they are similar to the EVOs.
Edit:
The end of post #1, I have how to install a EVO MAF in a 2G ECU. You could do the opposite for a 2G MAF in a EVO ECU
http://www.dsmtuners.com/forums/tuni...shing-faq.html
Download the 2055011 ROM and DEF.
All the MAF Scaling, Smoothing, Adder, etc, have been found.
The DSMLink 95 ECU and DSM 98 and 99 Flashable ECUs are totally different programming wise. Use maps from the 98/99 they are similar to the EVOs.
Edit:
The end of post #1, I have how to install a EVO MAF in a 2G ECU. You could do the opposite for a 2G MAF in a EVO ECU
The funny thing is, the Evo scaling you have there (I assume it is from a V or IV) is different to the VIII scaling, but they use the same MAF. I am not sure if your 2G scaling is the same as what I have, but the adder and MAF size are the same.
Nice, they finally have the DSM flashable ECUs working.
Now, maybe I can sell my 99 GST ECU that I kept when I used DSMLink on my DSM. I'm pretty sure I still have it here in a box somewhere.
Edit: Yep, still have my ECU...MD359402
Now, maybe I can sell my 99 GST ECU that I kept when I used DSMLink on my DSM. I'm pretty sure I still have it here in a box somewhere.
Edit: Yep, still have my ECU...MD359402
Last edited by l2r99gst; Jul 28, 2009 at 10:15 AM.
This should be a DIRECT correlation from the 2G maf readings. This is how the ECU works (same as how it works for the boost control adder really):
The actual value the ECU uses is bigger than the table will allow, so we incorporate an 'adder' that simply gets added to the base number.
So with the 2G MAF scaling, you take the number in the table and then add 64 to it. This gives you the value the ECU gives a crap about. Its the same thing for the Evo8 MAF scaling only it adds 140 to each value in the table.
So I took the 2G maf scaling and added 64 to each to get the values the ECU 'wants' to see. Then I subtracted 140 from these values. So now when the ECU implements its adder of 140, it will get the same results as if we were able to change the MAF ADDER from 140 to 64 ourselves. Also, the MAF SIZE needs to be updated from 357.5 to 286.0

You can also try changing the Airflow/baro comensation tables and the MAF filtering.
The actual value the ECU uses is bigger than the table will allow, so we incorporate an 'adder' that simply gets added to the base number.
So with the 2G MAF scaling, you take the number in the table and then add 64 to it. This gives you the value the ECU gives a crap about. Its the same thing for the Evo8 MAF scaling only it adds 140 to each value in the table.
So I took the 2G maf scaling and added 64 to each to get the values the ECU 'wants' to see. Then I subtracted 140 from these values. So now when the ECU implements its adder of 140, it will get the same results as if we were able to change the MAF ADDER from 140 to 64 ourselves. Also, the MAF SIZE needs to be updated from 357.5 to 286.0

You can also try changing the Airflow/baro comensation tables and the MAF filtering.
Last edited by Jack_of_Trades; Oct 19, 2010 at 08:43 AM.
This should be a DIRECT correlation from the 2G maf readings. This is how the ECU works (same as how it works for the boost control adder really):
The actual value the ECU uses is bigger than the table will allow, so we incorporate an 'adder' that simplay gets added to the base number.
So with the 2G MAF scaling, you take the number in the table and then add 64 to it. This gives you the value the ECU gives a crap about. Its the same thing for the Evo8 MAF scaling only it adds 140 to each value in the table.
So I took the 2G maf scaling and added 64 to each to get the values the ECU 'wants' to see. Then I subtracted 140 from these values. So now when the ECU implements its adder of 140, it will get the same results as if we were able to change the MAF ADDER from 140 to 64 ourselves. Also, the MAF SIZE needs to be updated from 357.5 to 286.0

You can also try changing the Airflow/baro comensation tables and the MAF filtering.
The actual value the ECU uses is bigger than the table will allow, so we incorporate an 'adder' that simplay gets added to the base number.
So with the 2G MAF scaling, you take the number in the table and then add 64 to it. This gives you the value the ECU gives a crap about. Its the same thing for the Evo8 MAF scaling only it adds 140 to each value in the table.
So I took the 2G maf scaling and added 64 to each to get the values the ECU 'wants' to see. Then I subtracted 140 from these values. So now when the ECU implements its adder of 140, it will get the same results as if we were able to change the MAF ADDER from 140 to 64 ourselves. Also, the MAF SIZE needs to be updated from 357.5 to 286.0

You can also try changing the Airflow/baro comensation tables and the MAF filtering.
Yes, that's the same as I did.
One thing you should be aware of:
The load limit and injector pulse width limit are directly related to MAF size, so with the 2G MAF, the load at which the limit comes in is reduced. For the 2G MAF, the load limit ends up being about 310 instead of 380 with an Evo8 MAF. If you are running a reasonably decent setup, you will hit the load limit quite easily. Fortunately John Banks has shown on here how to remove the limits.
The load limit and injector pulse width limit are directly related to MAF size, so with the 2G MAF, the load at which the limit comes in is reduced. For the 2G MAF, the load limit ends up being about 310 instead of 380 with an Evo8 MAF. If you are running a reasonably decent setup, you will hit the load limit quite easily. Fortunately John Banks has shown on here how to remove the limits.







