[Ovmsdev] Open issues blocking release 3.2.016

[Chris van der Meijden]

For the VW e-Up all is fine by me. The blocking by T26 as hypothetical
protection for triggering the extended 12v charging is still in the
code. That is, from my point of view, the way to go, as long is this
behaviour is still not completely understood.
Regards
Chris



Am Samstag, den 27.02.2021, 16:47 +0100 schrieb Michael Balzer:
>     As the other thread got off-topic: I'd still like to get forward
>     regarding release 3.2.016.
> 
>     
> 
>     We identified three open issues:
> 
>     
>       VW e-Up sometimes stays awake for 4-5 hours.
>       Wifi AP connection is unstable with some devices.
>       More frequent location flatbed theft false alerts.
> 
>       
>     
>     My current status on these is:
> 
>     
>       …is probably not a bug on the OVMS but rather a real behaviour
>         of the e-Up performing an extended 12V trickle charge.
>       …has only been reported by Steve Davies and seems (?) to have
>         been solved by the default scan timings – Steve?
>       …seems to be a Heisenbug, i.e. hasn't had any reports since we
>         added extended logging.
> 
>       
>     
>     Is my status correct? If so, I think these should no longer stop
> us
>     from releasing 3.2.016.
> 
>     
> 
>     Regards,
> 
>     Michael
> 
>     
> 
>     
>   
> 
> _______________________________________________
> 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/20210227/8f6fb1fa/attachment.htm>