[Ovmsdev] Issues since latest update (3.2.0.14)

Tue Sep 1 08:40:24 HKT 2020

I’ve asked the guy with issue on the support ticket to try 3.2.013.

Regards, Mark.

> On 1 Sep 2020, at 1:28 AM, Michael Balzer <dexter at expeedo.de> wrote:
> 
> FYI: I also had a crash report from a guy with a 2018 Nissan eNV-200 40KW using the Leaf adaption.
> 
> He wrote the last working OVMS version was 3.2.013-223-g7c41d3a6, all versions after that crash as soon as he starts the car.
> 
> I pointed him to the Leaf developers, but it seems he didn't manage to file an issue.
> 
> Regards,
> Michael
> 
> 
> Am 31.08.20 um 14:48 schrieb Sébastien Darveau:
>> Hi Mark,
>> 
>> I did change the DNS but it didn’t fix the problem so I reverted to previous version. It looks like it is Leaf 2015 specific as reported here by someone else:
>> 
>> https://www.openvehicles.com/node/2587 <https://www.openvehicles.com/node/2587>
>> 
>> I suspect the new wifi feature because it seems to happen when leaving the wifi range.
>> 
>> Thanks,
>> Sebastien
>> 
>>> On Aug 19, 2020, at 10:50 AM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>>> 
>>> Please try with 8.8.8.8, to rule out a dns issue.
>>> 
>>> The reason I suggest this is because I have seen that ‘parse error’ before resulting from failed dns lookups.
>>> 
>>> Regards, ?Mark
>>> 
>>>> On 19 Aug 2020, at 9:08 PM, Sébastien Darveau <sebastien.darveau at synnoetic.com <mailto:sebastien.darveau at synnoetic.com>> wrote:
>>>> 
>>>>  Strangely, it is connected on my home wifi. DNS are 212.9.0.135 and 212.9.0.136 and I can resolve openvehicles.com <http://openvehicles.com/> correctly with nslookup on my laptop. Since everything works perfectly after a reboot, it is not a dns issue but a degradation while the box is running. It seems to worsen when going out of wifi range and back but I’m still not sure about this.
>>>> 
>>>> A new error appeared this morning but probably unrelated:
>>>> 
>>>> E (140391333) can: can1: intr=14187292 rxpkt=14151479 txpkt=3057 errflags=0x8040d9 rxerr=0 txerr=131 rxovr=23 txovr=0 txdelay=0 wdgreset=0                     errreset=0
>>>> 
>>>> Thanks,
>>>> Sebastien
>>>> 
>>>>> On Aug 19, 2020, at 2:25 AM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>>>>> 
>>>>> What are your DNS servers set to?
>>>>> 
>>>>> Can you try with 8.8.8.8, if you aren’t already, and don’t use ISP/cellular DNS servers.
>>>>> 
>>>>> Regards, Mark.
>>>>> 
>>>>>> On 19 Aug 2020, at 2:02 AM, Sébastien Darveau <sebastien.darveau at synnoetic.com <mailto:sebastien.darveau at synnoetic.com>> wrote:
>>>>>> 
>>>>>> Hello,
>>>>>> 
>>>>>> Anyone else is having connection issues since latest update? I’m constantly loosing contact with the device and haven’t been able to open a console with USB but this time, I can still access it with the Web interface and noticed it can’t connect to server.
>>>>>> 
>>>>>> E (72178423) ovms-server-v2: mg_connect(api.openvehicles.com:6867 <http://api.openvehicles.com:6867/>) failed: cannot parse address
>>>>>> E (72178423) ovms-server-v2: Status: Error: Connection failed
>>>>>> W (72180093) simcom: UART hw fifo overflow
>>>>>> W (72192873) gsm-mux: Frame overflow (2048 bytes)
>>>>>> E (72238423) ovms-server-v2: mg_connect(api.openvehicles.com:6867 <http://api.openvehicles.com:6867/>) failed: cannot parse address
>>>>>> E (72238423) ovms-server-v2: Status: Error: Connection failed
>>>>>> E (72298463) ovms-server-v2: mg_connect(api.openvehicles.com:6870 <http://api.openvehicles.com:6870/>) failed: cannot parse address
>>>>>> E (72298463) ovms-server-v2: Status: Error: Connection failed
>>>>>> 
>>>>>> Address looks good though.
>>>>>> 
>>>>>> Sebastien Darveau
>>>>>> sebastien.darveau at synnoetic.com <mailto:sebastien.darveau at synnoetic.com>
>>>>>> 
>>>>>> _______________________________________________
>>>>>> OvmsDev mailing list
>>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <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 <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 <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 <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 <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
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

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