<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Post mortem analysis ?]]></title><description><![CDATA[<p dir="auto">Hello, after three month of 24/24 working my lopy4 (firmware 1.18) have stopped to send sigfox message. As i am far from board location (300km) i cannot know if it's a hardware failure or a software failure.<br />
Lopy4 is fitted on a board i have designed powered on main supply and mainly do some bluetooth communication every 1min with several bluetooth sensor and every 15min send data collected by sigfox.</p>
<p dir="auto">Between two bluetooth scan period i do a machine.idle() call. I never call gc.collect() and i haven't started watchdog (may be on the next software update i will add it).</p>
<p dir="auto">So my questions are :<br />
-When i go to the board location, is there any way to know what happened prevously ? eg is there any way to have the last exeception trace that previously occurs ?<br />
-What is the maximum time i can use for WDT instance can i do a</p>
<pre><code>wdt = WDT(timeout=120000)
</code></pre>
<p dir="auto">or even better a</p>
<pre><code>wdt = WDT(timeout=900000)
</code></pre>
<p dir="auto">that will permit me to refresh the watchdog after a sigfox send ?<br />
-How can i have via REPL the last reset cause of the board to see if a watchdog reset or power failure occurs between last REPL connection time?</p>
<p dir="auto">Thanks for your ideas and feedbacks</p>
]]></description><link>https://forum.pycom.io/topic/4073/post-mortem-analysis</link><generator>RSS for Node</generator><lastBuildDate>Fri, 16 Oct 2026 15:23:57 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/topic/4073.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 02 Dec 2018 08:44:24 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Post mortem analysis ? on Sun, 02 Dec 2018 10:14:07 GMT]]></title><description><![CDATA[<p dir="auto">Hello, after three month of 24/24 working my lopy4 (firmware 1.18) have stopped to send sigfox message. As i am far from board location (300km) i cannot know if it's a hardware failure or a software failure.<br />
Lopy4 is fitted on a board i have designed powered on main supply and mainly do some bluetooth communication every 1min with several bluetooth sensor and every 15min send data collected by sigfox.</p>
<p dir="auto">Between two bluetooth scan period i do a machine.idle() call. I never call gc.collect() and i haven't started watchdog (may be on the next software update i will add it).</p>
<p dir="auto">So my questions are :<br />
-When i go to the board location, is there any way to know what happened prevously ? eg is there any way to have the last exeception trace that previously occurs ?<br />
-What is the maximum time i can use for WDT instance can i do a</p>
<pre><code>wdt = WDT(timeout=120000)
</code></pre>
<p dir="auto">or even better a</p>
<pre><code>wdt = WDT(timeout=900000)
</code></pre>
<p dir="auto">that will permit me to refresh the watchdog after a sigfox send ?<br />
-How can i have via REPL the last reset cause of the board to see if a watchdog reset or power failure occurs between last REPL connection time?</p>
<p dir="auto">Thanks for your ideas and feedbacks</p>
]]></description><link>https://forum.pycom.io/post/23893</link><guid isPermaLink="true">https://forum.pycom.io/post/23893</guid><dc:creator><![CDATA[Eric73]]></dc:creator><pubDate>Sun, 02 Dec 2018 10:14:07 GMT</pubDate></item></channel></rss>