View Single Post
Old 12-04-2010, 11:10 AM   #27
lethaldose
Scooby Specialist
 
Member#: 189360
Join Date: Sep 2008
Chapter/Region: MAIC
Location: Virginia
Default

Quote:
Originally Posted by preludeIVgen View Post
Still same trouble with mine. Using ecuflash 1.29 I get:
[13:32:46.535] denso02_bootloader_cmd_start
[13:32:47.768] denso02_bootloader_cmd_start
[13:32:49.000] denso02_bootloader_cmd_start
[13:32:50.232] denso02_bootloader_cmd_start
[13:32:51.465] denso02_bootloader_cmd_start
[13:32:51.886] kernel get version
...then an error message pop-up.
Ecuflash 1.42 doesn't recognize the interface cable at all. Seems like a good chap, but I'd love to see this writeup from a client of his.

What was the rest of the error message?

Main thing about 02/03 ECU's with our cable is timing. When we first tested these with ECUflash 1.42.25.xx and our drivers you had to confirm ECUflash before the cooling fans performed their test cycle. (only with 02/03 cars) 04+ didn't matter.

The fans kick extremely fast so it does take a few attempts to get it right. I've had some mixed results from people regarding the bugeyes, had many that had no issues after they got the timing down, then had some that would still have an error.

I'm going to get my hands back on an 02 next week hopefully and confirm again with all latest versions of the software and make a video guide to solving the timing issues.
* Registered users of the site do not see these ads.
lethaldose is online now   Reply With Quote