EcuFlash, EvoScan, ECU Patches - Organization Needed
Sub-forums within sub-forums within sub-forums is a bad idea in my opinion. It'll make things unnecessarily complex and potentially more difficult to search. There also may be less people participating in discussions when you have to visit 10 different folders to see what's going on..
And we already have a general tuning forum, no one uses it is all: https://www.evolutionm.net/forums/fo...play.php?f=129
Combining ROMs and their patches under one roof and having some stickies with the most important topics is a good idea though.
I think there are 2 main problems:
1. Developers having to deal with 27,000 different ROMs
2. Users having to comb the forums for patches that are all over the place and aren't always developed for the same ROM.
Rest seems to work good..
And we already have a general tuning forum, no one uses it is all: https://www.evolutionm.net/forums/fo...play.php?f=129
Combining ROMs and their patches under one roof and having some stickies with the most important topics is a good idea though.
I think there are 2 main problems:
1. Developers having to deal with 27,000 different ROMs
2. Users having to comb the forums for patches that are all over the place and aren't always developed for the same ROM.
Rest seems to work good..
Last edited by mplspilot; Jul 24, 2008 at 10:55 AM.
folders within folders....why is that bad.
Sure it seems odd to be so many layers deep but it means it's well organized. I know about the general tuning section but the reason that most of us don't use it, is because we would rather post in EcuFlash. Our tuning questions tend to apply a bit to ecuflash. I wondered if it would be better for all tuning questions to go in the general tuning that already exists or to have a seperate one in stock Ecu folder.
I think one in the stock ecu folder makes sense becausae it limits the tuning questions to things that are capable with the stock ecu. In fact I think perhaps we could get rid of that general tuning questions section that already exists.
If you have a question post it in the existing sections for each product, most of them don't have much activity anyway. And if the question is more general and complex, post it in the advanced section.
Sure it seems odd to be so many layers deep but it means it's well organized. I know about the general tuning section but the reason that most of us don't use it, is because we would rather post in EcuFlash. Our tuning questions tend to apply a bit to ecuflash. I wondered if it would be better for all tuning questions to go in the general tuning that already exists or to have a seperate one in stock Ecu folder.
I think one in the stock ecu folder makes sense becausae it limits the tuning questions to things that are capable with the stock ecu. In fact I think perhaps we could get rid of that general tuning questions section that already exists.
If you have a question post it in the existing sections for each product, most of them don't have much activity anyway. And if the question is more general and complex, post it in the advanced section.
Last edited by dudical26; Jul 24, 2008 at 11:03 AM.
96940011 for 05 USDM Evos (which is the stock version) is problematic without someone figuring out where we can eliminate code/tables so that new code/tables can be added. 96530006 for 05 USDM Evos (from a Euro application) is problematic without someone figuring out how to enable the immobilizer.
So, uh, yeah.
This doesn't even begin to address the JDM and Euro ROMs.
As for the forum breakout suggestions: are we really seeing so much traffic right now that the EcuFlash forum needs to be broken out into a bunch of additional ones? While the distinction between flashing, logging, and programming may be obvious to the regulars here, most new folks (and some older folks) won't appreciate where the line in the sand is: communities aren't a nice neat hierarchy like technical folks like us would like them to be, they're messy and diverse. It also doesn't seem like the volume here really warrants a breaking up of discussion. (All IMHO, of course.)
At least some of what I suspect your end goal is could be solved neatly by a wiki, I'd think, rather than stickied threads whose first post goes stale within a few days of posting it, scattered through three or four different, but related, forums.
So, uh, yeah.
This doesn't even begin to address the JDM and Euro ROMs.As for the forum breakout suggestions: are we really seeing so much traffic right now that the EcuFlash forum needs to be broken out into a bunch of additional ones? While the distinction between flashing, logging, and programming may be obvious to the regulars here, most new folks (and some older folks) won't appreciate where the line in the sand is: communities aren't a nice neat hierarchy like technical folks like us would like them to be, they're messy and diverse. It also doesn't seem like the volume here really warrants a breaking up of discussion. (All IMHO, of course.)
At least some of what I suspect your end goal is could be solved neatly by a wiki, I'd think, rather than stickied threads whose first post goes stale within a few days of posting it, scattered through three or four different, but related, forums.
0015 for the VIII there is no downfall to running it and it has cleared up a few P0300 issues. Though I never had them at cruise just at idle but its fixed now too much timing advanced out down low oh well live and learn.
The main reason I updated is because Tephras patches are only supporting the 0014 and 0015.
In the future he can just use 0015 and VIII guys will just need to use that rom
The main reason I updated is because Tephras patches are only supporting the 0014 and 0015.
In the future he can just use 0015 and VIII guys will just need to use that rom
96940011 for 05 USDM Evos (which is the stock version) is problematic without someone figuring out where we can eliminate code/tables so that new code/tables can be added. 96530006 for 05 USDM Evos (from a Euro application) is problematic without someone figuring out how to enable the immobilizer.
So, uh, yeah.
This doesn't even begin to address the JDM and Euro ROMs.
As for the forum breakout suggestions: are we really seeing so much traffic right now that the EcuFlash forum needs to be broken out into a bunch of additional ones? While the distinction between flashing, logging, and programming may be obvious to the regulars here, most new folks (and some older folks) won't appreciate where the line in the sand is: communities aren't a nice neat hierarchy like technical folks like us would like them to be, they're messy and diverse. It also doesn't seem like the volume here really warrants a breaking up of discussion. (All IMHO, of course.)
At least some of what I suspect your end goal is could be solved neatly by a wiki, I'd think, rather than stickied threads whose first post goes stale within a few days of posting it, scattered through three or four different, but related, forums.
So, uh, yeah.
This doesn't even begin to address the JDM and Euro ROMs.As for the forum breakout suggestions: are we really seeing so much traffic right now that the EcuFlash forum needs to be broken out into a bunch of additional ones? While the distinction between flashing, logging, and programming may be obvious to the regulars here, most new folks (and some older folks) won't appreciate where the line in the sand is: communities aren't a nice neat hierarchy like technical folks like us would like them to be, they're messy and diverse. It also doesn't seem like the volume here really warrants a breaking up of discussion. (All IMHO, of course.)
At least some of what I suspect your end goal is could be solved neatly by a wiki, I'd think, rather than stickied threads whose first post goes stale within a few days of posting it, scattered through three or four different, but related, forums.

The wiki is a great idea, that might negate the need for subdivison of the forum. I have pm'ed a mod about setting one up.
But we still need standard rom versions.
Last edited by dudical26; Jul 24, 2008 at 11:50 AM.
There technically isn't a Tephra ROM for the USDM '05.
We will need to keep supporting both the 96940011 (USDM '05) and the 96530006 (Euro '05). Not everyone is willing to give up the immobilizer for Tephra's mods, so all other ROM mods will need to support the USDM ROM.
We will need to keep supporting both the 96940011 (USDM '05) and the 96530006 (Euro '05). Not everyone is willing to give up the immobilizer for Tephra's mods, so all other ROM mods will need to support the USDM ROM.
With more effort is it possible to mod 96940011. I know there is limited space but maybe if there are fewer roms to work on, more time can be spent making room on that rom.
What mods can currently be done with each rom?
I'm just trying to figure out the advantage of each rom.
What mods can currently be done with each rom?
I'm just trying to figure out the advantage of each rom.
There technically isn't a Tephra ROM for the USDM '05.
We will need to keep supporting both the 96940011 (USDM '05) and the 96530006 (Euro '05). Not everyone is willing to give up the immobilizer for Tephra's mods, so all other ROM mods will need to support the USDM ROM.
We will need to keep supporting both the 96940011 (USDM '05) and the 96530006 (Euro '05). Not everyone is willing to give up the immobilizer for Tephra's mods, so all other ROM mods will need to support the USDM ROM.
All of the ECU Boost control mods are available for both ROMs ... maybe the periphery mods too. Tephra and a couple of others have said that there simply isn't room in the 0011 ROM for the Tephra patches. Maybe if some tables were compressed or if there was a Tephra "lite" mod it could work ... I have no idea.
All of the ECU Boost control mods are available for both ROMs ... maybe the periphery mods too. Tephra and a couple of others have said that there simply isn't room in the 0011 ROM for the Tephra patches. Maybe if some tables were compressed or if there was a Tephra "lite" mod it could work ... I have no idea.
I suppose supporting both roms really is the only option. I will leave 0011 as the rom for 05's but when it comes time to publish information, we will note that 96530006 can also be used.
folders within folders....why is that bad.
Sure it seems odd to be so many layers deep but it means it's well organized. I know about the general tuning section but the reason that most of us don't use it, is because we would rather post in EcuFlash. Our tuning questions tend to apply a bit to ecuflash. I wondered if it would be better for all tuning questions to go in the general tuning that already exists or to have a seperate one in stock Ecu folder.
I think one in the stock ecu folder makes sense becausae it limits the tuning questions to things that are capable with the stock ecu. In fact I think perhaps we could get rid of that general tuning questions section that already exists.
If you have a question post it in the existing sections for each product, most of them don't have much activity anyway. And if the question is more general and complex, post it in the advanced section.
Sure it seems odd to be so many layers deep but it means it's well organized. I know about the general tuning section but the reason that most of us don't use it, is because we would rather post in EcuFlash. Our tuning questions tend to apply a bit to ecuflash. I wondered if it would be better for all tuning questions to go in the general tuning that already exists or to have a seperate one in stock Ecu folder.
I think one in the stock ecu folder makes sense becausae it limits the tuning questions to things that are capable with the stock ecu. In fact I think perhaps we could get rid of that general tuning questions section that already exists.
If you have a question post it in the existing sections for each product, most of them don't have much activity anyway. And if the question is more general and complex, post it in the advanced section.
Even less people ever go there.
And that's my point, people just like to hang out in this ECUFlash forum, it's good atmosphere with plenty of knowledge. Creating more specific subforums may disrupt it.. There's really no overwhelming activity here, that would demand splitting things.. I think.
I like the idea of a Wiki Format as well ... I'd say we keep this forum as it stands and continue to use it for discussion and development. The Wiki site would hold the decided upon techniques/data/patches in an organized fashion and would be kept up to date as development progresses.
For the '05 confusion, there should be a basic info page on the Wiki that outlines the things you need to know, like the MUT Table, what the Tephra patches are, how to modify the XML files, etc. the '05 ROM info should be kept there.
FWIW, I'm trained in information architecture and could help with structuring a site for this info. I am against the extra subfolders here on EvoM ... it would be too divided. there is a point of too much organization and sometimes you have to rethink your categories and minimize them.
I don't think there is too much info here (as stated earlier), but I think it does need organization. A BBS style environment really breeds disorganization for this type of info and it's not the best environment at this point.
For the '05 confusion, there should be a basic info page on the Wiki that outlines the things you need to know, like the MUT Table, what the Tephra patches are, how to modify the XML files, etc. the '05 ROM info should be kept there.
FWIW, I'm trained in information architecture and could help with structuring a site for this info. I am against the extra subfolders here on EvoM ... it would be too divided. there is a point of too much organization and sometimes you have to rethink your categories and minimize them.
I don't think there is too much info here (as stated earlier), but I think it does need organization. A BBS style environment really breeds disorganization for this type of info and it's not the best environment at this point.
Thanks for the feedback guys, lets forget the subfolder idea but focus on standard roms and a wiki. I already have the ball rolling on getting the wiki setup.
TouringBubble - can you please try to draw out a plan for the information for the wiki. Maybe a flow chart or whatever you want to use. Information architecture sounds very useful in this situation. That way once we get the wiki setup we can populate it with information quickly.
TouringBubble - can you please try to draw out a plan for the information for the wiki. Maybe a flow chart or whatever you want to use. Information architecture sounds very useful in this situation. That way once we get the wiki setup we can populate it with information quickly.
Last edited by dudical26; Jul 24, 2008 at 12:48 PM.
If you'll help ... Update the first post (or new thread) with ALL of the info we are looking to put on the Wiki site. I'll start with some here ...
Most current ROM IDs
Expanded XML Definitions for those ROMs
Expanded XML for EvoScan (I'd suggest .99 as well as the latest version)
Expanded XML For Mitsulogger
How to log OBDII data in LogWorks (From setup to logging)
MUT table explanation (Request ID's and such)
Latest Tephra patches
ECU Boost control mods (Load and PSI)
JDM MAP setup
2-byte explanation and values for latest ROMS
'05 ROM explanation (USDM and EDM ROM swap)
MAF Scaling tutorial
Injector scaling tutorial
Tuing tutorial
MIVEC Tuning
?? Explanation of different 2-byte load values ... corrected and uncorrected (I use both .. others might too)
Lean cruise
ISCV tuning
Axis scaling
Chime in people ...
Most current ROM IDs
Expanded XML Definitions for those ROMs
Expanded XML for EvoScan (I'd suggest .99 as well as the latest version)
Expanded XML For Mitsulogger
How to log OBDII data in LogWorks (From setup to logging)
MUT table explanation (Request ID's and such)
Latest Tephra patches
ECU Boost control mods (Load and PSI)
JDM MAP setup
2-byte explanation and values for latest ROMS
'05 ROM explanation (USDM and EDM ROM swap)
MAF Scaling tutorial
Injector scaling tutorial
Tuing tutorial
MIVEC Tuning
?? Explanation of different 2-byte load values ... corrected and uncorrected (I use both .. others might too)
Lean cruise
ISCV tuning
Axis scaling
Chime in people ...
If you'll help ... Update the first post (or new thread) with ALL of the info we are looking to put on the Wiki site. I'll start with some here ...
Most current ROM IDs
Expanded XML Definitions for those ROMs
Expanded XML for EvoScan (I'd suggest .99 as well as the latest version)
Expanded XML For Mitsulogger
How to log OBDII data in LogWorks (From setup to logging)
MUT table explanation (Request ID's and such)
Latest Tephra patches
ECU Boost control mods (Load and PSI)
JDM MAP setup
2-byte explanation and values for latest ROMS
'05 ROM explanation (USDM and EDM ROM swap)
MAF Scaling tutorial
Injector scaling tutorial
Tuing tutorial
MIVEC Tuning
?? Explanation of different 2-byte load values ... corrected and uncorrected (I use both .. others might too)
Lean cruise
ISCV tuning
Axis scaling
Chime in people ...
Most current ROM IDs
Expanded XML Definitions for those ROMs
Expanded XML for EvoScan (I'd suggest .99 as well as the latest version)
Expanded XML For Mitsulogger
How to log OBDII data in LogWorks (From setup to logging)
MUT table explanation (Request ID's and such)
Latest Tephra patches
ECU Boost control mods (Load and PSI)
JDM MAP setup
2-byte explanation and values for latest ROMS
'05 ROM explanation (USDM and EDM ROM swap)
MAF Scaling tutorial
Injector scaling tutorial
Tuing tutorial
MIVEC Tuning
?? Explanation of different 2-byte load values ... corrected and uncorrected (I use both .. others might too)
Lean cruise
ISCV tuning
Axis scaling
Chime in people ...
I think we should talk more about what should go in the wiki in another thread. Once I get the green light on the wiki from the mods, I will start that thread.






