Pages: [1] 2
Author Topic: Cant read 8D0907551D  (Read 26026 times)
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« on: October 02, 2013, 09:37:59 PM »

Hi guys,

I have tried MPPS and nefmoto without any luck, I assume the cluster immobilizer is stopping things. What are my options for reading and writing this ECU?

Thanks
Logged
panos1975
Full Member
***

Karma: +7/-6
Offline Offline

Posts: 105


« Reply #1 on: October 03, 2013, 07:01:46 AM »

Try to pull off  cluster's fuses before start reading with mpps.
Logged
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #2 on: October 03, 2013, 07:26:08 PM »

Pulled fuse 5 and 15 as the manual says these are for the cluster. The cluster and LCD still light up? This cant be right? Anyway made no difference, im sure I have the correct fuses. Any idea?
Logged
prj
Hero Member
*****

Karma: +1072/-481
Offline Offline

Posts: 6037


« Reply #3 on: October 04, 2013, 02:16:30 AM »

There are no problems reading and writing 551D via the port.
Possibly already tuned.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #4 on: October 04, 2013, 07:55:08 PM »

There are no problems reading and writing 551D via the port.
Possibly already tuned.

Ok thanks, the guy i bought it from claimed it was never flashed and was stock.
Logged
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #5 on: October 04, 2013, 09:40:36 PM »

This is the log file
Logged
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #6 on: October 06, 2013, 11:28:54 PM »

Finally got the ECU to read via MPPS. If I selected, B5 S4 2.7TT I got no response from ECU every time and still do.

So I tried B6 4.2 V8 ME7.1.1 and it started to send the ECU info, hit read and it started then crashed. So next time before I hit read I selected B5 S4 2.7TT again and it worked fine. I have no idea.

Now I cant connect with ME7Logger, everything is setup ok for the ECU. Just no connections at all Sad

Logged
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #7 on: October 07, 2013, 07:15:41 PM »

Well its a stock file, so I have no idea why im having all this trouble if the D box read and writes ok. Cant get ME7logger to connect at all Sad
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #8 on: October 07, 2013, 07:18:08 PM »

Something is disrupting the K-line. Run a new wire, or disconnect things until it works!
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #9 on: October 07, 2013, 07:31:55 PM »

Something is disrupting the K-line. Run a new wire, or disconnect things until it works!

Thanks man
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #10 on: October 07, 2013, 08:12:46 PM »

NP.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #11 on: October 07, 2013, 09:48:16 PM »

If I read the cluster eeprom with VAG EEPROM programmer , then run ME7logger it runs fine. Its the stupid cluster immobilizer, unfortunately I removed all 3 fuses to do with cluster and it did nothing. Unplugged ABS and removed all ABS fuses also. Can I remove the immobilizer from the cluster?
Logged
prj
Hero Member
*****

Karma: +1072/-481
Offline Offline

Posts: 6037


« Reply #12 on: October 22, 2013, 03:30:49 AM »

It has nothing to do with immobilizer.

Change connection method to SLOW-0x00 in the .ecu file, turn ignition on, let ME7Logger connect, then start the car.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #13 on: October 22, 2013, 04:59:59 PM »

It has nothing to do with immobilizer.

Change connection method to SLOW-0x00 in the .ecu file, turn ignition on, let ME7Logger connect, then start the car.

I got it working thanks, it was due to connection speed. Only weird thing I have now that I can figure out is: I have to read the cluster eeprom with Vag commander before ME7logger will connect. After I do this once, and with ignition still turned on or engine running ME7logger connects and stays connected fine everytime
Logged
prj
Hero Member
*****

Karma: +1072/-481
Offline Offline

Posts: 6037


« Reply #14 on: October 25, 2013, 12:59:39 AM »

I got it working thanks, it was due to connection speed. Only weird thing I have now that I can figure out is: I have to read the cluster eeprom with Vag commander before ME7logger will connect. After I do this once, and with ignition still turned on or engine running ME7logger connects and stays connected fine everytime

I already told you exactly what to do, you are free to ignore my advice though.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.021 seconds with 18 queries. (Pretty URLs adds 0.001s, 0q)