[Lab] [Bulk] Re: ESP8266 issues and data logger (Ken McKinnon)

[Jaime Yu]

Knowing Ken, I would bet he snacked the machine.

But I agree with ken original solution. Adding a watchdog will help
mitigate the issue. The Linux kernel has the capability built in so you
should be able to take advantage of it with out relying on an external
Arduino (although the Arduino solution is probably more reliable if the
kernel is really fubar'd).

Watchdog daemon that can help you out http://linux.die.net/man/8/watchdog

--
Sincerely,
Jaime Yu
B.Eng in Computer Engineering, System Hardware
Kernel Software Engineer at Juniper Networks

$CV = "http://cv.jaimeyu.com"
$Blog = "http://ask.jaimeyu.com"
$travvik ="http://ottawa.travvik.com"
$Project = "http://www.capstone490.com"
$Linkedin = https://www.linkedin.com/in/jaimeyu
$GitHub = https://github.com/jaimeyu


On Dec 8, 2014 5:29 PM, "Jim" <jim.kiskis at gmail.com> wrote:

> Do you mean wack damn thing or watchdog timer
>
> Sent from my iPhone
>
> > On Dec 8, 2014, at 4:48 PM, Ken McKinnon <klmckinnon at rogers.com> wrote:
> >
> > Your solution sounds pretty good.  I didn't realize that it was the
> ESP8266 vice the Arduino, guess I missed that.....
> >
> > I once had to fly to Resolute Bay (in the dark season) when a site
> failed, we couldn't connect to the site and it would not respond at all.  I
> fixed it by hitting the reset on the communication controller unit.  We
> implemented the WDT after that several $K trip.
> >
> > Ken
> >
> >
> >> On 2014-12-08 3:05 PM, Adrian Jones wrote:
> >> Ken,
> >> You raise an interesting idea but I'm not sure that this is required.
> >> Watchdog timers are great if the Arduino misbehaves. However, the issue
> I
> >> have is that it is the ESP8266 that  gets stuck in a loop, not the
> Arduino.
> >> When it is in this 'stuck' state, subsequent AT commands to the ESP8266
> >> throw errors (which I can capture) and this is a good indication that it
> >> needs resetting.
> >>  I already use an Arduino pin (via Schottky diode and 10k pull-up to
> 3.3V) to
> >> force a reset of the ESP8266 during the setup. This leaves it in a known
> >> state before I start sending AT commands to it. I have now added code to
> >> force a reset if 10 errors are seen in succession. This should address
> the
> >> problem.
> >>
> >> ------------------------------
> >>
> >> Message: 5
> >> Date: Sun, 07 Dec 2014 15:32:15 -0500
> >> From: Ken McKinnon <klmckinnon at rogers.com>
> >> To: lab at artengine.ca
> >> Subject: Re: [Lab] [Bulk] Re:  ESP8266 issues and data logger
> >> Message-ID: <5484B94F.6040206 at rogers.com>
> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >>
> >> Sounds like you need to add a watchdog function, something that sits
> outside
> >> the main code that gets tweaked once in a while and if it doesn't it
> will
> >> cause a reset.
> >>
> >> https://www.youtube.com/watch?v=BDsu8YhYn8g
> >>
> >> The Watchdog has a separate timer that ticks over at a set rate, if it
> >> overflows, it will force a reset.  The working code within your cycle
> >> periodically would have to clear the WDT thereby preventing it from an
> >> unplanned reset.
> >>
> >> It can also be done externally.
> >>
> >> Ken
> >>
> >>
> >>
> >> _______________________________________________
> >> Lab mailing list
> >> 1. subscribe http://artengine.ca/mailman/listinfo/lab
> >> 2. then email Lab at artengine.ca to send your message to the list
> >
> > _______________________________________________
> > Lab mailing list
> > 1. subscribe http://artengine.ca/mailman/listinfo/lab
> > 2. then email Lab at artengine.ca to send your message to the list
>
> _______________________________________________
> Lab mailing list
> 1. subscribe http://artengine.ca/mailman/listinfo/lab
> 2. then email Lab at artengine.ca to send your message to the list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://artengine.ca/pipermail/lab/attachments/20141208/4b6d3777/attachment.html>