[Ovmsdev] Ready for 3.2.009

Mon Feb 3 10:52:28 HKT 2020

Not sure. It was like that when I got to it.

  Firmware:          3.2.009-2-g39cdb7e/ota_0/edge (build idf v3.3-beta3-775-gdc1ca69 Feb  3 2020 09:00:33)
  Running partition: ota_0
  Boot partition:    ota_0
  Factory image:     3.1.001
  OTA_O image:       3.2.009-2-g39cdb7e
  OTA_1 image:       3.2.009-1-g92cc5ed
  Server Available:  3.2.009-2-g39cdb7e (no update required)

I think it all looks ok. You have the latest.

It now looks ok, and probably worth squeezing these last few updates in. So, I will make a 3.2.010 now and release to EAP.

Regards, Mark.

> On 3 Feb 2020, at 10:49 AM, Greg D <gregd2350 at gmail.com> wrote:
> 
> Hi Mark,
> 
> Saw the update Metrics look good now. What changed?
> 
> The module is reporting another update is pending for tonight. 3.2.009-2-g39cdb7e. Same version number...
> 
> Greg
> 
> On February 2, 2020 4:24:35 PM PST, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
> Greg,
> 
> On the server I am seeing you running 3.2.008-134-ge6ac0c7/ota_0/edge and all the data looks fine. For example:
> 
> ovms> metric list v.b
> ...
> Vehicle Response:
>   v.b.12v.voltage                          13.04V
>   v.b.12v.voltage.ref                      12.6V
>   v.b.cac                                  136.777Ah
>   v.b.consumption                          0Wh/km
>   v.b.current                              1A
>   v.b.health                               CAC 136.78Ah SOC 94% LIM 83% MIN 83% MAX 85%
>   v.b.p.level.max                          85%
>   v.b.p.level.min                          83%
>   v.b.power                                0.3985kW
>   v.b.range.est                            196.339km
>   v.b.range.ideal                          255.885km
>   v.b.soc                                  95%
>   v.b.soh                                  82.9213%
> 
> ovms> metric list v.c
> ...
> Vehicle Response:
>   v.c.charging                             no
>   v.c.climit                               24A
>   v.c.current                              0A
>   v.c.duration.full                        14Min
>   v.c.kwh                                  9kWh
>   v.c.mode                                 standard
>   v.c.pilot                                yes
>   v.c.state                                done
>   v.c.substate                             powerwait
>   v.c.time                                 0Sec
>   v.c.voltage                              0V
> 
> The temperature bug for Roadster is a known issue, and is fixed in 4082bb2a (and released in 3.2.009).
> 
> I triggered an update for you (to 3.2.009-1-g92cc5ed), and that installed ok. I’ll try to find out if the temperature bug is fixed now or not.
> 
> Regards, Mark.
> 
>> On 3 Feb 2020, at 5:08 AM, Greg D. <gregd2350 at gmail.com <mailto:gregd2350 at gmail.com>> wrote:
>> 
>> Um, I just noticed that all the metrics except for the 12v battery
>> voltage are zero.  The car is awake and charging right now, but hasn't
>> been driven since the software update to 3.2.008-134-ge6ac0c7, if that
>> matters.  I believe the TPMS metrics don't update until it's driven, but
>> I should be seeing the temps.  All gray and zero.
>> 
>> I tried putting the car in Drive (just sitting there), and the TPMS data
>> came on after a few minutes.  But the rest of the metrics are still zero
>> and gray.
>> 
>> The VDS shows the correct temps, and is operating normally.
>> 
>> Oops?
>> 
>> Greg
>> 
>> 
>> Greg D. wrote:
>>> My module updated to 3.2.008-134-ge6ac0c7 last night (2am local), and
>>> did the single update as it should.  m.version is consistent with this. 
>>> The module sees your 3.2.009-1-g92cc5ed as available.  Presume it will
>>> update tonight.
>>> 
>>> So, all "go" from this console.
>>> 
>>> Greg
>>> 
>>> 
>>> Mark Webb-Johnson wrote:
>>>> I’ve tagged 3.2.009 based on where we are today, and built on my edge.
>>>> 
>>>> If no problems reported overnight, I’ll push to EAP tomorrow.
>>>> 
>>>> Regards, Mark.
>>>> 
>>>>> On 2 Feb 2020, at 6:21 PM, Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> wrote:
>>>>> 
>>>>> Am 02.02.20 um 02:13 schrieb Mark Webb-Johnson:
>>>>>> Seems we are ready for another release. I made a number of fixes yesterday, and maybe able to make a few more today, then I am done and ready to release 3.2.009.
>>>>>> 
>>>>>> Anything else to put in this?
>>>>> OK, nothing open here.
>>>>> 
>>>>> Regards,
>>>>> Michael
>>>>> 
>>>>> 
>>>>>> Regards, Mark
>>>>>> _______________________________________________
>>>>>> OvmsDev mailing list
>>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>>>> -- 
>>>>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>>>>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>>>> 
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>> 
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
> 
> 
> -- 
> This space for rent...
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20200203/20415482/attachment.htm>