[Ovmsdev] 1.3.5

[Mark Webb-Johnson]

Jack,

Not good. Looking at the logs, the car was online and reporting, but the data from the CAN bus was 'stuck'. The reset of the module restarted it.

I don't think it is hardware/cabling, but it might be worth ensuring everything is tightly connected.

If it happens again, can you try to send a can-bus command (something like wake up car, etc), to see what happens, and let me know the exact time you sent that command?

Regards, Mark.

On 1 Oct, 2012, at 3:16 PM, Jack West <jackduncanwest at gmail.com> wrote:

> Mark,
> 
> Today my wife drove our car from our house (poor coverage) to a town about 60 miles away (good coverage). I used the app to check her SOC when she was there and though the app indicated "live", the data showed she hadn't left home yet.  I reset OVMS by the app and soon after was getting proper data.  It seems strange that the app would be showing "live", yet the data be incorrect and also still be able to be reset.  This was approximately 5PM local time if you care to look at the logs.  
> 
> Let me know if there is any other info you need.  As I did the reset remotely, I do not know what codes the LEDs were showing but this situation might be repeatable as it has now happened (at least I think it was the same thing) on the last two trips from our house into the city.
> 
> Best,
> Jack
> 
> On Sep 17, 2012, at 3:50 AM, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
> 
>> Jack,
>> 
>> Do you remember what code the lights were flashing?
>> 
>> I checked mine, and it was bizarre. Green LED was flashing 1 (GPRS up and connected), and red LED was off (no errors found). But, when I connected a PC to the DIAG port (thanks to v2 hardware I can do this now when the box is running), the modem responded just fine but there was no comms between the modem and the PIC. As the LEDs were flashing, the PIC was definitely running. It seems that the RS232 port was just dead on the PIC side. A hardware reset brought it back alive.
>> 
>> I guess I'll have to add a timer to the NET driver code for data last received on the modem port. If nothing is received in a few minutes, then time to reset everything.
>> 
>> Regards, Mark.
>> 
>> On 17 Sep, 2012, at 1:49 PM, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
>> 
>>> Jack,
>>> 
>>> Strange, mine did the same (at roughly the same time). Mine still hasn't recovered, but is in good coverage area now.
>>> 
>>> Without resetting, I'm going to put a serial console on it when I get home tonight. Hopefully I can see what is going on then.
>>> 
>>> Regards, Mark.
>>> 
>>> On 17 Sep, 2012, at 1:40 PM, Jack West wrote:
>>> 
>>>> I lost connectivity today with the car in our garage.  We live in a poor cell coverage area and this is not that unusual.  However, later today I drove into the city where coverage is excellent and OVMS did not reconnect.  After hard reset OVMS was able to connect.  If there is any other information I can supply, please let me know.  I updated firmware to 1.3.5 a couple days ago.
>>>> 
>>>> Jack
>>>> 
>>>> On Sep 2, 2012, at 9:03 PM, Mark Webb-Johnson <mark at webb-johnson.net> 
>>>>> If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.
>>>>> 
>>>> _______________________________________________
>>>> 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/20121001/f01108a4/attachment.htm>