On that topic, what other data can OVMS provide about the charging session? Just interested as to what we can/should include in OCM. For OCM this would be a flexible chunk of OVMS specific (JSON format) data attached to the checkin which OVMS can add/remove fields to over time. OVMS could also provide a textual comment "charged for 30 mins @ 240V/70A" or similar but we would have the more detailed breakdown available for later parsing. Chris On 23/05/2014 09:38, Tom Saxton wrote:
I'm not proposing that OVMS develop a charging location database. It merely stores charging reports, "at this date and time, someone charged at 240V/70A at this longitude and latitude."
Tom
On May 22, 2014, at 3:44 PM, Lee Howard <lee.howard@mainpine.com> wrote:
On 05/22/2014 02:49 PM, Tom Saxton wrote: I'd like to make sure that whatever happens with OVMS reporting charging station information stays open and stand-alone, not tied exclusively to OCM. Is OCM not open-enough already that it could simply be viewed as the charging-location database for OVMS? Why should OVMS duplicate the effort of developing a charging-location database?
Lee.
-- *Lee Howard* *Mainpine, Inc. Chief Technology Officer* Tel: +1 866 363 6680 | Fax: +1 360 462 8160 lee.howard@mainpine.com | www.mainpine.com
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev