CD87 - PT CAN Communication Fault

[houtan]

I originally started this out as a PM with gbalthrop. I am copying my original PM and his reply as the start of this post. Hoping with help I can figure out this issue.

My original PM that explains the issue:
Hi there. Sorry for messaging you out of the blue. I have been doing a lot of research on my issue and came across your posts helping others with wiring issues. I am stuck and would really appreciate any help if you have time.

I have a 2011 135i, n55, DCT.

Quick background when the issue occurred:
On a leisurely drive home after getting a smog check (which is performed through the obd port in CA), my idrive starts to list DSC, DBC, servotronic, and hill start assist malfunctions. I scan with MHD and only see the code CD87 - PT CAN Communication Fault. Also, the windshield wipers turn on sometimes when the malfunctions show up on the idrive.

The car drives very sluggish when the codes pop up and the disappear one by one. Then they come back. The CD87 fault doesn’t clear with MHD.

Hooked up ista when I got home and couldn’t communicate with the jbe module. I have an M jbe module so I can have servotronic active on my M3 steering rack. Tried a few more scans with ista and things got worse. The idrive screen displayed an electrical malfunction and car wouldn’t start. So I thought, my used jbe (jbbf) went bad, and reinstalled my original.

Car ran great for a few days but the dbc, DSC, and hill start assist malfunctions came back (no servotronic malfunction because the 135i jbe doesn’t have it). Same behaviors as before when the codes show up. The appear and disappear, wipers turn on, throttle response is slow. I grabbed a log and the throttle stays at 24% when the accelerator is at 100.

I can communicate with the car though, so that’s good. One of items in the test plan says it’s most likely the DSC. I can clear all the fault memory and the modules turn green. But the code comes back. The detailed fault memory from ista is below. If I understand it correctly, most of the faults are due to the DSC.

My TPMS has been triggering before I get out of my driveway, which is odd. My tire pressures are on the lower side, around 25psi. But if I reset the toms at that pressure I am assuming it should be fine. I disconnected the RDC module last night and will code it out as a test. But I don’t think it is the issue. When I am stationary with the TPMS screen showing, I see the reset button flash on and off every few seconds, as if it’s looking for a signal.

One other thing I thought of is reflashing the DSC with winkfp, but I don’t think that is the issue either.

I have pictures and videos of most of the stuff I mention, but can’t add it in PM.

Sorry for the long message! Codes are below.

Thanks,
Houtan

gbalthrop reply:
Suggestions:
1) Use ISTA or INPA to view "Freeze Frame Data"/ Fault Details for any Fault Code that has "Voltage" FF Data. We're looking for any "Over-voltage" or system Voltage > 16.0V. That will "Scramble" bus communications between Modules. It often causes Wiper "Self-Activation". Restart usually restores proper function (momentarily).

2) You can use "Hidden Menu 9.00" to view System Voltage on the instrument cluster, or use Scan tool to display KL30 Battery Voltage or KL87 Main Relay voltage, while you drive, or while engine runs.
https://www.carsaddiction.com/articl...er-hidden-menu

3) Voltage Regulator brush failure/wear on rear of Alternator is most likely cause of Over-voltage.

4) There are other possible causes, particularly if issue began after shop connection to OBD II Socket. You can use ISTA to view wiring (SSP document) of "OBD" II Socket (just search OBD with filter for SSP only. Then examine/test OBD Socket for any obvious damage, particularly to the D-CAN sockets/wiring.

Everything points to a Bus Fault. Whether caused by Overvoltage, OBD II Socket damage, or other Bus wiring/connector fault is the question. I'm NOT an expert on Bus issues, or HOW to diagnose them. I would suggest seeing what ISTA says about Bus Diagnosis, & seeing if ISTA "Test Plan" can help diagnose any of those fault codes.

Since we can't attach anything to PM, please start a new thread on the E9x forum, so others can contribute/learn. Hope to learn from your efforts!
George

===Break====

One other thing i did not mention in my original description was after replacing my "M" JBE with my original, the car ran fine on a round trip 1.5hr drive.

Two of my OBD pins have been very weird since I took ownership back in 2013. Two pins, that turned out to both be ground wires, were always bent in my OBD dongle. So, I ordered a new OBD connector and two new pins, and was able to replace everything. I did all of this after I did the 1.5hr drive. After the repair, the codes came back immediately on my initially test drive and my obd dongle no longer worked. So I reinspected my work and saw that I put the switched 12v pin in the wrong location. I fixed that without issue. Also, i unplugged a module right behind the OBD port to get a liitle more slack (is that the FRM module right there?) and it appeared I did not seat the plug correctly so I fixed that as well.

Unfortunately, codes are still there. I am also attaching a couple of pictures from ista showing the codes and what it recommends I troubleshoot first, which is the DSC. Please let me know if you have dealt with a similar issue or have any suggestions.

I should’ve also mentioned, the ekp error is normal. I have a bpm4 so their is no EKP.

[houtan]

Tried to update the DSC today just to reprogram it in case something got corrupted. I decided to give the reprogram a try since I was able to default code the DSC beforehand. Well, Did not go very well. Gets to 1% then fails. Winkfp error log is below. from my novice eyes it appears it is failing because it cannot talk to the dsc but would love confirmation. Also, now the windshield wipers are constantly on. dang it!

[16:29:52.407] [2025-01-04] [--] 1020 Error COAPIKF.CPP coapiKfInit 31
[16:29:52.407] [2025-01-04] [--] File could not be opened for reading info.eng

================================================== ==============================
[16:30:08.328] [2025-01-04] [<WinKFP Tool 32B] 1040 Error COAPIKF.CPP coapiKfRefreshGdaten 10
[16:30:08.328] [2025-01-04] [<WinKFP Tool 32B] Error in file processing (general) info.eng

[16:30:13.160] [2025-01-04] [<WinKFP Tool 32B] 3027 Error KFINFO.CPP CKfInfo::Open 2
[16:30:13.160] [2025-01-04] [<WinKFP Tool 32B] INFO file not found konnte ..\data\konv.tmp\info.ger nicht öffnen

[16:30:13.163] [2025-01-04] [<WinKFP Tool 32B] 3027 Error KFINFO.CPP CKfInfo::Open 2
[16:30:13.163] [2025-01-04] [<WinKFP Tool 32B] INFO file not found konnte ..\data\konv.tmp\info.ger nicht öffnen

[16:30:13.164] [2025-01-04] [<WinKFP Tool 32B] 3027 Error KFINFO.CPP CKfInfo::Open 2
[16:30:13.164] [2025-01-04] [<WinKFP Tool 32B] INFO file not found konnte ..\data\konv.tmp\info.ger nicht öffnen

[16:30:18.186] [2025-01-04] [<WinKFP Tool 32B] 3027 Error KFINFO.CPP CKfInfo::Open 2
[16:30:18.186] [2025-01-04] [<WinKFP Tool 32B] INFO file not found konnte ..\data\konv.tmp\info.ger nicht öffnen

[16:30:18.188] [2025-01-04] [<WinKFP Tool 32B] 3027 Error KFINFO.CPP CKfInfo::Open 2
[16:30:18.188] [2025-01-04] [<WinKFP Tool 32B] INFO file not found konnte ..\data\konv.tmp\info.ger nicht öffnen

[16:30:18.189] [2025-01-04] [<WinKFP Tool 32B] 3027 Error KFINFO.CPP CKfInfo::Open 2
[16:30:18.189] [2025-01-04] [<WinKFP Tool 32B] INFO file not found konnte ..\data\konv.tmp\info.ger nicht öffnen

================================================== ==============================
[16:30:23.761] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:30:23.761] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.765] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ===> Wechsel zu FlashState: 0 545
[16:30:23.765] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.766] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info SetEcuAdr 1196
[16:30:23.766] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.769] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info EcuAdr : 0x29 1203
[16:30:23.769] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.775] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ===> Wechsel zu FlashState: 1 545
[16:30:23.775] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.780] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Interface-Typ : OBD 823
[16:30:23.780] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.781] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:30:23.781] [2025-01-04] [<WinKFP Tool] Debug

================================================== ==============================
[16:30:23.794] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:30:23.794] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.796] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info GetDiagProt 1104
[16:30:23.796] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.799] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ProtAnzahl : 5 1114
[16:30:23.799] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.800] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info DIAG_PROT_NR1 : BMW-FAST 1125
[16:30:23.800] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.802] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info DIAG_PROT_NR2 : D-CAN 1125
[16:30:23.802] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.804] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info DIAG_PROT_NR3 : KWP2000* 1125
[16:30:23.804] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.806] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info DIAG_PROT_NR4 : KWP2000 1125
[16:30:23.806] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.808] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info DIAG_PROT_NR5 : DS2 1125
[16:30:23.808] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.809] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:30:23.809] [2025-01-04] [<WinKFP Tool] Debug

================================================== ==============================
[16:30:23.817] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:30:23.817] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.818] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info SetDiagProt 1154
[16:30:23.818] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.821] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info DiagProt : BMW-FAST 1164
[16:30:23.821] [2025-01-04] [<WinKFP Tool] Debug

[16:30:23.822] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:30:23.822] [2025-01-04] [<WinKFP Tool] Debug

================================================== ==============================
[16:30:58.435] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:30:58.435] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.437] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ===> Wechsel zu FlashState: 0 545
[16:30:58.437] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.438] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info SetEcuAdr 1196
[16:30:58.438] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.438] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info EcuAdr : 0x29 1203
[16:30:58.438] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.442] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ===> Wechsel zu FlashState: 1 545
[16:30:58.442] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.447] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Interface-Typ : OBD 823
[16:30:58.447] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.448] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:30:58.448] [2025-01-04] [<WinKFP Tool] Debug

================================================== ==============================
[16:30:58.457] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:30:58.457] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.458] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Ident 1276
[16:30:58.458] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.506] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ===> Wechsel zu FlashState: 2 545
[16:30:58.506] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.506] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:30:58.506] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.513] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:30:58.513] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.514] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ZifBackupLesen 1658
[16:30:58.514] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.587] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:30:58.587] [2025-01-04] [<WinKFP Tool] Debug

================================================== ==============================
[16:30:58.654] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:30:58.654] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.655] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info FlashStatusLesen 4090
[16:30:58.655] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.656] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info IsNewHwNr : 1 4097
[16:30:58.656] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.667] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ProgrammierStatus : 12 4105
[16:30:58.667] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.668] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ProgTyp : 2 4168
[16:30:58.668] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.669] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ProgOrder : 2 4172
[16:30:58.669] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.670] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:30:58.670] [2025-01-04] [<WinKFP Tool] Debug

================================================== ==============================
[16:30:58.678] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:30:58.678] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.679] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info AifLesen 1399
[16:30:58.679] [2025-01-04] [<WinKFP Tool] Debug

[16:30:58.743] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:30:58.743] [2025-01-04] [<WinKFP Tool] Debug

================================================== ==============================
[16:31:01.169] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:31:01.169] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.170] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info HwReferenzLesen 1484
[16:31:01.170] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.203] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:31:01.203] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.207] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:31:01.207] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.208] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ZifLesen 1605
[16:31:01.208] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.323] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:31:01.323] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.326] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:31:01.326] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.327] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ZifBackupLesen 1658
[16:31:01.327] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.399] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:31:01.399] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.407] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:31:01.407] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.408] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info AifLesen 1399
[16:31:01.408] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.468] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:31:01.468] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.597] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabimain 4216
[16:31:01.597] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.598] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ===> Wechsel zu FlashState: 2 545
[16:31:01.598] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.599] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Programmieren 3037
[16:31:01.599] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.600] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Interface-Typ : OBD 823
[16:31:01.600] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.601] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info SGBD-Name : 10FLASH 3087
[16:31:01.601] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.602] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info SGBD-Origin : BMW TI-430 Drexel 3090
[16:31:01.602] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.603] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info SGBD-Revision : 2.15 3092
[16:31:01.603] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.604] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info SGBD-Package : 1.35 3094
[16:31:01.604] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.605] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-Modulname : DSC81 3097
[16:31:01.605] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.606] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-Revision : 8.01 3098
[16:31:01.606] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.607] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-Author : ESG EE-21 Maximilian Heller,ESG GmbH EE-21 Sven Kurzeder,ESG GmbH EE-21 Michael Knoebl,BMW EE-21 Stefan Jurchen 3099
[16:31:01.607] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.608] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-Comment : Data generated by Romain.Paris@contiautomotive.com 3100
[16:31:01.608] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.609] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-SGFamilie : DSC81 3103
[16:31:01.609] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.610] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-SG_MAXANZAHL_AIF : 2 3104
[16:31:01.610] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.611] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-SG_GROESSE_AIF : 18 3105
[16:31:01.611] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.612] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-SG_ENDEKENNUNG_AIF : 1 3106
[16:31:01.612] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.612] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-SG_AUTHENTISIERUNG : Symetrisch 3107
[16:31:01.612] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.613] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-ProgrammUndDaten : : FALSE 3108
[16:31:01.613] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.614] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-ProzessorTyp : Standard 3109
[16:31:01.614] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.615] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-AuffuellenSwitch : : FALSE 3110
[16:31:01.615] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.616] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-DynamischeMXBL : : FALSE 3111
[16:31:01.616] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.617] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-WiederaufsetzenBlockSwitch : : TRUE 3112
[16:31:01.617] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.618] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-WartenNachECUProgrammMode : 1 3113
[16:31:01.618] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.618] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-TestSchluesselAuthentisierung: : TRUE 3114
[16:31:01.618] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.619] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-WiederaufsetzenSwitch : : FALSE 3115
[16:31:01.619] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.620] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-SgInnenTemperaturLesen : : FALSE 3116
[16:31:01.620] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.621] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-SgPhysHwNrLesen : : TRUE 3117
[16:31:01.621] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.622] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-TesterPresentHandlingSwitch : : TRUE 3118
[16:31:01.622] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.623] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-DebugSwitch : : TRUE 3119
[16:31:01.623] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.624] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-DIREKT_MOST_PROG : : FALSE 3120
[16:31:01.624] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.625] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-BUSRUHE_START_PUNKT : DatenDownload 3121
[16:31:01.625] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.626] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PABD-BUSRUHE_ENDE_PUNKT : DiagnoseEnde 3122
[16:31:01.626] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.627] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info MOST: min. Telegrammzwischenzeit : 5 3123
[16:31:01.627] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.628] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info OPPS: benutzt : : FALSE 3124
[16:31:01.628] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.629] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info OPPS: MOST-Zugang benutzt : : FALSE 3125
[16:31:01.629] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.639] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info LoeschZeit : 255 3140
[16:31:01.639] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.640] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info SignaturTestZeit : 40 3141
[16:31:01.640] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.640] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ResetZeit : 2 3142
[16:31:01.640] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.641] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info AuthentisierungZeit: 0 3143
[16:31:01.641] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.652] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ProgrammierStatus vor der Programmierung : 12 3155
[16:31:01.652] [2025-01-04] [<WinKFP Tool] Debug

[16:31:01.652] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Reset 2388
[16:31:01.652] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.190] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info MXBL : 251 3199
[16:31:04.190] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.191] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ===> Wechsel zu FlashState: 3 545
[16:31:04.191] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.468] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Anzahl Datenbloecke: 16 3371
[16:31:04.468] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.469] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(0) Startadressse = 00:00:03:AC Anzahl Bytes = 00:00:00:60 3409
[16:31:04.469] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.470] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(1) Startadressse = 00:00:03:AC Anzahl Bytes = 00:00:05:44 3409
[16:31:04.470] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.472] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(2) Startadressse = 00:04:80:00 Anzahl Bytes = 00:00:02:10 3409
[16:31:04.472] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.473] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(3) Startadressse = 00:04:82:30 Anzahl Bytes = 00:00:00:10 3409
[16:31:04.473] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.474] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(4) Startadressse = 00:04:82:F0 Anzahl Bytes = 00:00:07:50 3409
[16:31:04.474] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.475] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(5) Startadressse = 00:04:8A:C0 Anzahl Bytes = 00:09:C1:B0 3409
[16:31:04.475] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.477] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(6) Startadressse = 00:0E:4D:80 Anzahl Bytes = 00:00:4B:A4 3409
[16:31:04.477] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.478] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(7) Startadressse = 00F:81:2C Anzahl Bytes = 00:00:00:1F 3409
[16:31:04.478] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.479] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(8) Startadressse = 00F:81:60 Anzahl Bytes = 00:00:00:22 3409
[16:31:04.479] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.481] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(9) Startadressse = 00F:82:81 Anzahl Bytes = 00:00:00:4D 3409
[16:31:04.481] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.482] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(10) Startadressse = 00F:83:C0 Anzahl Bytes = 00:00:00:01 3409
[16:31:04.482] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.483] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(11) Startadressse = 00F:83:C3 Anzahl Bytes = 00:00:00:12 3409
[16:31:04.483] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.484] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(12) Startadressse = 00F:836 Anzahl Bytes = 00:00:00:03 3409
[16:31:04.484] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.486] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(13) Startadressse = 00F:83:E0 Anzahl Bytes = 00:00:00:06 3409
[16:31:04.486] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.488] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(14) Startadressse = 00F:84:4B Anzahl Bytes = 00:00:00:73 3409
[16:31:04.488] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.489] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Block(15) Startadressse = 00:FF:FF:00 Anzahl Bytes = 00:00:00:08 3409
[16:31:04.489] [2025-01-04] [<WinKFP Tool] Debug

[16:31:04.490] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Gesamtanzahl Bytes= 00:0A:1D:2D 3421
[16:31:04.490] [2025-01-04] [<WinKFP Tool] Debug

[16:31:06.009] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ===> Wechsel zu FlashState: 4 545
[16:31:06.009] [2025-01-04] [<WinKFP Tool] Debug

[16:31:06.037] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info Ein RoutineNotComplete bei FlashLoeschen erhalten 2598
[16:31:06.037] [2025-01-04] [<WinKFP Tool] Debug

[16:31:10.254] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info FlashLoeschen erfolgreich beendet 2588
[16:31:10.254] [2025-01-04] [<WinKFP Tool] Debug

[16:31:10.255] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ===> Wechsel zu FlashState: 5 545
[16:31:10.255] [2025-01-04] [<WinKFP Tool] Debug

[16:31:11.463] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### 1. Datenblock schreiben: : FALSE 3550
[16:31:11.463] [2025-01-04] [<WinKFP Tool] Debug

[16:31:11.464] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### Datenblock schreiben : 0 3568
[16:31:11.464] [2025-01-04] [<WinKFP Tool] Debug

[16:31:11.465] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### Datenblock schreiben : 1 3568
[16:31:11.465] [2025-01-04] [<WinKFP Tool] Debug

[16:31:13.269] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### BlockEnd = TRUE 3648
[16:31:13.269] [2025-01-04] [<WinKFP Tool] Debug

[16:31:13.336] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### Datenblock schreiben : 2 3568
[16:31:13.336] [2025-01-04] [<WinKFP Tool] Debug

[16:31:13.700] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### BlockEnd = TRUE 3648
[16:31:13.700] [2025-01-04] [<WinKFP Tool] Debug

[16:31:13.743] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### Datenblock schreiben : 3 3568
[16:31:13.743] [2025-01-04] [<WinKFP Tool] Debug

[16:31:13.761] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### BlockEnd = TRUE 3648
[16:31:13.761] [2025-01-04] [<WinKFP Tool] Debug

[16:31:13.800] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### Datenblock schreiben : 4 3568
[16:31:13.800] [2025-01-04] [<WinKFP Tool] Debug

[16:31:14.684] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### BlockEnd = TRUE 3648
[16:31:14.684] [2025-01-04] [<WinKFP Tool] Debug

[16:31:14.767] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### Datenblock schreiben : 5 3568
[16:31:14.767] [2025-01-04] [<WinKFP Tool] Debug

[16:31:15.778] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info ### Buffer aufuellen 3655
[16:31:15.778] [2025-01-04] [<WinKFP Tool] Debug

[16:31:17.134] [2025-01-04] [<WinKFP Tool] 2084 PABD/CABD DSC81 FlashSchreiben 1847
[16:31:17.134] [2025-01-04] [<WinKFP Tool] Flash download failed 10FLASH, FLASH_SCHREIBEN (...): IFH-0009: No response from controlunit

[16:31:17.135] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info *** WAS WAS WAS WAS WAS *** 3708
[16:31:17.135] [2025-01-04] [<WinKFP Tool] Debug

[16:31:17.136] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info PrgStatus lesen 3723
[16:31:17.136] [2025-01-04] [<WinKFP Tool] Debug

[16:31:17.181] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info *** WAS: WASBuffer_1 schreiben *** 3802
[16:31:17.181] [2025-01-04] [<WinKFP Tool] Debug

[16:31:18.440] [2025-01-04] [<WinKFP Tool] 7054 PABD/CABD DSC81 FlashSchreiben 1850
[16:31:18.440] [2025-01-04] [<WinKFP Tool] clear flash done - no answer from ECU (IFH-0009) but gateway o.k., no OPPS/Most 10FLASH, FLASH_SCHREIBEN (...): IFH-0009: No response from controlunit

[16:31:18.441] [2025-01-04] [<WinKFP Tool] 9000 PABD/CABD Debug-Info cabiexit 4276
[16:31:18.441] [2025-01-04] [<WinKFP Tool] Debug

[16:31:44.455] [2025-01-04] [<WinKFP Tool] 7054 Error COAPI2.CPP coapiRunCabd 6
[16:31:44.455] [2025-01-04] [<WinKFP Tool] clear flash done - no answer from ECU (IFH-0009) but gateway o.k., no OPPS/Most SG_PROGRAMMIEREN

[16:31:44.456] [2025-01-04] [<WinKFP Tool] 7054 Error COAPIKF.CPP coapiKfProgSgD2 19
[16:31:44.456] [2025-01-04] [<WinKFP Tool] clear flash done - no answer from ECU (IFH-0009) but gateway o.k., no OPPS/Most

[houtan]

gbalthrop , thanks for the suggestions, please see my replies below.
Suggestions:
1) Use ISTA or INPA to view "Freeze Frame Data"/ Fault Details for any Fault Code that has "Voltage" FF Data. We're looking for any "Over-voltage" or system Voltage > 16.0V. That will "Scramble" bus communications between Modules. It often causes Wiper "Self-Activation". Restart usually restores proper function (momentarily).

Reply: I have grabbed multiple logs using MHD and the battery voltage always stays between 13.7 and 14.41. I have logs that are a couple of minutes long and there is never a spike. Is this sufficient to rule out the alternator?

2) You can use "Hidden Menu 9.00" to view System Voltage on the instrument cluster, or use Scan tool to display KL30 Battery Voltage or KL87 Main Relay voltage, while you drive, or while engine runs.
https://www.carsaddiction.com/articl...er-hidden-menu

3) Voltage Regulator brush failure/wear on rear of Alternator is most likely cause of Over-voltage.

4) There are other possible causes, particularly if issue began after shop connection to OBD II Socket. You can use ISTA to view wiring (SSP document) of "OBD" II Socket (just search OBD with filter for SSP only. Then examine/test OBD Socket for any obvious damage, particularly to the D-CAN sockets/wiring.

Reply: at the obd port, i found the CAN high and low pins and I get 60 ohms when I place a probe in each location at the same time. I believe that’s normal.

Everything points to a Bus Fault. Whether caused by Overvoltage, OBD II Socket damage, or other Bus wiring/connector fault is the question. I'm NOT an expert on Bus issues, or HOW to diagnose them. I would suggest seeing what ISTA says about Bus Diagnosis, & seeing if ISTA "Test Plan" can help diagnose any of those fault codes.

Reply: I believe it’s a wiring issue but not sure. I am hoping with help from the forum I can figure it out. It’s just weird it popped up out of the blue. My car has around 65k miles on it, is in socal, and doesn’t see rain.

I’m also unclear on the best way to test the wires. Do I get something like this?

https://a.co/d/6DEEAlJ

[houtan]

I have been studying this thread to learn how to troubleshoot my issue. One of the few threads that actually diagnoses an issue from start to finish. https://www.e90post.com/forums/showthread.php?t=2121740

I was able to pull the PT CAN wiring diagram using ISTA.

1. Do I test these wires at the connector for each module? Are the tests done with the connectors plugged in or removed from the module?

2. Am I looking for voltage, ohms, something else? One data point I can't find is the normal values for the tests. Is that information also in ISTA?

3. Do I need an oscilloscope?

In the meantime, I am going to get my car in the air and start removing panels to do visual inspections where possible. There is a location identified in the thread I linked which points to the wheel well that I want to look at just to rule it out.

[JoshS98]

Originally Posted by houtan

I have been studying this thread to learn how to troubleshoot my issue. One of the few threads that actually diagnoses an issue from start to finish. https://www.e90post.com/forums/showthread.php?t=2121740

I was able to pull the PT CAN wiring diagram using ISTA.

1. Do I test these wires at the connector for each module? Are the tests done with the connectors plugged in or removed from the module?

2. Am I looking for voltage, ohms, something else? One data point I can't find is the normal values for the tests. Is that information also in ISTA?

3. Do I need an oscilloscope?

In the meantime, I am going to get my car in the air and start removing panels to do visual inspections where possible. There is a location identified in the thread I linked which points to the wheel well that I want to look at just to rule it out.

I tested with the connectors detached and putting a tiny wire into the connector, my probes weren’t small enough to slide next to the wires themselves.

Checked for voltages to confirm power to modules and then ohms to confirm the pt-can loop didn’t have a break.

Since you’re seeing 60ohms at the OBD then the DSC and EKMS seem to both have solid wiring up to that. Each one has a 120ohm resistor, in parallel goes to 60ohm.

An oscilloscope would definitely help see if there is noise on the bus. Dont fully know how to use them so can’t advise on that.

[houtan]

I was able to test a few things tonight and would greatly appreciate any feedback from JoshS98, gbalthrop, NZE90, or anyone else!

First, I removed the fuse for the windshield wipers since they were constantly on after my DSC programming fail. Please let me know if this will cause issues in my troubleshooting.

I decided to start at connector X6021 which is in the white “DME” box on the passenger side of the engine bay. Most of my codes are DSC signals to the DKG and this connector is between the DSC and DKG in the wiring diagram.

Voltages by pin number at X6021 are:
5, PT CAN H, 2.581
6, PT CAN L, 2.34
7, PT CAN H, 2.583
8, PT CAN L, 2.34
9, 15WUP, 11.06
10, no wire
11, SP GND (ground for switch), 18.5
12, SP SIGNA (signal, shift paddle, 5.45

Next I took ohms for the following pins at X6021:
5 / 6, 60 Ohms back probing with connector in place, 120 ohms when testing with connector removed
7 / 8, 60 Ohms back probing with connector in place, 120 ohms when testing with connector removed

Next I verified ohms on CAN H and L at the OBD connector using the attached picture. Anyone know how to find the OBD connector wiring diagram in ISTA? I am not using the correct search terms because I can’t find the diagram.

OBD Test result:
CAN H / CAN L ,60 Ohms

Then I tested voltage at the EKP connector:
9, PT CAN H, 2.62
16, PT CAN L, 2.39

I believe all the results are normal, right? Where would you go from here? Check the connector at the transmission?

Finally, what do the splices look like? Actual connectors or some sort of butt connector or something like the PT CAN clear covers (picture below)?

Thanks again for your help. Hopefully I am going in the right direction!

[houtan]

I got through a lot of troubleshooting so I am going to start updating the thread in logical chunks.

Using the PT CANBUS wiring diagram from ista, I located each module to verify ~60 ohms at each connector. All connections had 60ohms. The only connector I did not test at the actual connector was for the transmission. It was going to take a lot of work to get to and the wiring seemed intact. What I did instead is verified 60ohms and connector x6021, which has two sets of canbus wires going from it to the transmission. Then I checked for continuity between the CAN HI and LOW wires going to the transmission and both checked out. So I called it good for now.

Now that it seemed like my wiring was good, i decided the next step was to or a Pico 2204a oscilloscope. While I waited for that to get delivered, i decided to try and flash my DSC again. It felt like the BMW gods were with me that night, because the flash worked! I was really confused because I didnt do anything to fix the error. Just to see what happens, i decided to put all my connections back to each module and start up the car crossing my fingers somehow the car is fixed. But nope, code came back after 5 or so minutes.

Next post i will share my testing with the pico 2204a.

I am also attaching a picture of x6021 and the CANBUS wires that go to the transmission.

[houtan]

After verifying my wiring appeared to be good, I decided to purchase a pico 2204a oscilloscope to continue my diagnosis. I had never used an oscilloscope before so I watched a lot of youtube videos to learn how to use one and also what to look for.

I connected the leads to the can H and L wires under the white dme box. Once i opened the sw and saw the waveforms it was clear something was causing an issue on the PT can network. The first picture below will be a snapshot of what i was seeing.

From there i decided to start unplugging modules, and the first one i removed was my BPM4 (my aftermarket ekp). once removed I walked over to my computer screen and bingo, my PT can network signals looked normal again! Wow. i was very surprised to say the least that my robust ekp upgrade was causing the issue. PT can H and L should start at 2.5v, from there H should go up to around 4v or less, L should go towards 1.0V or less., and they should mirror each other. What was almost impossible for me to figure out with just a voltmeter is I was seeing 60ohms over the canbus wires at the BPM4, which meant it was functioning. But the oscilloscope showed me the truth! haha.

I tested the ekp a few times. sometimes it seemed to cause PT Can bus issues immediately, sometimes it took four or 5 minutes. This behavior definitely had me second guessing if it was actually the real issue. But it was the only thing that made sense (in my head at least).

Thankfully, Torqbyte, the company that created the bpm4 and sold the circuitry to EOS, was very responsive. I worked with a gentlemen named Kev, and based on my oscilloscope results, he thought it was probably the BPM4. But not 100%. So I sent the BPM4 to torqbyte so they can investigate.

Torqbytes initial check showed the resistor was working. But a few days later I received another email from Kev saying the engineers were able to find the resistor had a bad or poor solder connection that was
causing an intermittent issue! The resistor was soldered by EOS during assembly of their version of the BPM4, and it was not done correctly. Whew, boy was i relieved.

The PT can bus terminates with a 120 ohm resistor at two locations, the DSC and the EKP (or BPM4 in my case). The intermittent connection on the BPM4 side was causing all of the issues on the entire network.

The BPM4 should be back in the mail today and in my hands by the end of the week hopefully. I still have a lot of coding to add back in that I had to remove during my testing, but I am looking forward to getting my car back on the road.

Also, I realized why I was able to reflash my DSC, which I mentioned in my prior post. My guess is the BPM's intermittent connection was working for the time period it took to reflash in winkfp, and I just got lucky.

First picture is PT Can bus with BPM4 connected. Second is with it disconnected.

[wheela]

Wow, good job figuring this out, and learning a new skill in the process! And awesome support by Torqbyte! Really glad you got this sorted out and shared the journey with us.

[houtan]

Thanks.

Just to close this one out, the issue was the resistor in my EOS bpm4. Torqbyte replaced the resistor and sent the unit back to me. Car is up and running again.

[turbohugh]

Originally Posted by houtan

Thanks.

Just to close this one out, the issue was the resistor in my EOS bpm4. Torqbyte replaced the resistor and sent the unit back to me. Car is up and running again.

Im having a similar issue with the PT-Can errors. I also have a torque byte. I purchased it 2 years ago and it's been running fine until lately I'm getting weird fluctuations in my fueling. I thought it was wiring or pumps then started searching for the pt-can bus errors and landed here. Thanks for all the hard work you've done I think I will reach out to Torqbyte and see if they can help.

[houtan]

Hopefully it helps. Did you purchase the unit from EOS or torqbyte?

[turbohugh]

Originally Posted by houtan

Hopefully it helps. Did you purchase the unit from EOS or torqbyte?

Long ago I got it from EOS. TorqByte sorted me out. Took a little while to ship but once they got it they identified the issue, fixed it, sent it back, and helped me sort the slope/configuration values to correctly run my dual pumps. Again I hope this helps anyone else that may have gotten a EOS controller. There may have been a few misconfigured or faulty units, and at least in my situation the symptoms were so hard to trace without very persistent testing. This is definitely a potentially expensive issue but luckily for me it worked out well, considering.
All the best and #Salute to the guys at TorqByte for sorting things out.