When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I just though of something, maybe it's the intelligent battery sensor. The battery I had wouldn't hold a charge so I replaced it with an AGM and it's rated at 95ah. I registered it with the scan tool the option was 90ah there was no 95ah option so I picked 90ah. The car sat for a month and when I went to unlock it the battery was completely dead. I had to charge it up over night and that's when this started, so I checked battery status with the scan tool and got this...
The engine control cannot recognise the intelligent battery sensor. This may be due to the following causes:
IBS supply interupted BSD between DME/DDE and IBS
D6137_00000000_01_400
As long as the battery has a charge it will start. The IBS will not cause a crank no start situation in these conditions. Just unplug it and see what you get
I unplugged the IBS and tried it again but it still won't fire up. Could the battery registration in itself cause it not to start? The new AGM battery is rated at 95ah and the scan tool only gave me the option for 90ah, does that 5ah difference matter enough that it would damage anything? I'm using the same FTDI cable I did a few yrs ago and it worked fine with ISTA the vehicle interface type is set to EDIABAS default settings and its using com port 1. INPA loads fine and recognises the battery and ignition status but how to make it display in English would be great.
No that's how it works if you don't buy the original battery. You program it to the one that's just below what you have if it's not an aH match. I've been using interstate batteries for over 15 years in my BMWs without any issues.
Mikes Easy BMW Tools is in English but you'd also need to update SP-DATEN to v71 after install
Ok thanks for the info on the battery setup, I have it set to 90ah already. I'm looking online for the Mike's tools and the updated SP-DATEN files, I'll give that a shot and see where it takes me.
I fixed the interface issues with ISTA it's working for me now, I attached a screenshot of the faults being detected. Does it look like I have CAS/DME sync problems? If so can it be fixed with the Foxwell scan tool, INPA or ISTA?
No it looks like you have an electrical and/coding problem. Your CAS is not on, your DME is not communicating, nothing is communicating on your MOST and you have modules with programming aborts which indicates someone tried to do something when they had no idea what they were doing. There's no way that thing was starting up. You need to fix your power first then programming/coding. Need to brush up on how to use WINKFP and NCSEXPERT. Both are going to be needed to fix the issues you're having with the modules and MOST unless you have ISTA/p that may be able to fix some of the issues.
Last edited by seanjordan20; 09-15-2024 at 07:32 PM.
Damn this is a much deeper problem than I had anticipated. I've never done any programming on the car and wouldn't have a reason to do that. Could my changing the battery to 95ah AGM possibly have fried the electronics? The car sat for over a month after the battery was replaced and it did have the eccentric shaft sensor failure prior but it would at least start up. I'm going to guess and say this is going to take a huge amount of time to sort out. I l'm still looking for the sp-daten files for E60 online and have had no luck yet. So now I need to find the ISTA/P, learn how to use it and not make the problem worse. I was thinking there was a bad sensor somewhere I overlooked, but no way, that'd be too easy. Thanks for your insight I do appreciate your time to reply, I now have some direction of where to go with this.
I had 11.4v left on my battery and I'm thinking that's what gave me the horrible scan because no programming was done on the car. I unplugged the battery completely and put in on a trickle charge overnight and into the following day. I put it back in the car and ran another vehicle test with ISTA and it looks much better but it still won't start. I don't believe any of these faults would keep it from starting up. Is there a way I can test if the DME is sending signal to the coils? I read a post about someone having similar problems, crank no start, they did a CAS & DME alignment with INPA to fix it. It might be a last resort but my question is would doing that have side effects or would it just re-sync the signals between them? I'm searching forums looking for ideas, things to check, making sure I didn't overlook something stupid while trying to figure this out. Would the S 0193 keep it from firing up?
I would do the CAS/DME alignment to see if it fixes the no start issue. It can't hurt and only save you time if that is your issue. If it doesn't work then you can run tests in ISTA to see if you are getting power where you need it but I don't see anything that would prevent starting at this point.
09-15-2024, 10:22 AM
