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?
Does anybody else have an OVMS fitted to a Nissan Leaf AZE0-2?
Hi Paul, I'm new to OVMS so very far from expert, it's been a steep learning curve. I had very similar issues (might yet repeat) but I found that installing the "OVMS connect" app and switching v3 server has helped. Also you say that you are not using remote climate; this can be THE point of issue. When our 2018 env200 does not respond, activating climate is the almost sure fire way to wake the car and then the other activations will work.
At moment I'm trying to write script for start / stop charge of the car (without reliable success so far...) and hope to create custom button commands for 80% and 100% charging options. Still not 100% convinced I have the car set up with best parameters for reliable function but slowly getting there - of course you have a different car so you experience will vary.
I have bitten the bullet and pulled my car apart to get at the TCU.
On this model (AZEO-2 Japanese model with G trim) the TCU is connected to BOTH the CAR-CAN bus and the AV-CAN bus. This was easily verified by measuring (with the 12V battery disconnected) continuity between the OBD-II port pins and the pins of 40 pin TCU connector.
Inside the TCU the CAR-CAN pins of the connector are easily accessible and can be readily cut. I have done so. No functionality was lost:
- Remote control features had already been lost when the car was exported from Japan as a used vehicle.
- The hansdfree mic still works.
+ The OVMS has correctly stopped and started charging when it should, A/C was started and stopped when requested on the OVMS app and I was able to lock and unlock the car from the app while A/C was on. Now that I've modified the TCU to stop it interfering with the OVMS, presumably it will now operate reliably!
But.. How do we get the installation manual updated to provide the correct instructions for the AZE0-2?
Clone the github repo, update the documentation .rst file, commit, and send in a pull request.
If you don't know git, then perhaps just send in the suggested changes (add this paragraph, change that, etc) to OVMS developers mailing list, and someone there should be able to help.