There seems to be an issue with the latest OBD2 polling code changes (?) https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/221 …or maybe it's just a Volt/Ampera issue? We should try to clarify / resolve that for 3.2.002. It would be so nice if Espressif would at least communicate on the PSRAM fix progress… Regards, Michael Am 08.05.19 um 07:31 schrieb Mark Webb-Johnson:
Let’s cut-off at Friday night (UTC). Then, Saturday I will build a 3.2.002 and put it into ‘eap'. Then perhaps ‘main’ mid next week?
I had hoped that Espressif would fix the PSRAM corruption issue, but they say still working on it - I think no point waiting longer for that.
Regards, Mark
On 8 May 2019, at 1:23 PM, Anko Hanse <anko_hanse@hotmail.com> wrote:
Hi Michael,
I am currently testing a change that I would really like in there, as it is a follow-up to earlier changes in this version (making the Leaf code less dependent on the 'max_gids' setting) So far the tests gave no issues, so I think I will be ready to push my changes either tomorrow or Friday. Could you wait with the new release until then?
OKidoki, Anko
-----Original Message----- From: Michael Balzer <dexter@expeedo.de> Sent: Wednesday, 8 May 2019 6:58 AM To: ovmsdev@lists.openvehicles.com Subject: [Ovmsdev] Time for 3.2.002?
The Twizy code has finally reached release 1.0. With my recent additions, all V2 features I planned to include in V3 are now done.
As we're also again >200 commits from 3.2.001, maybe it's time for 3.2.002?
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@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