[Ovmsdev] New features: sufficient charge alerts, ideal max range

[Michael Balzer]

Mark,

it doesn't seem the old Android App supports setting arbitrary features? 
I currently have to use SMS to set them.

I need these configs to be persistent as the module does quite a lot of 
resets at the moment, it seems especially if GPRS connectivity is bad.

I just had to take yet another persistent feature slot (13) in use to 
store my last known range due to permanently losing my range 
calculations during charge.

I tried to sort out why I get those resets and found the
     // Temporary kludge to record in feature #10 the number of times 
this happened
...but my value was not increased, even after I watched the module doing 
a reset.

Is there another condition for an automatic reset? I found none...

I thought feature slots are especially meant for this kind of user 
configuration. I could avoid using feature slots at all if a) the module 
would only do a reset if absolutely needed (so I don't lose my local 
configuration) and b) I can introduce a car specific command to set my 
local configuration. Or is there another way?

Regards,
Michael


Am 11.11.2012 13:35, schrieb Mark Webb-Johnson:
> 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 at expeedo.de> wrote:
>
>> Mark,
>>
>> I just checked in my latest Twizy updates:
>>
>> https://github.com/dexterbg/Open-Vehicle-Monitoring-System/commit/0a70e483baf182f4226d1a1afc8d0734c2fa48d9
>>
>> 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 at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

-------------- next part --------------
A non-text attachment was scrubbed...
Name: dexter.vcf
Type: text/x-vcard
Size: 206 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20121111/c4f6574a/attachment-0002.vcf>