Michael, I guess you need these as features, so they can be set from the App? If so, can they be put as experimental at the moment? Those won't survive a reboot, but are less impacting. I suggest 0x05, 0x06 and 0x07. For MAXRANGE, that is fine. Make it a permanent feature, 0x0D. Regards, Mark. On 11 Nov, 2012, at 7:42 AM, Michael Balzer <dexter@expeedo.de> wrote:
Mark,
I just checked in my latest Twizy updates:
https://github.com/dexterbg/Open-Vehicle-Monitoring-System/commit/0a70e483ba...
These contain two extensions that could be generally useful:
1) As the Twizy "ideal" range varies widely depending on your driving, geography and environment, I implemented a feature for that config.
2) If I just need an intermediate charge for a certain SOC or range (to get home for example), I can now activate an alert for one or both values.
I used the next three free feature slots for these:
#define FEATURE_SUFFSOC 0x0A // Sufficient SOC feature #define FEATURE_SUFFRANGE 0x0B // Sufficient range feature #define FEATURE_MAXRANGE 0x0C // Maximum ideal range feature
I know, feature slots are getting full... what do you think?
Regards, Michael
-- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
<dexter.vcf>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev