The more power you make the more you will need the bigger maps. I see you are on the stock turbo still. Once you go larger and start really hitting higher load's the big maps will be invaluable to you.

 

I'm with the OP on this one. BIG MAPs are way too big. In fact, the OEM maps are too big. We really only have need for a two cell map. Think about it. The engine is either in idle/cruze or under boost. Period. One cell for idle/cruze and one cell for under boost. Tuning would be so easy even a caveman could do it.

 

I think we should get rid of those maps all together. It is far more efficient to have the fuel pass through a reservoir that regulates the fuel flow through a one way valve that can sort of precisely measure the fuel as it enters the main air stream into the intake.

As you know, gravity sucks and it can also be used to regulate the specific gravity of hte fuel being burned...

 

^^ umm how do we then workout air flow

sorry it almost feels like every1 is again the OP, but i rotfl cuz a lot of people wanted to goto the big maps and now to go back would be silly.... plus as said before just use the same scaling as stock that way its as easy as before

 

I think everyone's getting on the OP's back about this, without considering that he may not have realized you could simply use the stock scalings if you want smaller maps.

(It's not unreasonable to want less per-RPM resolution in cases where you're taking advantage of the 1/3-degree increments that the ECU can use under the hood when interpolating between RPM points, since you can't directly specify "11.3 degrees at 5000 RPM". It turns out that less per-RPM resolution results in increased timing resolution, if you're very careful about it. I'm less inclined to play tricks like that, though, because you can go crazy chasing your tail.)

 

Related Question: From my understanding... the Evo8 ECU is quite small in memory size. It is my understanding that to make room for the larger cell count maps (big maps) that areas in the rom that were blank (just a few) and areas that were viewed as redundant were rewrote to accomodate the big maps.

Could tephra or one of the other tephra eggheads chime in on this? NOT a flame, I am AMAZED at the options and quality of what v7 can do, and what the evo community (true open source huh?) have done with the mod. I am curious however how the 8 ECU being as small in available memory as it is.. can run the big maps correctly, without effecting SOME drivability or other ecu issues.

Thanks!

 

Is anyone else having problems with the big map converter in excel? Works fine for timing map, but with the smaller fuel map I can't get it to come out right...I'm sure it's just me doing something wrong...Sorry about the OT..

 

So theres a consensus... Big Maps FTW!!!

Mods... can u please lock, lol.

 

My opinion still sticks, that for 95% of the guys using it, it just looks pretty.

If going for a pump gas on kill mode, I'll use the V7 for the additional resolution in timing, but most people I've seen using them are not taking any advantage of the extra resolution.

I've never had any problem smoothly ramping my timing (degree by degree) to my liking with the standard map definition. Thats for stock turbo cars all the way to T3's and Red's pushing over 380load.

 

Good question!

There's two kinds of memory in the ECU, and a question like this really needs to differentiate between the two. There's the ROM space (which can only be changed by reflashing; this is what you edit with EcuFlash), and there's RAM (which is used by the ECU for temporary storage while the car is running). Think of it as the difference between a DVD and a hard drive or RAM in your computer. We're pretty limited on both resources, but "running out" means different things for each.

The maps typically all live in ROM. The practical effect of this is that as long as you can find a contiguous chunk of space for the new thing you want to add, go to town; it won't have any affect on anything else. If you have to move something to accommodate it, you simply have to fix up any references to it. 96530006 had a TON of free space in it (relative to other VIII ROMs, anyway), so finding room for the new "big maps" wasn't a big deal.

RAM is a different matter; there's at least one item in RAM (the stack) that grows without bound, so you have to be careful to leave it enough space. (Almost all other uses of RAM are "static"; ie. you know ahead of time whether a particular address is in use.) jcsbanks did some great investigation early on to determine how much room we had to allow for the stack, which has given us some rules-of-thumb for how much we can add without the stack interfering with our additions.

The only real new RAM consumer, aside from some very minor memory use in tephra's new code, is the live map/DMA stuff. Originally, it turned out that there was enough room for the live maps, along with a bunch of additional stuff (RAM MUT table, etc); with the big maps, there was significantly less available space, but careful consideration of what got moved into RAM made everything fit, while still leaving all the headroom that jcsbanks worked out.

Now, tephra's code has a significant impact on how the car runs (fueling, launch control, etc), but that was sort of the point.

tl;dr: None of this stuff actually affects how the car operates, except for the parts where we want it to.

This all applies to the VIII ECUs; the IXs have significantly more room (both ROM and RAM), although the addition of the MIVEC maps and code probably had something to do with that.

 

Logic, thanks for the directed reply... I was fearing it would get lost in the black hole that is some of the evoM population.

As a previous computer tech, I understand the rom/ram setup, I just didn't know how the tephra mod was utilized across both spaces.

To get to a personal level... I should in essence be able to take my VIII rom, copy over all tables in it to the v7, (resized where necessary obviously) flash it to the ecu, and have in essence the same driving experience? Aside from allowing alternate maps, valet, etc etc etc. (

Most Basic Concern: v7 has tons of great features, just ensuring I am not sacrificing ANY oem safegaurds, or drivability on the VIII ECU to have the ability of the new features from tephra & co.

Again, Logic... thank you for the spot on reply.

 

1:24am when you posted.. lets just hope you were really tired

 

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.

 

I think it depends on the setup. I only use v7 bigmaps on customers that ask for it. or if its a car that i feel needs the big maps. If you are stock turbo making 3-400 hp, i think the small maps are fine. But try tuning 7-8-900 horspower cars on small maps...

 

The only tuner I would consider paying $$ for (i.e. credible) in the area said the same thing regarding the big maps. Thanks