problem reading ecu with ecuflash
MalibuJack: I've emailed Colby, hopefully he can shed some light. Thanks for the help.
3gt: I've used a friends ODBII lead without any probs - it's not a USB one, just refular serial port. But I don't think there's anything wrong with the harness etc - i'm convinced it's the USB drivers playing up. Thanks for the help.
Please could someone tell me, if you run up ECUFlash with a 1.3M cable attached to the PC but not to a vehicle, what does ECUFlash report the cable as? Is it a "FT232R USB UART A3001LCw" or is it reported as "OpenPort 1.3".
Not sure how ECUFlash recognises it, but I think it's this step that's failing for me for some reason.
3gt: I've used a friends ODBII lead without any probs - it's not a USB one, just refular serial port. But I don't think there's anything wrong with the harness etc - i'm convinced it's the USB drivers playing up. Thanks for the help.
Please could someone tell me, if you run up ECUFlash with a 1.3M cable attached to the PC but not to a vehicle, what does ECUFlash report the cable as? Is it a "FT232R USB UART A3001LCw" or is it reported as "OpenPort 1.3".
Not sure how ECUFlash recognises it, but I think it's this step that's failing for me for some reason.
Burgers, I'm the other end of the country. North-East - near Whitby.
If I don't have any joy in the next couple of days, any chance you'd be able to test my cable if i post it down to you - i'll pay all return postage costs of course, just be nice to prove the cable is working or not.
It's a real pain when something like this happens the first time you try. I don't know for sure whether it's the cable/car/software install or a mixture of all 3 so it's a matter of elimination.
If I don't have any joy in the next couple of days, any chance you'd be able to test my cable if i post it down to you - i'll pay all return postage costs of course, just be nice to prove the cable is working or not.
It's a real pain when something like this happens the first time you try. I don't know for sure whether it's the cable/car/software install or a mixture of all 3 so it's a matter of elimination.
It should be reported as an Openport 1.3 or Openport 1.3 Mitsubishi
If its reported as the OEM chip ID, then it might not have had its settings correctly flashed into it, or it is having a different type of problem.
If its reported as the OEM chip ID, then it might not have had its settings correctly flashed into it, or it is having a different type of problem.
I received some software off Colby this morning that he wrote especially to allow me to flash the cable at my end. Worked a treat and have now successfully read the map from my car!
Many thanks to all who helped, and a big thumbs up for Colby. Cheers!
Many thanks to all who helped, and a big thumbs up for Colby. Cheers!
Thread
Thread Starter
Forum
Replies
Last Post





