ST10F280

[chokchman]

Hello all
yesterday i have installed ST10flasher on my PC and i have tried to launch it, just by curiosity, to see what it looks like and i had these error messages:





Do you know what does it means?i specify that i did not connect interface or ECU because i have nothing yet

[chokchman]

Hello
Resistors 560ohms in place:




Now i'm waiting to recieve the VAG-COM interface
Mac Gyver please take a look to your PM
Thank you

[chokchman]

Wiring done with chatterton around the terminals:



Wiring connected to the ECU:





I am still waiting for the VAG-COM interface from France, it arrived by plane yesterday and the package should be delivered in a few days

[ivoo]

Hello all
yesterday i have installed ST10flasher on my PC and i have tried to launch it, just by curiosity, to see what it looks like and i had these error messages:





Do you know what does it means?i specify that i did not connect interface or ECU because i have nothing yet

You must have connected ECU in boot mode, then "reload monitor" or start ST10 flasher again.

[chokchman]

The interface is finally in my possession!

i will try to contact Mac Gyver to help me via skype for the ST10flasher use

[chokchman]

First aborted attempt yesterday with my friend Mac Gyver (super nice guy, thank you Jose Luis), it was impossible to read the ECU in bootmode!The pinout connections were OK, the ECU was energized by a 12v transformer (which gave exactly 11,75v).
The same error message appeared:





Jose Luis advised me to try with 470 resistor or 330 resistor instead of 560 actually in place

[chokchman]

I have tried again with another loader that delivers 13.2v in continuous but i have the same error!
I have also tried with 470 resistors then with 330 resistors then with simple jumpers (wires) but without success, always the same monitor error!
Please can someone confirm me that the connections and pinout in the following picture are right?


Thank you

[datapage]

see the photo in its remediation
Software st10 f works fine in ediabas com1 interface db9.
usb not very good.
kkl no good.

[chokchman]

Is it necessary to energize the three 12v pinouts?Or only one is enough?

[datapage]

boot yes,12 more...

[chokchman]

Hello all
I am so desperate by this ST10flasher that i don't know how i must begin my message!
The connections, the wires and the pinouts are right and are following this drawing:



The enenrgy source gives 13,2V measured with a multimeter.

Mac Gyver helped me many times by teamviewer but we fail everytime

The VAG-COM interface is correctly installed, with the right drivers, and is setted on com1 :



Before beginning to use ST10flasher Mac Gyver has modified the file Startup.ini in the ST10flasher program.The original startup.ini file was setted as follows:



Mac Gyver has modified it as follows:



When all is connected and ECU energized we launch ST10flasher and we have this first error:



We click on OK and we have this second error:

[chokchman]

When we click Ok, it opens the ST10flasher window like this:



If i try to check the blank banks by clicking on "Blank check" i have this error:



But sometimes i succeed to check blank banks!

And i can not set the com port speed because the field is empty:



Of course i can not dump, sometimes it begin to read then it goes in error:



With Mac Gyver we thought to a problem of source voltage or of faulty contact between wire terminals and ECU pinout so he advised me to try with the ECU connected directly in the car (with car battery perfectly working) but it gave the same errors!

Is there here in the forum some specialists of this kind of ECU and of the ST10flasher software that could help me to find a solution?
Thank you

[Zmann]

i don't use st10flasher so can't tell. wouldn't you like to get the job done with xprog? if own one.

[chokchman]

i don't use st10flasher so can't tell. wouldn't you like to get the job done with xprog? if own one.

I am open to all suggestions and I am ready to try all solutions

[Zmann]

I agree learning the new method to the same job but if it's in trouble i would rather minimise all unsure factors, the new interface, sw, etc.

being back to xprog, if you've already owned one you know having no problem with it. simply check back to your another related thread I put some info in.