[Ovmsdev] Wrong Roadster Data

[Mark Webb-Johnson]

Tom, Michael,

I've implemented a fix for this in:

7831e4c #97 CAN overflow (lockups)

It is the latest v2.1.1 bleeding edge code.

What I've done is take the code snippet out of vehicle_twizy.c and put it in vehicle.c, so that all vehicles benefit from it.

Michael: Please check. It seems ok, and I don't think will affect you.

Regards, Mark.

On 18 Dec, 2012, at 2:51 AM, Tom Saxton <tom at idleloop.com> wrote:

> Rebooting the device fixed the problem.
> 
> I didn't get your email until after I had rebooted, but if it happens again
> I'll try the reset command.
> 
>    Tom
> 
> on 12/16/12 4:42 PM, Mark Webb-Johnson wrote:
> 
>> Tom,
>> 
>> I think this is definitely Michael's can-bus-lockup issue.
>> 
>> The problem seems to be that if the can bus overflows (or gets some other sort
>> of error?) then it sets a flag in the controller, and the controller won't
>> deliver any more messages until the flag is cleared. The bus still has
>> messages, but they don't get to the OVMS App. The OVMS code in the car will
>> keep reporting the old bus values - the only indication would be the stale
>> indicators would all go stale as there were no more messages seen by the code.
>> 
>> What Michael has done for the Twizy code (where he was seeing this often) is
>> to add a once-a-second check for the can bus error flag, and clear the
>> controller error condition if he sees it. He reported that solved his problem.
>> 
>> With the v2 code we are working on, I'm taking his can bus error clear code
>> and making it a standard for all cars. The roadster code will benefit from
>> this.
>> 
>> I think that if you reset the module (either sms RESET, or use the smartphone
>> module reset function), the error should clear (as a reset will re-iniitialse
>> the can bus controller. Can you try this? You'll know if it works if the SOC
>> immediately switches to the correct value.
>> 
>> Regards, Mark.
>> 
>> On 17 Dec, 2012, at 12:07 AM, Tom Saxton wrote:
>> 
>>> Opening the door didn't help.
>>> 
>>> I was wondering if I was getting data from another Roadster, so I checked
>>> the Location view. It's showing the spot where the car was parked yesterday
>>> afternoon, and in fact all of the data is consistent with that: SOC and
>>> locked status. Since then, the car has been driven twice and charged, so
>>> plenty of opportunity to get current CAN bus readings.
>>> 
>>> The other odd thing is that it shows it's been parked for 5 minutes every
>>> time I update it.
>>> 
>>> The only thing unusual yesterday was that I realized I hadn't locked the car
>>> a couple of minutes after we parked, so I used OVMS to lock the car, and
>>> checked the Car view to confirm it was locked.
>>> 
>>> Could that have frozen things for some reason?
>>> 
>>> I'll try rebooting the car module before I drive it this morning.
>>> 
>>>   Tom
>>> 
>>> on 12/16/12 6:29 AM, Mark Webb-Johnson wrote:
>>> 
>>>> Tom,
>>>> 
>>>> I just checked the server logs, and the car seems to be online.
>>>> 
>>>> 2012-12-16 09:22:12.710176 -0500 info  main: #65 C SAX217 msg handle S
>>>> 73,M,-1,0,stopped,standard,135,105,32,254,100,29,7,14,0,1,200,1
>>>> 
>>>> It is reporting 73%.
>>>> 
>>>> Maybe some issue with the message reception on the can bus? Can you try
>>>> opening a door with the app running, and see if it registers?
>>>> 
>>>> [Michael, working on the Twizy, found an issue where the can bus buffers
>>>> could
>>>> overflow, causing no more can messages to be received - I haven't seen it on
>>>> the Roadster before, but it is possible this is what you are seeing]
>>>> 
>>>> Regards, Mark.
>>>> 
>>>> On 16 Dec, 2012, at 10:23 PM, Tom Saxton <tom at idleloop.com> wrote:
>>>> 
>>>>> There's something odd going on with OVMS and my Roadster this morning. I'm
>>>>> seeing data that claims to be live, but which is totally wrong.
>>>>> 
>>>>> I got home last night with a 50% charge and set the Roadster to charge at 2
>>>>> am. When I checked it this morning at 6:20, OVMS said the car was at 73%,
>>>>> live, parked for 5 minutes, and locked. When I checked the car, none of
>>>>> those were true. The car's at 97%, has been parked 9.5 hours, and is
>>>>> unlocked.
>>>>> 
>>>>> I've never seen OVMS be wrong and claim to be "live".
>>>>> 
>>>>>  Tom
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>> 
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>> 
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> 
> 
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

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