[spdy330]

Long Tran in Elmonte can most likely do it and EAS in Santa Ana.

[335ibob]

Originally Posted by CasperSYTFU

for panic search for SONDERTASTE_PANIKALARM in CAS

for the chirp volume search BUZZER_HIGH_LEVEL in DWAS, change the wert value

thanks for the info but I still need a local coder because I do not have the cable. maybe I will post in the regional section as well.

[spdy330]

I told you above who was local

[335ibob]

Originally Posted by spdy330

I told you above who was local

missed your post. thanks for the info.

[Maxx2]

Originally Posted by Black Bimmer

Well that was fun, finally got the alarm coded and fully functional. I changed the FA on the CAS and NFRM modules, then tried to process car > code car but kept getting an error. Finally just coded the individual CAS, DWAI, and DWAS modules using the blank .man file trick and it worked! Lock/unlock chirp, hood switch, panic alarm, tilt switch all functional.

I just tried this and am getting an error when trying to read and or code the DWAS module. I keep getting the error shown below. Just fyi, the alarm appears to working (chirps) but, it is soo quiet I can barely hear it. I wanted to increase the volume but it's in the DWAS module. Any ideas??

Also, I just read the error.log file in C:\NCSEXPER\BIN and this is what I see repeatedly:

ERROR! Modul: LFCDHDIA.CPP (A_E65.IPS/IPO), Proc: CDHapiResultText, LineNr: 01, ErrorNr: 2000
COAPI-2000: EDIABAS or SGBD error
BIP-0009: BEST VERSION ERROR


Update:
Just found this in a EDIABAS error pdf:

BIP-0009: BEST VERSION ERROR
EDIABAS_BIP_0009
Meaning: Erroneous BEST version of the ECU description file.
Causes: The ECU description file addressed was compiled by a compiler which is not compatible with this EDIABAS version.
Error correction: Compile the ECU description file using the compiler included in this EDIABAS version.
Target system: WIN SCO QNX

[Maxx2]

Problem solved:

I did some reading on the BEST VERSION error and it has to do with the version used to create the ECU files which are not recognized by EDIABAS 6.4.7. In an attempt to resolve this compatibility issue I proceeded to install EDIABAS 7.2.0. Just a word of caution when installing EDIABAS 7.2.0, the EDIABAS.INI will not work as it is and required a few settings changes to make it work. Once I installed the new verison of EDIABAS I was immediately able to connect and code the DWAS module of the car.

Alarm coding related:
I first proceeded to code the DWAS with an empty .MAN file to set everything to default values. Then I read the module and when I first looked at the BUZZER_LOW_LEVEL and BUZZER_HIGH_LEVEL they were set like this:

BUZZER_LOW_LEVEL
wert_04
wert_05
BUZZER_HIGH_LEVEL
wert_05
wert_06

I then left only (1) wert_08 for each and coded the module. I tested the alarm and it was just as quiet as before so I read the module again and to my surprise the settings were different and looked like this:

BUZZER_LOW_LEVEL
wert_01
wert_02
wert_06
wert_07
wert_08
BUZZER_HIGH_LEVEL
wert_06
wert_07
wert_08

I then left only (1) wert_01 for each and coded the module. I tested the alarm and now it is significantly louder. I'm not sure if it is maxed out, but it is better. As before, I read the module again and to my surprise the settings were different yet again. ( Similar to above but I didn't record it). Has anyone experienced anything like this?

I have attached a copy of my DWAS .TRC file after the wert_08 coding and reading it back. (saved as .txt for uploading purpose)

[fizzerd]

-DWAI module:
LAUTSTAERKE
nicht_aktiv > aktiv
ALARM_OPT_FERNLICHT
nicht_aktiv > aktiv
QUIT_AKUST_SCHAERF_KLAPPE
nicht_aktiv > aktiv
PANIK_ALARM
nicht_aktiv > aktiv
QUIT_AKUST_ENTSCH
nicht_aktiv > aktiv
DEF_QUIT_AKUST_ENTSCH
nicht_aktiv > aktiv
DEF_QUIT_OPT_ENTSCH
nicht_aktiv > aktiv
DEF_QUIT_AKUST_SCHAERF_KL
nicht_aktiv > aktiv
ANFRAGE_FENSTERPOSITIONEN
nicht_aktiv > aktiv
PIAU_AKUST_ENTSCH
nicht_aktiv > aktiv
PIAU_AKUST_SCHAERF_KLAPPE
nicht_aktiv > aktiv
SIGNAL_HK
nicht_aktiv > aktiv

-CAS: (panic alarm)
SONDERTASTE_PANIKALARM
nicht_aktiv > panikalarm
MOTORHAUBENKONTAKT (hood switch), thanks onebadmofo
nicht_aktiv > aktiv

Anyone know which line is for the interior sensor? My interior sensor was working before the coding but after the coding everything for the alarm works except the interior sensor..

[E90aL]

Originally Posted by fizzerd

Anyone know which line is for the interior sensor? My interior sensor was working before the coding but after the coding everything for the alarm works except the interior sensor..

I don't know which line it is but you could look for the differences of your trc file and the one I posted.

[giovane]

I retrofitted and coded the alarm as suggested. Everything works fine, but the only thing is that I cannot program the chirp through the turning indicator as indicated by the manual (see picture below). Basically there's no acoustic option, as if I never installed and coded the alarm.
Anybody knows in there's a code for that?

[Elliott@DetailAddict]

FUNK_INNENRAUMSCHUTZ is the interior sensor.

[6cylinder]

@giovane: After you have added the alarm system to your vehicle options have you already coded your KOMBI with an empty MAN file? Maybe your KOMBI do not know about your new installed alarm system.

[giovane]

Originally Posted by 6cylinder

@giovane: After you have added the alarm system to your vehicle options have you already coded your KOMBI with an empty MAN file? Maybe your KOMBI do not know about your new installed alarm system.

I didn't code the KOMBI to defaults.
I will try and report asap! Thank you!

[AcidLotus]

I also could not add +K302 and code the car without errors, or so it seemed. Later, I came back and read the FA and it had +K302 in both the CAS and NFRM. So I coded the DWAI module the way I wanted it, and all the settings work.

However, I have iDrive but do not have module CAPPL. Instead, there is a CIC module, and I read values from that, but don't see anything related to what's listed on the 1st page under the CAPPL module. Any ideas? This is on a 2009 LCI 335xi with iDrive, presumably with CIC.

[onebadmofo]

Originally Posted by AcidLotus

I also could not add +K302 and code the car without errors, or so it seemed. Later, I came back and read the FA and it had +K302 in both the CAS and NFRM. So I coded the DWAI module the way I wanted it, and all the settings work.

However, I have iDrive but do not have module CAPPL. Instead, there is a CIC module, and I read values from that, but don't see anything related to what's listed on the 1st page under the CAPPL module. Any ideas? This is on a 2009 LCI 335xi with iDrive, presumably with CIC.

DWA = aktiv

[AcidLotus]

Originally Posted by onebadmofo

DWA = aktiv

That appears to already be set. Is there a particular place within the iDrive that I should be looking for these options? I'm guessing they would be under the Settings > Locks menu? Or is there another setting that I need to change somewhere?

[dr004]

Originally Posted by NiVeDh

You don't have to code all those values.

Just code $302 to VO and then code the entire car to defaults. It will automatically set the correct values for the new VO.

Thanks this worked perfectly for me...............just got to redo my "personal things now"

[onebadmofo]

What's a proper procedure for PDC retrofit? I did the VO and coded whole car but there's no beeping. Screen works

[nitehawk]

Bump. I just installed my alarm and want to make sure I put in everything properly.
What alarm features should work prior to coding? Currently, just the LED on the rearview blinks upon locking the car. It flashes very quickly at first and then onto a more normal pace. Nothing else works. I have yet to hear the siren go off. Is that normal until I get the car coded?

[fizzerd]

Originally Posted by nitehawk

Bump. I just installed my alarm and want to make sure I put in everything properly.
What alarm features should work prior to coding? Currently, just the LED on the rearview blinks upon locking the car. It flashes very quickly at first and then onto a more normal pace. Nothing else works. I have yet to hear the siren go off. Is that normal until I get the car coded?

Check the interior sensor. Put the driver window down. Lock car and after a few minutes put your hand through the window. Does the alarm go off?

Everything should work after coding. My interior sensor however was working right away after installation.

[nitehawk]

Originally Posted by fizzerd

Check the interior sensor. Put the driver window down. Lock car and after a few minutes put your hand through the window. Does the alarm go off?

Everything should work after coding. My interior sensor however was working right away after installation.

Thanks for the tip; I tried this and it worked It was my first time hearing the siren go off, which is pretty loud. I read the CAS module and panic alarm is currently disabled. Coding will be done very soon...

[moreno1]

Retrofited the alarm last night on my E92. At first I had the clown nose, chip upon locking and unlocking doors. After coding and adding +k302 to my VO, coded each module in expertmode then I was able to have the following:
1 - Inside motion sensor
2 - Hoodswitch
3 - panick alarm
4 - and obviously the on/off control for the chip in the BC stalk

I also installed the shock sensor that one member is selling here. I tested it and it works like a charm. The hoodswitch and motion sensored were tested as well and i'm good to go!!
Thx to all contributors :-)!

[matrix76]

Originally Posted by moreno1

Retrofited the alarm last night on my E92. At first I had the clown nose, chip upon locking and unlocking doors. After coding and adding +k302 to my VO, coded each module in expertmode then I was able to have the following:
1 - Inside motion sensor
2 - Hoodswitch
3 - panick alarm
4 - and obviously the on/off control for the chip in the BC stalk

I also installed the shock sensor that one member is selling here. I tested it and it works like a charm. The hoodswitch and motion sensored were tested as well and i'm good to go!!
Thx to all contributors :-)!

Glad to hear it worked out for you, M