shpub
Established Member
It is a nightmare for you but as someone who has been on the other side of the fence, i.e. having to write the software and then test it , it is a nightmare for the manufacturer. These systems only work because of the standards that define how they should interoperate but that does not stop tweaks and changes which can make or break a system especially when the system then relies on a slight deviation that gets tidied up without telling anyone else.
When I was with Motorola, we froze all the software that was running on the computers that were used to generate software because just little tweaks from the compiler supplier, Microsoft at al. These changes could mean the difference between something working and not working later. The issue of then having to track this down and fix it was horrendous so we did not allow any updates.
OTA is seen as an advantage but there is an argument of "if it ain't broke don't fix it". The Tesla MG5 charging program is an example of this in that the MG5s used to work but now with a couple of software revisions from TESL, the same cars no longer work. Tesla blame MG... Customers blame MG for not meeting the standards yet the reality is that it is more likely that Tesla changed something in the behaviour which MG did not know how to cope with. If Tesla had not made the changes, there would not be a problem. If MG had a better understanding of what chargers might do outside of the standard, the problem would be solved. Who is to blame?
As for overriding user settings... that will depend on the recovery strategy that is used. I used to reset the user settings if an unexpected error occurred because I did not know if the user setting combination was part of the problem! They might be valid settings but did they cause a chain of events that led to the problem. I could save them but then it would create a loop where the system would not not allow a recovery or opportunity to overwrite the "wrong" settings. When stuff bricks it is often because it is trying to do something in a loop with no escape opportunity.
Its like the display option on a PC - put in the wrong option and the display screws up. If the PC did not reset those display settings using a timeout, they could not be changed back.
As for combinations: Owners have Powerwalls with umpteen software versions, PV controllers from many suppliers with a charging unit from someone else all with different versions. Manufacturers cannot test all the combinations especially when the Powerwall seems to get a new update every 6 weeks.
I would reset the car. Charge at another source and site and then talk to the dealer.
When I was with Motorola, we froze all the software that was running on the computers that were used to generate software because just little tweaks from the compiler supplier, Microsoft at al. These changes could mean the difference between something working and not working later. The issue of then having to track this down and fix it was horrendous so we did not allow any updates.
OTA is seen as an advantage but there is an argument of "if it ain't broke don't fix it". The Tesla MG5 charging program is an example of this in that the MG5s used to work but now with a couple of software revisions from TESL, the same cars no longer work. Tesla blame MG... Customers blame MG for not meeting the standards yet the reality is that it is more likely that Tesla changed something in the behaviour which MG did not know how to cope with. If Tesla had not made the changes, there would not be a problem. If MG had a better understanding of what chargers might do outside of the standard, the problem would be solved. Who is to blame?
As for overriding user settings... that will depend on the recovery strategy that is used. I used to reset the user settings if an unexpected error occurred because I did not know if the user setting combination was part of the problem! They might be valid settings but did they cause a chain of events that led to the problem. I could save them but then it would create a loop where the system would not not allow a recovery or opportunity to overwrite the "wrong" settings. When stuff bricks it is often because it is trying to do something in a loop with no escape opportunity.
Its like the display option on a PC - put in the wrong option and the display screws up. If the PC did not reset those display settings using a timeout, they could not be changed back.
As for combinations: Owners have Powerwalls with umpteen software versions, PV controllers from many suppliers with a charging unit from someone else all with different versions. Manufacturers cannot test all the combinations especially when the Powerwall seems to get a new update every 6 weeks.
I would reset the car. Charge at another source and site and then talk to the dealer.
