FiFi
Standard Member
No need to apologise Jonathan - it can only be a good thing that generally the idea that this could happen is thought of as impossible! I will update when I next hear from the dealer
'airbags' aren't filled with air - they are filled very rapidly by the gaseous products of the combustion (deflagration) of a substance such as sodium azide (there are other substances; pyromechanics is a big and very specialist subject); if the airbag has initiated it will be quite obvious, although the bag itself will, after inflation, deflate (mostly) equally rapidly as the gas cools. It sure as hell shouldn't have 'a bit poking out...'Hi Tigi not sure what you mean but if you can see the airbag pushing through the plastic seal of the centre section of your steering wheel and it’s white dust on the steering wheel would you take the chance of driving it? Might not activate but I definitely won’t be putting it to the test
I suppose it depends on how much faith you put in the manufacturer?Does anybody remember the day when purchasing a car, you received a finished product. Like a video game, it had been tested, and what you received was what you were going to have. Now, with Tesla and all cars electronic, after an update, you never know if you are going to have an update which will completely change the way the car drives. Just like games. Feels like we are somewhat driving a video game.
slightly off topic.
The issue here is twofold: (i) the scale of model testing needed to provide an adequately high 'confidence interval' (level of confidence of correct operation) prior to release, (ii) ensuring the 'model' adequately represents reality. Key to understanding complex systems (like the new cars) is that the budget bounds the modellers manhours-on-job, hence bounding the V&V (Verification; part (i) above) & Validation (part (ii) above) effort. A big area...Does anybody remember the day when purchasing a car, you received a finished product. Like a video game, it had been tested, and what you received was what you were going to have. Now, with Tesla and all cars electronic, after an update, you never know if you are going to have an update which will completely change the way the car drives. Just like games. Feels like we are somewhat driving a video game.
slightly off topic.
FiFi; we all sympathise/agree with the sentiment and overall meaning of what you've written there, but the reality of 'code' is that most often the 'bugs' are very simple 'low-level' instructions that occur due to a number of reasons - coder error at the fundamental stage is only one of them. Usually the bugs can be pre-empted at coder level by doing such stuff as 'N2' (n-squared) analysis, which is a way of checking all inputs and outputs of a function. But at a lower level, where the machine code is (usually) auto-compiled (i.e. the actual computer instruction set is created from the human/high-level function designer), the compilers can (do) have their own bugs, so even flawless top-level 'code' can have bugs introduced within the actual compiling hence computational stages. [See 'Incose' for further insight.]My husband has a Tesla - in general I do not ever compare or contrast my MG4 with his on performance or range, features etc as that would be ridiculous. However, his updates are direct to the car and a detailed report of what is being updated is provided and this can be accessed. Off topic the AA guy last week told me of a call out he went to when he was told to leave the Tesla he was attending on the drive as the repair that was needed would be sent through to the car and it would be repaired by next morning which he said felt like a real wow moment.
Dealer says I’m not to assume that this issue is due to an update and we need to wait for the investigation to be completed to be sure that this isn’t just a coincidence. However, a big concern for me whichever way this goes is that the dealer does not know what is going on your car. I want to know what they are adding to my car when I get my car back. I don’t want just a code to the unit concerned, I want to know what it is and what it does. This has to change and something we should push for I think.
Also, since all updates apart from to the entertainment system are updated at the dealer & I picked up my car on 5th November and by 14th December there were 5 updates available for my car so what are we supposed to do about having these updates added when there is no other need for the car to go back to the dealer? Do we call the dealer every now and then asking if updates are available and book it in? Will they do an update whilst you wait appointment? Otherwise the updates will back up and our cars will be running on different versions? It does feel a bit ’clunky’.
The only coding issues I had with my 2020 Mitsi ASX was with the service staff. Their computational output vs their instructional input were always naff. I believe there could have been a coding glitch in the centres revolving around the ‘I’m too good for this job’ or potentially the ‘I’m doing the bare minimum to get by’. The latter involves a severe deficiency in their listening module. I think they were recently testing the new ‘Blank Stare 2.0’ module.FiFi; we all sympathise/agree with the sentiment and overall meaning of what you've written there, but the reality of 'code' is that most often the 'bugs' are very simple 'low-level' instructions that occur due to a number of reasons - coder error at the fundamental stage is only one of them. Usually the bugs can be pre-empted at coder level by doing such stuff as 'N2' (n-squared) analysis, which is a way of checking all inputs and outputs of a function. But at a lower level, where the machine code is (usually) auto-compiled (i.e. the actual computer instruction set is created from the human/high-level function designer), the compilers can (do) have their own bugs, so even flawless top-level 'code' can have bugs introduced within the actual compiling hence computational stages. [See 'Incose' for further insight.]
I don't mean to be pious or preachy here, just realistic. We collect our sesr tomorrow, hopefully (if the airbags/keylocking/breather/... are all sorted prior), but our ID.3 has a few foibles on the car computer side, so even paying for 'German efficiency' doesn't get one entirely out of the problem area.
Good luck!
Sorry I completely disagree. I had one of the first uk M3P’s. Whilst yes Tesla were constantly providing OTA updates they didn’t always get it right. Remember the appalling auto wipers? Many attempts to get this right. The horrendously dangerous phantom braking? Again ages to fix. The UI changes that moved everything around and made it harder to see? Yes OTA is brilliant but by no means perfectly tested each version.I suppose it depends on how much faith you put in the manufacturer?
I used to love seeing what had changed with the early OTA updates that were regularly ported to the model 3. My performance model had 2 power increases during the time I owned it, think it gained just short of 50hp in total. Also lots of UI improvements, bug fixes and new functions added such as auto battery pre-conditioning. I can't remember anything that felt 'untested' and made it worse.