<?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[So GPy is phase-out now what?]]></title><description><![CDATA[<p dir="auto">We have a design based on the GPy, on our own board, with our CE and security testing done. But as you may have heard the GPy and a whole bunch of the other OG modules are being discontinued. As I do have a board that is using this module, I have to look for the options. Seems like the new Pycom modules will not have the same footprint. but asking Pycom, I get no answers. And no answers seems like a repeat of the last couple of years of collaboration with Pycom to be honest. So I am thinking to myself, perhaps we should just forget about it, and move on. Start from fresh somewhere else. But that means wasting a lot of money and energy. So I understand this is not the typcial post in a tech forum, but as Pycom is silent (well, they can fill out the blanks here of course) I just need to ask if anyone knows anything more about the footprint of the new modules? If you happen to know a good, viable option to the GPy that I can look at instead? Hopefully with a little bit more focus on longevity and collaboration. Thanks for participating in the discussion.</p>
]]></description><link>https://forum.pycom.io/topic/7601/so-gpy-is-phase-out-now-what</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Mar 2026 01:38:53 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/topic/7601.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 15 Jun 2022 18:35:43 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to So GPy is phase-out now what? on Wed, 15 Jun 2022 18:35:43 GMT]]></title><description><![CDATA[<p dir="auto">We have a design based on the GPy, on our own board, with our CE and security testing done. But as you may have heard the GPy and a whole bunch of the other OG modules are being discontinued. As I do have a board that is using this module, I have to look for the options. Seems like the new Pycom modules will not have the same footprint. but asking Pycom, I get no answers. And no answers seems like a repeat of the last couple of years of collaboration with Pycom to be honest. So I am thinking to myself, perhaps we should just forget about it, and move on. Start from fresh somewhere else. But that means wasting a lot of money and energy. So I understand this is not the typcial post in a tech forum, but as Pycom is silent (well, they can fill out the blanks here of course) I just need to ask if anyone knows anything more about the footprint of the new modules? If you happen to know a good, viable option to the GPy that I can look at instead? Hopefully with a little bit more focus on longevity and collaboration. Thanks for participating in the discussion.</p>
]]></description><link>https://forum.pycom.io/post/40473</link><guid isPermaLink="true">https://forum.pycom.io/post/40473</guid><dc:creator><![CDATA[Don-iot]]></dc:creator><pubDate>Wed, 15 Jun 2022 18:35:43 GMT</pubDate></item><item><title><![CDATA[Reply to So GPy is phase-out now what? on Thu, 16 Jun 2022 07:24:55 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/5629">@Don-iot</a> Looking at the pictures, the new F01 H7 modules fit on a M.2 formatted carrier board. According to the pictures, it looks like a 60x22 mm M.2 board.<br />
Whether you can expect Pycom to deliver a different service than in the past years is up to you. In my experience hardware was well manufactured and worked reliable, once it was available. What always was lacking was a consistent software development and support.</p>
]]></description><link>https://forum.pycom.io/post/40477</link><guid isPermaLink="true">https://forum.pycom.io/post/40477</guid><dc:creator><![CDATA[robert-hh]]></dc:creator><pubDate>Thu, 16 Jun 2022 07:24:55 GMT</pubDate></item><item><title><![CDATA[Reply to So GPy is phase-out now what? on Thu, 16 Jun 2022 09:34:25 GMT]]></title><description><![CDATA[<p dir="auto">Thanks <a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/98">@robert-hh</a> for your excellent support through the years! I had my battles and at this point all problems are solved. When moving to a new platform I will most likely have to do all CE and safety tests again. I am evaluating moving to another platform, however if I can get more tech info from Pycom and a road map I can possibly change my mind. However my mails to the sales address remains unanswered, hence my reaction here.</p>
]]></description><link>https://forum.pycom.io/post/40478</link><guid isPermaLink="true">https://forum.pycom.io/post/40478</guid><dc:creator><![CDATA[Don-iot]]></dc:creator><pubDate>Thu, 16 Jun 2022 09:34:25 GMT</pubDate></item><item><title><![CDATA[Reply to So GPy is phase-out now what? on Wed, 29 Jun 2022 13:43:24 GMT]]></title><description><![CDATA[<p dir="auto">I also produce a product that is reliant upon the Gpy.  We are looking for stock and then have the big question of the next step.  Is there a replacement product?  Will it still use python and the same capability or compatibility?  Will it fit our current board design?</p>
<p dir="auto">This does seem like a product that will be important moving forward and not just for my company but...   A plug and go replacement will be ideal and I would welcome any input or feedback that includes viable suggestions.<br />
Thanks to all of you pioneers!</p>
]]></description><link>https://forum.pycom.io/post/40649</link><guid isPermaLink="true">https://forum.pycom.io/post/40649</guid><dc:creator><![CDATA[Thomas Millard]]></dc:creator><pubDate>Wed, 29 Jun 2022 13:43:24 GMT</pubDate></item><item><title><![CDATA[Reply to So GPy is phase-out now what? on Sun, 03 Jul 2022 17:49:25 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/10383">@Thomas-Millard</a> Good that you responded to my post. It seems like the new module has a different footprint, so there is no hot-swappable solution ahead. Perhaps we can produce such a thing based on the OEM-modules if you are interested, would probably be cheaper if we can share costs?</p>
]]></description><link>https://forum.pycom.io/post/40657</link><guid isPermaLink="true">https://forum.pycom.io/post/40657</guid><dc:creator><![CDATA[Don-iot]]></dc:creator><pubDate>Sun, 03 Jul 2022 17:49:25 GMT</pubDate></item><item><title><![CDATA[Reply to So GPy is phase-out now what? on Thu, 21 Jul 2022 18:35:16 GMT]]></title><description><![CDATA[<p dir="auto">I saw PyCom now provided some more information about the phase-out process:<br />
<a href="https://pycom.io/hardware-end-of-life-announcement/" target="_blank" rel="noopener noreferrer nofollow">https://pycom.io/hardware-end-of-life-announcement/</a><br />
<a href="https://pycom.io/pycom-hardware-roadmap-qa/" target="_blank" rel="noopener noreferrer nofollow">https://pycom.io/pycom-hardware-roadmap-qa/</a></p>
<p dir="auto">Tl;dr is basically that the current hardware will be phased out by December 2022 and there will be time to place one last order from PyCom. The new hardware will work with the old code after some pin adjustments etc. (according to PyCom themselves). You can now program the hardware using C++ too.</p>
<p dir="auto">There isn't, however, any information on how the new boards will work electrically and they state that the board size will be slightly bigger than the GPy.</p>
]]></description><link>https://forum.pycom.io/post/40737</link><guid isPermaLink="true">https://forum.pycom.io/post/40737</guid><dc:creator><![CDATA[techykermit]]></dc:creator><pubDate>Thu, 21 Jul 2022 18:35:16 GMT</pubDate></item><item><title><![CDATA[Reply to So GPy is phase-out now what? on Thu, 21 Jul 2022 18:52:02 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/4806">@techykermit</a> said in <a href="/post/40737">So GPy is phase-out now what?</a>:</p>
<blockquote>
<p dir="auto">The new hardware will work with the old code after some pin adjustments etc.</p>
</blockquote>
<p dir="auto">Which means: expect major porting effort.</p>
<p dir="auto">I guess the new hardware is what they announce as the F01 series, for which there is an offer for a development pack. The new hardware looks promising on paper, using the STM F7xx as hardware and Murata radio devices. Let's see how Pycom manages the firmware.</p>
]]></description><link>https://forum.pycom.io/post/40738</link><guid isPermaLink="true">https://forum.pycom.io/post/40738</guid><dc:creator><![CDATA[robert-hh]]></dc:creator><pubDate>Thu, 21 Jul 2022 18:52:02 GMT</pubDate></item><item><title><![CDATA[Reply to So GPy is phase-out now what? on Tue, 24 Oct 2023 08:55:58 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">Just for reference, our GPy replacement Walter is going live on Crowd Supply very soon. We already tested with some beta testers and you can read the review in this topic: <a href="https://forum.pycom.io/topic/7748/the-future-of-pycom/32">https://forum.pycom.io/topic/7748/the-future-of-pycom/32</a></p>
<p dir="auto">For everybody interested, this is the Crowd Supply link: <a href="https://www.crowdsupply.com/dptechnics/walter" target="_blank" rel="noopener noreferrer nofollow">https://www.crowdsupply.com/dptechnics/walter</a></p>
]]></description><link>https://forum.pycom.io/post/41612</link><guid isPermaLink="true">https://forum.pycom.io/post/41612</guid><dc:creator><![CDATA[Daan Pape]]></dc:creator><pubDate>Tue, 24 Oct 2023 08:55:58 GMT</pubDate></item></channel></rss>