I missed one important change for the summary:

The first RAMPS parameter ("start") now needs to be given in per mille instead of percent, and allows a value range of 1..250.

This allows for fine control over the start ramp, which also applies to transitions from driving to recuperation.

Stored profiles need to be updated manually.

Regards,
Michael

Am 06.08.2014 23:39, schrieb Michael Balzer:

https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/efe844828aa5ef9e68bbbf940379015a79ee14c8

    - Automatic recuperation level adjustment from BMS max power reading
    - SEVCON auto-login retries on switch-on
    - Power map debug output optimized
    - CFG POWER now allows power_low param up to 139% (same level as high=130%)
    - Send power statistics only if 25+ Wh used
    - Collect power (/current) min/max values per GPS section
    - Preop mode safety check in configmode() to protect against delayed SMS
    - Accel/decel stats now based on running average of speed changes
    - Client scripts now generate CSV header lines

Note: had to exclude Tesla Roadster specific CAN data from diag module
 to get space. If other cars need these, a new preprocessor switch
 can be introduced.

- Bugfix: RT-PWR-Log speed/accel stats output fixed for 0 distances
  (charge/onoff)
- Now checking for carbits vehicle alert & (new) info suppression
  (info suppression applies to trip reports)

Framework:
- Added car bits flag FEATURE_CB_SVINFOS (0x10): 1 = suppress vehicle
  informational notifies (currently only used on Twizy)



Regards,
Michael

_______________________________________________
OvmsDev mailing list
OvmsDev@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

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev