Bennett,

I committed some code over the (long chinese new year) weekend to try to handle this. Problem is that there are some edge cases where the behaviour may be unexpected.

For example:


At the moment, I've got it coded as:


While I was at it, I also implemented a few other nice features:

  1. I fixed the ESS < 0celcius bug (signed char not the same as signed int, in a cast)
  2. I added a RADIUS parameter to ACC. You can now specify 'RADIUS xxx' (in feet if the car is Imperial, or metres if the car is Metric - just using 3 feet = 1 metre). The default is still 100metres, but you can now tune this on a per-ACC-location basis. P.S. Take care - GPS jumps around and is probably only accurate to 10 or 20 metres in most open air cases (less if view to the sky is obstructed). You can probably get away with small ACC radiuses for HOMELINK activation, but for charging I would leave it reasonably high. The algorithm to find an ACC location will find the _first_ matching location (by acc location number).

Regards, Mark.

On 1 Feb, 2014, at 11:12 pm, Bennett Leeds <bennettleeds@gmail.com> wrote:

I had a power failure last night, so charging was interrupted.I went to the iOS app to charge, and it did, then stopped. Tried again. Went out to the car and saw that "Charging Stopped by Request."

Sent a "ADD DISABLE 1" message, and than charging started fine.

Shouldn't a charge initiated from the smartphone app happen no matter what? For a crude implementation,it could do a temporary ACC DISABLE until charge is complete and then reinstate ACC.

thanks
- Bennett

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev