openecu.org

Hi everyone!
New guy here...

Not big on introductions so I will tell you what I have and you will know how I got here.

I bought a blue bugeye sti 02' a week ago... love the car to bits... I had an Audi S3 Quattro pre and there is no comparison. Which brings me to openecu, with the S3 tuning was very limited. but the Scooby the psibilities are endless.

I downloaded ecuexplorer and found that my vagcom OBDII cable worked on the scooby!

I can read the diagnostics but im having trouble with reading or downloading maps. I know I should connect the green connector under the dash (I have) and jumper the white block (this is the part where im stuck, which wires goes where?)

Sorry for the very long post, but thanks for reading!
Any help will be appreciated gr8ly!

Take a look here for a walk through of the read/reflash of a scooby

http://www.scoobypedia.co.uk/index.php/ ... ashingECUs
and
http://www.scoobypedia.co.uk/index.php/ ... gToYourECU

Also be aware that your cable (vagcom) may not read and reflash even though it does connect for logging and such. There are a lot of cables that will just read data.

Yep saw that read it and came to the following conclusion.
I need the white block connector jumper.



but looks like I can just jumper 1 with 2 and 3 with 4?



Right? or will I get the below result?

ya it's just a jumper, but for a just few $$ it's worth picking up. Lots of peeps just use paperclips.

Back, tried the paperclips the fan came on and off as well as the enginelight on the dash... tried to read from the ecu but got the below..

1452 byte kernel read.
kernel checksum is valid (n = 2).
kernel image loaded and verified.
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
kernel flash disable
rkrv: preamble 1 no response
<< PROCESS COMPLETE >>


could it be that the vagcom cable doesnt alow this?

That is what it looks like to me, There are several post with people using cables such as the cobb cable that get the same results when attempting to reflash. They log just fine but reflashing is another story.

Sorry.

Thanks anyway

1 more question, now that I am able to only use the vagcom for viewing diagnostic info... any hits ot tips on viewing troublesome info? e.g. knock/timing retard or boosting retard?

You will want to keep a close eye on IAM , feedback knock correction, EGT and A/F. Though for A/F you should really be using a WB not the build in sensor, it's range is too limited to give accurate tuning information.

For a complete list of what to watch/log read
http://www.xpttuning.com/osecuroms/view ... ?f=2&t=323