step by step instruction how to dump the ROM?

[BoxerFan]

Hi,

Can anyone share any step by step instruction how to dump the ECU ROM from a DBW MY05 Aus Liberty 2.0GT?

Also, can the above be achieved using the Tactrix 1.0G cable, or must the 1.2 cable be used?

Thanks for any help.

[cboles]

The 1.0 cable will not work for a DBW ECU.

Colby

[LGT-3-6]

The 1.0 cable will not work for a DBW ECU.

Colby

Why is this? Is it because of baud rate? I see this project has matured considerably and would like to get this going properly for LGT's. I'm a hardware and software guy, so let me know what I can do to help...

[cboles]

The software works fine with LGTs - you just need a 1.2 or 1.3 cable. The 1.0 cable can't go fast enough - it is a baud rate issue.

Colby

[LGT-3-6]

The software works fine with LGTs - you just need a 1.2 or 1.3 cable. The 1.0 cable can't go fast enough - it is a baud rate issue.

Colby

Well if we just want to wait an hour, any reason it can't be downgraded to a low baud rate? No need to obsolete hardware for a small wait. Source would be nice to play with :p looks like beta code that's on here

[cboles]

I will be making variable baud rate kernels in the future. The issue really comes down to customer safety. As long and 1.0 and 1.2 users are still using the VCP drivers, I don't have a good way to detect whether someone has a 1.0 or 1.2 cable, the result of which I could use to determine the best baud rate. Once could do a loopback test with the kernel to determine the fastest usuable baud rate, but I would be concerned about using that method in case the bandwidth changes due to thermal issues, etc. I don't want everyone running on the ragged edge of what their cable, wiring, and ECU will support. Once I have logging support, I will wean 1.2 users of the VCP driver, and will be able to detect the 1.2 hardware. At that point, all unknown cables will run at a conservative baud rate.