[ifr]

Originally Posted by Fpgiuliano

The problem is on the firmware 03/2021 (first version)
I have laserlights but I don’t know if is extended also to led

I'm thinking its specific to the laserlights.

It's the same buzzing sound you get when the car has been driven in the dark and then parked. The lights stay on buzzing for a bit then go off. With 03/2021.530 that buzzing is there all the time, from the moment the car unlocks even if the lights dont need to be on.

[ramparts]

Fzd (roof module) and RAM for me. All sorting in 20 mins.

[ifr]

Originally Posted by davidoff86

Fzd (roof module) and RAM for me. All sorting in 20 mins.

you got led or lasers?

[ramparts]

Originally Posted by ifr

you got led or lasers?

Just adaptive leds

[ifr]

Originally Posted by davidoff86

Just adaptive leds

I'm thinking it was a lasers specific issue.

Mine (G05) did BDC, RAM, DDE, FLEL and FLER in 12 minutes. I'm just relieved when there is no HU to update!

Show's its model and option specific with the updates.

Have you seen the ICAM2 IP connect error when calculating measures? Do you have park assist plus with surround view?

[ramparts]

Originally Posted by ifr

I'm thinking it was a lasers specific issue.

Mine (G05) did BDC, RAM, DDE, FLEL and FLER in 12 minutes. I'm just relieved when there is no HU to update!

Show's its model and option specific with the updates.

Have you seen the ICAM2 IP connect error when calculating measures? Do you have park assist plus with surround view?

Originally Posted by ifr

I'm thinking it was a lasers specific issue.

Mine (G05) did BDC, RAM, DDE, FLEL and FLER in 12 minutes. I'm just relieved when there is no HU to update!

Show's its model and option specific with the updates.

Have you seen the ICAM2 IP connect error when calculating measures? Do you have park assist plus with surround view?

Got the 360 cameras, yeah.

No faults at all in ISTA currently, I did have those issues however with 20/11, they went away with 21/03

[ifr]

Originally Posted by davidoff86

Got the 360 cameras, yeah.

No faults at all in ISTA currently, I did have those issues however with 20/11, they went away with 21/03

I get the ICAM2 fail to connect error in ISTA prior to programming.

I don't even have an ICAM2, it's ICAM3, which explains why it can't connect to the ECU, so looks like an ISTA 4.28.x bug.

Doesn't cause an issue, but is annoying as it interrupts the measures calculation. I expect it will just 'disappear' with 4.29.x

[ramparts]

Originally Posted by ifr

I get the ICAM2 fail to connect error in ISTA prior to programming.

I don't even have an ICAM2, it's ICAM3, which explains why it can't connect to the ECU, so looks like an ISTA 4.28.x bug.

Doesn't cause an issue, but is annoying as it interrupts the measures calculation. I expect it will just 'disappear' with 4.29.x

I did notice that it incorrectly names itself. Seems to interchangeably still be called TRSVC as well. But I defo have the icom3 variety as I've eye balled it in my boot

[Kacpi_23]

Hi,

Maybe I can help here somehow with my experience. Before making update over the air to 11.2021.540 I had no errro lte on ista.
After update to 11/2021 there is a fault stored with the name "800B84 TRSVC Coding Data implausible" with -1km. All systems working fine, so I don't care about it but still strange that after the normal Rollout of the 11.2021 update over the air I got bow this error. Seems like the versions was not 100% ready to roll out ....

[ifr]

Originally Posted by Kacpi_23

Hi,

Maybe I can help here somehow with my experience. Before making update over the air to 11.2021.540 I had no errro lte on ista.
After update to 11/2021 there is a fault stored with the name "800B84 TRSVC Coding Data implausible" with -1km. All systems working fine, so I don't care about it but still strange that after the normal Rollout of the 11.2021 update over the air I got bow this error. Seems like the versions was not 100% ready to roll out ....

Thanks.

Mine isn't a car based error. It's an ISTA read error. There is nothing stored on the car so not related to any upgrade. Just a bug in ISTA itself and not the SDP.

[ramparts]

Originally Posted by Kacpi_23

Hi,

Maybe I can help here somehow with my experience. Before making update over the air to 11.2021.540 I had no errro lte on ista.
After update to 11/2021 there is a fault stored with the name "800B84 TRSVC Coding Data implausible" with -1km. All systems working fine, so I don't care about it but still strange that after the normal Rollout of the 11.2021 update over the air I got bow this error. Seems like the versions was not 100% ready to roll out ....

Originally Posted by Kacpi_23

Hi,

Maybe I can help here somehow with my experience. Before making update over the air to 11.2021.540 I had no errro lte on ista.
After update to 11/2021 there is a fault stored with the name "800B84 TRSVC Coding Data implausible" with -1km. All systems working fine, so I don't care about it but still strange that after the normal Rollout of the 11.2021 update over the air I got bow this error. Seems like the versions was not 100% ready to roll out ....

As ifr says, you can safely ignore this, it's a bug in ista that goes away in 4.28.x

[ifr]

That said, I have noticed something iffy in the config.

ISTA 4.28.x (including up 4.28.41), complains it cant get an IP address for ECU ICAM2, when calculating programming measures. Not a major issue as the measures plan doesn't have it in-scope for programming anyway.

The SVT has ICAM3 listed as below, with cafd as shown.

CAFD_00008081_006_010_005 identifies as ICAM2, as do the previous i-step cafd.

So, something not right. The SVT/cafd naming disconnect goes back many i-step iterations, so I'm not totally convinced that's the reason for the IP connection error. I'd be twitchy if the programming measures had ICAM2 (or 3?) in-scope for programming.

[Kacpi_23]

Sorry, above i meant 11.2020 of course

[Paladin1]

Originally Posted by RSnic

Would you be kind enough to elaborate on how Alexa is working as I'm in US still waiting on 11/2020?

Thanks

You don't get it with 11/2020 in the US either....

[RSnic]

Indeed, having gotten 11/2020 OTA, still no Alexa Integration in US. Guess we'll have to wait for the myBMW app in lieu of Connected Drive app

[Bambazonke]

Originally Posted by ifr

I've upgraded my G05 to 03/2021.525 and have noticed......... nothing!

aSLA bug where the car suddenly thinks its in an 80/100mph zone is still there. Very dangerous, and I think is probably the nav data as there are no signs saying 80mph!

More disappointing is a lack of new features listed in coding for MY22. Hopefully they are holding them back, but I'm thinking that dev resource may now be committed to the iNext/iX.

Anyone on 03/2021 notice anything new?

Alexa is working really well, but that's not new to 03/2021 specifically.

Edit: TLA is much improved with this software release

Had my first annual inspection yesterday. Dealer kindly updated the car to 03/2021.36 Nothing new to report had plenty of time (4 hrs 430kms) to play around with the DAP function and go through the whole iDrive Menu. The assisted steering still bombs out at the end of overtaking lanes and bumpy roads where the road has subsided from seasonal flooding.

Now that my annual visit to the dealer is over I intend to do some advanced FDL coding namely aSLA However before i proceed I would like to get confirmation from all you coding guru's has the coding for any of the aSLA parameters changed with this latest iStep?

I have a copy of IFR's coding sheet I downloaded in Feb which I intend to use I have also downloaded the latest psdzdata which now includes 03/2021 BTW my previous istep was 07/2020.60
Thanks

[Deja011]

Originally Posted by Bambazonke

Had my first annual inspection yesterday. Dealer kindly updated the car to 03/2021.36 Nothing new to report had plenty of time (4 hrs 430kms) to play around with the DAP function and go through the whole iDrive Menu. The assisted steering still bombs out at the end of overtaking lanes and bumpy roads where the road has subsided from seasonal flooding.

Now that my annual visit to the dealer is over I intend to do some advanced FDL coding namely aSLA However before i proceed I would like to get confirmation from all you coding guru's has the coding for any of the aSLA parameters changed with this latest iStep?

I have a copy of IFR's coding sheet I downloaded in Feb which I intend to use I have also downloaded the latest psdzdata which now includes 03/2021 BTW my previous istep was 07/2020.60
Thanks

Hi Bambazonke,

Coding for aSLA is still the same follow ifr spreadsheet. Makes sure to write down the values you are changing if you need to revert back. There are other ways to get them but this is simply the easiest method.

Also make sure you have esysx which supports mapping for 7/20 or 11/20.

[Bambazonke]

Originally Posted by Deja011

Hi Bambazonke,

Coding for aSLA is still the same follow ifr spreadsheet. Makes sure to write down the values you are changing if you need to revert back. There are other ways to get them but this is simply the easiest method.

Also make sure you have esysx which supports mapping for 7/20 or 11/20.

Thanks for the confirmation. I have already downloaded & made backup copies of the FA, SVT & the HU MGU NCD file that I have already tweaked. Need to learn how to save the NCD file as a FWL file and how to do comparisons of before and after coding

Always remembered Tokenmaster's You Tube video on coding where he made a point of making multiple copies in case the coding corrupted the files or the Laptop bombed out. I am using E Sys Pro Launcher V3.7with PSdZData 4.28.21 at the moment.

[ifr]

Originally Posted by Bambazonke

Thanks for the confirmation. I have already downloaded & made backup copies of the FA, SVT & the HU MGU NCD file that I have already tweaked. Need to learn how to save the NCD file as a FWL file and how to do comparisons of before and after coding

Always remembered Tokenmaster's You Tube video on coding where he made a point of making multiple copies in case the coding corrupted the files or the Laptop bombed out. I am using E Sys Pro Launcher V3.7with PSdZData 4.28.21 at the moment.

Nothing to add to what Deja011 said, other than

1) don't use LP 3.7. esysx is required for this coding
2) update psdzdata to 4.28.41 to support your newer i-step target

You might get away with coding aSLA with LP and older psdzdata but I would never do it. There will be a LOT of trimmed codes, and codes that TM didn't map correctly, so don't correspond with what is in the spreadsheet.

aSLA is a great feature that improves safety and convenience. Except when it sets the car to 100mph in a 30 zone because TomTom didn't provide quality mapping data!! I'd like to see an option to turn off use of the mapping data, and just rely on the KAFAS sign read.

esysx natively allows for ncd comparisons. With the expert licence you cane easily compare 2 x FA and 2 SVT to get a whole car comparison.

Manually, you simply save a file(s) to FWL from esysx launched esys FDL editor. Have 2 folders, one with the before files and one for the after. Use winmerge to compare the differences within the plain text files.

You can build a manual list of your stock ncd/fwl easily in esysx. In coding verification, load your stock FA and SVT. Export to FWL. Move the files to a folder called 'stock' (for example). Makes changes to your FA file offline. Load that modified FA in coding verification. Export to FWL. Move the files to a folder called 'Changed'. Use winmerge to compare folders.

Again, this can be done natively and simply in esysx with expert licence. With standard licence you need to follow the manual process I listed above.

[Bambazonke]

Originally Posted by ifr

Nothing to add to what Deja011 said, other than

1) don't use LP 3.7. esysx is required for this coding
2) update psdzdata to 4.28.41 to support your newer i-step target

You might get away with coding aSLA with LP and older psdzdata but I would never do it. There will be a LOT of trimmed codes, and codes that TM didn't map correctly, so don't correspond with what is in the spreadsheet.

aSLA is a great feature that improves safety and convenience. Except when it sets the car to 100mph in a 30 zone because TomTom didn't provide quality mapping data!! I'd like to see an option to turn off use of the mapping data, and just rely on the KAFAS sign read.

esysx natively allows for ncd comparisons. With the expert licence you cane easily compare 2 x FA and 2 SVT to get a whole car comparison.

Manually, you simply save a file(s) to FWL from esysx launched esys FDL editor. Have 2 folders, one with the before files and one for the after. Use winmerge to compare the differences within the plain text files.

You can build a manual list of your stock ncd/fwl easily in esysx. In coding verification, load your stock FA and SVT. Export to FWL. Move the files to a folder called 'stock' (for example). Makes changes to your FA file offline. Load that modified FA in coding verification. Export to FWL. Move the files to a folder called 'Changed'. Use winmerge to compare folders.

Again, this can be done natively and simply in esysx with expert licence. With standard licence you need to follow the manual process I listed above.

Thank you for the advice & how to do comparisons with files in FWL format I will revert back once I get the later version of the PSdZdata you quoted

[ifr]

At its most powerful level, with the right knowledge, you can generate your own FA and SVT for any vehicle as long as you know it's VIN and model details. You don't need cafd from a doner vehicle to compare against. You can build your own FA with the options you want the car to be registered with, build date , model type (USA vs ECE) etc. Use that to build an SVT, then compare that with your own FA/SVT generated fwl.

I can tell the difference between a US G05 built in 2019 vs a DE G05 built in 2021. Every coding detail without needing access to either car. Where there are hardware differences due to specified options, these are omitted from the SVT and therefore out of scope for comparison.

Similarly you can compare every feature between a MY19 car and a MY22 car as long as you have the MY22 psdzdata, esysx version that supports that psdzdata, and correctly modified FA and MY22 SVT

I'm not posting anymore DAP related future coding. I'm sharing this info so that others can start looking deeper at how the coding works. Anyone so inclined to do this level of coding should have the technical skills and self-serve attitude to fill in any blanks through personal research. If you feel the need to ask specific questions and have the answer delivered directly then this type of coding discovery is not for you. Read the esysx manual, read the esys manual, read the ISTA manual. Understand how the car works and the systems interoperate. Understand how the activation conditions work and the underlying boolean code as used by BMW engineers and developers to control features. Be aware that there are codes that when activated will effectively 'brick' some ECU's. It's a lot of work and carries risk, that most don't appreciate.

[ifr]

Originally Posted by Bambazonke

Thank you for the advice & how to do comparisons with files in FWL format I will revert back once I get the later version of the PSdZdata you quoted

Just a heads up. If you find yourself about to post a question about not being able to find 'x code', and you are using LP, then don't do it!
Just go buy esysx