[Ovmsdev] Storing Calibration Data

[Michael Balzer]

Tom,

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.

Regards,
Michael


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

-------------- 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/20160506/ca24ca17/attachment-0002.vcf>