PS ... and if we are starting to run out of available MUT locations then it might just *require* us to have 2 or more "standards" for the most common type of patches. Nice thing about Tephra mods, as you know better than me, is that his 2->1 byte opens up MUT. Seems like it might be a worthwile patch to ask from him to 1) do the other 2-bytes the same way and 2) offer a 2->1byte only patch for those of us who haven't decided to go as far as doing the full Tephra path. Sure it is mostly because I'm lazy, but I'm still tuning the basics before I mess around with anything else.

 

This is Semi-OT but also on-topic of our MUTness
Ok, I just looked back to my oldest tune (I don't have the stock copy of my rom, this is an AMS base flash) and I notice that my only differences to my current v5.10 MUTs are 41 (load 1 byte)
MUT40 (went from 608f to 8417)
MUT3C (Went from 6AE9 to 8409)

I know they aren't part of the JDM MAP/direct boost control... anyone got any good ideas what these were for?


EDIT: nevermind, I looked at the 5.8 thread and saw:

I should add these to the defs

 

There is no real reason to offer a map without the tephra patch. Aside from the fact that is the most common patch, every feature can be disabled. Just install the patch and use or dont use what you want.

 

Yeah, I'm definitely in agreement with that one.

 

For the 04 USDM roms you are showing 94170015, however I have seen a few 04's that use 96420008 and we could not change the ROM ID to 94170015. Or am I missing something in my reading.

 

Perhaps, but I'm not installing it until I plan on using something from it, and 2->1byte load isn't enough I like to reduce all variables that I am not using and the last thing I need is to fight some oddball issue only to find out it was from a bug in a patch that I'm not using.

If you do plan on only offereing patched ROMs (I assume you mean ROM since I don't know what you mean by Map in this context) then it should come with all those features disabled by default if it doesn't already.

That being said, it looks like right now there are enough empty MUT addresses to not have to worry about running out. So as far as EcuFlash / EVOScan definitions are concerned, there is no reason not to include every single definition / request since the worst that happens is they aren't used.

 

These are my proposed MUT locations (some already changed in V5.10, but no accompanying XML defines them properly)

08 - O2 Simulated 6AE9 (the value your ECU sees from the O2 sim patch included in v5.10, this would normally be stock location)
09 - Clutch Switch 6A35

18 - Alt map voltage 8425 (voltage in bytes that your ECU sees on the alt-map input pin)
19 - Alt map Activation 8929 (0 deactived - 3 for activated)

38 - Averaged MAP 6AED - JDM also (the value your ecu sees if using v5.10, this would normally be stock location)
40 - Non-Averaged MAP 8417 - JDM also (actual current MAP value)
41 - Load 1 Byte 840B
3c - real O2 8409 (actual current rear O2 value)

That short list leaves these and many more for other logging:

20, 22, 23, 25, 31, 33-37, 39

I'd like MrFred, Tephra, or Evo4Mad to review these if possible just in case I'm digging into something that might be useful elsewhere/later.

 

I have a question...I might just be confused but what exactly is 02 sim.

In fact do you mind expanding slightly on what each of those paramaters are, aside from clutch switch, alt map, and 1byte load.

 

edited

 

 

lol ^^^

fosty - see the other thread about 8425/29

personally if everyone is happy with 1byte load, we can dump 2byte load ie MUT00,01.

Also I reckon logging 2byte RPM is a waste, so we can use 00,01,02,03 for some of these... I prefer not to overwrite the other ID's... just in case

 

Yup, OK, changing MUT83 to be the voltage (since it is).

(Tephra is referring to this post: https://www.evolutionm.net/forums/sh...&postcount=940 )


FYI if anybody didn't catch it (I wasn't clear)... some of those listed don't actually require changing the MUT value, its just changing the wording or location in the evoscan defs. I'll re-organize and get crackin' in the morning.

 

I updated my tuning tutorial on the Wiki ... I'll try to finish it soon.

Also, I noticed an error but couldn't figure out how to edit the page. the list of current ROMs has VIII and IX listed backward ... 88590015 is under "8" and the rest are under "9." I tried to fix but couldn't ... I'm still new to the while Wiki thing.

 

I agree - 2 byte RPM is not needed. And I am happy with using only 1byte load.
This will free up 2 more MUT's

 

If you are referring to the catagory page
http://evoecu.logic.net/wiki/Category:ROMs

Then I believe this is how wikimedia organizes pages. THe 8 & 9 do not refer to evo 8 and 9 but rather the first number of the file. In the actuall download page here the roms are organized correctly. The catagory page is not for informing users, it is more just to see what files exist.