<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
thanks Jaime...Bus meet Ken as I'm thrown under it.....<span
class="moz-smiley-s5"><span> :-D </span></span><br>
I have never struck a piece of hardware that didn't desparately need
it......<br>
<br>
Ken<br>
<br>
<div class="moz-cite-prefix">On 2014-12-08 5:55 PM, Jaime Yu wrote:<br>
</div>
<blockquote
cite="mid:CAN6ZaWG-Qm-hG=3t7wbE5gS_yDt62_YXoBmDFCvY+PhJyCnkKQ@mail.gmail.com"
type="cite">
<p dir="ltr">Knowing Ken, I would bet he snacked the machine.</p>
<p dir="ltr">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). </p>
<p dir="ltr">Watchdog daemon that can help you out <a
moz-do-not-send="true"
href="http://linux.die.net/man/8/watchdog">http://linux.die.net/man/8/watchdog</a></p>
<p dir="ltr">--<br>
Sincerely,<br>
Jaime Yu<br>
B.Eng in Computer Engineering, System Hardware<br>
Kernel Software Engineer at Juniper Networks</p>
<p dir="ltr">$CV = "<a moz-do-not-send="true"
href="http://cv.jaimeyu.com">http://cv.jaimeyu.com</a>"<br>
$Blog = "<a moz-do-not-send="true" href="http://ask.jaimeyu.com">http://ask.jaimeyu.com</a>"<br>
$travvik ="<a moz-do-not-send="true"
href="http://ottawa.travvik.com">http://ottawa.travvik.com</a>"<br>
$Project = "<a moz-do-not-send="true"
href="http://www.capstone490.com">http://www.capstone490.com</a>"<br>
$Linkedin = <a moz-do-not-send="true"
href="https://www.linkedin.com/in/jaimeyu">https://www.linkedin.com/in/jaimeyu</a><br>
$GitHub = <a moz-do-not-send="true"
href="https://github.com/jaimeyu">https://github.com/jaimeyu</a></p>
<p dir="ltr"> </p>
<div class="gmail_quote">On Dec 8, 2014 5:29 PM, "Jim" <<a
moz-do-not-send="true" href="mailto:jim.kiskis@gmail.com">jim.kiskis@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Do you mean
wack damn thing or watchdog timer<br>
<br>
Sent from my iPhone<br>
<br>
> On Dec 8, 2014, at 4:48 PM, Ken McKinnon <<a
moz-do-not-send="true" href="mailto:klmckinnon@rogers.com">klmckinnon@rogers.com</a>>
wrote:<br>
><br>
> Your solution sounds pretty good. I didn't realize that
it was the ESP8266 vice the Arduino, guess I missed that.....<br>
><br>
> 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.<br>
><br>
> Ken<br>
><br>
><br>
>> On 2014-12-08 3:05 PM, Adrian Jones wrote:<br>
>> Ken,<br>
>> You raise an interesting idea but I'm not sure that
this is required.<br>
>> Watchdog timers are great if the Arduino misbehaves.
However, the issue I<br>
>> have is that it is the ESP8266 that gets stuck in a
loop, not the Arduino.<br>
>> When it is in this 'stuck' state, subsequent AT
commands to the ESP8266<br>
>> throw errors (which I can capture) and this is a good
indication that it<br>
>> needs resetting.<br>
>> I already use an Arduino pin (via Schottky diode and
10k pull-up to 3.3V) to<br>
>> force a reset of the ESP8266 during the setup. This
leaves it in a known<br>
>> state before I start sending AT commands to it. I
have now added code to<br>
>> force a reset if 10 errors are seen in succession.
This should address the<br>
>> problem.<br>
>><br>
>> ------------------------------<br>
>><br>
>> Message: 5<br>
>> Date: Sun, 07 Dec 2014 15:32:15 -0500<br>
>> From: Ken McKinnon <<a moz-do-not-send="true"
href="mailto:klmckinnon@rogers.com">klmckinnon@rogers.com</a>><br>
>> To: <a moz-do-not-send="true"
href="mailto:lab@artengine.ca">lab@artengine.ca</a><br>
>> Subject: Re: [Lab] [Bulk] Re: ESP8266 issues and
data logger<br>
>> Message-ID: <<a moz-do-not-send="true"
href="mailto:5484B94F.6040206@rogers.com">5484B94F.6040206@rogers.com</a>><br>
>> Content-Type: text/plain; charset=ISO-8859-1;
format=flowed<br>
>><br>
>> Sounds like you need to add a watchdog function,
something that sits outside<br>
>> the main code that gets tweaked once in a while and
if it doesn't it will<br>
>> cause a reset.<br>
>><br>
>> <a moz-do-not-send="true"
href="https://www.youtube.com/watch?v=BDsu8YhYn8g"
target="_blank">https://www.youtube.com/watch?v=BDsu8YhYn8g</a><br>
>><br>
>> The Watchdog has a separate timer that ticks over at
a set rate, if it<br>
>> overflows, it will force a reset. The working code
within your cycle<br>
>> periodically would have to clear the WDT thereby
preventing it from an<br>
>> unplanned reset.<br>
>><br>
>> It can also be done externally.<br>
>><br>
>> Ken<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Lab mailing list<br>
>> 1. subscribe <a moz-do-not-send="true"
href="http://artengine.ca/mailman/listinfo/lab"
target="_blank">http://artengine.ca/mailman/listinfo/lab</a><br>
>> 2. then email <a moz-do-not-send="true"
href="mailto:Lab@artengine.ca">Lab@artengine.ca</a> to send
your message to the list<br>
><br>
> _______________________________________________<br>
> Lab mailing list<br>
> 1. subscribe <a moz-do-not-send="true"
href="http://artengine.ca/mailman/listinfo/lab"
target="_blank">http://artengine.ca/mailman/listinfo/lab</a><br>
> 2. then email <a moz-do-not-send="true"
href="mailto:Lab@artengine.ca">Lab@artengine.ca</a> to send
your message to the list<br>
<br>
_______________________________________________<br>
Lab mailing list<br>
1. subscribe <a moz-do-not-send="true"
href="http://artengine.ca/mailman/listinfo/lab"
target="_blank">http://artengine.ca/mailman/listinfo/lab</a><br>
2. then email <a moz-do-not-send="true"
href="mailto:Lab@artengine.ca">Lab@artengine.ca</a> to send
your message to the list<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>