The installation instructions for this model (2016 AZE0-2) do NOT request the disconnection of the TCU like they do for the earlier and later versions (it notes it is on the CAR CAN bus). Is this deliberate or a misinterpretation of the authors' intent? I have neither attempted disconnection of the TCU nor have I disabled its output.
I have had intermittent problems with the OVMS failing to lock / unlock / start charging / stop charging for the 3 years I've been using it. We haven't been using the remote climate control feature so I will not comment on that. This failure mode can occur...
1. when using the Android app
2. when using the the web interface
3. after setting the OVMS to stop charging at a specified SoC (I usually set this to 81%) and the SoC being reached. This is of most concern to me as it it why I got the OVMS. There is no other simple way of preventing charging from running to 100% SoC.
These features (i,e, OVMS commanding the car) work sometimes but then inexplicably stop working even when tried repeatedly. They have tended to work again after unplugging the OVMS for a short while, or maybe after rebooting it. Since the app was updated recently I have no longer had success at getting the OVMS to successfully "stop charging" by any method.
Is it possible that this behaviour is the result of a conflict with the TCU?