Ошибка zcs ecu

Thread: NCS Expert Coding Issue (COAPI-2041)

Thread Tools

NCS Expert Coding Issue (COAPI-2041)

Hope someone could help. I have a 2009 E87 that I have been able to code successfully with NCS Expert in the past. Unfortunately the FRM module fried one day and the service shop replaced it with a new part. To make it work they had to program the car. That bounced up the I-level to E89X-18-07-520 (factory E89X-09-09-516). I assume some modules also got updated software.

My issue is that when I try to execute Read ECU or CODIERDATEN_LESEN for NFRM NCS Expert complains that COAPI-2041: Wrong ECU coding index A_PL2FRX: CODIERINDEX = 33h FRM2_E89.C08: CODIERINDEX = 08. I believe the car did not have index 08 in the past either since looking at my backup files the car used to have FRM3_E89.C32 when exported from NCS Expert.

Do I have wrong settings in my NCS Expert or do I need to get new daten files somewhere? Or how can I overcome this issue?

Then I do have another question as well. When I look at the ECU module details in ISTA, the Encoding Index does tie back to NCS Expert index once the ECU is read for some modules but not all. Should those be the same? Like for KOMBI ISTA shows encoding index 8 and NCS Expert pulls KMBI_PL2.C08 as well. Can I use this to determine if the module got flashed at the service? Or are these something completely different things.

Any help would be appreciated. would like to get some of my changes back.

I would start with looking for the newest possible FRM3_E89.C** coding file, which should be a fairly easy starting point, and then use Tool Set and the FRM3.prg, to look for the date of the last flash-programming session. The module is responding to diagnostic requests, so I would imagine it’s an NCS file issue.

Источник

Error in cabd look at cabi err and error log coapi 2041

Previously I had a module with corrupted EEPROM.

I have repaired the EEPROM using XPROG software and when installed back to the car, it started working.

So I wanted to:
Update with WINKFP + Change VIN.
VO Code
Default code to the car.

I have updated with WINKFP sucessfuly and VIN has been changed.
I went into NCS EXPERT and tried to read FRM module but it throws error:

Error in CABD!Look at CABI.ERR and ERROR.LOG

COAPI-2041: Falscher SG-Codierindex A_PL2FRX: CODIERINDER = 33h
FRMFA.C09: CODIERINDEX = 09
COAPI-2041: Falscher SG-Codierindex CODIERDATEN_LESEN

What could be the cause?

How would I do that without first reading FRM in NCS expert? Or am I confusing myself?

Is this correct steps I should do after WINKFP update:
NCS Expert using Expert Mode
1. Make sure the connection is good and that you have changed VIN prior to this step.
2. Load NCS expert using “Expertmode”.
3. F1
4. F3
5. Select chassis
6. Select module CAS (or other if other contains correct VO).
7. F2 (Enter FA)
8. Select chassis and enter VIN
9. Add the required VO’s and change date if required.
a. To change date, first delete it and add the required data e.g. #0409
10. Once done editing VO’s, select OK.
11. F6
12. Back
13. F4 and choose CAS.
14. F2 – change job to FA_WRITE or CODIEREN.
15. F3-execute the job.

Also, does FSW_PSW manipulation should be enabled?

Источник

Error in cabd look at cabi err and error log coapi 2041

в меню есть 2 опции но я не понимаю какая из них что делает

а по поводу обхода, просто снять електро привод и руками отмотать тормоза ?

Для того, кто НЕ слышал про существование ASAP, ты молодец. ну а кто форум не читал — вАще бог :facepalm:

Как в СА говорили: не доходит через голову — дойдет через руки и ноги :bad:

Удалось там докопаться до истины и победить данную проблему?

Столкнулся с аналогичной проблемой на E39 ’01 года, поставил светодиодную подсветку в номер.
По гуляющему в инете описанию по кодированию, параметров:
KALTUEBERWACHUNG_KZL-освещение номерного знака справа
KALTUEBERWACHUNG_KZL_LI — освещение номерного знака слева
в своём блоке LCM не обнаружил, у меня он LCM.C18
=======
рекомендованные
KENNZEICHENLI_PRUEF = ПРОВЕРКА подсветки номера сзади
FEHLER_KENNZ_LICHT = вывод сообщение о неисправности на приборку
отключают только вывод ошибки на приборку, а диоды в подсветке всё равно противно мерцают.
Какие ещё варианты возможны? Или мутить с конденсатором?

И никто (из знающих!) не будет. либо вкрячивай ручную регулировку, либо смирись.

Вот тут есть один «пользователь», так он тебе распишет на пару страниц, что надо изучать матчасть. и ведь будет прав, сам того не желая :biggrin1:

Copyright ©2000 — 2023, Jelsoft Enterprises Ltd.

Источник

Thread: NCS Expert error: «Error in CABD!»

Thread Tools

NCS Expert error: «Error in CABD!»

I’m trying to change the Daytime Running Lights setting to Active on my 2004 E60. So I went through the following steps:

• Hooked up my car using the modified VAGCOM cable to my laptop
• Started NCS Expert, used the «ZCS/FA f. ECU» button and it read my VIN and info from the car.
• Clicked back, NCS thought about it a while and created the FSW_PSW file.
• Made a backup of the WORK folder
• Copied FSW_PSW to FSW_PSW.MAN and changed DAY_RUN_LIGHT to aktiv.
• Selected Process ECU
• Selected the CAS ECU
• Jobname is set to SG_CODIEREN and shows CAS2.C05, A_E65CAS.IPO, CAS.PRG
• Clicked «Execute Job.»
• NCS worked for a while and then came back with an error message: «Error in CABD! Look at CABI.ERR and ERROR.LOG! COAPI-1043: error during processing CBD-file CAS2.C05»

I don’t know where CABI.ERR is but I found ERROR.LOG and I believe this is the section in question:

ERROR! Modul: CDH.C, Proc: CDHGetNettoDataFromCbd, LineNr: 01, ErrorNr: 1043

COAPI-1042: error during processing CBD-file
CAS2.C05

>> ERROR! Modul: COAPI2.CPP, Proc: coapiRunCabd, LineNr: 06, ErrorNr: 1043
SG_CODIEREN

Prior to attempting this, I updated my E60 files from Progman SSS v32. I ran laden.bat in the sp-daten-e60daten folder. Just to see if maybe it did apply the setting anyway, I re-ran the ZCS/FA f. ECU button but DAY_RUN_LIGHT still shows as nicht_aktiv.

I think that covers it. Any ideas?

Источник

Thread: NCS Dummy — Taking the expert out of NCS Expert

Thread Tools

[ 1995 Alpine White Coupe M3 Track Build | 1997 Techno Violet M3/4/5 | 2000 Imola Red M5 DINAN S1 | 2001 Phoenix Yellow M3 | 2009 Blue Water 335d ]

I still need to run NCS Expert to export the settings to the modules right? just double checking, making sure am not missing something =)

Correct. NCS Dummy is just a data interpreter for the module dumps.

Thanks for the confirmation!

One more question that I have seen the answer too before but can’t seem to find the post again, I been searching for about 2 hours no with no luck. so please excuse my ignorance.

Where do I find out what module# I have? if someone could provide the link to the thread that explains the steps I would be very appreciated.

If my memory serves me right it was something with SSS or something?

I use INPA 3x. Shift-F8 Special test, Quick Ident. And save it as a PDF.

But Im sure there are other ways. you can do it module by module in INPA as well.

I use INPA 3x. Shift-F8 Special test, Quick Ident. And save it as a PDF.

But Im sure there are other ways. you can do it module by module in INPA as well.

you sir rock, thanks

Are there any instructions on how to get the trace editor tab? I have searched but no luck..

haurelio: The trace editor is only available when you have a trace file loaded.

All I can say is WOW!

This is some amazing work and its truly appreciated that you did this for the community.

Im new here, and greatly appreciate the simplicity this provides!

now to order me a cable and start coding!

thank you for your reply and excuse my ignorance, But how do you load a trace file?

haurelio: First you must fetch a trace file from the car with NCS Expert. For instructions on how to do that, refer to chapter Reading «FSW_PSW.TRC» and «NETTODAT.TRC» trace files with NCS Expert in the topic start. Once you have the trace file, select the appropriate chassis and module in NCS Dummy (or rename the trace file to a «chassis-module-filename.trc» structure, like «E31-GM2.C25-FSW_PSW.TRC» to automatically select chassis and module) and load the tracefile in the «FSW/PSW or Nettodata trace» input box. You can either drag-and-drop the trace file over that input box or use the «Browse. » button to navigate to the trace file. After the trace file was successfully loaded the «Trace Editor» tab page appears.

thank you revtor. Finally was able to use it.. great piece of software.

I have an M3 KMB_E36.C27 and want to change the endvalues of RPM and Speed.

In KMB_E36.C27 it isn’t possible, in . C25 its possible.

Hope someone can help.

Last edited by Rockiii; 10-18-2012 at 04:26 PM .

Rockiii: Exactly what is the problem? Do you get an error message? Please be elaborate.

The Problem is, i can’t chance the value in c27.
Its not shown.
In c25 it would work.

Is it possible via disassembly and reassembly to put this values from c25 to c27?

I only need to chande the
«DZM-Skala Endwert»

Function keyword «DZM_SKALA_ENDWERT» exists in both «KMB_E36.C25» and «KMB_E36.C27» so there’s no need to use disassembly. If you mean the function is not shown in the NCS Dummy Trace Editor that’s probably because you started from a FSW/PSW trace file and the module has a custom value stored for that specific function. FSW/PSW trace files cannot represent custom values and NCS Expert simply omits these functions from the trace file. NCS Dummy cannot recover what is not included.

Solution? Don’t load the «FSW_PSW.TRC» trace file in NCS Dummy but the «NETTODAT.TRC» file. Nettodata trace files contain a lot more information than FSW/PSW trace files.

If you want to use custom values for «DZM_SKALA_ENDWERT» you will have to use disassembly of course.

Ok! Thanks so far. I will try this tomorrow.

Tried it today, it doesn’t work. I couldn’t find the DZM_SKALA_ENDWERT.

Also the Speedometer

Rockiii: Please post your «FSW_PSW.TRC» and «NETTODAT.TRC» trace files.

Hello,
I have little problem I do the steps with creating the FSW_PSW.MAN but I stil have this problem
COAPI-1020: Datei konnte nicht zum lesen geoeffnet werden
C:NCSEXPERBINsgfam.dat
Please i need help if someone know from where is this problem

kolbo: I think your NCS Expert installation is broken. You are probably missing files like «E36SGFAM.DAT» in the «NCSEXPERDATENE36» folder.

Thank you for quick replay Revtor.
I checked and your absolutely right I was missing all files. I reinstall Ncs and now seem that everything is OK.

Thanks for this excellent software. If you are still looking, attached are the files from a US model R52 cooper S vert 2007 w/xenons, HK (with DSP) US model passenger seat ‘digital scales’ and PDC. The KOMBI threw an error during the read with NCS expert.

Joylove: Thanks a lot for the trace files, Joylove. Much appreciated!

NCS Expert help, R52 KMB read/write error COAPI-2041: wrong ecu coding index

Asking this in here because a few experts might have this thread on subscribe.

I’m trying to use NCS expert to read and code a 2007 R52 Cooper S Kombi. All other modules work well using R50 daten, I don’t see R52 daten.

When I try to read the KOMBI the FSW_PSW.trc is created but NCS expert throws a fault:

>> ERROR! Modul: COAPI2.CPP, Proc: coapiRunCabd, LineNr: 06, ErrorNr: 2041
CODIERDATEN_LESEN

ERROR! Modul: CDH.C, Proc: CDHCheckIdent, LineNr: 03, ErrorNr: 2041
COAPI-2041: wrong ecu coding index
A_KMBR50: CODIERINDEX = 11h
KMB_R50.C06: CODIERINDEX = 06

NCS Expert selects the files KMB_R50.C06, A_KMBR50.IPO, KOMBII50F.PRG.

And when I try to open the KMB trace file with NCS dummy I get

Although I don’t need NCS Dummy to make the seatbelt chime change, I thought it’s error might be relevant to the NCS Expert issue.

Does anyone recognise this NCS Expert issue and know a fix please? Thanks :

Источник

Adblock
detector

Часовой пояс GMT +3, время: 01:32 .

Доброго времени суток Всем, уважаемые автолюбители!

В данной записи будет приведена — пошаговая инструкция по кодированию BMW, при помощи NCS Expert Tool и NCS Dummy.
Понятно, вроде инструкций во всемирной паутине валом, но, вопросов в личку все равно приходит достаточное количество, о различных ошибках, вопросах о параметрах, да и записей на драйве2 с вопросами по кодированию, просьбе о помощи и т.д. выше крыши. Поэтому я и решил создать так сказать подробный пример, пошаговую инструкцию по этому вопросу, чтобы по 10 раз на неделе не расписывать одно и тоже. Это так же даст понять, что по такому принципу, никаких ошибок и неудачных попыток не будет. Нет, я не против вопросов в личку, на сколько возможно стараюсь помочь Всем и каждому.
Как и раньше, кодирование будет осуществляться в программе NCS Expet Tool, а так же в данной записи приведу пример работы с NCS Dummy, которого считаю отличным помощником при кодировании BMW, и всем настоятельно советую этим помощником пользоваться. Последние версии программы NCS Dummy Вы можете отслеживать и обновлять здесь. Ссылка на скачивание (1.7 МВ), версия 0.6.0.7, нужно распаковать архив, программа не требует установки, просто запускаем для работы файл NcsDummy.exe. В архиве так же присутствуют файлы профиля для NCS-Expert, их нужно скопировать в папку профилей NCS-Expert, т.е. по пути c:NCSEXPERPFL, потом соответственно загрузить в NCS-Expert.
Если хотите узнать о других полезных программах для работы с ЭБУ BMW, то Вам сюда.
При работе с ЭБУ, стоит так же учитывать, что весь софт на ПК настроен и установлен верно, да и я об этом не раз упоминал, что правильно настроенный софт, это уже большая часть успеха, потому как большинство ошибок при работе с ЭБУ, как раз по этой причине и мешают нам работать.

Итак приступим!
Приведу пример по кодированию, путем активации двойного мигания аварийкой, на кузове е39.
— Подключаем кабель к авто (на моем примере используется k+dcan), который может себе позволить каждый, включаем зажигание (в общем ничего нового:), запускаем программу NCS EXpert Tool, выбираем строку загрузки профиля:

Тут прошу заметить, что профиль я загружаю, который был вместе с программой NCS Dummy, потому как в процессе буду работать с этой программой:

Далее выбираем строку VIN/ZCS/FA:

Затем выбираем строку ZS/FA из ЭБУ :

Выбираем кузов требуемого авто, в моем случае е39:

Выбираем ЭБУ, из которого будет считан так называемый контрольный шифр ZCS или FA, в моем случае ZCS. Разницы нет из kmb или ews считывать zcs, но рекомендую VIN брать из EWS, т.к. в приборке хранятся только последние 7 знаков.

В итоге получаем номер кузова авто (VIN) и тот самый шифр ZCS.
Данные ZCS раскладываются на 3 составляющие:
1. GM — содержит информацию о кузове, о рулевом управлении, модели двигателя и т.п.
2. SA — опции установленные в машине
3. VN — список версий номеров ЭБУ(типа драйверов) для кодировки
В моделях свежее, комплектация, опции, блоки и оборудование записано в коде FA.

После считывания и идентификации авто, нажимаем кнопку «Назад», затем выбираем «Кодирование ЭБУ», выбираем из списка необходимый блок, в моем случае LCM, нажимаем кнопочку «Базовые функции», выбираем строку «coapiReadSgGetFswPsw«:

В следующем окошке видим маркировку ЭБУ и его кодировочный индекс, в моем случае LCM.C15, эту цифру запоминаем, так как она нам понадобится для Dummy. Нажимаем «ОК» тем самым подтверждая работу с блоком.

Внимание! Если необходимо поправить/отредактировать кодировочный индекс блока на «правильный», то правим его в данном окне, перед подтверждением команды «ОК». Дабы не было в дальнейшем ошибки о несовпадении кодировочного индекса. Зачастую редактировать индекс блока необходимо после его замены. Как например я описывал в записи замены блока света LCMII на LCMIII, соответственно изменился и индекс с 15ого на 18ый, но, так как шифр комплектации остался прежним, то и после считывания zcs из блока ews, индекс блока света будет считываться заводской(т.е. 15ый), даже после установки нового блока с индексом 18. Вот, я просто меняю цифру на 18, и продолжаю работу с блоком, никаких ошибок не будет. Данный вопрос можно решить редактированием шифра ZCS, но, есть вероятность, что обновляя шифр под блок света, мы можем и обновить индексы кодировочные других блоков, что соответственно приведет к другим ошибкам и предупреждениям, поэтому, можно шифр не редактировать, а просто вбивать вручную!

Все это мы сделали для того, чтобы создать файл TRC, со списком параметров требуемого ЭБУ, файл FSW_PSW.TRC создался в папке WORK программы NCS Expert, вот:

Можно было воспользоваться операцией «CODIERDATEN_LESSEN», кому как удобнее, смысл тот же.
Далее можно редактировать файл TRC вручную, сохранять с заменой в файл MAN (рабочий файл), но, я лично пользуюсь утилитой NCS Dummy, о которой упоминал ранее, функционал программы очень большой, а самое главное, подробно расписаны и переведены на английский язык определенные строки и параметры, описаны функции, легко разобраться с помощью переводчика, какая строка за что отвечает, так же можно пользоваться поиском, при поиске определенной строки. Интерфейс удобен и понятен, не составит труда разобраться желающим.
Не закрываем NCS Expert, запускаем программу NCS Dummy. Далее:
1) выбираем кузов авто, в моем случае е39;
2) выбираем номер блока из списка (та самая цифра, которую мы получили при создании файла ЭБУ — LCM.C15), можно конечно загрузить маркировку блока через фильтр Dummy, но разницы нет, кому как удобнее;
3) Выбираем файл FSW_PSW.TRC, который создали ранее;

В принципе в программе по стандарту, указан путь папки WORK, где находится trc файл.
Тем самым загрузили параметры и опции созданного файла в программу Dummy, видим список параметров, с описанием и пояснением.
Так как я собрался активировать функцию — двойного мигания аварийкой, то в поиске по параметрам вбиваю слово «WARNBLINKER»:

По умолчанию стоит «einfachimpuls», чтобы активировать двойное мигание меняем на «doppelimpuls». Если нам необходимо что то еще, то по тому же принципу ищем необходимые строки и меняем на требуемые параметры.
Далее экспортируем файл с измененным параметром в папку WORK программы NCS Expert, нажимаем кнопочку «Export FSW/PSW», затем выбираем строку «Export FSW_PSW.MAN»:

Обратим внимание, что тем самым мы заменили пустой рабочий файл MAN, с измененными требуемым параметрами.
Переключаемся на программу NCS Expert, меняем операцию на «SG_CODIEREN», при помощи кнопочки «Смена операции»:

Проверяем чтобы была запись «JOBNAME =SG_CODIEREN», и нажимаем «Кодировать ЭБУ». Если все сделали правильно и успешно, то будет запись «Код-ние окончено. ОК»

Закрываем программу, отключаем шнурок, радуемся проделанной работе:

Прошу обратить внимание, что программа у меня русифицирована, в версиях с другими языками, строки будут отличаться!
Список полезных опций и параметров, которые еще можно активировать, я описывал в этой записи. По их активации — работаем по тому же принципу.
Это так сказать простейшая опция для примера, на самом деле возможности и хитрости безграничны. Программа Dummy, позволяет так же рассчитывать и создавать свои значения в некоторых параметрах, например интервал ТО, и так далее и тому подобное.

Данной записью, я хотел лишь помочь, и показать, что без каких либо проблем и ошибок можно работать с ЭБУ, с учетом правильного настроенного софта и самого главного времени и желания. Где скачать и как правильно настроить софт, читаем здесь. У меня стоит сборка как раз из этой статьи, проверено не на одном ПК. Буду рад если кому либо помог, для начинающих полезная инструкция.

Всем спасибо за внимание, до встречи!

1. NCS Expert help — ‘Central coding key is faulty’ ideas?
   

   Hey everyone,

   I’m attempting to use NCSexpert to do some minor coding on my E38. It’s 1995 build date 730iL. The problem I’m running in to is that after I’ve loaded my profile (Revtors expert profile FYI) I cannot read anything from my car. Here’s what happens;

   1) I click ‘VIN/ZCS/FA’ (F1)
   2) I click ‘ZCS/FA f. ECU’ (F3)
   3) I choose my chassis (E38)
   4) This is where my problem lies

   I have two options — EWS or IKE. If I select EWS, it gives me the following error;

   Central coding key is faulty
   COAPI-1081 Faulty GM-Key C1
   FFFFFFFFy

   If I try and use the IKE, it says the following;

   VIN is faulty
   COAPI-2020 : no answer from ECU
   IFH-0009: NO RESPONSE FROM CONTROLUNIT

   Any ideas what’s going on? I don’t think it’s even reading my VIN properly, as at the top of the page it shows ‘FG WBA0000000DG94362Q’ which is obviously completely wrong as it’s put a bunch of 0’s in place of letters and numbers, and added a Q to the end. But I’m basically stumped now… ADS cable by the way, set to ADS in EDIABAS.ini. If I set it to STD:OBD, I just get a transmission disturbed message, so it’ll only work in ADS mode with NCS I assume.

   I have also tried NCSexpert 3.0.8 and 3.1.0 and both do the same thing. As per an old thread I saw where Iceman mentioned that NCS 3.0.8 and 3.1.0 can be picky about what EDIABAS version you use, I have now also tried both versions of NCS on both versions of EDIABAS (6.4.3 and 6.4.7). All combinations give me the same errors posted above.

   *edit* And here’s something else that may or may not be of any relevance. If I fire up INPA and scan my ‘Central Body Electronics ZKE’, it gives me a warning saying «Version mismatch, malfunction possible» then proceeds to do some kind of manual check of ‘PM modules’ whatever that is. After a minute it comes up fine and I can view all my coded ZKE options like alarm warnings, light check warnings etc etc… Does this help point to a potential cause for all my problems? I’m beginning to wonder if someone hasn’t screwed around with this car in the past some time and done some damage here.

   What on earth is wrong with my car??

   Last edited by Sobek; 01-25-2014 at 12:55 AM.

   

   ---

2. Could be several things. Port settings. Interface settings. EDIABAS version. Faulty install. Interface or the CAR.

   What interface?

   Check your email.

   95 840Ci, Calypso Red/Silver, 83k — 99 740i, Black/Black, 185k, Alpina Mods — 01 740i, Titanium/Silver, 40k, Sport Pkg
   Complete Turnkey Diagnostic/Programming systems available…PM for details.
   
   http://www.8Coupe.com — Please register, spot, and help the project.

   ---

3. Thanks. As we discussed, I’ve corrected the port settings as per the guide (FIFO buffers both on 8, no flow control, 9600 baud etc etc), but still no go. I’m using an ADS interface cable, EDIABAS version 6.4.7 (though I have also tried 6.4.3 and had the same results). NCS version 3.1.0, but as before I have also tried 3.0.8 and tried mixing different NCS versions with different EDIABAS versions, always the same errors as above.

   I can access, scan and read all information for both the EWS and IKE modules perfectly fine through INPA — analog and digital readings, ident information, model, build date, code numbers etc etc, it’s all there without issue. Yet for whatever reason, NCS won’t do its job. It still gives me that «Central coding key is faulty» error on the EWS, and «VIN is faulty — no answer from ECU» for the IKE. I’ve triple checked and all module files for the E38 are present in my NCS install — hell another member even sent me his full functioning NCS install with way more modules than my stock one ever had, and even that doesn’t work. I also always use Revtor’s expert profile, though I have also just tried the standard ‘Expertmode’ profile too.

   This is doing my head in. Clearly the modules are fine if INPA can read them and scan / clear errors and so forth, so what’s the deal with NCS? I’ve followed everything to the letter, and even tried totally wiping ALL of my NCS/INPA/EDIABAS installs and starting from scratch, with the same results.

   

   ---

4. check the ncs profil-editor ,all setting car-keymemory, etc,etc.

   ---

5. I use Revtor’s expert profile… If I edit that, I can see that all of the options are enabled as they should be. Something tells me it’s not a profile issue, NCS is clearly communicating with the car, it’s just as if the information is getting confused somewhere along the way. I just can’t understand what the problem is. Wonder if it’s something to do with my car being a 730, not exactly common and possibly not a mix of modules that NCS is optioned for? Not sure.

   

   ---

6. had the same problem on my e46, turned out the coding key on the car was actually faulty. Had to modify it and recode the GM, and EWS modules. Basically you have to manually enter your vehicle FA based on your build options, then write those files to your car. It can all be done in NCS expert, but i dont remember the exact steps.

   edit, just realized your car is ZCS coding, not FA. steps are similar, but you will need to create the 3 ZCS codes. If you give me your vin number(along with any retrofits you have done electronically, IE nav, different steering wheel, etc) i can create them for you.

   Last edited by legoman67; 01-24-2014 at 02:20 PM.

   Current:

   — 09 335i MSport, FBO.
   — 98 Euro M3, Estoril Blue
   — 04 M3, Carbon Black, 6 Speed Coupe
   — 06 M5, Black on Black, Full Leather.
   — 73 3.0CS, Tagia Green, 5 speed M30b35 converted

   Ex’s:

   1984 325e, 1988 325IX, 1992 525I, 1995 540i/6, 2002 330i, 2005 330xi, 1992 850i, 2003 330i #1, 2003 330i #2, 2002 330ci, 2004 330ci, 2007 328CI, 2007 335i, 2001 M3, 2006 M5 6 speed

   ---

7. Im thinking ediabas.ini settings are off…

   ---

8. Originally Posted by legoman67
   

   had the same problem on my e46, turned out the coding key on the car was actually faulty. Had to modify it and recode the GM, and EWS modules. Basically you have to manually enter your vehicle FA based on your build options, then write those files to your car. It can all be done in NCS expert, but i dont remember the exact steps.

   edit, just realized your car is ZCS coding, not FA. steps are similar, but you will need to create the 3 ZCS codes. If you give me your vin number(along with any retrofits you have done electronically, IE nav, different steering wheel, etc) i can create them for you.

   Sounds good, my VIN is WBAGJ22090DG94362. Are you able to track down the procedure for writing the new codes? Also, what are the risks involved? Would hate to brick something important over some flashing lights and alarm sounds haha. Oh and I have no electrical retrofits, just cosmetic stuff and general maintenance (750 wood bits, replaced old sensors and such). Probably the only thing ‘electrical’ I changed was to replace my TV module with a newer version that gave me the extra menu options and supports 16:9 should I ever get that some day.

   Let me know how you get on and we can go from there

   Originally Posted by purplecty
   

   Im thinking ediabas.ini settings are off…

   Thanks mate, got your message.

   Last edited by Sobek; 01-24-2014 at 09:35 PM.

   

   ---

9. Something is out of whack. Your getting TWO different errors. One module the VIN is hosed, and the other seems like the ZCS doesnt match. Show me a quick test Ident dump of your modules.

   95 840Ci, Calypso Red/Silver, 83k — 99 740i, Black/Black, 185k, Alpina Mods — 01 740i, Titanium/Silver, 40k, Sport Pkg
   Complete Turnkey Diagnostic/Programming systems available…PM for details.
   
   http://www.8Coupe.com — Please register, spot, and help the project.

   ---

10. Originally Posted by Sobek
    

    Sounds good, my VIN is WBAGJ22090DG94362. Are you able to track down the procedure for writing the new codes? Also, what are the risks involved? Would hate to brick something important over some flashing lights and alarm sounds haha. Oh and I have no electrical retrofits, just cosmetic stuff and general maintenance (750 wood bits, replaced old sensors and such). Probably the only thing ‘electrical’ I changed was to replace my TV module with a newer version that gave me the extra menu options and supports 16:9 should I ever get that some day.

    Let me know how you get on and we can go from there

    Thanks mate, got your message.

    First try to read your ‘IKE’ module as you have been doing, it should show you
    somewhere on the screen the exact one you have(IE: IKE_E38.Cxx, x’s will be numbers) Write down this number.

    Ok, open NCS expert and load revtor profile
    hit f1 for ‘VIN/ZCS/FA
    f1 again ‘Enter ZCS’
    select E38
    Enter your vin number WBAGJ22090DG94362
    select the ‘calculate checksum’ box, and hit ok
    Enter the next 3 numbers as follows:

    GM: 44221010
    SA: 00000A418B004008
    VN: 00000002A8

    also select the ‘Calculate checksum’ box and click ok.

    Now you are ready to program, hit F6 back. (IMPORTANT! MAKE SURE YOUR FSW_PSW IS BLANK AT THIS POINT!!)

    Now choose ECU, ‘IKE’
    select the correct one based on the numbers you wrote down in the beginning.
    hit f1 ‘change jobs’, and select SG_CODIEREN
    hit f2 ‘Execute job’
    Wait for it to finish

    You should be done, now you can go back to the main menu, and attempt to read the data like normal. When you are asked to choose an ECU under ‘ZCS/FA f.ecu’ make sure to select ‘IKE’

    You can also do this programming using GT1 or DIS using those 3 numbers i gave you. If you go into ‘Programming’ then recode car.

    Last edited by legoman67; 01-25-2014 at 01:21 AM.

    Current:

    — 09 335i MSport, FBO.
    — 98 Euro M3, Estoril Blue
    — 04 M3, Carbon Black, 6 Speed Coupe
    — 06 M5, Black on Black, Full Leather.
    — 73 3.0CS, Tagia Green, 5 speed M30b35 converted

    Ex’s:

    1984 325e, 1988 325IX, 1992 525I, 1995 540i/6, 2002 330i, 2005 330xi, 1992 850i, 2003 330i #1, 2003 330i #2, 2002 330ci, 2004 330ci, 2007 328CI, 2007 335i, 2001 M3, 2006 M5 6 speed

    ---

11. Originally Posted by IcemanBHE
    

    Something is out of whack. Your getting TWO different errors. One module the VIN is hosed, and the other seems like the ZCS doesnt match. Show me a quick test Ident dump of your modules.

    You mean the INPA quick ident test correct? I can do that in an hour or two once I’m back home.

    Originally Posted by legoman67
    

    First try to read your ‘IKE’ module as you have been doing, it should show you
    somewhere on the screen the exact one you have(IE: IKE_E38.Cxx, x’s will be numbers) Write down this number.

    Thank you for that, I was doing a little reading in the mean time and the procedure pretty much matches what I was expecting. The problem there is that I am almost certain the IKE module number never shows up anywhere (in NCS Expert at least, as soon as I click to connect to the IKE or EWS, I just get the errors above and nothing else changes). I’m guessing INPA won’t be any good for this as you’re looking for a module name / number that’s in a naming format used by NCS, right?

    I’ll still give it a go but… Given that it can’t even communicate with the IKE at all, I’m thinking I may be unable to complete the ZCS writing to it given I can’t get the specific module number. We’ll see!

    

    ---

12. Alright guys I’ve been out and having a play with it. I’ll start first with the information you wanted Ice;

    INPA-PrintFile — id_daten.pdf

    Notice it still has that odd looking VIN number for the EWS. Next, I thought I’d take another look at the EWS information in INPA, and this is what I see;

    dwgg.jpg

    Again, same odd VIN, but you can also see it reporting that FFFFFFFy for the C1, C2 and C3 options at the bottom. Next, a few days ago when I started all this, I cleared a bunch of old codes stored in the EWS. Mostly sporadic errors and those and gave no information at all. However today, this one code has shown up;

    nb0p.jpg

    Anything interesting or just random nonsense? And lastly legoman, here is exactly what I see when I try and read my modules;

    EWS;

    wjgc.jpg

    IKE;

    6oma.jpg

    Nowhere in NCS, either on that screen or any other, does it show me any module numbers that I could use to identify which one to code too. The only thing that does change is the little ‘Nrcl-no’ in the top right, which from what I can gather relates to the version of the daten files I’m using right?

    Let me know what you guys think

    

    ---

13. Module dump looks fine except for the VIN on the EWS. Code the VIN to EWS. Then Id code the ZCS to the car.

    95 840Ci, Calypso Red/Silver, 83k — 99 740i, Black/Black, 185k, Alpina Mods — 01 740i, Titanium/Silver, 40k, Sport Pkg
    Complete Turnkey Diagnostic/Programming systems available…PM for details.
    
    http://www.8Coupe.com — Please register, spot, and help the project.

    ---

14. You might have to lay this one out clearly for me as I’m still brand new with NCS sorry. You wouldn’t suggest coding both the VIN and ZCS data above directly to the EWS? I thought I HAD to add the ZCS data even when just trying to code the VIN on the EWS or IKE (just from what I’ve been able to view online and Youtube etc). The other thing is, as I can’t read either the EWS or IKE, I can’t get the specific module versions as per the list in NCS. However I note that in NCS Dummy it only shows 3 EWS modules for the E38; EWS.C01, C02 and C81. Assuming they’re in production order, I would guess my EWS is .C01 as it’s one of the earlier 04/95 build dates?

    Just need to be clear on exactly what steps to take, last thing I need is to cripple something just because I didn’t ask the obvious questions

    Last edited by Sobek; 01-27-2014 at 04:51 AM.

    

    ---

15. Do you have DIS? If so, trying doing the recoding in that using the ZCS codes i gave you. It wont need module numbers

    If not, you could try just picking one and going with it, worse case is its wrong and you have to do it again with the next one. try C01 on the IKE. Its pretty hard to brick modules with NCS because all the info your supplying is just supplementary settings.

    Last edited by legoman67; 01-27-2014 at 05:51 PM.

    Current:

    — 09 335i MSport, FBO.
    — 98 Euro M3, Estoril Blue
    — 04 M3, Carbon Black, 6 Speed Coupe
    — 06 M5, Black on Black, Full Leather.
    — 73 3.0CS, Tagia Green, 5 speed M30b35 converted

    Ex’s:

    1984 325e, 1988 325IX, 1992 525I, 1995 540i/6, 2002 330i, 2005 330xi, 1992 850i, 2003 330i #1, 2003 330i #2, 2002 330ci, 2004 330ci, 2007 328CI, 2007 335i, 2001 M3, 2006 M5 6 speed

    ---

16. Actually I do have DIS working, SSS didn’t work because I’m using ADS, but I was able to do diagnostics with DIS. Wasn’t aware it could do any coding… I’ve got v57 on my laptop I believe, hope that won’t be a problem. I’ll do a little reading online and see what steps are required to code the ZCS in DIS — if I can’t progress any further with NCS just yet, then it can’t hurt to try.

    Also, with regards to NCS, you mean to say that even if I code to the IKE using the wrong module number (C01 instead of C02 for example) it shouldn’t stop the module from working altogether? I figured it would at the worst case just result in some missing features or maybe error codes. I’m more than happy to go down that path in this case.

    I take it that if I successfully code the new ZCS to the IKE, that I can basically just ignore the erroneous data in the EWS and only use the IKE for coding / VO-reading needs from here on out? Thanks again guys.

    

    ---

17. DIS 57 cant do coding tou need DISv44 and its coding is limited…

    ---

18. Ahh I see. I do have a DIS v44 image, would only take 5 mins to switch over to it. I’ll give it a run tonight, it either works or it doesn’t.

    But still just to confirm — once I’ve sorted out coding the VIN and/or ZCS to the IKE, I can just ignore the EWS for all future work, correct?

    

    ---

19. Once you get the VIN corrected in the EWS, use the IKE to code the ZCS.

    95 840Ci, Calypso Red/Silver, 83k — 99 740i, Black/Black, 185k, Alpina Mods — 01 740i, Titanium/Silver, 40k, Sport Pkg
    Complete Turnkey Diagnostic/Programming systems available…PM for details.
    
    http://www.8Coupe.com — Please register, spot, and help the project.

    ---

20. Seems you guys want me to do two different things, and I’m just getting myself confused here.

    I’ll keep it simple : NCS only allows me to code the VIN at the same time as the ZCS — I see no way to code JUST the VIN alone to any given module. Is there any harm in me coding the VIN and ZCS details to the EWS straight away? Since the ZCS data is screwed up on the EWS anyway, it seems I’ll have to code that data to it at some point regardless, no?

    I’m just looking for clear, simple instructions. Don’t hit me!

    

    ---

21. Originally Posted by Sobek
    

    Seems you guys want me to do two different things, and I’m just getting myself confused here.

    I’ll keep it simple : NCS only allows me to code the VIN at the same time as the ZCS — I see no way to code JUST the VIN alone to any given module. Is there any harm in me coding the VIN and ZCS details to the EWS straight away? Since the ZCS data is screwed up on the EWS anyway, it seems I’ll have to code that data to it at some point regardless, no?

    I’m just looking for clear, simple instructions. Don’t hit me!

    once your able to recode 1 module properly, you will be able to recode all the other modules from that ones ZCS. (simply open it in ncs, and then code it with an empty FSW_PSW). The one module that is properly coded is the one NCS will use to determine what modules you have.

    If you use DIS v44, it will do it all at once.

    and yes, worst case with the wrong version is some stuff wont work, and you will have to reprogram it.

    Last edited by legoman67; 01-28-2014 at 12:20 PM.

    Current:

    — 09 335i MSport, FBO.
    — 98 Euro M3, Estoril Blue
    — 04 M3, Carbon Black, 6 Speed Coupe
    — 06 M5, Black on Black, Full Leather.
    — 73 3.0CS, Tagia Green, 5 speed M30b35 converted

    Ex’s:

    1984 325e, 1988 325IX, 1992 525I, 1995 540i/6, 2002 330i, 2005 330xi, 1992 850i, 2003 330i #1, 2003 330i #2, 2002 330ci, 2004 330ci, 2007 328CI, 2007 335i, 2001 M3, 2006 M5 6 speed

    ---

22. Cant he just code the whole car or just the modules needed using expert mode to get the proper ZCS? Or he cant even get to that step because of the errors?

    Last edited by purplecty; 01-28-2014 at 12:50 PM.

    ---

23. Originally Posted by legoman67
    

    once your able to recode 1 module properly, you will be able to recode all the other modules from that ones ZCS. (simply open it in ncs, and then code it with an empty FSW_PSW). The one module that is properly coded is the one NCS will use to determine what modules you have.

    If you use DIS v44, it will do it all at once.

    Thank you, that clears up some thoughts I was having. I figure that way if I can at least get the IKE sorted with the proper VIN and ZCS, then I should be good to go. I don’t mind if the EWS still contains garbled ZCS data — if I can code modules, I can code modules, I have no need or desire to screw with the EWS system at any point anyway.

    Originally Posted by legoman67
    

    and yes, worst case with the wrong version is some stuff wont work, and you will have to reprogram it.

    This is also good to hear. I’m annoyingly anal — I like to have ALL the facts before doing something, specially something as important as this… it’s probably frustrating to you guys with all my questions (just DO it already!!) but I need to know these things before I take any ‘risks’ with my car.

    I think what I’ll do is fire up DIS v44 tonight and see if I can’t get the VIN and ZCS corrected on the IKE first. I did a little ‘offline’ module coding run with DIS last night without my car hooked up, and it seems pretty straightforward. Failing any success with DIS, I’ll look at recoding the IKE through NCS instead. I just need something to work, and if it’s DIS then that’s fine with me as it does offer a more user friendly approach to coding it seems

    

    ---

24. Success.

    Fired up DIS v44 and went through the ZCS/VA coding menu. I didn’t screenshot it, but it first tried to access the IKE automatically and said something along the lines of «Coding data required from EWS not present, code EWS to continue» (I’m simplifying that a LOT mind you) and only gave me the option to code the EWS when I clicked next. It then asked for my VIN, and pre-filled it with the sort-of incorrect one from above (WBA000000 etc), so I put in my full correct VIN. The ZCS data it gave me was interesting though… It matched the GM and SA to what legoman posted, but the VN was VERY different. I debated whether to accept what it suggested or to go with legoman’s code, but I gave it the benefit of the doubt and let DIS run with its own numbers. It coded the EWS successfully, and then NCS was happily reading the EWS without issue.

    So this morning I successfully coded on one-touch open/close windows, and one-touch open/close sunroof. I plan to code off the license plate light bulb checks as I have LEDs that I want to use that don’t have resistors built in, and I need to try and work out how to code off the parking light bulb checks too. Also, I had a very interesting thing happen… I turned on my acoustic arming and disarming — easily the one thing I wanted the MOST — and what does it do? It just beeps the HORN once and twice. What the? Is there a setting somewhere that can tell it to use the alarm siren and not the horn for the arming & disarming sounds? Come to think of it, when I was fiddling with trunk fuses many months back and accidentally set off the alarm then, it only beeped the horn too. Could this is an Australian thing? How annoying!

    Anyway, if you’ve got any suggestions there I would love to hear them. But I wanted to thank you all again for helping me get this all sorted out. It’s incredibly satisfying to finally be able to do all my own coding and properly ‘individualise’ my car

    

    ---

25. Wow, thanks for all the info, as this is exactly the same issues that I am having with my ’98 540i!

    Currently d’loading V.44 and will install it tomorrow. Hope it works.

    Thanks,
    Terry

    ---