RomRaider

so ive come to find out ecuflash v1.28 is the only version that works with other interface cables (ie. VAG-COM) after that you can only use the tactrix cable.

so what im trying to figure out is if i can modify the definitions to work with the later version or im going to ask tactrix if they can email me the code script for the later versions of ecuflash and modify it so i can select com ports which shouldnt be a problem seeing as ecuflash is opensource i can do whatever i want with it.

am i wrong?
any input on the subject would be appreciated or support.
eventually im going to figure this out

Unfortunately, Ecuflash is not opensource.

Hmm... I use 1.34 with non-Tactrix cables just fine.

I think there are versions of VAG-COM cables that use newer FTDI chips internally that do not operate the same as the older versions of chips or EcuFlash does not recognize the chip number as FTDI, as I have two cables that will not work with the 1.34 version.

ECUFlash is a closed source cost sharing freeware application (ECUFlash : Tactrix Cable :: Android OS : Android Phone, except the open source part) that was originally touted as open source by its creators. At one point it did come with a source preview with some pieces of the code.

CN: The only way you'll accomplish this is to reverse engineer it.

As much as I'm disappointed at the closed source and pseudo-false-advertising, the standalone logging with the O̶p̶e̶n̶ClosedPort 2.0 is still a great tool, despite the lackluster support. So I'd still recommend picking one up.

does ecuflash v1.34 support CAN? this is the main reason im trying to figure this out.

as of now i can only flash up to 06 dbw and id like to open up my options

Yes, new versions support CAN ecus. I wonder if the VAG-COM cables even support CAN. Surely they offer a solution, but I wouldn't be surprised if the cheap cables didn't even support it.

Sounds like you may be tuning cars for money. If you are, stop being a cheapskate and support the people that give you a relatively cheap solution and invest in a proper cable. Used ones can go for under $100.

Not without a CAN controller chip inside them.

To flash CAN ECUs you need a cable that is J2534 compatible. Even then, EcuFLash will only work with an Openport 2.0. I have a Mongoose and EcuFLash will not recognize it.

currently im just reading roms for the experience and would like to be able to access more vehicles to tune my friends cars for fun, otherwise if i was getting paid i would have already bought an openport to avoid the hassle but seeing as i cant afford one i have to work with what i have.

but thanks for the kind words

im probably just going to end up rewriting the definitions minus the 16bitbase and 32bitbase seeing as early versions of ecuflash wont read them.

ill post my progress and if i have any success, ill probably post a link of my rewriten metadata if it works for those who are in the same boat as me and just want a bigger playground

If you have any experience with C#, I have a project (SharpTune) at http://github.com/Merp that can read ECUFlash definitions and construct a full definition object using the base inheritance scheme. At that point, it doesn't take much to dump the objects to a different xml format, just rewrite the exportXML function for your needs.

Fixed. Even if it's just old html copy, it's seriously misleading, and highly uncool.

been talking to someone at tactrix and he clarified that openecu indeed is closed source... interesting. also vagcom doesnt support CAN unfortunetly but i guess thats what i get for buying a 5 dollar cable. was orginally hoping i could do without a tactrix cable for experimental purposes but seems i have reached my limits. oh well with enough pissing and moaning to tactrix i managed to score a 10% discount on an openport. so ill probably end up messing with some definitions while i save up.