Leaf 2016: Timed climate control start aborted by pilot interruption

[chris8086]

Situation:

• Leaf Tekna 2016, with TCU present
• Dashboard charge timer disabled
• Dashboard climate timer set to warm interior by 07:50
• Low power (13A) EVSE connected since previous night
• Previous night's charging was stopped by configured SOC limit

When the climate timer decides it needs to activate, OVMS records the follow sequence:
2024-12-05 07:20:02.946 GMT D (303250766) events: Signal(vehicle.charge.pilot.off)
2024-12-05 07:20:03.046 GMT D (303250866) events: Signal(vehicle.charge.pilot.on)
2024-12-05 07:20:04.056 GMT D (303251876) events: Signal(vehicle.charge.start)
2024-12-05 07:20:04.276 GMT I (303252096) ovms-server-v3: Tx notify ovms/notify/info/v-nissanleaf/charge/status=Target charge level reached (53%)
2024-12-05 07:20:04.366 GMT I (303252186) v-nissanleaf: Stop Charging

This suggests to me that the sudden current draw causes a spurious absence of pilot signal. When the pilot is restored, the vehicle thinks the cable has just been plugged in and so it needs to start charging. It does so, then OVMS realises what's going on and tells the car to stop charging.

The problem is that this sequence of events also cancels climate control, meaning the car fails to warm up.

Obviously OVMS software cannot fix the hardware issue of an interruption to pilot signal. But I am wondering what is the best workaround to implement. One idea is to have a configured time period during which SOC limit is not applied. This would mean I could tell it to ignore SOC between 07:00 and 08:00, with the result that OVMS won't intervene, and climate control won't be interrupted by a charge stop command.

Would that be a reasonable approach?

fault-debug-log.txt