"Big Map"...reality is here

[repforenzo]

Originally Posted by silverside

my load logs in at 168% all the time doesn't matter though cause the computer still uses the fuel/timing values in the 100% column.

the question is have you fixed this problem

Which load reading? ECULoad is the one that needs addressing.

[PharmEcis]

Originally Posted by silverside

yes and the sucking a hell of a lot of air is what causes the load values over 100% that everyone has. hence the need for the larger map. you sir need to do some reading.

I see I have an apprentice in the making!

[acamus]

Originally Posted by repforenzo

Which load reading? ECULoad is the one that needs addressing.

Actually it is 2 byte load that needs adressing when you are over 160.
the limit is limitation of 1 byte request. Maximum integer value that 1 byte can hold is 255. So applying scaling 5/8 * 255 = 160, there is no way around this, and there are also some CEL checks that are monitoring this value to be in the range.
Anyway if you want to tune for bigger load you can use 2 byte load modification. There is also limitation of 2 bytes but you will never reach that (5/16*65536=20480).

[silverside]

Originally Posted by repforenzo

Which load reading? ECULoad is the one that needs addressing.

i think it was load calculated. its been a while since i have done any tuning as i hit a roadblock with the load getting beyond what the computer will do. plus the car has been apart a lot in the last 4 months with the clutch problems. sad part is im still N/A

[Silvertune]

Yes sir I won't deny. I'm donig a lot of reading and have a long way to go. Tuning is my weak spot and I'm hoping this goes through so I can follow it. Its either that or buy a fricken haltech.

[Dragon34x]

Originally Posted by acamus

Actually it is 2 byte load that needs adressing when you are over 160.
the limit is limitation of 1 byte request. Maximum integer value that 1 byte can hold is 255. So applying scaling 5/8 * 255 = 160, there is no way around this, and there are also some CEL checks that are monitoring this value to be in the range.
Anyway if you want to tune for bigger load you can use 2 byte load modification. There is also limitation of 2 bytes but you will never reach that (5/16*65536=20480).

Hey, Just wanted to personally say thanks! (As you probably already may know, i'm the guy who was doing the testing of the xml and rom files and stuff)

[WarmAndSCSI]

Greg is absolutely right... not only does the V6 ROM not know how to calculate load > 100%, our MAF is capped at 1150 Hz or so. I can't remember if this is ECU-side or MAF-side... I made a post a few years back asking about it, and nobody knew.

The only way I've been able to make any power whatsoever on this platform is with an e-Manage Ultimate piggybacked on the stock ECU. Setup properly, and with adequate fueling and ignition, you can make at least 600 WHP. It's hack-job tuning, but it works (and it's better than people who "tune" with just a rising rate AFPR!).

The best solution would be to move to an Evo-like ECU and ROM... with a 3.5-bar MAP as well like with the Evo X.

[Dragon34x]

Originally Posted by WarmAndSCSI

Greg is absolutely right... not only does the V6 ROM not know how to calculate load > 100%, our MAF is capped at 1150 Hz or so. I can't remember if this is ECU-side or MAF-side... I made a post a few years back asking about it, and nobody knew.

The only way I've been able to make any power whatsoever on this platform is with an e-Manage Ultimate piggybacked on the stock ECU. Setup properly, and with adequate fueling and ignition, you can make at least 600 WHP. It's hack-job tuning, but it works (and it's better than people who "tune" with just a rising rate AFPR!).

The best solution would be to move to an Evo-like ECU and ROM... with a 3.5-bar MAP as well like with the Evo X.

I can tell ya right now... you're in the wrong... Proof will be posted up real soon. I just need to get the "ok" to do so

[WarmAndSCSI]

Originally Posted by Dragon34x

I can tell ya right now... you're in the wrong... Proof will be posted up real soon. I just need to get the "ok" to do so

There's no way to prove that you logged the correct data item via the right address...

Trust me, I'm not wrong about the MAF cap, at least for a model year 2001 V6 Eclipse/Galant.

You will find that once you're making any significant power or torque whatsoever, that the stock MAF input just won't work any more.

Making around 700 lb-ft at the crank, I would have been registering at least ~300% load. That is something I guarantee the stock MAF will not let you register. That's the equivalent of about 1600 Hz @ 4500 RPM. Not gonna happen.

Read what I said one more time... I should have more specifically stated the stock ROM cannot register above 100% load, but what I said about the MAF limit holds true. You're going to have to figure that one out for yourself. All of what I said above of course only applies to a proper suck-through MAF setup... Things become greatly complicated when you start talking about a (crappy) blow-through setup.

Anyway, good luck with that... and especially good luck with seeing 10 knock count under load on a boosted 6G7x. That won't last very long, any which way.

edit: and I remember more clearly now. MAF input is capped on the ECU side because I tried feeding it higher airflow values via my e-MU speed density setup, and it would not register anything higher than 1150 Hz. Made tuning for 23 PSI of boost a real bitch...

[Dragon34x]

Originally Posted by WarmAndSCSI

There's no way to prove that you logged the correct data item via the right address...

Trust me, I'm not wrong about the MAF cap, at least for a model year 2001 V6 Eclipse/Galant.

You will find that once you're making any significant power or torque whatsoever, that the stock MAF just won't work any more.

Making around 700 lb-ft at the crank, I would have been registering at least ~300% load. That is something I guarantee the stock MAF will not let you register. That's the equivalent of about 1600 Hz @ 4500 RPM. Not gonna happen.

Read what I said one more time... I should have more specifically stated the stock ROM cannot register above 100% load, but what I said about the MAF limit holds true. You're going to have to figure that one out for yourself. All of what I said above of course only applies to a proper suck-through MAF setup... Things become greatly complicated when you start talking about a (crappy) blow-through setup.

Anyway, good luck with that... and especially good luck with seeing 10 knock count under load on a boosted 6G7x. That won't last very long, any which way.

i've seen 20+ counts of knock and its still holdin up like a champ. That "crappy" blow through setup is what I am using... I have a 05 GT, MAF's should be identical, and yes the MAF's do have a cap limit, that limit is not something that most of us will ever reach (you may be the exception). Thats all i'll say for now, like i said before, you'll have your proof soon

[WarmAndSCSI]

Originally Posted by Dragon34x

i've seen 20+ counts of knock and its still holdin up like a champ. That "crappy" blow through setup is what I am using... I have a 05 GT, MAF's should be identical, and yes the MAF's do have a cap limit, that limit is not something that most of us will ever reach (you may be the exception). Thats all i'll say for now, like i said before, you'll have your proof soon

I've seen that MAF cap get reached on an N/A 6G74 before... you'll see it with 3 psi on a suck-through setup.

And any blow-through setup on a Karman vortex MAF is just ridiculous. You'll soon discover that if you ever run more than a few PSI of boost... think of how you're 1.) pressurizing the plastic housing itself 2.) pressurizing the barometric pressure sensor (which has a reading limit within the ECU of a few hundred ft below sea level IIRC), and 3.) registering airflow of pressurized air (meaning the airflow reading will always be lower than the actual mass airflow into the engine, meaning inaccurate tuning). I'm not calling you dumb, I'm calling your blow-through MAF setup dumb.

[Silvertune]

If the MAF is capping at 3psi, then how are people tuning cars with much more boost then that?

Wouldn't using a GM MAF help with our fuelling issues and with this MAF cap?

[silverside]

Originally Posted by Silvertune

If the MAF is capping at 3psi, then how are people tuning cars with much more boost then that?

Wouldn't using a GM MAF help with our fuelling issues and with this MAF cap?

with piggybacks and standalone systems like i said you need to do some reading

[WarmAndSCSI]

Originally Posted by Silvertune

If the MAF is capping at 3psi, then how are people tuning cars with much more boost then that?

Wouldn't using a GM MAF help with our fuelling issues and with this MAF cap?

Piggyback ECU's, standalones, more fuel pressure etc... like said above. In a suck-through setup on a 6G74, you would definitely be ECU-airflow capped by 3 psi. That is unless that airflow limit doesn't exist on newer V6 ECU's. It's been there on both a 2000 and 2001 ECU I have worked with.

And no on the GM MAF, the ECU still doesn't recognize above a certain airflow input (unless these ROM modifications have fixed that - but that would be something new since that limit doesn't exist in Evo land). A GM MAF could, however, be used in a blow-through setup with more success than with the stock MAF. Still, the fueling wouldn't be correct for the actual mass air flow @ atmospheric pressure through the engine.

[SPD_FRK]

The way you tuned was in the past and we are trying to move onto something much better. Though you mention very legit items to take into consideration, one would have to consider the alternative of an MAF from the 3000 GT platform if necessary.

We also need to wonder how the MAF is able to be used within the piggyback setup fine, but apparently as you state it is "capped" at roughly 1150hz. If this is true, we also need to consider how the 4cyl platforms are running the stock MAF sensor (Ivory8g I know is) on a boosted setup. Even those here in the Eclipse community who have flashed the Evo's ROM to their Eclipse ECU are I assume still running the stock Eclipse MAF. I know there is a member here in Colorado who is running that combination atleast...


Maybe I am just going in a circle on this issue, but to me something just doesn't add up.

[WarmAndSCSI]

Originally Posted by SPD_FRK

The way you tuned was in the past and we are trying to move onto something much better. Though you mention very legit items to take into consideration, one would have to consider the alternative of an MAF from the 3000 GT platform if necessary.

We also need to wonder how the MAF is able to be used within the piggyback setup fine, but apparently as you state it is "capped" at roughly 1150hz. If this is true, we also need to consider how the 4cyl platforms are running the stock MAF sensor (Ivory8g I know is) on a boosted setup. Even those here in the Eclipse community who have flashed the Evo's ROM to their Eclipse ECU are I assume still running the stock Eclipse MAF. I know there is a member here in Colorado who is running that combination atleast...


Maybe I am just going in a circle on this issue, but to me something just doesn't add up.

I'm going to hold by the fact that a properly-tuned e-Manage Ultimate + a little EcuFlash magic is the best way to make power on this platform without going full standalone (i.e. if you live in a CARB-like state like me). And by power, I mean anything more than 320-350 WHP.

You will find more and more limitations with the stock ECU each time you try to up the ante. Mark my words...

And it's not the MAF that is limited, it's the input into the ECU. The ECU doesn't interpret anything greater than the value I mentioned. Our MAF is identical to the 4 cyl MAF IIRC, and very similar to the Evo one, if not identical electronically. I've seen 4 cyl logs before, and it doesn't seem like they have this cap at the ECU end.

People are using MAF setups using piggybacks just fine because they allow you to add injector pulsewidth directly when setup accordingly. In fact, you can add duty cycle/pulsewidth relative to boost pressure, or MAF Hz if you so desire. The problem arises where you end up needing higher ECU-side load cells when you have large enough injectors that you cannot increase the IDC any more (+IDC is maxed at +100%) because of re-scaling on the ECU side. This is where I was stuck at, and needing a different solution so I could keep a consistent tune without over-richening the ECU fuel maps when I ended up going with larger injectors.

Until somebody pushes the envelope a little bit (making at least 400 WHP) I won't be convinced that your ROM hacks actually work. It happens all the time in the Evo world... hell, I threw a rod through the side of my 4B11T because somebody had mis-mapped a boost control table in the EcuFlash ROM definition, causing me to run 40+ psi of boost in the mid-range. These kind of ROM changes aren't "working" in my book until somebody tests them under every condition - and a mild boost setup is far from testing anything to the limits as far as I'm concerned. Even Tephra over on EvoM asks for lots of user feedback on each ROM modification he releases. And guess what... the modifications are not spot-on all the time.

This is great if you figured it out, but all you're going to be able to prove is it works for a setup that is only pushing ~160% load (which is much at all) on a blow-through setup. I want to see it working for 250%+ load on a suck-through setup before I'm convinced, because that's what a stock Evo ECU is able to do.

[SPD_FRK]

Originally Posted by WarmAndSCSI

I'm going to hold by the fact that a properly-tuned e-Manage Ultimate + a little EcuFlash magic is the best way to make power on this platform without going full standalone (i.e. if you live in a CARB-like state like me). And by power, I mean anything more than 320-350 WHP.

You will find more and more limitations with the stock ECU each time you try to up the ante. Mark my words...

The only limitation we found so far was not having the big maps, or getting it to read above 100%, which we have done so far...and this project is still in its early stages like all others before it.

Originally Posted by WarmAndSCSI

And it's not the MAF that is limited, it's the input into the ECU. The ECU doesn't interpret anything greater than the value I mentioned. Our MAF is identical to the 4 cyl MAF IIRC, and very similar to the Evo one, if not identical electronically. I've seen 4 cyl logs before, and it doesn't seem like they have this cap at the ECU end.

So then really all that needs to be sorted out is the input to the ECU. I mean if I understand this correctly, then the MAF itself isn't capped, just the ROM information for the stock ECU likely is then.

Originally Posted by WarmAndSCSI

People are using MAF setups using piggybacks just fine because they allow you to add injector pulsewidth directly when setup accordingly. In fact, you can add duty cycle/pulsewidth relative to boost pressure, or MAF Hz if you so desire. The problem arises where you end up needing higher ECU-side load cells when you have large enough injectors that you cannot increase the IDC any more (+IDC is maxed at +100%) because of re-scaling on the ECU side. This is where I was stuck at, and needing a different solution so I could keep a consistent tune without over-richening the ECU fuel maps.

This may be something else to add to the flash then if possible, that will have to be addressed to the developer on this project.

Originally Posted by WarmAndSCSI

Until somebody pushes the envelope a little bit (making at least 400 WHP) I won't be convinced that your ROM hacks actually work. It happens all the time in the Evo world... hell, I threw a rod through the side of my 4B11T because somebody had mis-mapped a boost control table in the EcuFlash ROM definition, causing me to run 40+ psi of boost in the mid-range. These kind of ROM changes aren't "working" in my book until somebody tests them under every condition - and a mild boost setup is far from testing anything to the limits as far as I'm concerned.

Not many have pushed the power levels to the extent you have, yet. This entire project had to start from somewhere and get things rolling on this flash. Look back a couple years on the 6g74 swaps even, everything started form something and progressed to where they are at today. A lot of people are interested in this flash, and obviously a lot of your fellow Evo owners seem pretty happy with the capabilities of the EcuFlash method of tuning.

If a rod was thrown due to mis-mapping, then the tune and tuner is at fault, the same thing could just as easily have happened to anybody running anything else for tuning. Anybody who did the same thing on the Evo Flashed ECU in the Eclipse or Galant could have easily done the same thing...just part of tuning.

[mysticj]

If the load calculations from the Evo rom and 6g7x rom are the same, then airflow cap(Hz) or air mass input from both roms need to be compare.

[WarmAndSCSI]

My point was, that one should not assume ECU modifications are working until they are actually tested in every scenario. In my case, a mistake was made in mapping out a ROM by one or more individuals for the use of an entire community. It wasn't a value that the tuner (me) specified, it was an XML definition mapping mistake made by a developer. If it hasn't been tested, it absolutely doesn't work... thanks to almost 5 years of enterprise software development for teaching me that.

I don't know if you have experience tuning Evo's, but 160% load is very, very low in terms of load. I really think this has to be shown working for 250%+ load before we call this a viable tuning option.

Also, a big part of Evo tuning is actually having the Fuel map target AFR's being relatively close to actual AFR. Get that working by being able to tweak MAF scaling to represent the actual VE of the engine, then you've got something going (RPM-relative tuning of scaling, not just the universal MAF scaling). Otherwise, the stock ECU still will not be close to being as capable as a good piggyback.

I'd shoot to get these things working:

1.) Fuel and ignition tables working for up to 340% load
2.) MAF Hz recognition of 1600+ Hz (as would be required by the above)
3.) Getting around any potential timing retard limits (the Evo X has these for the MR model, the auto V6 might have these as well)
4.) 2-byte logging of load
5.) MAP support so people can log boost, and the ECU can potentially use the MAP like the JDM Evo IX and Evo X do.
6.) ECU boost control! As nice as the Evo X's would be great... (this would put it above any piggyback and put it in AEM EMS territory)
7.) load limits for over-boost (wastegate malfunction) protection

Get all of that, and the stock ECU will become on par with an Evo for EcuFlash-tuning. Another thing to consider is possibly utilizing a hot-wire MAF like included with the newer Eclipses, Galants, and Evo X. Such a MAF could actually be used in a blow-through setup with reliability.

[SPD_FRK]

Originally Posted by WarmAndSCSI

My point was, that one should not assume ECU modifications are working until they are actually tested in every scenario. If it hasn't been tested, it absolutely doesn't work... thanks to almost 5 years of enterprise software development to teach me that.

I don't know if you have experience tuning Evo's, but 160% load is very, very low in terms of load. I really think this has to be shown working for 250%+ load before we call this a viable tuning option.

That is why I wanted to get this ball rolling, we still have a ways to go to do all of this testing. The key focus right now has been on getting the ECULoad above 100% which we have done so far. I know 160% is very low, but this is a positive step in the right direction for the development here honestly, nobody can deny that fact.

Originally Posted by WarmAndSCSI

Also, a big part of Evo tuning is actually having the Fuel map target AFR's being relatively close to actual AFR. Get that working by being able to tweak MAF scaling to represent the actual VE of the engine, then you've got something going (RPM-relative tuning of scaling, not just the universal MAF scaling). Otherwise, the stock ECU still will not be close to being as capable as a good piggyback.

This is something that we do have to monitor and look at to be sure of as well. The MAF scaling stuff is additional things that need to be sorted out as this flash develops more.

Originally Posted by WarmAndSCSI

I'd shoot to get these things working:

1.) Fuel and ignition tables working for up to 340% load
2.) MAF Hz recognition of 1600+ Hz (as would be required by the above)
3.) Getting around any potential timing retard limits (the Evo X has these for the MR model, the auto V6 might have these as well)
4.) 2-byte logging of load
5.) MAP support so people can log boost, and the ECU can potentially use the MAP like the JDM Evo IX and Evo X do.
6.) ECU boost control! As nice as the Evo X's would be great... (this would put it above any piggyback and put it in AEM EMS territory)
7.) load limits for over-boost (wastegate malfunction) protection

Get all of that, and the stock ECU will become on part with an Evo for EcuFlash-tuning. Another thing to consider is possibly utilizing a hot-wire MAF like included with the newer Eclipses, Galants, and Evo X. Such a MAF could actually be used in a blow-through setup with reliability.

We already have the 2byte load logging done with the current version, the fuel and ignition tables can easily be scaled out to 340-360 depending how you index each column. The timing limits will have to be looked at more I suppose to see if there are any of those limits. The MAP support would be nice to add and is something to push for when the previous items are addressed/confirmed.

If this is a n00b thing to ask, shoot me...im still learning a lot and I appreciate the good discussion going here. The load limits, would that be comparable to the MAF or Load Clipping feature? We do have the MAF clipping in this flash if that matters?

[WarmAndSCSI]

Originally Posted by SPD_FRK

We already have the 2byte load logging done with the current version, the fuel and ignition tables can easily be scaled out to 340-360 depending how you index each column. The timing limits will have to be looked at more I suppose to see if there are any of those limits. The MAP support would be nice to add and is something to push for when the previous items are addressed/confirmed.

Right, but actually testing each and every one of those load cells will be the key. This is uncharted territory, unlike with the Evo, where the ROM is setup this way from the factory.

Originally Posted by SPD_FRK

If this is a n00b thing to ask, shoot me...im still learning a lot and I appreciate the good discussion going here. The load limits, would that be comparable to the MAF or Load Clipping feature? We do have the MAF clipping in this flash if that matters?

I'm speaking of a safety feature. For the Evo VIII-IX, exceeding the load/boost limit causes a wastegate cut. For the Evo X, it also can cause a hard throttle cut in addition since it has electronic throttle control. It's simply an RPM vs. Load % table.

I'd love to test this all myself... and my car would have been the perfect way to exercise the upper limits of these modifications, but it's down and being parted out. I don't suspect I'll be returning to working on the 6G7x platform any time soon. It's such a money pit... The stuff is even more expensive and fickle than on a brand new Evo! Crazy... for something that isn't even AWD or inherently performant

This will be a perfect solution for a mildy-boosted setup, but it will take a lot of work to get it suitable for anything wild & crazy...

[SPD_FRK]

Originally Posted by WarmAndSCSI

I'm speaking of a safety feature. For the Evo VIII-IX, exceeding the load/boost limit causes a wastegate cut. For the Evo X, it also can cause a hard throttle cut in addition since it has electronic throttle control. It's simply an RPM vs. Load % table.

I'd love to test this all myself... and my car would have been the perfect way to exercise the upper limits of these modifications, but it's down and being parted out. I don't suspect I'll be returning to working on the 6G7x platform any time soon. It's such a money pit... The stuff is even more expensive and fickle than on a brand new Evo! Crazy... for something that isn't even AWD or inherently performant

This will be a perfect solution for a mildy-boosted setup, but it will take a lot of work to get it suitable for anything wild & crazy...

I will have to do some more reading on the load/boost limit stuff I guess. I understand what you are trying to explain, but I am eager to learn more about that as it is a very good "safety net" for high hp platforms using this.

I would have suggested you for testing, but well we both know how the Galant shit blew up in the last few months

The main reason I am trying to work on this as much as I can is because I am going to be tuning my setup via this flash...and it won't be "mild." This car stuff in general is a money pit...I can't play with the Lancer, or the new vehicle when we get one...so why not on the $500 Galant lol

[PharmEcis]

You need to give this ROM to Repforenzo and let him test it on his 10 psi draw through SDS setup. That should give us loads over 220% at least.

[tdevriesgb]

This is all great. This is a huge step for this platform. I am all for it. Even with everyones negativity here, if you step back and look at the big picture here you will all see how much information is being relayed here. Now as long as it gets relayed to the developer or he has a chance to read this info is the key. Now I know all of you are very busy, but is there anyone that can help me with my xml definition? Also does anyone have tuned defintion that they could share with me. I would like to compare my tune with others. I have found factory tunes to vary alot on my 2g stratus. example 01 r/t maps are way different from an 02 se maps, yet I found the se seem to be quicker from the start. Granted I don't have access to a dyno to say for sure.

[SPD_FRK]

Originally Posted by PharmEcis

You need to give this ROM to Repforenzo and let him test it on his 10 psi draw through SDS setup. That should give us loads over 220% at least.

That will be the next one who tests the 03-05 Flash honestly. I have to wait for another revision to be made from Acamus.

[SPD_FRK]

Original post has been updated, ROM features listed, and the patch has been put into a zipped folder as an attachment for downloading by everybody. Please do not hesitate to donate to Acamus via the link posted as well. Anything is greatly appreciated and goes directly to Acamus for his work and continued support/development on this patch

[silverside]

I am in the process editing my 02 rom to accept the new tables. I will let yall know if i get it to work.

[SPD_FRK]

Originally Posted by silverside

I am in the process editing my 02 rom to accept the new tables. I will let yall know if i get it to work.

Keep in mind the only one we have done still is of the 05 ECU, not sure if that will work for the 01-02 or not?

[silverside]

Originally Posted by SPD_FRK

Keep in mind the only one we have done still is of the 05 ECU, not sure if that will work for the 01-02 or not?

right but now that i have an example to decode i can apply the same principals to my 02 rom and make it work. just like i have with the other features i have added to my ecu. im not as dumb as many of yall make me out to be ya know

[PharmEcis]

You are one of the few smart ones around here Silverside...

If you have the original 05 ROM, it's easy to do a hex compare to see what addresses have been changed. Then you can translate those addresses over to the 01-02 ROM.

Technically, if you delete the immobilizer, you should be able to run the 05 ROM on any 3G V6 flashable ECU. It will just pop codes for the missing equipment.

[Dragon34x]

Originally Posted by PharmEcis

You are one of the few smart ones around here Silverside...

If you have the original 05 ROM, it's easy to do a hex compare to see what addresses have been changed. Then you can translate those addresses over to the 01-02 ROM.

Technically, if you delete the immobilizer, you should be able to run the 05 ROM on any 3G V6 flashable ECU. It will just pop codes for the missing equipment.

cuz i'm nice....

[acamus]

Originally Posted by silverside

right but now that i have an example to decode i can apply the same principals to my 02 rom and make it work. just like i have with the other features i have added to my ecu. im not as dumb as many of yall make me out to be ya know

Do not port the code to other ROM yet, there are two more things to be added/corrected.

[silverside]

Originally Posted by PharmEcis

You are one of the few smart ones around here Silverside...

If you have the original 05 ROM, it's easy to do a hex compare to see what addresses have been changed. Then you can translate those addresses over to the 01-02 ROM.

Technically, if you delete the immobilizer, you should be able to run the 05 ROM on any 3G V6 flashable ECU. It will just pop codes for the missing equipment.

that says a lot comming from you. and the side by side comparison is my trick darn now the world knows.

I prefer to keep the rom im using and just edit it anyway. gives me a better understanding of how everything works

Originally Posted by acamus

Do not port the code to other ROM yet, there are two more things to be added/corrected.

keep us posted

[SPD_FRK]

Picked up an 03 GTS M/T ECU at the junkyard this morning (along with the 5pd trans stuff).

Acamus thanks for keeping in contact with us all here.

[silverside]

Got a copy of IDA pro adv. Wow that makes this easier. found my mut table. workin on the 2byte logging

[tdevriesgb]

I am very interested in this but for my 02 dodgibushi Stratus with an automatic. I don't have the knowledge to rewrite a rom like you do and would be happy to donate to your cause if you get one i can use.

Acamus, have you been adding into your rom an immobilizer delete to make it more universal?

[acamus]

Originally Posted by silverside

that says a lot comming from you. and the side by side comparison is my trick darn now the world knows.

I prefer to keep the rom im using and just edit it anyway. gives me a better understanding of how everything works


keep us posted

I have corrected 1 byte logging, no response from testers yet, if you can PM your email addy, I can send it to you as well

[acamus]

Originally Posted by tdevriesgb

I am very interested in this but for my 02 dodgibushi Stratus with an automatic. I don't have the knowledge to rewrite a rom like you do and would be happy to donate to your cause if you get one i can use.

Acamus, have you been adding into your rom an immobilizer delete to make it more universal?

Tyson, I could do the porting to Stratus, but last time I have done the definition file for you, you have not been happy to donate, so I have suspicion that it will not be a good deal.

If you search around you will find how to disable immobilizer.

[repforenzo]

Originally Posted by PharmEcis

You need to give this ROM to Repforenzo and let him test it on his 10 psi draw through SDS setup. That should give us loads over 220% at least.

I have it, but I can't do much until first week of April.

[silverside]

pm sent. thanks

[espguitarist3]

In the past hour i've learned a ton about this ecuflash platform. i'm comparing an evo ROM and the eclipse ROM. One of the biggest differences i'm wondering about is the MAF filtering although the only variable that is different is the low filter. do we know what exactly is being filtered?

Also the MAF size for the eclipse is 240 g/s and the evo is like 300 g/s If the airflow amount were to calculate load, wouldnt it make sense for the max g/s to be the cap for load? is 240 g/s our 100 percent?

Also if you look at the high octane fuel maps for the evo there are many other options to edit when editing the map as opposed to a GT map

(second edit)
actually it looks like the 05 GT ROM is based on an evo7 not the evo8 that i was comparing with.. the extra options are on the evo7base file

[silverside]

the maf for the gt is 305.6 g/s.there are different mafs for the 2.4l vs 3l

also the load is calculated based on airflow, temp, and running conditions (throttle position, baro, ect...)
This is why i can read 130% load at 100 throttle and 2k or at 70 throttle and 5k
anyone thats knows more please feel free to correct me on this

[espguitarist3]

yes i have the 05 GT rom and it says 240 is the max

I think theres something wrong with this map anyway because the fuel one goes all the way to 0 load and then to 2560 then to 5120, even though it should only go to 100 (or 0 as the tutorial I got the evo rom from says)

I got them from the rom file on the site hoping to tinker around and try to understand things better and learn

[espguitarist3]

yes i have the 05 GT rom and it says 240 is the max

I think theres something wrong with this map anyway because the fuel one goes all the way to 0 load and then to 2560 then to 5120, even though it should only go to 100 (or 0 as the tutorial I got the evo rom from says)

I got them from the rom file on the site hoping to tinker around and try to understand things better and learn

[silverside]

not all of the definitions are correct. i have looked at most of the eclipse ones. you need to find a complete one to play with it will make things a lot easier for ya

which rom are you viewing?

[espguitarist3]

the evo is EVO8 JM9693.hex from another site...and all of the dropdown menu's work

the eclipse is 05_ECLIPSE_GT_MT_94450007.hex
from the thread ECUFlash Definition Files and ROMS
and i put all the files in the same folder, that rom was the first one I could get to work

[silverside]

yeah dude that def file is wacked try a different one. like i said i have almost all of the eclipse files and that one is def messed up.

[espguitarist3]

(replied to your pm)

do you know of a working one on the site?

[silverside]

most of them work fine but that one gives me problems too

this one works 05_ECLIPSE_GTS_AT_86620007.hex

[espguitarist3]

this one has less available maps then the other...and a maf size of 53g/s

[silverside]

you need to download the updated definition files. that one is fine on mine but all my stuff is up to date

[acamus]

Originally Posted by silverside

pm sent. thanks

Mail sent

[Dragon34x]

Originally Posted by acamus

I have corrected 1 byte logging, no response from testers yet, if you can PM your email addy, I can send it to you as well

I haven't gotten any emails

Which reminds me... I dunno if this is a ecu flash thing or not but i thought i'd let ya know about this.... I finally got a chance to throw in a wideband o2 sensor on my setup (during the dyno runs) and noticed that the ecu isn't throwing in the requested amount of fuel in. fuel pressure is fine and the injectors are not maxed out. Think there may be a problem? I got screen shots of what i'm talking about if ya want to see them. Thanks

edit: NVM, i just checked my inbox and found the stuff... I'll test it out shortly and send you the results. thanks

[02meclipsegt]

Congrats on the dyno run Armondo, I wish I could have been there. I'd try the. Vr4 fpr and see if that helps.

[dlm04RT]

Hey SPD_FRK, it looks like the donation page is having issues. It keeps telling me I've entered an invalid amount. Has anyone sucessfully dontated using the link or did you use the send money feature after logging in?





UPDATE: Nevermind . . . it wanted a comma rather than a decimal point. Stupid foreigners!

[tdevriesgb]

Originally Posted by acamus

Tyson, I could do the porting to Stratus, but last time I have done the definition file for you, you have not been happy to donate, so I have suspicion that it will not be a good deal.

If you search around you will find how to disable immobilizer.

At the time, I ended up with some personal and monitary issues. then i lost your email address and didn't know how to get a hold of you. i am sorry for that. if you forward me a paypal address i would be happy to donate. would you be interested in unlocking the rest of my rom? or would this be obtainable through this rom you may build for the 01-02 auto line-up?

[tdevriesgb]

Originally Posted by tdevriesgb

At the time, I ended up with some personal and monitary issues. then i lost your email address and didn't know how to get a hold of you. i am sorry for that. if you forward me a paypal address i would be happy to donate. would you be interested in unlocking the rest of my rom? or would this be obtainable through this rom you may build for the 01-02 auto line-up?

Sent.

[acamus]

Originally Posted by silverside

keep us posted

With the latest correction, EcuLoad shows what it should, the problem was
EcuLoad aka MUT_1C was connected with different scaled variable that had a limit at 100.

If you guys are interested in force inspection pass patch I may do it.

Thank you all who have donated.
It seems you have build the budget for buying OP2.0 cable

[acamus]

Originally Posted by tdevriesgb

Sent.

would you be interested in unlocking the rest of my rom?

Thank you, I will port Big Maps, Knock CEL and load correction to your rom.

I am not quite sure what are you after now, there is a ton of stuff in your ECU even thou you have not downloaded complete ROM (only first 256KB).

I would rather focus on the problem that cannot be tuned by means of available EcuFlash tables.

Please state what you are missing.

If you want to download complete 512kB, please use evo 7 GTA template.

[silverside]

Originally Posted by acamus

With the latest correction, EcuLoad shows what it should, the problem was
EcuLoad aka MUT_1C was connected with different scaled variable that had a limit at 100.

If you guys are interested in force inspection pass patch I may do it.

Thank you all who have donated.
It seems you have build the budget for buying OP2.0 cable

im interested i was reading that thread last night

I have something else i want to talk to you about too but i want to get you some more cash first