View Poll Results: Should the size of big maps be reduced?
Yes
12
15.79%
No
64
84.21%
Voters: 76. You may not vote on this poll
Big maps-too big
That's the goal: switch and go.
The reality is a little more complicated, and hence why the tephramod threads are so long.
96530006, for example, is a substantially different code tree than what originally shipped on your car (it's originally from a Euro/Aus-market 2005 Evo). A good example of something people almost inevitably end up doing is correcting a badly-adjusted BISS screw; the stock code does a great job of masking over a mis-adjusted BISS, but 96530006 will throw a code if you're not at least in the ballpark. There's a couple of other little items that will cause a few issues, and most of them are pretty well-documented at this point, but it's not as straightforward as I think everyone would prefer.
Since a 9417-based tephra version is available at this point, that's probably the closest ROM to what you're currently running, and should provide the least amount of conversion hiccups. You need to make sure you follow the instructions (copy your immobilizer, etc), but overall it should be pretty painless.
The reality is a little more complicated, and hence why the tephramod threads are so long.
96530006, for example, is a substantially different code tree than what originally shipped on your car (it's originally from a Euro/Aus-market 2005 Evo). A good example of something people almost inevitably end up doing is correcting a badly-adjusted BISS screw; the stock code does a great job of masking over a mis-adjusted BISS, but 96530006 will throw a code if you're not at least in the ballpark. There's a couple of other little items that will cause a few issues, and most of them are pretty well-documented at this point, but it's not as straightforward as I think everyone would prefer.Since a 9417-based tephra version is available at this point, that's probably the closest ROM to what you're currently running, and should provide the least amount of conversion hiccups. You need to make sure you follow the instructions (copy your immobilizer, etc), but overall it should be pretty painless.
Does that question/concern make sense? or am I thinking about this wrong. Thanks again Logic.
In that paragraph, I was specifically referring to switching to 96530006. Right now, you're running code written for a USDM 2004 Evo (probably some version of 9417?). 96530006 was originally deployed on a Euro/Aus 2005 Evo. Different year, and different domestic market. The maps that you're copying aren't the whole story; there are code (and, in some cases, hardware) differences that can require a bit of tuning to work around.
The BISS issue, in particular, is one that bites everyone, which is why I mentioned it. The USDM code hides the fact that there's a physical misconfiguration, just like your car can seem to run perfectly well with throttle body shaft seals that can't hold more than a few psi without leaking. The Euro code doesn't attempt to work around the problem (at least, not much; the car is still quite drivable), it instead throws a code and expects you to go get a screwdriver.
The difference, most likely, can be found in the thousands of pages of US emissions and market requirements.
The differences aren't because of tephra's code; you'll have the same problems if you tried switching to a stock/untouched version of 9653.
Now, all that being said: there's a new(er) release from tephra that's based on 94170015 that Evo_Kid/Shameless petitioned him to create. I haven't personally used it, but the idea there ought to be that it's a drop-in replacement for you, because it should be the exact same code base that you were running before, with some additions. There's a thread for people using that as well, which might be a good place to look for common issues that folks run into.
The BISS issue, in particular, is one that bites everyone, which is why I mentioned it. The USDM code hides the fact that there's a physical misconfiguration, just like your car can seem to run perfectly well with throttle body shaft seals that can't hold more than a few psi without leaking. The Euro code doesn't attempt to work around the problem (at least, not much; the car is still quite drivable), it instead throws a code and expects you to go get a screwdriver.
The difference, most likely, can be found in the thousands of pages of US emissions and market requirements.
The differences aren't because of tephra's code; you'll have the same problems if you tried switching to a stock/untouched version of 9653.Now, all that being said: there's a new(er) release from tephra that's based on 94170015 that Evo_Kid/Shameless petitioned him to create. I haven't personally used it, but the idea there ought to be that it's a drop-in replacement for you, because it should be the exact same code base that you were running before, with some additions. There's a thread for people using that as well, which might be a good place to look for common issues that folks run into.
understood.. I don't recall my rom version at the moment.. tonight after some datalogging, I'll be sure to check.. and share.. I keep thinking it was one that wasn't listed alot... either 946xx or 964xxx.. I will definitely stay in touch with you. Thanks again.
My only issue with the big maps is the small resolution on my netbook that I use for logging. So I have to carry two laptops when tuning. One for logging, one with a screen resolution large enough to view the map...
ya the big maps suck to edit on laptops and especially netbooks.
I don't even think about it, turn the key on, car cranks, evoscan starts logging. Turn key off, evoscan stops logging, script emails me the logs (3g connection), then car turns off.
That's why I have a carputer that logs 100% of my car's run time...and now I'm scripting it to email me the logs as soon as I turn the key off but before the computer goes to standby.
I don't even think about it, turn the key on, car cranks, evoscan starts logging. Turn key off, evoscan stops logging, script emails me the logs (3g connection), then car turns off.
I don't even think about it, turn the key on, car cranks, evoscan starts logging. Turn key off, evoscan stops logging, script emails me the logs (3g connection), then car turns off.
That's why I have a carputer that logs 100% of my car's run time...and now I'm scripting it to email me the logs as soon as I turn the key off but before the computer goes to standby.
I don't even think about it, turn the key on, car cranks, evoscan starts logging. Turn key off, evoscan stops logging, script emails me the logs (3g connection), then car turns off.
I don't even think about it, turn the key on, car cranks, evoscan starts logging. Turn key off, evoscan stops logging, script emails me the logs (3g connection), then car turns off.
Interesting...
1) You don't need to use all the resolution... Just rescale the axis how you want it, then make the rest of the numbers huge:
2) I can't remember what my second point was...
edit - I remember...
2) I have asked Colby to add scrollbars into EcuFlash, he is going to check it out... This was for the MAF_Scaling table on the EvoX (150 odd rows long) - but will assist you netbook guys as well
1) You don't need to use all the resolution... Just rescale the axis how you want it, then make the rest of the numbers huge:
2) I can't remember what my second point was...
edit - I remember...
2) I have asked Colby to add scrollbars into EcuFlash, he is going to check it out... This was for the MAF_Scaling table on the EvoX (150 odd rows long) - but will assist you netbook guys as well
I understand there was ways to go around how big the maps are.
But in my opinion the resolution is really overkill. If you look at most big maps the values are the same in most of the cells.
However the masses have spoken so it doesn't really matter. But I still say they are still a pain to deal with unless your working with a 22" monitor or your running a big screen resolution. If you can get scroll bars put into ECUflash that would solve half the problem. I'm not sure why people got as bent out of shape over the thread though.
But in my opinion the resolution is really overkill. If you look at most big maps the values are the same in most of the cells.
However the masses have spoken so it doesn't really matter. But I still say they are still a pain to deal with unless your working with a 22" monitor or your running a big screen resolution. If you can get scroll bars put into ECUflash that would solve half the problem. I'm not sure why people got as bent out of shape over the thread though.