I will look around and try to dig up the info on the clutch switch position.

For now why dont we make a list of standard MUT requests and what we want to assign each to...at least for the purpose of the maps on the wiki.

MUT00 - ??
MUT01 - ??
etc...

 

here ya go....variable for the clutch switch. we should definilty include this as a loggable item in the evoscan file

https://www.evolutionm.net/forums/sh...&postcount=213

 

Ok, I've got an evoscan file going with the alt-map stuff at the bottom just for giggles (matching the instructions I have up)
I added boost error and 1byte load... everything else from the mods is already in there.

What is the def for clutch?
..anything else I should add?
Are we sure that the multiple CU type tables will not break earlier versions of evoscan?

edit: I think adding stuff that is not a standard MUT is OK as long as it doesn't replace something else that is already a standard. I didn't realize the clutch switch position was like that. I think things like that would be better added to the wiki for people to do on their own than included in the rom file. I (personally) think that keeping included modifications like that to a minimum is a key to having a project like this work.

 

So long as any mod is being included in a Pre-made ROM, it should be included as a defintion in EvoScan and ECUFlash. The worst thing that happens is someone patches their rom on their own using a different MUT ... well if they are doing that they should know to modify the request in EvoScan anyway. You've at least saved them the time of creating the defintion and all they need to do now is modify it.

 

Great Work!!! Cheers to all involved!

 

added a 3-port section: http://evoecu.logic.net/wiki/3_Port_Boost_Control Update anything I missed please!

 

Don't get me wrong, if we have an open MUT location that isn't being used that would be great. I just think if someone didn't copy the evoscan information and we overwrote (for example) load 2 byte with alt voltage and activation we could potentially be screwing people up more than we ever possibly imagined.

If someone can give me a few open MUTs that aren't currently used and are OK to use I'll throw them in there.

 

awesome!

 

I don't think we should really worry about supporting old version of evoscan. Its too much hassle. We should try to get everyone to just run the newest evoscan version.

 

ok for MUT here we go.

MUT 00 and 01 used to be for 2 byte load but with tephra v5.10 you no longer need both and can use just one, so...

MUT00 - Clutch Switch Position
MUT01 - 2->1 byte load (tephra mod)
MUT02 - 2 Byte RPM Low
MUT03 - 2 Byte RPM High
MUT04 - 2 Byte Air Flow High
MUT05 - 2 Byte Air Flow Low
MUT06 - Alt Map Voltage (I'm not sure if this is being used)
MUT07 - Alt Map Status (I'm not sure if this is being used)

 

By default tephra v5.10 and evoscan 2.5 are using

MUT 00-01 for 2 byte load
MUT 02-03 for 2 byte RPM
MUT 04-05 for 2 byte airflow
MUT 06 - Timing advance
MUT 07 - Coolant Temp
MUT 41 1 byte load


.....I don't think any of those should be removed. Thats why I don't like using those as standards...

I'm fine with basically anything that will work that is not already in the 2.5 defs.

EDIT: Based on the horrible excel doc I just came up with it looks like these are what we have free:

08, 09, 18, 19, 20, 22, 23, 25, 31, 33-37, 39, 40... and a few others. I don't know a ton about MUTs, so I don't know what is OK to overlay here....

 

whats wrong with that....Just switch 00 and 01 from 2byte load to the new 2b->1b load so that you free up a MUT. Then use that MUT for clutch position.

All of your roms in the wiki include tephra v5.10 so they all will have the 2b->1b mod.

 

What do you think about that edit I just did to my last post? I'm just really not a fan of changing something that is a default across many places, especially if we can just do it somewhere else.

 

yea that makes perfect sense to me....
Keep what is already standard and add in where there is free space for clutch, and alt map voltage and status. And then once we have added those lets keep them standard across the range.

 

A good point. But I suppose at some point you (the royal you) just have to make the hard choice, even if it means change, and then document the crap out of it. Let people know that they HAVE to match the EvoScan XML defs with their ROM. Tell them that so long as they get both the ROM and the XML defs from the Wiki they should match because you made them that way. If they aren't then they need to modify it.

Also along these lines, using the Wiki to define the definative MUT table addresses would be a good way to keep track of things. I think most of that is already started but I'm not sure if it is in one single place for easy reference. Probably belongs in the Logging section even though it is sort of patching. I see the def for adding it to ecuflash is in the patchin section ... but from there I don't see a good discussion on all the various things to put in there.

I can't do it at work otherwise I'd start it. Convenient huh