Negative. Have you seen the amount of posts around here that begin "help, I just flashed a rom from the internet onto my car and now it won't start?". The bar to getting a rom into the car is very low now so you can still blow up a car.

 

Sorry was just reading through the thread to catch up. The idea is sound on paper but unless that wiki is kept up to date (same problem with the "thread of all important ECUFlash links") then we've not made a step forward. The more important thing would be to find someone/some people with the time to keep it up to date.

 

I intend to standardize the version of EcuFlash and EvoScan used.

There is no reason for everyone to be using all sorts of different versions.

There will be one tutorial for EcuFlash 1.29 and then another for the latest version
I think everyone can use the latest version of evoscan.

 

This is a very good thing. The idiots are still paying other people to do it for the most part... Like me

I've been logging and reading this sub forum for months now and I still want to walk through all of this stuff with a pro at least once so I don't fail.

Looks like I will have to change my name to 94170015 : (

 

That's the point of a Wiki ... any of the contributors can update their own sections or other sections as well. Mrfred and Tephra keep their data up to date, but they can't depend on anyone else to keep links to their data up to date. With the Wiki system, they would update their own sections and a static link would always point to the latest data.

It would take a little more effort, but hopefully others will step up and help keep the misc. data up to date.

 

I think what we may find is that it should take less effort as there is only one place for the contributor to update info, and less time spent repeating the same info over and over. At least it should [shrug]

 

Some people for whatever reason on their systems cannot use 1.29 and above and then you have the vice-versa situation where they can only use 1.29 and above. Those people then get left out in in the cold, depending on which direction you go.

For evoscan, once again some people can't use some of the later versions or have been having problems with it. I know that some versions back some particular widebands weren't working with a particular version in that case, the 2nd point won't work either.

The best option would be to have this decision voted on by the forum and go with the majority. Which I would hope you were planning to do?

 

Which could already be done today without a wiki. By using proper thread management and linking .

I'll step back from this thread for now and see how it plays out...

 

I agree, it could be done already. However, since only the author or a mod can edit posts, the threads such as "Valuable ECU Topics" will eventually be out of date. With a Wiki system you increase the number of contributors and there is more likely someone that will take over and keep the info up-to-date.

Also, with the Wiki you wouldn't have 250 posts of "OMG this patch is great" to sift through for relevant information. There would be the info and nothing else. This forum would still exist to answer questions for those that have them and I would think that any needed info resulting from Q and A here would be transferred to the Wiki.

 

Alright,

Well I have not heard anything back from the mods about creating a EvoM wiki so I guess this one is on us. I was thinking we should use software from.

http://www.mediawiki.org/wiki/MediaWiki

Does anyone have a webserver that they can throw this up on to get us started?
Once we get it started and have it running fine, I can pay for a webserver.

 

pm Zeus - he might be able to help

Also Mediawiki is pretty good (not that I have compared it to any other wiki software )

 

Done. Hopefully he can help.

 

While we wait more to hear if EvoM is going to be able to help us out with this one, I have started a stock ECU wiki of my own.

I have it here while we build it up. Please help me to get this thing going.

I have just done a VERY ROUGH version of it to get things rolling.

 

I think the wiki should document every ecu patch available. It will talk about what the patch does and how to use it. However, it will not discuses how to implement the patch as this will not be necessary. We will create a database of matching Roms, Definition XMLs, and Evoscan Settings bundled together in a zip file for every common combination.

For example for every rom ID, there will be a file for tephra mod. And another file for tehpra mod plus direct boost, JDM Map, Lean spool disable, etc...

This way a used needs only to go to the site, read about the different mods, and decide which ones they want to use. Then the find the file contained the modifications that they want and there good to go.

 

I somewhat lost track of this thread so i am not sure if this was discussed.

I dont know much about hex files but i have heard the idea of having a loader. Should all the patch guys consider releasing patches in a manner we can load and unload them onto a ROM? Is this possible? Is it hard to implement? I dont want to add more work i am just trying to think of ways to make patching easier.