Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
Bricked KOMBI Module with WinFKP ?
25-01-2022, 16:04 PM,
Post: #21
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
Cable have wrong latency set, this make wrong communication with some ECUs
|
|||
25-01-2022, 16:41 PM,
(This post was last modified: 25-01-2022, 16:41 PM by JuiCe.)
Post: #22
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
(25-01-2022, 16:01 PM)Node Wrote: You killed CPU software, not EEPROM data. Have you checked COM emulation timing settings as mentioned in one of first posts? Yes I always run 1 MS port delay, port COM1. I installed BMW tools 212 and then i updated with SPDATEN V69 using BMW coding tools, ediabas/ncs then winfkp. So taking eeprom out was the wrong way of fixing problem ? I killed CPU software? Shouldnt work by OBD maybe with an ICom ? |
|||
26-01-2022, 05:29 AM,
Post: #23
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
|
|||
26-01-2022, 12:34 PM,
(This post was last modified: 26-01-2022, 12:36 PM by JuiCe.)
Post: #24
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
Here comes de eeprom dump from cluster.
I tried to unplug fiber inside the cluster to have a luck on OBD Can but here error comes |