


add support for EVO 5/6 and other Mitsubishi H8 reflashing.

increase maximum allowable ISO9141 baud rate to be 125000 baud.fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC.fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers.(no changes other than new firmware payload).fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity.fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger).this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors. allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed).add some retries to kernel reads, instead of failing.actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models.fix programming voltage warning errors in Subaru HC16 kernels.up to Generic2048K, including all powers of 2, plus many other common sizes. add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for.support for flashing H8/539FA processor (e.g.It is not much more than making changes with a power commander or setting up and using a data logger. I played with the software 3-4 years ago. I need to order one for my bike, but have not yet. Regardless, if that is your goal, the ECU editor is the only way I would do it. Petrik posted the raw tables one time to show it. I haven’t looked at the tables in the last couple of years but if I remember correctly the timing retard was only under part throttle conditions in the lower gears to smooth the response. I don’t think you will gain as much as you might think. Plus you take a bunch of the unknown out of it and there is a much better chance of it working correctly the first time. Greg started building them to supply the demand and I’d bet his price is very competitive (or likely cheaper) than trying to buy the parts 1 at time. All of the instructions are available to build the interface if someone is handy enough with electronics. The hacking of the ECU and software development was done independently. You are not under any obligation to buy anything from Greg to use the software.
