Quote:
Originally Posted by LexxM3
Quote:
Originally Posted by gpitts
Quote:
Originally Posted by EJELITE
Quote:
Originally Posted by LexxM3
Just for the record, comments to me did indicate the information was for a steering stability issue that occurs below -15C, not just "cold". I had failed to mention that as it did not occur to me it might be an issue differentiator, but time will tell.
Any chance your software update is prototype?
|
I'll ask if the update is prototype if/when I hear from them today. The steering issue is noticeably worse the colder the temps, but my steering starts acting up right around 0C if its left outside for a few hours. My guess is the 'fix' should certainly encompass anything warmer than -15C if it corrects anything below that temperature. |
There's no concept of "prototype firmware". I can't imagine BMW putting anything short of a production candidate firmware update in a production vehicle. To do otherwise would be foolish at best.
Clearly their validation failed to uncover this issue, which is indeed a significant one that increases the risk of driving the vehicle in the very conditions that we bought it for to begin with! |
I don't disagree. It may be a "production candidate" rather than "prototype", but neither would (or should ever be) treated as "production quality". Even if a "production candidate" ends up being released as "production" with zero changes, until the process reaches the "production quality" metrics, it is by definition not at production quality.
I am now getting "confirmation" that what is "suddenly" available now is a pre-production of the "late July 2019" update for this issue. In "quotes" because ... who the heck really knows except BMW corporate.
An initial indication of "late July"
release of this safety-critical update versus the now sudden current availability is disconcerting to say the least. It points to invalid info in the entire story as it doesn't make coherent sense per @gpitts comments. |
You're right - only Corporate knows the timing and the real story.
I only raised the "production candidate" possibility because I've worked in the world of firmware for more years than I care to admit, and on a few occasions I've approved limited release of firmware that was technically production candidate status. In those cases, the code was simply awaiting higher-level sign off to promote the same 1s and 0s to production status, and that approver was away due to travel, vacation, etc. Exceptions like that can happen, but they're rare for sure.