BMW Forum - BimmerFest BMW Forums banner

Changing the turn signal stalk (HBA retrofit)

Tags
hba
1 reading
14K views 49 replies 6 participants last post by  patrickahogan  
#1 ·
In pursuit of HBA, I bought a used turn signal stalk which has the HBA button on it. Before I take out the original stalk from my car, I would like to know if changing just the lever will be enough, or will I have to change the whole steering column stalk? I bought the whole thing, just in case, but it came with the red thing on top broken and nevertheless I would prefer to use my stuff if possible.

Please see the pictures attached of the lever with the HBA button included and if someone has a picture of the connector of the non-HBA lever, it would be very much appreciated.
 
#2 · (Edited)
The stalks are the same between the stalks with or without the HBA button. It is on the FLEXRAY bus, along with the BC button, which is on the same stalk...you are OK to install on your existing clockspring.

BUT for those that are trying to add heating and/or vibe, the clock spring must be changed out, as the connector on the rear is missing pins to support the power from the JBE for the heating/vibe function , and the front 4-pin connector to plug in the steering wheel harness at the 4 O'clock position on the front of the clock spring are missing. Silly since power is already in the clockspring and the LIN bus interface (blue wire) is also routed. The steering wheel harness must be changed if adding heating/vibe to support the addition of the steering wheel electronics module.

OP, if you still want a picture, I can post.

BTW, if you pop off your steering column cover, you can access the 3-wire, 4-contact connector on the right stalk w/o removing the steering wheel or clockspring, and verify the BC and HBA buttons work on your new stalk first. Then if all is OK, you can start disassembly, removing the battery (-) terminal in the trunk, remove your steering wheel airbag, removing your steering wheel, then finally your clock spring.

When you reassemble your clock spring, it's much easier if you mount your stalks to the back plate (the one with no circuit card installed), leave the stalk harnesses unplugged, then marry the two plastic housing together, making sure that the mechanicals are aligned for both stalks, then move stalks around to verify full movement, then put two screws in. Then route your stalk harnesses up and down over the plastic harness posts, then plugging in the stalk harness connectors. Then put in your remaining screws. verify that your reassembly did NOT pinch your stalk wires.

Hope this helps.
 
#3 ·
Thank you very much for the response!

What had me worried wasn't the three wires, but the metal connectors on the base which are 2 + 2 + 3 = 7. But you say it's the same on the non-HBA version, so I should be ok, right?

My hypothesis is that the metal connectors do the communication via the FLEXRAY bus and the three wires with the four pin connector are a fail-safe backup for the turn signals/flasher to work... I found this on the documentation (functional description of "Steering column switch cluster") which I think(?) supports my hypothesis:

The footwell module receives the requests of the turn indicator/high-beam switch as well as the button for the high-beam assistant. The signals from the steering column turn indicator/high-beam switch for the direction indicator lights and the headlight flasher are transferred via FlexRay. In order to increase availability the steering column switch cluster is connected directly to the footwell module via a cable. The signals - e.g. for the headlight flasher or turn indicators - are transferred redundantly across this cable.
Sorry for being so pedantic...
 
#6 ·
Wow, thanks for starting this thread and the detailed info. I'm also under the same boat as OP and always wanted to use my own clock spring and that's why gave up on the thought of installing HBA.
This thread, however, gives me confidence that I can keep my clock spring and just swap out the stalk. (y)
Looking forward to hearing about your experience. And I'm off to finding a HBA enabled stalk. ;)
 
#8 ·
A quick related question: I have an F10 LCI from production date 11/2014. If I get the HBA stalk from a pre-LCI F10 and replace it on my LCI clock spring, should that work? I'm assuming the hardware connections and FlexRay encoding of pre-LCI stalks is the same as LCI stalks, but need confirmation if anybody knows. Thanks!
 
#11 ·
I made a first attempt at coding it, but I wasn't successful. I successfully added 5AC to the FA and then coded the ECUs: KAFAS2, FRM and CAS (CAS was probably not needed). Problem is, my new HBA button on the stalk, acts as a second button for the board computer. So, maybe I need to exchange the whole stalk and not just the lever, OR I need to code something else too (SZL maybe? I forgot to even check if there exists an ECU for SZL). I read about coding LHM (x2) and TMS (x2), too. Is that correct?

Then with bimmercode, I changed HU_NBT -> 3000 -> HIGH_BEAM_ASSISTANT to "aktiv". But this didn't change anything also. How should I check if the high beam assistant is functioning? Will I see the icon with the A in the dashboard when night lights are on and set to Auto? Do I need to travel at a speed to just see the icon?
 
#12 · (Edited)
Hello OP, when installing a BMW function, such as HBA, the whole system must be present for it to work, specifically item #1 below...while you did update item #3, you should check that your rear view mirror is FULLY compliant....and if you need to upgrade, ensure your mirror harness has LVDS lines populated in the harness going from the mirror's connector to the KAFAS module. The KAFAS module must be on the PT-CAN connected to the ZGM module.

1. KAFAS camera or FLA camera
2. Rain-light-solar-condensation sensor
3. Steering column switch cluster
4. Car Access System (CAS)
5. Footwell module (FRM)
6. Crash Safety Module (ACSM)
7. Roller drive of cover (Note: inside of your headlight)
8. Stepper motors of the LWR (Note: inside of your headlight)
9. Integrated Chassis Management (ICM)
10. Central Gateway Module (ZGM)
11. Junction Box Electronics (JBE)

FlexRay Bus
  • ZGM to ICM
  • ZGM to SZL
PT-CAN
  • ZGM to KAFAS
  • ZGM to KOMBI
K-CAN2
  • ZGM to FRM
  • ZGM to RLSBS (Rain Light Solar Condensation Sensor)
  • JBE to RLSBS
Once you get the system functioning correctly you should get a "double" headlight icons on your KOMBI (one is the high beam and the other is a headlight icon w/ an "A" = assist)

Let us know how it works out...
 
#13 ·
M_Bimmer, my car has KAFAS2 (only used for road sign detection at the moment) and adaptive headlights, so I think all hardware is now already in place.

Questions are:
  • Do I need to swap whole steering column stalk, or do I just miss coding for a module? Now SZL things the extra button is for the board computer too.
  • What ECUs should be coded for HBA to work on an F11? There is supposed to be a way for HBA to be always on, even if someone doesn't have the button and that I think is a good test to at least know the coding works.
 
#14 ·
I'd have to go do some investigation.....I don't remember seeing the SZL module listed in the E-SYS FDL tree in which you could FDL Flash the MCU (PSdZ Data), but you can try to update the firmware if it's listed in the FDL tree.

I also don't remember seeing the HBA VO feature in the SZL module in VO features.....heating was, but don't remember HBA....maybe someone else can chime in...or if you give me a few days, I can go look...up to you.

Cheers
 
#16 ·
Within E-SYS, you can do both FDL coding (Flash the firmware) or VO Code (turn on/off Firmware Functionality = active/non-active). When you flash code, it can reset the FW back to the factory I-Step version (and it's VO settings), or you can use an newer version of I-Step to flash each module with a new FW version (which will then reset the VO settings based on the list of vehicle options list by VIN)

There are several APPS that support VO coding, such as BimmerCode (which I use) via a Bluetooth OBD II adapter.

BTW, it looks like SZL_LWS is a module that can be FDL coded (listed in the E-SYS FDL tree):
List of ECUs
 
#17 ·
I shall definitely try to code SZL module too!

As for definitions, my understanding is this:
  • VO Coding: Changing the "Vehicle Order" of the car, to include options not originally present. For example adding 5AC in the list of options. After adding the options you want in the FA (Vehicle Order), you have to code the affected ECUs for the option you changed, so their defaults are in line with the car's FA.
  • FDL Coding: Changing specific options in an ECU (module). VO Coding will remove any FDL Coding you have done, as it replaces module settings with default values for the VO.
 
#18 ·
Changing non HBA Stalk to HBA Stalk does NOT work.
I tried it myself last week and now I have two dead SZL.

HWEL and HWAP are different and coding is not enough.
 
#22 ·
When you try to only retrofit the left stalk with HBA in the SZL, then you end up with two BC Buttons. Even with 5AC VO Coding.
When you calculate TAL with 5AC the SZL wants a different SWFL but also a different HWEL and HWAP.

You can now go on and select HW-Kennungen aus SVT-Ist after Read-ECU and the HWEL turns blalck, but HWAP ist still red.
After flashing SZL with red HWAP the Flexray does not respond any more and the SZL is dead. It now does not show up after ECU-Read and ZGW reports Flexray issue.

Conclusion: Dead SZL
 
#23 ·
Ok, that's scary! If I understand correctly, SZL with 5AC needs another firmware and not just coding. And when you flashed the needed firmware, it was dead. You didn't just press "Code" on the SZL, correct? If correct, did you try it and e-sys didn't let you, or it didn't have any effect and so you proceeded with further e-sys suggestions?

Sorry for the "rewrite", but I don't know what these are: "SWFL", "HWEL", "HWAP", "HW-Kennungen aus SVT-Ist", "SGW".
 
#24 ·
HWEL = Hardwareelectronics
HWAP = Hardwareapplication
SWFL = Software or Firmware
ZGW = Central Gateway
HW-Kennungen aus SVT-Ist = Hardwarecodes from SVT-Actual
BTLD = Bootloader

No, coding gives you two BC Buttons and flashing fails at SWFL deploy with error.
Although BTLD is the same on both SZL. And because of that I pressed start flash on the Frankenstein SZL. But whatever...
 
  • Like
Reactions: NotHere
#25 ·
No, coding gives you two BC Buttons and flashing fails at SWFL deploy with error.
So, coding is safe to do, but won't have any effect.

Although BTLD is the same on both SZL. And because of that I pressed start flash on the Frankenstein SZL.
That sucks! And now you don't even see SZL to be able to flash it again... :(
 
#27 · (Edited)
Horsty, I'm sorry for your loss, but you were very helpful!

My current plan of action is:
  • Not mess around with my Frankenstein SZL
  • Try to code HBA and set it to always on, just to be certain it can be done and it works
  • De-Frankenstein my SZL and put the HBA-enabled one in the car, complete.
  • Do steering angle sensor adjustment and coding of the new SZL on my car

This project just got a lot longer :)
 
#29 ·
I'm using ZGW02-High with newest Software so there isn't any updatability.

I really don't know what the differences are and the only thing to get the dead one up and running again is to clone the prozessor inside I guess.
 
#32 ·
I just checked with bimmercode (in expert mode) my FRM module, and it has "automatisch" as an option for FRM/3050/FLA_AUTO_AKTIV/, so coding is not possible for me.

I will swap the whole steering column stalk and report back. It will take at least 20-30 days more for this to happen though...
 
#33 ·
So, not directly related, I've been working on coding my F10 over the last two weeks, and there seems to be an inconsistency on the forums regarding terminology. I will just state that VO coding, FDL coding and firmware update through TAL calculation (E-SYS) are different. FDL is nothing more than a non-BMW set of VO codes, so expect similar results.....but if you TAL calculate, and change the FW versions in your ECU's, you get different results than just VO coding. I went from F010-03-14-503 to F010-11-07-520. Each ECU firmware update transformed my car (Make sure you have a backup FA file). You may have to inject a new CAFD file after an ECU firmware upgrade.....but that is easy to do.

I just updated my KOMBI firmware, then VO coded, and magically my heated steering wheel message on my instrument cluster shows up which I couldn't get since 2014.

Wondering if firmware update to SZL would allow you to use the stalk upgrade only......anyone game?

(BTW if any of the 31 above posts did firmware update and I missed it...I apologize)