You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
2013-09-18 2.5.3 Firmware 2.5.3
## Updates to thinkcity
## Remove DIAG and add ACC to V1_Production build config
## Remove InternalGPS from V2_TR_Production build config, as not required
## Cooldown: safety check (only recycle if charging), and revise cooldown current to 13A
## Support definition of location in SMS commands
## Tesla Roadster: HVAC#1 should be 0x8F not 0x87
## Logging: Don't reserve a log slot if the respective logging option is disabled
## Improve cooldown status reporting on SMS STAT
## Tidy-up of minSOC
## Move chargelimit charge stop to common vehicle.c function (not acc)
## Tesla Roadster: Updates to Tom's charge-time-predictor, with thanks
## Log cooldown charges as mode=5, and fix excessive-logging-bug related to cooldown cycles
## Logging: Send log messages one-by-one, to avoid buffer overflows
## ACC: Number homelinks from 1..3
## Tesla Roadster: support for chargelimits
## Make SMS "RESET" reset the module completely
## Complete rework and expansion of checkpoint numbers
## Stop charge after cooldown, if no subsequent charge requested
## Report CAC as part of charge log record
## Typos in acc for net_state_enter
## Show debug checkpoint, for DIAG SMS with debugcrash
## Support vehicle_fn_minutestocharge
## Add a timezone parameter (-)HH:MM
## ACC: Support timed charges
## Move car_cooldown_wascharging to global, and make use of it in ACC
## Introduce some delays to allow car to wake up
2013-08-27 2.5.2 Firmware 2.5.2
## Updates to vehicle_thinkcity.c (getting to a pretty usable vehicle module)
## Make car_tbattery signed integer, and integrate thinkcity changes
## Only report range and soc limits if >0
## Merge thinkcity changes: Think City AC-line voltage/current in SMS STAT SMS migrated from standard handler to vehicle_thinkcity.c
## Tesla Roadster: Don't stop charge after cooldown, if previously the car was already charging
## Log cooldown charges that become normal charges as two separate charges
## Tidy up diag, by removing temp test code T1 T2 T3
## Create individual configs for TeslaRoadster and RenaultTwizy (to allow all features for these cars)
## Add TRACK (type XX) vehicle that just tracks GPS
## string_to_mode utility function
## Rework vehicle inclusions. Tesla Roadster, Renault Twizy and Volt/Ampera are production. Everything else is experimental
## Add experimental vehicle Kyburz DXP
## Add HVAC message details
## Support HVAC bit in car_doors5, and cooldown cycles
## Range and charge limits handled by ACC
## Basic ACC implementation, but without timed charges
2013-08-16 2.5.1 Firmware 2.5.1
## Framework to build logging module in experimental modes
## FIsLatLongClose utiliy function (courtesy of Tom Saxton)
## Twizy: Mi/Km conversions updated to new functions
## Switch to use macros, for clarity and maintainability
## ACC integration to build environment
## Parameter support for base64 encoded parameters
## utils support for mode display
## ACC support for net_sms
## Switch logging system to use new "h" historical data submission, with acknowledgement
## Go from 4->6 log records, based on free space
## Tesla Roadster: Notify server if charge limit is changed
## Tesla Roadster: Notify server if charge mode is changed
## v2.5.1 protocol guide
## Add core support for cooldown
## Tesla Roadster support for cooldown
## Stub implementation, with basic functionality, for ACC
## Zero logging records on init, plus other safety checks
## Only initialise logging on a normal power up
## Standardise 3 diag tests: T1, T2 and T3
## Only send logging msgs if link is connected
## Fix logging prefix and some logging tests
## Revisions to CAR_IS_CHARGING logic
## Misc bug-fixes for logging
## Report distance in miles (rather than 10ths of miles)
## Remove dr++ and cr++ sequence numbers, as not required
## Make ACC commands case insensitive
## Fix bug acknowledging log record #0
## Move digital speedo feature (Tesla Roadster) from experimental to fully supported, and implement opt-in feature bits
## Honour opt-in flags for logging
## Only report debug crash reason if not normal power up, and only report once
A few things I've noticed when the roadster is trying to cool down on its own (not with OVMS): It appears to run the HVAC until there is some pre-defined difference between the brick temp (not sure which one but I think avg) and the coolant temp. It doesn't appear to start the HVAC again until 2 conditions are met: the coolant temp comes up to match the avg brick temp, and there is almost no difference between the highest and lowest brick temps. For most of the range-mode charge it attempts to keep the temp near 25C and near the end attempts to lower it to around 15C.
So I just installed firmware 2.5.4 and set the ACC parameters to do a cooldown.
I drove about 7 miles, returned (my homelink automatically worked, by the way - cool), and plugged in. Interestingly enough a cooldown starte even though the battery temp per OVMS showed 77 deg F. After 10 minutes the battery temp is now 72 deg F and cooldown is still running. Why would cooldown run when battery temp is < 88 deg F?
My parameter #15 has an encoded value similar to parameter #16. Shouldn't this be 31:60 per the documentation (or blank)?
So I just installed firmware 2.5.4 and set the ACC parameters to do a cooldown.
I drove about 7 miles, returned (my homelink automatically worked, by the way - cool), and plugged in.
Just noticed that comment. Homelink worked perfectly? So, as you drove up to your house, and it opened your gate/door automatically?
If so, thanks for confirming that. It is a really cool feature, but we don't have homelink here so I've been unable to test it properly.
Homelink has worked twice now, perfectly.
Re: parameter #15...I assumed that and changed it. No cooldown when I got back from the latest drive (battery temp was 70 deg F).
I guess it doesn't matter if I'm displaying Imperial units (i.e. my battery temp was above 31 deg F and didn't trigger cooldown)?
2013-10-11 2.5.4 Firmware 2.5.4
# Make MINSOC drive NET_NOTIFY_CHARGE (rather than NET_NOTIFY_STAT)
# Input GPIO control for input RA2..RA5, and output RC0..RC3
# ThinkCity: Updates to Think City support
# iMiev: Updates to Mitsubishi vehicle support
# Think City: Added support for switching on/off external heater/auxilary via Valet Mode button
# ACC: Aggressively stop charge if cooldown is done
# ACC: If we are waiting for a charge, but the charge is started, then stop it
# Range and SOC limits stop exactly ON the limit
# Think City: car_parktime added
# Fix for command handler with net_msg_cmd_msg
# Tesla Roadster: fix for mins remain estimate if SOC limit but no RANGE limit
# Use <=0, not ==-1, as indication range limit is not set
# ACC: Move old STAT command to PARAMS?, and add a new STAT command to show true status
# ACC: If charge is done, in acc location, and unplugged, transition to parked-in state
# ACC: Repeat tx charge mode and limit commands, during cooldown and acc charge, if necessary
# Tesla Roadster: Disable cooldown on boot
# ACC: Race condition for charge finishes before cooldown flag is cleared
# ACC: Setting params now returns a summary
# ACC: Reset acc state, if enable/disable or setting parameters
# ACC: Integer/Byte overflow workarounds
# ACC: Workaround race condition where charge may take a few seconds to actually start (when commanded)
# Tesla Roadster: Provide defaults for range, soc and cac in charge estimates
# Support car_chargeestimate
# ACC: rework to use new car_chargeestimate
2013-09-18 2.5.3 Firmware 2.5.3
## Updates to thinkcity
## Remove DIAG and add ACC to V1_Production build config
## Remove InternalGPS from V2_TR_Production build config, as not required
## Cooldown: safety check (only recycle if charging), and revise cooldown current to 13A
## Support definition of location in SMS commands
## Tesla Roadster: HVAC#1 should be 0x8F not 0x87
## Logging: Don't reserve a log slot if the respective logging option is disabled
## Improve cooldown status reporting on SMS STAT
## Tidy-up of minSOC
## Move chargelimit charge stop to common vehicle.c function (not acc)
## Tesla Roadster: Updates to Tom's charge-time-predictor, with thanks
## Log cooldown charges as mode=5, and fix excessive-logging-bug related to cooldown cycles
## Logging: Send log messages one-by-one, to avoid buffer overflows
## ACC: Number homelinks from 1..3
## Tesla Roadster: support for chargelimits
## Make SMS "RESET" reset the module completely
## Complete rework and expansion of checkpoint numbers
## Stop charge after cooldown, if no subsequent charge requested
## Report CAC as part of charge log record
## Typos in acc for net_state_enter
## Show debug checkpoint, for DIAG SMS with debugcrash
## Support vehicle_fn_minutestocharge
## Add a timezone parameter (-)HH:MM
## ACC: Support timed charges
## Move car_cooldown_wascharging to global, and make use of it in ACC
## Introduce some delays to allow car to wake up
2013-08-27 2.5.2 Firmware 2.5.2
## Updates to vehicle_thinkcity.c (getting to a pretty usable vehicle module)
## Make car_tbattery signed integer, and integrate thinkcity changes
## Only report range and soc limits if >0
## Merge thinkcity changes: Think City AC-line voltage/current in SMS STAT SMS migrated from standard handler to vehicle_thinkcity.c
## Tesla Roadster: Don't stop charge after cooldown, if previously the car was already charging
## Log cooldown charges that become normal charges as two separate charges
## Tidy up diag, by removing temp test code T1 T2 T3
## Create individual configs for TeslaRoadster and RenaultTwizy (to allow all features for these cars)
## Add TRACK (type XX) vehicle that just tracks GPS
## string_to_mode utility function
## Rework vehicle inclusions. Tesla Roadster, Renault Twizy and Volt/Ampera are production. Everything else is experimental
## Add experimental vehicle Kyburz DXP
## Add HVAC message details
## Support HVAC bit in car_doors5, and cooldown cycles
## Range and charge limits handled by ACC
## Basic ACC implementation, but without timed charges
2013-08-16 2.5.1 Firmware 2.5.1
## Framework to build logging module in experimental modes
## FIsLatLongClose utiliy function (courtesy of Tom Saxton)
## Twizy: Mi/Km conversions updated to new functions
## Switch to use macros, for clarity and maintainability
## ACC integration to build environment
## Parameter support for base64 encoded parameters
## utils support for mode display
## ACC support for net_sms
## Switch logging system to use new "h" historical data submission, with acknowledgement
## Go from 4->6 log records, based on free space
## Tesla Roadster: Notify server if charge limit is changed
## Tesla Roadster: Notify server if charge mode is changed
## v2.5.1 protocol guide
## Add core support for cooldown
## Tesla Roadster support for cooldown
## Stub implementation, with basic functionality, for ACC
## Zero logging records on init, plus other safety checks
## Only initialise logging on a normal power up
## Standardise 3 diag tests: T1, T2 and T3
## Only send logging msgs if link is connected
## Fix logging prefix and some logging tests
## Revisions to CAR_IS_CHARGING logic
## Misc bug-fixes for logging
## Report distance in miles (rather than 10ths of miles)
## Remove dr++ and cr++ sequence numbers, as not required
## Make ACC commands case insensitive
## Fix bug acknowledging log record #0
## Move digital speedo feature (Tesla Roadster) from experimental to fully supported, and implement opt-in feature bits
## Honour opt-in flags for logging
## Only report debug crash reason if not normal power up, and only report once
I installed 2.5.4 last evening. So far looks very stable. I have not tried a cool down yet but ACC is working fine for a timed charge.
I have a 1.5 Roadster....should I worry about the battery drain on the 12v battery caused by OVMS?
Anyone know the drain current of the OVMS box?
2013-11-28 2.5.5 Firmware 2.5.5
# Fix mode numnbers for display of range and performance charge modes
# V1_TeslaRoadster config: include logging, but no room for ACC
# TeslaRoadster: CTP prediction based on charge limit, not current current
# ACC: Use car_chargesubstate!=0x07 instead of pilot signal
# Add TEMPS SMS command for temperatures
# ACC: Delay CTP calculations until acc charge mode is stable
# ACC: Remove 30 minute safety margin for CHARGEBY
# Config changes to optimise what is in each config
2013-10-11 2.5.4 Firmware 2.5.4
# Make MINSOC drive NET_NOTIFY_CHARGE (rather than NET_NOTIFY_STAT)
# Input GPIO control for input RA2..RA5, and output RC0..RC3
# ThinkCity: Updates to Think City support
# iMiev: Updates to Mitsubishi vehicle support
# Think City: Added support for switching on/off external heater/auxilary via Valet Mode button
# ACC: Aggressively stop charge if cooldown is done
# ACC: If we are waiting for a charge, but the charge is started, then stop it
# Range and SOC limits stop exactly ON the limit
# Think City: car_parktime added
# Fix for command handler with net_msg_cmd_msg
# Tesla Roadster: fix for mins remain estimate if SOC limit but no RANGE limit
# Use <=0, not ==-1, as indication range limit is not set
# ACC: Move old STAT command to PARAMS?, and add a new STAT command to show true status
# ACC: If charge is done, in acc location, and unplugged, transition to parked-in state
# ACC: Repeat tx charge mode and limit commands, during cooldown and acc charge, if necessary
# Tesla Roadster: Disable cooldown on boot
# ACC: Race condition for charge finishes before cooldown flag is cleared
# ACC: Setting params now returns a summary
# ACC: Reset acc state, if enable/disable or setting parameters
# ACC: Integer/Byte overflow workarounds
# ACC: Workaround race condition where charge may take a few seconds to actually start (when commanded)
# Tesla Roadster: Provide defaults for range, soc and cac in charge estimates
# Support car_chargeestimate
# ACC: rework to use new car_chargeestimate
2013-09-18 2.5.3 Firmware 2.5.3
## Updates to thinkcity
## Remove DIAG and add ACC to V1_Production build config
## Remove InternalGPS from V2_TR_Production build config, as not required
## Cooldown: safety check (only recycle if charging), and revise cooldown current to 13A
## Support definition of location in SMS commands
## Tesla Roadster: HVAC#1 should be 0x8F not 0x87
## Logging: Don't reserve a log slot if the respective logging option is disabled
## Improve cooldown status reporting on SMS STAT
## Tidy-up of minSOC
## Move chargelimit charge stop to common vehicle.c function (not acc)
## Tesla Roadster: Updates to Tom's charge-time-predictor, with thanks
## Log cooldown charges as mode=5, and fix excessive-logging-bug related to cooldown cycles
## Logging: Send log messages one-by-one, to avoid buffer overflows
## ACC: Number homelinks from 1..3
## Tesla Roadster: support for chargelimits
## Make SMS "RESET" reset the module completely
## Complete rework and expansion of checkpoint numbers
## Stop charge after cooldown, if no subsequent charge requested
## Report CAC as part of charge log record
## Typos in acc for net_state_enter
## Show debug checkpoint, for DIAG SMS with debugcrash
## Support vehicle_fn_minutestocharge
## Add a timezone parameter (-)HH:MM
## ACC: Support timed charges
## Move car_cooldown_wascharging to global, and make use of it in ACC
## Introduce some delays to allow car to wake up
2013-08-27 2.5.2 Firmware 2.5.2
## Updates to vehicle_thinkcity.c (getting to a pretty usable vehicle module)
## Make car_tbattery signed integer, and integrate thinkcity changes
## Only report range and soc limits if >0
## Merge thinkcity changes: Think City AC-line voltage/current in SMS STAT SMS migrated from standard handler to vehicle_thinkcity.c
## Tesla Roadster: Don't stop charge after cooldown, if previously the car was already charging
## Log cooldown charges that become normal charges as two separate charges
## Tidy up diag, by removing temp test code T1 T2 T3
## Create individual configs for TeslaRoadster and RenaultTwizy (to allow all features for these cars)
## Add TRACK (type XX) vehicle that just tracks GPS
## string_to_mode utility function
## Rework vehicle inclusions. Tesla Roadster, Renault Twizy and Volt/Ampera are production. Everything else is experimental
## Add experimental vehicle Kyburz DXP
## Add HVAC message details
## Support HVAC bit in car_doors5, and cooldown cycles
## Range and charge limits handled by ACC
## Basic ACC implementation, but without timed charges
2013-08-16 2.5.1 Firmware 2.5.1
## Framework to build logging module in experimental modes
## FIsLatLongClose utiliy function (courtesy of Tom Saxton)
## Twizy: Mi/Km conversions updated to new functions
## Switch to use macros, for clarity and maintainability
## ACC integration to build environment
## Parameter support for base64 encoded parameters
## utils support for mode display
## ACC support for net_sms
## Switch logging system to use new "h" historical data submission, with acknowledgement
## Go from 4->6 log records, based on free space
## Tesla Roadster: Notify server if charge limit is changed
## Tesla Roadster: Notify server if charge mode is changed
## v2.5.1 protocol guide
## Add core support for cooldown
## Tesla Roadster support for cooldown
## Stub implementation, with basic functionality, for ACC
## Zero logging records on init, plus other safety checks
## Only initialise logging on a normal power up
## Standardise 3 diag tests: T1, T2 and T3
## Only send logging msgs if link is connected
## Fix logging prefix and some logging tests
## Revisions to CAR_IS_CHARGING logic
## Misc bug-fixes for logging
## Report distance in miles (rather than 10ths of miles)
## Remove dr++ and cr++ sequence numbers, as not required
## Make ACC commands case insensitive
## Fix bug acknowledging log record #0
## Move digital speedo feature (Tesla Roadster) from experimental to fully supported, and implement opt-in feature bits
## Honour opt-in flags for logging
## Only report debug crash reason if not normal power up, and only report once
I've been using 2.5.4 for a couple weeks now (no cooldowns required here in the great white north anymore so hard to know how well it works). My only negative feedback is on Homelink...
The Homelink signal is so strong that it can trigger my garage door from around the street corner (apparently in the gap between houses before the house on the corner). I assume the corner house then blocks the signal for a couple seconds because when I turn the corner (and thus have cleared the house on the corner) Homelink appears to still be sending and ends up stopping the garage door mid-opening. This only happens if I come down the street 90 degrees from my street, if I come straight down my street it doesn't trigger "twice." Probably nothing you can do.
Making the trigger rangers for account locations adjustable might help?
It would. If I set it for 50m instead of 100m, for example, it wouldn't trigger until I was around the corner (I think).
Actually, 50m might be a better fixed range anyway - when I turned the auto on I was concerned that from 100m down the street I may not be able to see the door. If a garage door was already open and someone was unloading groceries, for example, the door could come down on the trunk/hatch before I could reverse it.