fix missing ExtraDataIndex values when dequeing rx messages.report ERR_TIMEOUT in more places where waits fail.fix wait condition problems in port to boost library causing communication problems with driver.fix bug where startMsgFilter was looking for the wrong synchronization stamp.DLL no longer uses Qt to make smaller and more portable, uses boost library instead.Fix bug where patches and some other metadata was not appearing in metadata view.Problems with failed readEcuIdentification requests in CAN Mitsubishis are ignored in case they are not supported in the current mode.Fix problems with FTP uploads of unknown ROMs.Fix bug where vehicle type dialog selects first item if you do not interact with tree view, even though another item is shown as selected.get Evo X recovery mode write back in ECU menu options.fix bug where reading response from kernel could report "msg buffer too small" when it was not.fixed MSVC compiler library issue which made EcuFlash incompatible with Windows XP.added additional delays when communicating with Mitsubishi bootloaders to avoid the ECU occasionally not receiving bytes.Update checker now looks at build numbers to notify you of incremental improvements that don't have a new minor version change.Allow for other responses in wrx02 bootloader init sequence (possibly for ecutek'd ECUs).mitsucan heuristically determines correct checksum area size.adding clarification to message indicating nothing was written due to no differences in ROM images.User Boot MAT is still not supported yet pending read support for this area. Added SH boot mode support for SH725XX processors.File dialogs offer all ROM types by default.Changed driver signing certificates back to SHA1 from SHA256 for compatibility with pre-Win8 OS versions until MS release SHA256 kernel mode signing updates for these.Fixed MSVC compiler library issue which made J2534 DLL incompatible with Windows XP.Fixed Openport 1.3 driver INF file section naming error which was preventing this driver from installing correctly.I flashed it again and it was functioning normal. I have a 2015 R1 and it didn't flash properly once. I honestly never heard of a 2004 being able to be flashed so it may be riskier to try it to ones below 2006. Some guy on this forum bricked his ecu on a 2004. a company in england used to advertise they can fix the ecu if you brick it. if it locks up it bricks the ecu while being flashed. some yamaha's have a immobilizer anti-theft system. not many people have problems but it has happened. However, there is a risk with flashing a ecu. could you theoretically gain 10, yes as long as you know what you're doing and have access to a dyno. So long story short, yes it makes a difference. especially if you're having some kind of issue and need to change the settings. So keep that in mind if you go with ftecu, if you're at a track and have no wifi you can't do anything to your bike. I went with woolich because unlike FTECU you don't need internet access to use it. or make any changes I want to everything else. now I can run a auto tune at any time and change the fuel mapping. (thank europe not usa for ruing the bikes). since starting in 2017 the euro 4 emissions put a stop to the bike having a built in diagnostics. some of the newer bikes 2017 and up you can use the flashing software for diagnostics. ignition timing, turn off the trouble code warning light for the exup valves. you can change what rpm the upper fuel injectors start working, what rpm the intake track changes length. but some examples are fan temp adjustment when it comes on and goes off. Not only can you modify the fuel mapping you can adjust things that yamaha made adjustable in the ecu. you can do more with the flash than you can with a piggyback system such as a power commander.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |