[Ovmsdev] Storing Calibration Data

Tom Saxton tom at idleloop.com
Sat May 7 03:22:33 HKT 2016

What I proposed was using data from the CAN bus to determine the Leaf pack size, then based on that use the appropriate nominal new pack Gids and rated range to calculate rated range from current SOC. I don't think that would require storing any parameter data. It's like the options on the Roadster based on v1.5 or v2.x.


On 5/6/16, 10:30 AM, "Michael Balzer" <ovmsdev-bounces at lists.teslaclub.hk on behalf of dexter at expeedo.de> wrote:

>if you want to store data that cannot be changed directly by the user,
>consider using a memory structure and base64 or binary storage in some
>parameter slot(s). That gives you 32 byte storage space per parameter
>slot, and you can combine multiple parameters if you need more.
>Have a look at the Twizy code: parameters 16..21 are marked as binary
>and exluded from direct manipulation. They contain struct
>twizy_cfg_profile data and can only be changed indirectly through a
>specific command extension.
>Am 03.05.2016 um 18:13 schrieb Tom Saxton:
>> As for configuration, I think there's real value in having a pack energy number, like rated miles, that isn't configurable so it can be compared between owners. If the parameters change, I think it should be based on model configuration (which I'm hoping can be determined from the CAN bus), and not from owner configuration.
>Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>OvmsDev mailing list
>OvmsDev at lists.teslaclub.hk

More information about the OvmsDev mailing list