[Ovmsdev] v2.2.5
Mark Webb-Johnson
mark at webb-johnson.net
Tue Apr 2 20:52:32 HKT 2013
Tom,
After 24 hours in my car, it has been 156.94 through 2 charges and 2 drives. I'm not sure how Tesla calculates this, but it seems very stable.
It was also 156.99 just three weeks ago - Car doesn't like sitting idle while I'm sick :-(
There are some app changes being made at the moment - once those are done, I'll get it added to the Info screen on the Apps.
Regards, Mark.
On 2 Apr, 2013, at 1:16 AM, Tom Saxton <tom at idleloop.com> wrote:
> I'm so looking forward to being able to easily get the CAC value!
>
> In our Roadster, the CAC seems to update when the SOC settles, which is
> typically about 10 minutes after a charge or drive, although sometimes it
> takes longer. So it would be perfect to query the CAC:
>
> - 30 minutes after a charge
> - 30 minutes after the car is turned off
> - when the car is turned on within 30 minutes of a charge or turn off
>
> If you don't want to mess with that complexity, (a) and (b) are pretty
> effective. Based on what I've observed, I would expect (b) and the following
> (c) to always return the same result for a Roadster, bu it would be
> interesting to confirm that.
>
> Tom
>
> on 4/1/13 3:59 AM, Mark Webb-Johnson wrote:
>
>> This is now in my car, and running well.
>>
>> For CAC, I had:
>>
>> rx msg S 66,K,222,0,charging,standard,206,200,56,0,100,0,5,1,0,0,0,-1,0
>>
>> then, I started a charge, and now get:
>>
>> rx msg S 66,K,223,0,charging,standard,206,200,56,0,100,0,5,1,0,0,0,-1,15694
>>
>> That's what I would expect - the code will poll for latest CAC whenever (a) a
>> charge starts, (b) the car is turned on, or (c) the car is turned off.
>>
>> Regards, Mark.
>>
>> On 1 Apr, 2013, at 5:30 PM, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
>>
>>>
>>> Back from the brinkŠ Good grief, there is some nasty stuff coming out of
>>> China now.
>>>
>>> I managed to spend some time on OVMS firmware today, and built v2.2.5. Change
>>> log is:
>>>
>>> 2013-04-01 2.2.5 Firmware 2.2.5
>>> ### Fixes for charge notification logic on VA
>>> ### Show charge, trunk and alarm notifications in DIAG
>>> mode
>>> ### Speed, parking, and general tidy-ups for VA
>>> ### Switch ambient temperature to PID 0x801f for VA
>>> ### Auto-calibration for 12V line reading
>>> ### Twizy version 2.6.1 - power line plug-in detection
>>> ### Add car_doors5 for rear doors, frunk and 12v
>>> charging
>>> ### 12v alert by MSG protocol fix
>>> ### Rework of 12V reference logic
>>> - Filters out single peaks / misreadings
>>> - Sends "OK" alerts if voltage level restores w/o
>>> charging
>>> - 15 minutes calmdown before taking new ref
>>> voltage
>>> - No alerts while car is on
>>> ### ESS SOC DIAG (for TR)
>>> ### Initial support for CAC in TR and TZ modules
>>> ### Experimental Tazzari (TZ) module
>>> ### Experimental Nissan Leaf (NL) module
>>>
>>> All is in github.
>>>
>>> I haven't run it in my car yet, but it tests out fine on the bench. It is
>>> going into my car in a few minutes time.
>>>
>>> Major changes are the experimental support for Tazzari, some bug fixes and
>>> 12V work on Twizzy, and support for CAC readings in Tazzari and Tesla
>>> Roadster (including protocol extensions to report back to apps).
>>>
>>> Regards, Mark.
>>>
>>> P.S. I haven't had time to make anything good for 1st April this year
>>> (although I did consider an experimental module for Hummer support). Anyway,
>>> please consider any bugs in this version just an April fools joke.
>>>
>>> _______________________________________________
>>> 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
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
More information about the OvmsDev
mailing list