[M_Bimmer]

Not trying to hijack NotHere's (OP) thread, but Horsty, can you elaborate on "dead" clockspring?

Given that the left stalk is on the FlexRay bus, not sure how it caused a dead clockspring.....

 

[Horsty]

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

 

[NotHere]

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".

 

[Horsty]

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...

 

[NotHere]

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...

 

[Horsty]

Yes and yes. But you can happily try it yourself.

 

[NotHere]

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

 

[M_Bimmer]

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...

Thanks Horsty.....and hopefully you aren't too upset (OP wanted to know the electrical differences between the stalks, which I provided...never claimed I "checked' the electronics compatibility)

This thread has me itching to try this swap...I have a non-HBA clockspring (original to the car) and an HBA stalk (on my car now) which I'll Frankenstein together and see what it does...I'll report back on my findings.

I'm now wondering if your "dead" clockspring is merely a FlexRay bus contention issue...and both ends of the bus requires firmware update. FlexRay is a bit more complex than LIN or CAN....

If my clockspring becomes "dead" then I'll undo the Frankenstein, but this will confirm that the circuit card in the clockspring (SZL) are different between the HBA and non-HBA versions.

 

[Horsty]

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.

 

[kamrankazmi]

This thread has me itching to try this swap...I have a non-HBA clockspring (original to the car) and an HBA stalk (on my car now) which I'll Frankenstein together and see what it does...I'll report back on my findings.

Hi @M_Bimmer, were you able to test this theory? I'm waiting on a confirmation that this thing works with original non-HBA SZL before I order the HBA stalk. Thanks!

 

[NotHere]

I'm waiting on a confirmation that this thing works with original non-HBA SZL before I order the HBA stalk.

What we know so far is that for you to have the option to switch auto mode on/off you definitely need to change the whole stalk (which entails a steering angle sensor adjustment with ISTA-D).

As for coding the HBA to be always on, I would describe it as a work in progress. I VO coded FRM and KAFAS modules, but I missed switching HBA to be always on in the FRM module (I thought the setting was in the HU_NBT module). Look at this comment: HBA (5AC) coding with Speed Limit present and Shawn's reply. I hope I have aktiv as an option on my car and not automatisch...

 

[NotHere]

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...

 

[M_Bimmer]

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)

 

[NotHere]

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)

@Horsty did just that and fried his SZL. Don't try it...

 

[M_Bimmer]

@Horsty did just that and fried his SZL. Don't try it...

He "bricked" it...slightly different from "frying".....I just bricked all my ECU's trying to update the firmware and recovered everyone of them...took me 9 hours....It made me very knowledgeable on programming my F10...

My first step would be to make the physical change - HBA stalk on a non HBA clock wheel (SZL)...install on my car. Since SZL is associated with both of my FA and SVT_ist, I create a copy of SVT_ist and call it SVT_soll, and then do TAL calculation. I'll load my FA (not read), the SVT_soll, then TAL_calculation file. Use F0101_11_07_520 as Target, and use last as F010_03_14_503. Once I run this, firmware should be updated. SZL doesn't need a CAFD, so now I'd check to see if the new HBA stalk works.....this would confirm that the firmware disables/enables the I/O from the stalk on the SZL MCU, not the VO coding, which are nothing more than bit flips to enable/disable features.....a firmware change though can change the I/O assignment on the SZL MCU.

This may take a week to try out....

 

[kamrankazmi]

This may take a week to try out....

You sound very convincing.
I'll patiently wait for you to try this out and let us know the outcome. Let's hope for the best! 🤞
Thanks!

 

[M_Bimmer]

Forgot one key step...add "5DL" to FA before TAL execution....

S5DLA = High Beam Assist...

 

[NotHere]

Forgot one key step...add "5DL" to FA before TAL execution....

S5DLA = High Beam Assist...

AFAIK, 5DL = Surround view. Maybe you mean 5AC?

 

[M_Bimmer]

Yes I did mean "5AC".....result of multitasking...😕

 

[kamrankazmi]

I ended up replacing the whole clock spring assembly (that comes with new HBA stalk), added 5AC to the FA, flashed the SZL and VO coded KAFAS2 and FRM. The HBA is working nicely.