[Ovmsdev] Framework V3.1

[Michael Balzer]

Also, the "S" corruption originates from just a 
single wrong character inserted in the encoded 
protocol message, i.e.

+cGF352j_<F3>_FeLiJ59cMLlOXpRJhGa7sMGM9Rg/WeXeJuwKGCiuqv8p4FVNCKiHEsEnf9WeNbnm6JGPz7yxD7KjlQtOSVFtHXH2DGUa+C0x5ZaZRiSv6HpLxBkvIEBEu0f4EBPjF+X
or
+dUShf7R71hcb7msV8SCXu55xEwG9Z3Dx9G4UNuO9V7t7JFnGYwSmrf5aWouO+rm1PdZfQgLENbGLMVbv/tRfkEA+vZRPapkU_<DB>_KSO92hqvnrVcgJOVYNiglaXPqMt92lKXatEVO1

-- IMO that cannot originate from the base64 
encoding, so can only come from some UART TX 
related problem (?)

May be a serial log can show what's happening here.



Am 05.01.2017 um 13:06 schrieb Michael Balzer:
> Tom,
>
> from my logs archive:
>
> a) I found "duplicate car login" and "unable to 
> decode" errors from your car beginning on 
> 2016-12-14 15:50 (UTC)
> ...that was with firmware 2.8.7/NL1.0/V2/V2E9
>
> b) garbage characters first occurred in the "S" 
> messages beginning with 2017-01-01 12:16
> ...that was right after changing your firmware 
> to 2.9.2/NL1.0/V2/V2E9
>
> The "L" message corruptions due to the stp_l2f 
> bug started on 2017-01-04 03:05 with 
> 3.1.1/NL1.0/V2/V2E9.
>
> The "S" corruptions only occur with your car (on 
> my server).
>
> My earliest log kept is from 2016-12-10, and 
> your car messages were clean and error free 
> until 2016-12-14 15:50.
> Can you tell what has changed on 2016-12-14 15:50?
>
> Regards,
> Michael
>
>
> Am 05.01.2017 um 04:08 schrieb Tom Parker:
>> On 05/01/17 02:00, Michael Balzer wrote:
>>
>>> Checking the server log I found another bug I 
>>> introduced some time ago in the server push 
>>> notification code.
>>> I just restarted the fixed server, tell me if 
>>> the authentication notifications still occur.
>>
>> The authentication success/failed messages are 
>> still occurring.
>>
>> At 10:39 today I got a trunk open while in 
>> valet mode alert via SMS but not via email and 
>> communication stopped. I'm not setting the 
>> trunk or valet bits in the leaf firmware.
>>
>> I'm logging the server traffic with client.pl 
>> and I see this, where <FA> represents the raw 
>> hex 0xfa and ^E is probably whatever ctrl-e is.
>>
>> Thu Jan  5 10:29:24 2017  Server message 
>> decodes to: MP-0 T0
>> Thu Jan  5 10:29:24 2017  Server message 
>> decodes to: MP-0 
>> S77,K,0,0,stopped,standard,105,0,0,0,0,0,0,0,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1,-1<FA>_<8D>D<80>~^^D<A0>^Ev<D7>O<FA>
>> ~^N
>> Thu Jan  5 10:29:24 2017  Server message 
>> decodes to: MP-0 T0
>> Thu Jan  5 10:29:24 2017  Server message 
>> decodes to: MP-0 Z0
>> Thu Jan  5 10:29:35 2017  Server message 
>> decodes to: MP-0 Z1
>> Thu Jan  5 10:39:25 2017  Server message 
>> decodes to: MP-0 Z0
>>
>> I think there must still be a corruption bug 
>> somewhere. It might be time to bisect.
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>
>


-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.teslaclub.hk/pipermail/ovmsdev/attachments/20170105/797e3c10/attachment.html>