<?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[Topics tagged with pin wake up]]></title><description><![CDATA[A list of topics that have been tagged with pin wake up]]></description><link>https://forum.pycom.io/tags/pin wake up</link><generator>RSS for Node</generator><lastBuildDate>Fri, 17 Apr 2026 21:34:40 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/tags/pin wake up.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 31 Mar 2018 21:07:52 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[py.setup_int_pin_wake_up() has no effect when a button is pushed]]></title><description><![CDATA[@fsergeys yes, we physically cut the header for that pin, so the only things that remain connected are the sensor and the PIC on the Pysense in our case. The LoPy was just bringing havoc when in deep sleep mode.
You may want to experiment by using jumper cables between the WiPy and PyTrack at first, connecting everything but that pin, but I’m pretty sure you’ll get better results that way.
Of course things would be very different with a WiPy 3, LoPy 4 or any of the other modules that implement deeep sleep directly rather than having to rely on an external board.
]]></description><link>https://forum.pycom.io/topic/2951/py-setup_int_pin_wake_up-has-no-effect-when-a-button-is-pushed</link><guid isPermaLink="true">https://forum.pycom.io/topic/2951/py-setup_int_pin_wake_up-has-no-effect-when-a-button-is-pushed</guid><dc:creator><![CDATA[jcaron]]></dc:creator><pubDate>Sat, 31 Mar 2018 21:07:52 GMT</pubDate></item></channel></rss>