Galleto Problem

[mitching]

I tried on 3 different computers now. But I keep getting the screen below (link) on ECU read. ECU Data is collected fine.

No progress bar movement and no file created.

I hope the link below is acceptable. Didn't know where else to upload/share it with you guys.

Imageshack - errora.jpg


Ohh, and the car is a 307 1.6 HDI from 2005.

[philkerman]

I suppose first things first, get the latest driver from D2XX Direct Drivers

And then try again, it could be a dodgy unit, has it previously worked on any other cars etc?

Phil

[mitching]

Originally Posted by philkerman

I suppose first things first, get the latest driver from D2XX Direct Drivers

And then try again, it could be a dodgy unit, has it previously worked on any other cars etc?

Phil

Ok, that I will. It worked fine on my 406 both reading and writing.

[mitching]

Updated the driver to the march 2011 edition from the supplied webpage on my Windows 7 machine. Same error though.

But but but, I noticed something that I found a little weird while trying to read it. The ECU data displayed actually tells me that we are dealing with a Bosch EDC16C3/9.17 , that's the non-FAP ECU. WTF? Shouldn't it have detected a EDC16+ ECU? Am I reading it wrong or could someone already have done some seriosly remapping to the ECU?

[jmkent]

It is compatible with Windows 7 I presume.... alot of these aren't.

[mitching]

I believe it was mentioned in a link Scotcruz posted, that if you at some point could not read or write to/from the ECU, one should remove the fuse supplying power to the instrument panel. I don't know why, but it's worth a shot. Unfortunately it will have to wait, as I haven't got much spare time on my hands these days. Darn it...

[mitching]

Originally Posted by mitching

I tried on 3 different computers now. But I keep getting the screen below (link) on ECU read. ECU Data is collected fine.

No progress bar movement and no file created.

I hope the link below is acceptable. Didn't know where else to upload/share it with you guys.

Imageshack - errora.jpg


Ohh, and the car is a 307 1.6 HDI from 2005.

Hi Guys,

Still seeing having the problem above, when trying to read the ECU on a 307 1.6 HDI. I tested it on my 406, where the Galetto will read the ECU just fine. What the heck could cause this?

I'm also a little puzzled about the Galetto info window telling me that it detects a EDC16C3/9.17 ECU when connected to the 307. From what I understand this ECU is the one used for non-FAP models??? That's just weird.

Praying for a miracle.

[philkerman]

Have you attempted a read using the EDC16C3 3.9?

[mitching]

Originally Posted by philkerman

Have you attempted a read using the EDC16C3 3.9?

Yep. Also my initial thought, when I discovered the ECU data not matching. It threw the same error when reading, unfortunately.

How do you really confirm the ECU model in the car? Bettyswollocks posted my cars info in his thread showing that the original engine supplied was a DV6TED4 FAP. So it should be the Bosch EDC 16+ C34 ECU being in use and not the Bosch EDC 16 C3.9. Just not according to Galletto.

All I want to achieve is removal of the FAP, before it goes haywire. But not a simple task, when reading the ECU is impossible.

[mitching]

Originally Posted by philkerman

Have you attempted a read using the EDC16C3 3.9?

After closer study it actually reports a slight different "errore" message when I select the EDC16C 3.9 driver.

" ERRORE READ 840000 " - EDC 16 C 3/9

" ERRORE READ 160000 " - EDC 16 C 34

Darn it... I think I've tried it 100 times now. :-D

Perhaps I should try to unplug the battery for an hour and give it a go again?