Pages: [1]
Author Topic: BDM Anomaly  (Read 3831 times)
raiden76
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« on: March 09, 2015, 06:02:17 AM »

Hi, a customer's came in that was not able to readout from the BDM port by another tuner.

Upon inspection of the ECU (Bosch MED 9.1.2 - TTRS Manual) I can see that one of the pad was lifted off the board and another was completely missing.

I was able to connect a make shift pad to replace the missing one and connected my EVC BDM to the port.

To test the BDM port, I used BDMtoGo to take a read of the ECU but it prompt with error message "No Connection DSDO = GND".

If my understanding is correct, the ECU is in reflash/programming mode when DSDO = GND?

The reason I think it might be in reflash mode is because the ECU when in the car acts like it is in reflash mode, with warning messages on Dash and no communication with ECU.

Is there a way to by pass/disable this mode so that it functions in normal mode?

The reason why I ask is, when I put the ECU back into the car after it has been on the BDM and getting the error message, the ECU appears to be in normal mode and engine will start and run with no issue. However, if the ignition is turned off, the ECU then reverts back to what seems to be in reflash/programming mode. Note: a full VCDS Scan shows no errors once the initial faults are cleared.

This would suggest to me, when ECU gets put into the BDM something is being triggered which allows it to run for the 1st initial start.

I have tested this several times, by doing the following:

- Put ECU on BDM Frame with Probe
- Switch On and attempt to read out
- BDMtoGO displays fail error message
- Cancel attempted Read
- Switch Probe Off
- Put ECU back into car, the car will start and engine runs
- Switch off Engine
- Switch ignition on, attempt to start the car and multiple subsystem error messages appears on dash display & warning alarm (beep,beep,etc.)
- The messages are the same as when a car is being flashed via the OBD port
- Engine does not start and there is no error messages in immobiliser to indicate that it is this that is stopping the engine from starting

How is the above able to occur?
Is the car in another state other than reflash there must be some way kicking it into normal running mode, just like the initial 1st start after being in the BDM with attempted read.

Has anyone seen anything like the above before? Is it possible to disable the BDM mode or possibly desolder/solder a component to get this to work?

Thank you.

Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #1 on: March 09, 2015, 08:01:54 AM »

BDM can be disabled you know. Not saying that's the issue, but something to think about.
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
raiden76
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #2 on: March 09, 2015, 08:33:04 AM »

Hi ddillenger,

Thanks for the reply, I understand that and agree with you. In this case, I don't believe it is because the other tuner could not get a readout from the ECU.

Unfortunately, I don't use the BDM all that often and don't have enough information on how exactly to solve the problem.

Does anyone know how to get it out of this "reflash" mode? Is it a case of powering a pad, earthing a pad, etc?

I'm wondering if it is possible that maybe some solder is lodged down the tiny through hole that the DSDO pad is connected to? Ever seen or heard of that happening?

Logged
IamwhoIam
Hero Member
*****

Karma: +52/-115
Offline Offline

Posts: 1071


« Reply #3 on: March 20, 2015, 03:46:09 AM »

ECU needs to be flashed back to stock through OBD2 and then you can tune it through OBD2. Sounds like a checksum problem with the "tuned" file that's in it.
Logged

I have no logs because I have a boost gauge (makes things easier)
Pages: [1]
  Print  
 
Jump to:  

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