Darwinn

iTrader: (6)

tephra, can I help with testing? (if needed)
I'll try stock 88570008 today on my car(88840017). Maybe it will start and run fine.

I am very interested to switch to universal rom, that will work with sd and have all your patches. I cant live anymore with maf, I am ready to buy ems... but cash is the problem. and compatibility of stock ecu dont allow to do that...

tephra

iTrader: (6)

well i would upgrade to 88570008 first - get that going then look at doing V5.10 or V7...

iTune

iTrader: (3)

So am i reading this correctly? i'm running 96530006 currently, is this ROM end of life in the Tephra lineup? What's the advantages of using the 96530706 ROM over the 96530006?? I have already ported once and would rather not do it again, as i have 96530006 T5.10 running PERFECTLY.

fixem2

iTrader: (30)

The 96530706 ROM is the same as 96530006. Tephra renamed it so the "07" portion means it is his version 7 of the Tephra mods.

tephra

iTrader: (6)

yeah - makes distributing XML's a lot easier... less screwing around for the End User..

iTune

iTrader: (3)

I kinda figured that was the case, because up until this point, i have never heard of the 96530706 ROM....haha. I like this idea, because this will make sorting out XML's a lot easier. Good idea.

iTune

iTrader: (3)

Do i need to change the 96530706 XML name to 96530006 in EcuFlash and delete the old 96530006 XML? Or, can i leave the old 96530006 XML and just add the new 96530706 XML to the folder?

One more thing, do i need to add the immobilzer code to this new XML or is it already in there for us USDM guys?

tephra

iTrader: (6)

leave the exising xml alone - if anything just clean up the current one to remove and old tephra mods..

then just copy the TephraMod-96530706.xml into your ecuflash dir.

you will need to copy the immob bits yourself (unless you use Phenems rom's)

SoCal Rally

This thread is titled V6 testing, yet in some of the later posts I see mention of V7 test builds, so I am a little confused:
- is V6 'officially released'?
- what are the feature updates in V7?
- I see mention of a V7 test build for the Evo VIII, but I don't see any mention of a V7 version test build for the USDM IX (ROM ID 88590015)?
- is there an 'official' site to download both the latest officially released and currently under development versions of each ROM and its XML definitions (i.e. as opposed to e.g. look for the link on page 41 of thread 402800 in the EcuFlash forum on EvoM)?

P.S. Thanks to tephra, mrfred, Malibu Jack, and all the other developers and testers.

tephra

iTrader: (6)

all will be revealed soonish.

I expect V7 to be out of testing next week, at that time I will post up the usual official thread...

it's ok to be confused - this wasn't really an open beta, I didn't make it easy so that noobies didn't try out dodgey software

SoCal Rally

David, thanks for the prompt response.

Understandable, that answers my question #2 and potentially question #3.

Re my questions #1 & #4:
- I have read about 400 of the almost 800 posts in this thread so far, and without reading the other half, I still don't see any mention of whether V6 is officially released, and if so where the ROMS and their corresponding XML definition files can be found?

- it would be really helpful if there was a single non-moving download location where one could always find the latest officially released version, and also the latest version that's currently undergoing development and testing

Thanks again for all the hard work you and the others do for the Evo community!!

tephra

iTrader: (6)

1) V6 was never officially released, it sorta turned into V7 after a number of changes to the code base.

2) were not that organised.. there is a wiki, but its not really 100% up to date...

fostytou

iTrader: (15)

1&2) You could assume if you didn't find something it might not exist

Official releases have had (and I would assume always will have) an official release thread with the official downloads in the first post along with all pertinent information, updated as necessary.

----

Not trying to be a jerk, but probably at least 1/3rd of those 800 posts are because people didn't read the other posts. Notice that your 2 posts caused 2 posts by tephra and my 1 post, all of which are questions that are already answered or where the answer could be implied.

Oracle1

iTrader: (1)

Thanks for clearing that up Dave.

I meant kill switch for the BCS, 3 boost settings

SoCal Rally

David, thanks for the explanation.

I submit that if there was a well organised and well maintained fixed download location, with both the latest official release, and also the currently in-development release (alpha/beta test releases), each with a list of:
- feature upgrades
- bugs fixed
- known problems
- relevant notes
- etc.

that it would actually significantly decrease the amount of support time both you and others generously dedicate to answering questions. Most established community-driven software projects are organized this way for this exact reason, and also for ease of use.

This thread would then likely only contain entries from people submitting feedback and error reports related to the latest test release. And then anyone asking questions already answered could simply be referred to the download location for more info.


Actually, in the software world it is very unusual for a software release to skip a version number, so in this case despite spending several hours reading many hundreds of posts, it was not expected.

I submit that if the software releases were better organized as suggested above:
- none of the extra 1/3 of the 800 posts would even be necessary (mine included)
- only those submitting feedback or discovered problems (and those interested) would even have to read the 800 (which would then be significantly reduced in number) posts in the first place

I'm trying to provide constructive suggestions here that sould significantly increase the ease of use, and decrease the amount of time required for all concerned (development and support community in particular).

And again, I am very grateful for the time and effort that everyone in the community spends both developing and supporting EcuFlash.