|
Title: Problem with ECU can't read or write via OBD Post by: pedrosousa on December 11, 2014, 02:14:02 AM I have an 8N0906018H ECU to change a car from 512Kb to 1MB ECU.
Car Harness it's done and checked, now the probelm it's with the ECU. On car, the ECU can't be read/write or even see ECU data with Galletto or MPPS, Vag-com can read but says to "many communications errors". On Bench in boot mode, with galletto can read, write and see ECU DATA. It's possible to access to EEPROM and change to immo off with visual ME7 tool. Continuing on Bench not in boot mode, MPPS can't read ECU DATA or the Flash DATA or wirte, with Vag-com it connects but some times give the "many communications errors". Galletto can't read/write, ECU DATA it's possible but the info comes with lost characters. I've tested the ECU some 8 mouth ago and it was working good, now it's happening this, can't really understand what I've done to create this problem. Any suggestion how to solve it, or I'll need to buy a new one?? Title: Re: Problem with ECU Post by: aef on December 11, 2014, 04:19:22 AM Maybe your in car wiring destroyed your ecu?
try to use a straight k-line from ecu to connector or pull hifi and dash fuses. Title: Re: Problem with ECU Post by: pedrosousa on March 09, 2015, 09:57:40 AM OK new issue, tested the ecu in car, the car is running without problems, I can do diag via vag-com and all the stuff but I can't read or write with MPPS.
Ising MPPS: In ECU Id it says: Without Information or ECU not Found What can be the problem??? Title: Re: Problem with ECU can't read or write via OBD Post by: prj on March 09, 2015, 01:57:35 PM The 8N suggests an Audi TT.
The older cluster in Audi TT worked fine over OBD AFAIK. However, maybe you put it in another car, that has an older cluster? Before MY2000 there are many issues connecting in KWP2000 mode to cars with immo in the dash. Many dashes do not let anything through but KWP1281... others disconnect in the middle of the programming session. That said, ECU Data should work on MPPS because it gets the info over KWP1281 IIRC. Title: Re: Problem with ECU can't read or write via OBD Post by: majorahole on March 09, 2015, 02:01:16 PM clone cable? could be the connections on the cable side. i had an issue with not seeing my ecu(med9, but shouldnt matter) my connection was crap, the cable wouldnt go in far enough to make full contact with all the pins.
Title: Re: Problem with ECU can't read or write via OBD Post by: pedrosousa on March 10, 2015, 03:04:44 PM Yes it's a clone cable but I change to stock ECU and it works.
My next test, it's the K-line cable, I'll route one to the OBD conector. It's a S3 8L with narrowband ECU, I'm changing to wideband one, the odd is that I have two wideband ECU 8N0906018H and one works OK via OBD the other not... ( the one that works good has the crash signal pin broken , and pin 62 also broken) K-line it's connected to the air bag unit, and I think that the crash signal pin connects also to the same ECU, this could be making the difference between the two units??? Or I'm wrong? Title: Re: Problem with ECU can't read or write via OBD Post by: prj on March 11, 2015, 12:14:36 PM I have never been able to read or write S3 8L narrowband with any tool clone or actual over OBD.
Connection drops after a while due to cluster closing connection. So I am curious what works for you on stock ECU. Title: Re: Problem with ECU can't read or write via OBD Post by: pedrosousa on March 11, 2015, 02:11:25 PM Stock ECU I use clone galletto and clone MPPS with the fuse!!! :D
Some times I need to remove the fuse (10%) Another car S3 8L with this ECU code, it's a pain in the ass to use clone MPPS, need to remove the dash fuse always, and turn the igniton on/off a couple of times, but it works. My problem is with the 018H wideband... I even get the message "to many communications errors" using vag-com This weekend I'll test with a wire, from the ECU, to the OBD port to see if it solves, if that work, I'll use an switch to diag/flash Title: Re: Problem with ECU can't read or write via OBD Post by: prj on March 12, 2015, 07:07:33 AM Which number fuse do you pull?
I found if I pull the fuse so that the cluster goes blank I get no connection at all... Title: Re: Post by: pedrosousa on March 13, 2015, 10:52:05 AM It's the one that make clustes go blank... there's two, it's the left one... it work.
You can also turn off ignition it reads... Tested in more than one car... original ecu 8n0906018n Title: Re: Problem with ECU can't read or write via OBD Post by: prj on March 13, 2015, 12:10:30 PM Thanks, will try on the next one I encounter.
Title: Re: Post by: vwaudiguy on March 13, 2015, 04:27:29 PM It's the one that make clustes go blank... there's two, it's the left one... it work. You can also turn off ignition it reads... Tested in more than one car... original ecu 8n0906018n It would be great to know what fuse number this is. I'd like to look up a wiring diagram, and see what this powers. Title: Re: Post by: pedrosousa on March 13, 2015, 06:31:13 PM It's fuse number 11...
Routed the k-line cable to the obd connector but with the 018h unit still can't read or write via obd. Galletto says error sending awake signal Title: Re: Post by: pedrosousa on August 08, 2015, 03:00:27 AM News on this....
The vag-com message it's a cable problem not a car problem. I can read dtc and log data with a TEXA original diagnostic tool. Now the two 018h can't be read or write with galletto or mpps via obd... So I'm using the (stock ecu) narrowband lambda to tune... No solution for this... Is there any bit to check that block ecu read/write via obd...??? Title: Re: Post by: armageddon on August 17, 2015, 11:31:05 AM Is there any bit to check that block ecu read/write via obd...??? procura no topo do ficheiro por 09 0A 0B 0C 0F do que li por aqui, trocando 0F para 00 impede leitura por OBD search at the beginning of file for 09 0A 0B 0C 0F from what I have read over here changing 0F to 00 block OBD read Title: Re: Problem with ECU can't read or write via OBD Post by: pedrosousa on December 13, 2015, 02:34:38 PM Problem solved, car wiring problem... Replaced the wideband adaptor with a stock wideband car harness and it works now...
|