[allotherareused]

Hi guys,
I have problem with DSC, progman ruined this ...

Just to give you complete picture, let me explain what I've done in past and recently :
Car is 320D, year 2005, vin ending on KT70090, I've got it as used car

Like 1-2 year ago I've bough D-KAN cable and with this came some version of DIS/SSS. Once this is installed I wanted to do some things but that didn't has options, for example to turn on DRL. By supposing that this is version problem I've updated everything possible in this moment and that was done without the problem, I clearly remember that DSC is updated as well, BO and CDC aren't obviously because this is not MOST interface.

Recently I've bough OPS clone and by opening software (Progman) I've found more options.

Well, in many way to do some changes Progman was permanently insisting to update modules and finally I've let him update ... so there is moment when everything went wrong :

Couple modules are updated, as well MOST modules (BO/CDC) but DSC failed. This always said something like 1000 CoApi generic error.

As this is not working I've checked here how to do it using WinKFP, but this fail as well, actually, now even wipers didn't stop after failed update. Will try again SSS to find is this at least can stop ...
My last doubt is that DSC is replaced and not with orignal one and this is not writen in VO, but ... if this is ... how another software few years ago did update ? Or this one made problem actually ? Anyway, I can't use old progman anymore because new progman have updated VO.

And finally starting with relevant info if you can help me to understand what is wrong and few question :

Progman was insisting that version in DSC is "*" (unknown I guess ...) and should be 6778164
I've checked and this file is in folder DSC81 (.\E89\data\DSC81\6778164A.0pa)

I've checked what INPA have to say about this (better to put text than picture I guess ...):
Identification :
ADR: 29
Gen. name: DSC
JobStatus: OKAY
SGDB: DSC_87
GROUP: D_DSC
Part No.: 6778164
VarI: 4842
DiaI: 05B0
CiI: 7
HwI: 05
Sw-No FSV: 4.30.12

Based on this my questions are :
- Is possible than DSC is not original but replaced, VO not updated and that for wrong version is writen ? Why this file is in "DSC81" and INPA say this is "DSC_87" ?
.\E89\datan folder doesn't have any "DSC_87" file but do have couple "DSC_84" and "DSC_89"
- Where is phisically located DSC module on E90 so I can check is this is replaced or not (I guess there would be part number ..., INPA also said this is MK60) ?

- What are options to reset that to previous status ? As I said before : old progman version have updated and that were working, but this progman won't update anymore because new progman have changed VO:

if I remember correctly that was : E89X-08-09-530
now this is : E89X-10-03-501

can I in some way change this on the car in order to update DSC only or to tweak somehow old progman in order to accept working with this car ...

General computers knowledge is not a problem at all, my problem is because I don't know so much about how this software is working.

[Sensible_]

First, are you using an external power supply? If no, you need to use one as what you are describing could be symptoms of a low battery.

Second, ditch progman. Use Winkfp comfort mode and let it auto select the correct update. If it fails, post log here...

[cryptomit]

so much information at once.

Tell us what problems do you have with your car right now?

I assume that DSC, ABS lights on your dash and also wipers dont work, correct?

My suggestion is to download full sp-daten, import them to/by WINKFP and try comfort mode as sensible says. It must work.

oh, and btw. DSC isn't in VO, cause it is standard option in every e9x.

[makkan00]

E9x uses dsc_87 so progman is rubbish at what it did.
As said earlier by sensible, use winkfp.

[cryptomit]

exactly, Progman ruins ecus everytime someone is using it.

[allotherareused]

I have already downloaded SP_Daten 2.53.00x and my last try was with WINKFP. Also, using charger and this is around 13.7-13.8 V going down to 13.1 when wipers start (DSC programming start it ...).

As I said before, that was in progman first, progman ruin DSC but at least let it in "some" undefined state.

Last try was using WINKFP and this failed with LOTS of errors, I've took some SS but this is incomplete, will repeat in a hour and post here.

Anyway :
WHAT is then file for DSC_87 ? SP_Daten I've have in .\E89\data have folders:
DSC81
DSC84
DSC89
DSC890
DSC90
DSCM80
DSCM90


There is no DSC_87, I can't recognize this.


Also, some new info :
I've tryed to stop wipers at least, have started again progman (which mark now DSC as red option and don't want to update), but now progman said that
part number is 6774072
(and before were trying to update 6778164)

File search in complete E89 folder can't find any 6774072*.* file

Really have doubt is this is original DSC, would like to take look at phisical device in meantime but don't know where is ... whatewer, next update and winkfc log in like 2 hr ...

Tnx in advance guys

[allotherareused]

Originally Posted by Sensible_

First, are you using an external power supply? If no, you need to use one as what you are describing could be symptoms of a low battery.

Second, ditch progman. Use Winkfp comfort mode and let it auto select the correct update. If it fails, post log here...

The problem is what is correct update ? There are now bunch of unreliable part numbers or Zb.No, I am not sure is inpa showing correct Zb.No and where from read this, what if this is already updated with wrong number ?

[allotherareused]

Here are updates :

As first :
INPA now can't read address 29 and not showing DSC as existing in informations
INPA can't read 29 (DSC) in read UIF

Now WinKFP don't want to update this that seems, like this not exists :





I haven't done anything after first post but now this is different than errors I've has in last attempt.


I hope you notice that I've already tried with WinKFP and after this crash which STARTED and crashed, now wipers works after ignition. Progman in first attempts were claiming update to 6778164 but since progman don't see DSC (marked red) apparently expecting 6774072

As there is no file 6774072 I've tried following, just for test :




Just to clarify some details, I guess people with more experience may use that to help :

I really don't understand what are numbers 6778164 and 6774072, is this is part number or combination of partnumber and version ?

There is one file in E89\data\DSC81 folder named 6778164A.0pa, but I guess this is wrong one and this is root of the problem.
I wasn't able to find any file named 6774072*.*
There is file E89\ecu\dsc_87.prg but I can't find reference to this file, possibly force this to be writen to address 29 may bring car up ? Any idea how to ?


And finally, answer what is current car status :

Yesterday, after Progman update status was just you were guessing, lots of lights on but everything works, even I beleive ABS were working, just not DSC.

Yesterday, after WinKFP update and crash there is also steering wheel lock simbol, wipers just don't stop at all. I didn't tried to drive but I guess this is not good idea now

Today ... nothing new ... at some moment I've tried to disconnect battery and reconnect after 30 sec, nothing new ...

Error yesterday when everything went wrong was
2089 PADB switching programming mode failed 10FLASH, DIAGNOSE_MODE (ECUPM): ERROR_ECU_CONDITIONS_...
(I've took picture, don't have complete error ...)

[allotherareused]

I did some research online and looks like original part number is 6774072, that for car now when can't see DSC claim this is part. Anyway, this is wrong ...

http://www.realoem.com/bmw/showparts...34&fg=20&hl=23

That seems to be in folder DSC81 but somehow there is no reference to original version, who care, I've found version :

File DSC81.HIS

;Zusbauhistorie vom 26.09.2012 16:03
;SG-TYP: DSC81
;ZB-ALT ZB-NEU FREIKENNUNG
;--------------------------'
6769845,6769882,01,HB
6769749,6769845,00,HB
4026164,6760429,00,HB
6760429,6767565,00,HB
6767565,6767847,00,HB
6769081,6769749,00,HB
6768163,6769081,00,HB
6767847,6768163,01,HB
4025427,4026164,00,HB
4026172,4028431,00,HB
6769019,6769882,00,HB
6784764,6785573,01,HB
6769882,6769779,00,HB
6787837,6789301,01,HB
6771487,4035449,01,HB
4035449,6771799,00,HB
6769779,6771487,00,HB
6772214,6774598,01,HB
6771799,6772214,00,HB
6777513,6778164,00,HB
4028431,4028822,00,HB
6777159,6784764,01,HB
6776056,6780912,01,HB
6780912,6777159,00,HB
4028822,6769019,01,HB
6776053,6776056,00,HB
6778164,6776053,01,HB
6774598,6777513,01,HB
6789301,6862871,01,HB
6785573,6787837,01,HB

File DSC81.HWH

;Hardwarehistorie vom 26.09.2012 16:03
6776053A G , 6776056A E , 6780912A G , 6777159A E , 6784764A E ;
4026175A G , 4028433A E ;
6769019A G , 6769882A G , 6769779A G , 6771487A E , 4035449A G , 6771799A G , 6772214A E , 6774598A E , 6777513A G , 6778164A F ;
6768163A G , 6769081A G , 6769749A G , 6769845A E ;
6766117A G , 6767567A E ;
6785573A F , 6787837A E , 6789301A E , 6862871A F ;

As per this guy list, this is all same, just probably different control unit

http://www.ebay.com/itm/Reparatursat...item4628a035e2

Finally : I've checked version on control unit, metalic part is marked as 6771486 and control unit is 6771487. As per second file I've copied here, and following line this end on version in folder :
6769019A G , 6769882A G , 6769779A G , 6771487A E , 4035449A G , 6771799A G , 6772214A E , 6774598A E , 6777513A G , 6778164A F ;

Now I know that WinKFC have correct version and was trying to update correct version, only question is : if this is now not responding because this is "half updated" by some reason, what I can do ?

I still have hope, but ... in case everything goes wrong : is possible to replace control unit with used one ? I've read somewhere that WIN is saved and can't be changed, what are implications ?

[Sensible_]

Module probably in dead state now.

Maybe NFS Emergency flash can help in standard tools. If you make proper selections. But I think not

[allotherareused]

Originally Posted by Sensible_

Module probably in dead state now.

Maybe NFS Emergency flash can help in standard tools. If you make proper selections. But I think not

Well, if this is dead : what are implications if I buy used module ? I've seen somewhere that some modules have vin saved inside and can't be changed, question is, will this works and will raise some error ?

and, do you have some link how to do emergency flash ?

[Sensible_]

See here for NFS guide. http://www.e90post.com/forums/showthread.php?t=849434

VIN is stored in module yes, however only certain modules have protected VIN e.g. CAS / DDE / KOMBI. I don't think DSC is protected.

You can see all module VINs in INPA by reading UIF.

I don't think this is your problem.

Only other way to repair is to write a virgin dump to the module eeprom.

If NFS fails I'd just buy a used unit and fit that, change VIN with tool32, update with Winkfp and finally code to default with NCSEXPERT

[allotherareused]

At this moment have removed connecter (not so much space there ...), put some contact spray, connect again and try emergency update as in post.

BTW. just realized that all address in INPA is hexadecimal, there just aren't any adr as good example for this

Result ... same :

VIN WBAVC31016KT70090 29.12.2014 13:53


Emergency flash not OK

0x29 6778164
Programming not ok. Fatal Error
Error: Error 200: Error on reading HW-Number from ECU or logistic file Please check: Connection of ECU, Diagnosis line, ECU-Address, Logstic files
Error: Error 9000: PABD Debug-Info cabimain 4216 Debug
Error: Error 9000: PABD Debug-Info Ident 1276 Debug
Error: Error 7014: PABD DSC81 Ident 1282 ECU adresses are set - no answer from ECU (IFH-0009) but gateway o.k., no OPPS/Most 10FLASH, IDENT: IFH-0009: No response from controlunit
Error: Error 9000: PABD Debug-Info cabiexit 4276 Debug
Error: Error 7014: Error COAPI2.CPP coapiRunCabd 6 ECU adresses are set - no answer from ECU (IFH-0009) but gateway o.k., no OPPS/Most SG_IDENT_LESEN
Error: Error 7014: Error COAPIKF.CPP coapiKfGetHwNrFromSgD2 3 ECU adresses are set - no answer from ECU (IFH-0009) but gateway o.k., no OPPS/Most

Originally Posted by Sensible_

Only other way to repair is to write a virgin dump to the module eeprom.

I think this is doable for me, I have some basic knowledge and friend of mine is expert + have all needed hardware, we just at this moment haven't clear which cpu is there ... need to open it.

Now need to find schematic in order to do it faster. I Guess 6778164A.0pa is file to be written, correct ?

Another problem is : bleeding. Looking for option to remove control unit without hydraulic part but can't see screws like on this post.

http://www.e90post.com/forums/showthread.php?t=600491

Don't know how all of this will result, possibly experienced guys guide may help, will keep updating how this is going on and probably DIY of eprom writing if this result.

Some other things calling attention and would like to hear your comment about that guys :

If you see on my image that were using :
10FLASH.prg
080100DSC81.ipo

Where from exactly this thing is finding reference to that 2 files ? Asking because the 6778164A.0pa file in first line have :
$REFERENZ 0181R30F0C1A Z

but this is not the file that seems, anyone understand how exactly that thing works ?

[allotherareused]

Hi guys,

Thins thing is just dead. I've removed, separated and we have opened control unit but so far there is not so much to do because can't find online some starting point.

The idea was to put firmware directly to unit but by connecting this in lab we just can't made this working. Obviously, problem is connector and what is coming from the car. Following wiring diagram seems to be correct one, at least by couple pin I can recognize but when power is connected to terminal30, terminal 15, etc ... this is just not powering up in lab (oscillator is not working). When I connect this to the car oscillator is working (5.5 MHz). That state would be good starting point in lab, but ... some of 42 pin is missing (connector have 47 pin, I've connected 5 already).

As CPU is some TI chip with integrated CAN communication module the idea is to have this working in lab and to try to update trough CAN in LAB, but as I said, this is not starting, obviously, some wire is missing. That for my question is :

- Anyone have connector diagram or any idea why this is not powering up ? I've connected :
1,4,32 - 13.8 V
16,47 - Ground

- Anyone have doc. for this TI CPU ? This should be be some dual risc CPU, 100 pin, name is TMS471 (but somehow search end on MSP430xxx). I have found online some limited info about TMS470 but this is not enough (from this one I've found that CAN is integrated in CPU).

- As MK60 is used in many car : is this is in any car identified as address 0x29 or can be some other ? My guessing is that this just can't be dead, this just don't know anymore what is address to talk to CAN (that is why we want to connect this in lab, there is no noise/messages from other devices).


http://e30.leenw.com/Images/2006-05-...%20Diagram.PDF

[Sensible_]

Can you take a photo of PCB and upload here...

My advice is to forget CAN update and write Virgin dump to flash IC then program with winkfp...

[allotherareused]

I've left this in lab of friend of mine, we still can try few thungs, in meantime here is :

- 3 Photo I was taking to search for CPU name etc
- 1 Photo with connectors (we were checking CAN bus message, where is power ... all connector info I've got so far are wrong or incomplete)
- 1 extract from evolution/integration presentation, there is minor difference between mine and this one on right side, few components are not on same place but this is same thing.

Thing called MCU60 in this presentation is what you can find as TMS471 on photo. This according to presentation dual 32 bit RISC CPU and there is no documentation for this. This is high integrated specific cpu, without complete doc to understand what is doing which one pin we can't write anything to memory. To explain better :

This have separated memory for :
boot ROM
FLASH
RAM
ROM
and all of that except boot ROM exists as parity, everything is twice.

With this integration level and without documentation this is impossible to write anything to memory. Also ... there is some hardware problem, some component is dead or "almost" dead but can't find what.

This is designed to be fail safe, at this moment we even don't know why oscillator works once only in LAB. This is not transmitting anything to CAN and with oscillator not working I don't think this even listen. Powered up to 13.8 V current is 12 mA, once only when oscillator were working that were like 100 mA.

[allotherareused]

I may continue to play with this one in order to learn how thing works but don't want to waste time anymore, gona buy used DSC.

In another thread have asked about compatibility (http://www.e90post.com/forums/showthread.php?t=1074597) here is question about VIN.

I've found many post about VIN change using NCSExpert or WinKFP but none of them is complete, so question is :

Anyone have link to complete manual how to change VIN using either NCSExpert or WinKFP ? NFS emergency update will change VIN in update process ?

[Sensible_]

Originally Posted by allotherareused

I may continue to play with this one in order to learn how thing works but don't want to waste time anymore, gona buy used DSC.

In another thread have asked about compatibility (http://www.e90post.com/forums/showthread.php?t=1074597) here is question about VIN.

I've found many post about VIN change using NCSExpert or WinKFP but none of them is complete, so question is :

Anyone have link to complete manual how to change VIN using either NCSExpert or WinKFP ? NFS emergency update will change VIN in update process ?

You can change vin with tool32 or Winkfp.

For tool32 simply load your DSCXX.PRG and select job: 'fg_schreiben' then enter FULL vin, including checksum. (You can see full vin in NCSexpert, with VO.

For WINKFP, select comfort mode, then update ZUSB, select ECU family DSCXX (whatever version you have), go back, enter VIN - checksum not needed, then program ZUSB update. Winkfp will update the module and write new vin to UIF.

[allotherareused]

Originally Posted by Sensible_

You can change vin with tool32 or Winkfp.

For tool32 simply load your DSCXX.PRG and select job: 'fg_schreiben' then enter FULL vin, including checksum. (You can see full vin in NCSexpert, with VO.

For WINKFP, select comfort mode, then update ZUSB, select ECU family DSCXX (whatever version you have), go back, enter VIN - checksum not needed, then program ZUSB update. Winkfp will update the module and write new vin to UIF.

tnx. Only one problem I have for purchase now is to be sure what is compatible but I guess anything from hardware history list in this thread should works, probably anything from E87, E90, E91, ...