|
|
|
|
||||||||||
| Xoutpost server transfer and maintenance is occurring.... |
| Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management |
 |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
|
#1
02-18-2016, 11:44 AM
|
|||
|
|||
|
Quote:
__________________
2009 35d, 2006 325i & 330i 
|
|
#2
02-20-2016, 03:50 PM
|
|||
|
|||
|
progress
ninja_zx11: Ground was also my first thought. I check continuity throughout the vehicle and found no issues. If IBS, I would think a code would appear?
smassey321: Ground was indeed disconnected at the negative battery terminal. Weather is great today so finally got back into it. The good news is I'm back to a no start condition with good cranking and no error codes. I'm embarrassed to say that the fault was my own. When I pulled down the fuse box/junction box (JB) to check relays and fuses, it only rotates down a little because of the wires. There is one connector on the top side that is particularly short and needs to be disconnected to access the fuses. Once disconnected, it isn't really visible unless you tuck your head under the dash. I noticed that many of the error codes were CAN related. I was thinking CAS but I never touched that controller so I back to the JB I went armed with wiring diagrams and my O-scope. This time I had to get up underneath it to look at the bottom JB connector and that's when I saw the dangling top side connecter. Plugged it back in, re-connected the battery,erased the codes and I'm back to it cranks but doesn't fire. In the hope that this helps others, below is my error report with that connector undone, a photo of the connector and the empty socket in the fuse box. Yes, I did see the empty socket before but there are several empty sockets ( fuse and relay ) so it didn't catch my attention. E R R O R M E M O R Y ----------------------- Date: 14.02.2016 16:52:19 Model: E70 Scope: all control module JobStatus: OKAY Quantity: 22 ----------------------------------------------------------------- ADR Gen. name JobStatus Number of errors Error code Kind of error 00 JBBF OKAY 5 Error stored A6D1 61 C918 64 A737 64 A6C9 68 C914 64 01 MRS OKAY 3 Error stored 9415 E0 9414 E0 93FB E0 12 DME/DDE OKAY 14 Error stored 4DF3 61 4BE3 61 4BE8 61 482F 61 49F3 61 4C23 61 4C28 61 4C13 61 4458 61 4C3D 61 4D3D 61 4BF3 61 4992 61 4B4D 61 17 EKP OKAY No Error stored 19 VGSG OKAY No Error stored 2A EMF OKAY 3 Error stored 6022 E4 6041 E4 D395 E4 36 TEL/MULF OKAY No Error stored 37 AMP OKAY No Error stored 40 CAS OKAY 2 Error stored A0B5 64 A0B0 28 45 RLS OKAY No Error stored 50 SINE OKAY No Error stored 55 ISPB OKAY No Error stored 56 FZD OKAY No Error stored 60 KOMBI OKAY 5 Error stored A3AA 60 A3AC 60 A3B9 60 A550 60 A556 60 62 MOSTGW OKAY No Error stored 63 MASK/CCC OKAY 1 Error stored E1E9 20 64 PDC OKAY 3 Error stored E21A 60 E21C 60 E21E 60 6B HKL OKAY No Error stored 6D FAS OKAY No Error stored 72 FRM OKAY 7 Error stored 9CBA 64 9CC4 64 9CC3 64 E594 64 A8C1 24 A8C3 24 A8B6 24 92 VIRTSG92 OKAY No Error stored A0 CCC OKAY No Error stored ================================================== ===============   Back to troubleshooting the no start condition. I used INPA (don't have ISTA) to read the CAS and found a few suspicious results. Need to investigate further but it looks like the immobilizer (EWS) hasn't detected the presence of a valid key. I'm new to INPA so I don't know what I should be seeing in some of the read controller functions. Next I'll connect to my 335D and compare readings.
|
|
#3
02-20-2016, 11:33 PM
|
|||
|
|||
|
Glad you got it cranking again.Yes it could well be the CAS.I am sure you will find the culprit soon...
|
|
#4
02-21-2016, 09:29 AM
|
|||
|
|||
|
If it cranks then the key is recognized. The DDE and CAS are VIN specific for EWS4 handshake - no synch.
What faults are stored now? Most importantly readout the memory from the DDE with the description and conditions.
|
|
#5
02-21-2016, 08:15 PM
|
|||
|
|||
|
I've found some conflicting info about EWS4. One POV is as you've noted - crank = EWS4 ok, no EWS4 sync - uses handshake. The other says that the CAS controls cranking and the DDE controls fuel so the CAS can recognize the key and allow cranking but if it doesn't return a valid value to the DDE based on the encryption key, it won't start the engine.
And there's more conflicting info! When I check the EWS status using the DDE73 script in INPA, I receive a "RELEASE OF IGNITION AND INJECTION ISSUED (CHALLENGE RESPONSE SUCCESSFUL)". Great but recently a single 4C18 error code appeared in the DDE error memory which indicates that there is a problem with the receipt of the terminal 15 based message from the CAS. I guess I believe the latter because it won't start! That fault doesn't appear when reading the errors via "functional jobs". No faults shown in that report, the CAS or EWS4 error report. Rheingold on the way...hope that helps.
|
|
#6
02-22-2016, 10:15 PM
|
|||
|
|||
|
Quote:
|
|
#7
02-22-2016, 11:36 PM
|
|||
|
|||
|
Quote:
You'll see a German error message after choosing the DDE73 script. It says there's a language mismatch. Ignore that. Click the left button (ok) and the first DDE73 menu should appear.
|
|
#8
02-23-2016, 01:20 AM
|
|||
|
|||
|
After reading some other posts it looks like INPA somehow disturbed DDE and EWS/CAS. Not my work but you can try this:I found it here.
1- Launch inpa 2- Select the engine 3- Choose the model of the engine 4- Select option: activate 5- Select option: EWS (Or CAS.not sure??) 6- Select option: reset ----> in progress ----> click ok 7- Back to the main menu, ie, back, back, back, and close the INPA 8- Open the inpa and check the errors. That errors should have gone by now. 9- Turn the ignition off, remove the obd connector and start your car. Last edited by ninja_zx11; 02-23-2016 at 01:28 AM.
|
|
| Bookmarks |
|
|
|
|
Hybrid Mode
