[kenbrinkman]

I just installed the alarm retrofit kit which was really simple, it took less than an hour. The follow up coding went pretty good but I have a weird issue. I thought I did it correctly because I added the +K302 to the FA in the CAS/FRM modules then changed some of the specific settings instructed by this thread. The ones I changed are down here:

-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

-DWAS module: (change if chirp is too quiet)
BUZZER_HIGH_LEVEL
wert_06 > wert_04
wert_07 > wert_05
wert_08

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


My issue is that the alarm only chirps on unlock, not upon locking. Everything else works, like the hood sensor, tilt sensor, interior sensor, clown nose, etc. The only thing that doesn't is the chirp when I press the lock button either on the remote or the door handle. But unlocking with either beeps twice like it should. Weird right? And there's no settings in the BC/instrument cluster either.

Should I just write a blank MAN file to restore the defaults? I've never done that before and I guess it would remove all the other coding right?

Maybe someone knows if one line is incompatible with another?

[PichaDis11]

Proper method as I've read is to code the module in expert mode/ profile. Rather than coding with a blank man file. Just a hint, I've done this install myself so hopefully someone can help you more on this. For now retrace your steps to make sure you've everything.

[kenbrinkman]

After searching around today, I found that I missed this one:

QUIT_AKIST_SCHAERF
activ

Simple enough. So I got that working and I also did the read ecu/code ecu with the KOMBI module in Expertmode so how I have the alarm options in the BC stalk. Thanks for your help.

[makkan00]

Originally Posted by kenbrinkman

After searching around today, I found that I missed this one:

QUIT_AKIST_SCHAERF
activ

Simple enough. So I got that working and I also did the read ecu/code ecu with the KOMBI module in Expertmode so how I have the alarm options in the BC stalk. Thanks for your help.

What alarm options do you get in kombi?
Strange, as in UK this alarm is standard but none of the car has buzzer option on the odometer.

[kenbrinkman]

Originally Posted by makkan00

What alarm options do you get in kombi?
Strange, as in UK this alarm is standard but none of the car has buzzer option on the odometer.

So far as I can tell the kombi module, as it relates to the alarm, is only responsible for the alarm options in the BC stalk that turns the acoustic beeps on or off when locking/unlocking the car. iDrive equipped cars might have more options, but I'm not sure. When installing the alarm I added the +K302 to the VO in the CAS and FRM modules as instructed by everyone. This enabled the DWAI/DWAS modules to code. However, an important last step is to reflash the kombi module using the Expertmode profile method (read kombi, change job to sg_codieren, execute job) to reset defaults on the module. By doing this, the kombi recognizes that the VO has changed and adds the US default values (like the BC stalk options).

The kombi module on your UK car knows the alarm is there since it's standard equipment, but the code in the module is set not to display the BC stalk settings by default unlike how it is in the US. You or someone else could do some digging to find the line(s) that need to change from nicht_activ to activ in the kombi module to enable it.

Hope that helps some, and hopefully someone else will chime in if I'm off.