<?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[FiPy]]></title><description><![CDATA[For all topics related to the FiPy]]></description><link>https://forum.pycom.io/category/42</link><generator>RSS for Node</generator><lastBuildDate>Tue, 20 Oct 2026 18:36:00 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/category/42.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 19 Sep 2023 15:59:14 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[FiPy: upload failed (using Pymakr on VSCode)]]></title><description><![CDATA[@Julia-Steiwer As you should have noticed, Pycom Inc ceased it's operation, and there is no service any more for Pycom products, be it hardware or software like Pymakr. The latter should still work with the older VSCode versions. So if you want to use PyMakr, you have to stick with an working combo of an older VSCode version and PyMakr.
]]></description><link>https://forum.pycom.io/topic/7811/fipy-upload-failed-using-pymakr-on-vscode</link><guid isPermaLink="true">https://forum.pycom.io/topic/7811/fipy-upload-failed-using-pymakr-on-vscode</guid><dc:creator><![CDATA[robert-hh]]></dc:creator><pubDate>Tue, 19 Sep 2023 15:59:14 GMT</pubDate></item><item><title><![CDATA[Guru Meditation error on nanogateway example]]></title><link>https://forum.pycom.io/topic/7793/guru-meditation-error-on-nanogateway-example</link><guid isPermaLink="true">https://forum.pycom.io/topic/7793/guru-meditation-error-on-nanogateway-example</guid><pubDate>Tue, 14 Mar 2023 14:46:19 GMT</pubDate></item><item><title><![CDATA[Current LTE Firmware update process bricks FiPy&#x27;s]]></title><link>https://forum.pycom.io/topic/7763/current-lte-firmware-update-process-bricks-fipy-s</link><guid isPermaLink="true">https://forum.pycom.io/topic/7763/current-lte-firmware-update-process-bricks-fipy-s</guid><pubDate>Fri, 02 Dec 2022 16:53:16 GMT</pubDate></item><item><title><![CDATA[No module named requests]]></title><description><![CDATA[@Sunt-Beat you need to install modules on the device, not on your computer.
You’ll probably need to use the “micro” version of the module, urequests.
]]></description><link>https://forum.pycom.io/topic/7759/no-module-named-requests</link><guid isPermaLink="true">https://forum.pycom.io/topic/7759/no-module-named-requests</guid><dc:creator><![CDATA[jcaron]]></dc:creator><pubDate>Thu, 24 Nov 2022 17:19:17 GMT</pubDate></item><item><title><![CDATA[Is there a way to use an ethernet board with Fipy?]]></title><link>https://forum.pycom.io/topic/7752/is-there-a-way-to-use-an-ethernet-board-with-fipy</link><guid isPermaLink="true">https://forum.pycom.io/topic/7752/is-there-a-way-to-use-an-ethernet-board-with-fipy</guid><pubDate>Mon, 14 Nov 2022 20:38:00 GMT</pubDate></item><item><title><![CDATA[Problem with start programming.]]></title><link>https://forum.pycom.io/topic/7729/problem-with-start-programming</link><guid isPermaLink="true">https://forum.pycom.io/topic/7729/problem-with-start-programming</guid><pubDate>Sun, 02 Oct 2022 15:45:15 GMT</pubDate></item><item><title><![CDATA[LTE-M with Magenta Austria does not attach]]></title><description><![CDATA[I think I finally found an answer on how to properly reset the modem in case it just won't attach to a network.
Reset the modem by sending following AT-command:
lte.send_at_cmd('AT+SQNSFACTORYRESET=?')
Unlike lte.factory_reset() - which seems to use AT-command AT+SQNSFACTORYRESET - this command will successfully reset the modem to factory state.
A reboot of the device is necessary to finalize the reset!
After this process the modem should attach to the network without any issues!
Also, for further information see: AT Commands Reference Manual, 15.1 Device Reset to Factory State
]]></description><link>https://forum.pycom.io/topic/7725/lte-m-with-magenta-austria-does-not-attach</link><guid isPermaLink="true">https://forum.pycom.io/topic/7725/lte-m-with-magenta-austria-does-not-attach</guid><dc:creator><![CDATA[Alexander Pilhar]]></dc:creator><pubDate>Thu, 29 Sep 2022 14:17:41 GMT</pubDate></item><item><title><![CDATA[Does not attach LTE]]></title><description><![CDATA[So I got this working. The problem was that the SIM was never initiated. I put the SIM inside a Android phone to check if the SIM works (it did work) and after that it worked inside the FiPy. So the problem might be that the Pycom library does not know how to register the SIM on the network for the first time.
]]></description><link>https://forum.pycom.io/topic/7721/does-not-attach-lte</link><guid isPermaLink="true">https://forum.pycom.io/topic/7721/does-not-attach-lte</guid><dc:creator><![CDATA[Tarmo Saluste]]></dc:creator><pubDate>Tue, 27 Sep 2022 07:07:50 GMT</pubDate></item><item><title><![CDATA[OSError: the requested operation is not possible when using send_raw()]]></title><link>https://forum.pycom.io/topic/7715/oserror-the-requested-operation-is-not-possible-when-using-send_raw</link><guid isPermaLink="true">https://forum.pycom.io/topic/7715/oserror-the-requested-operation-is-not-possible-when-using-send_raw</guid><pubDate>Wed, 21 Sep 2022 21:12:11 GMT</pubDate></item><item><title><![CDATA[FiPy Firmware Update Results in no REPL &#x2F; serial response]]></title><description><![CDATA[@Antman You can always load any firmware of your choice using the pycom downloader. That include the most recent PyBytes firmware versions.
]]></description><link>https://forum.pycom.io/topic/7712/fipy-firmware-update-results-in-no-repl-serial-response</link><guid isPermaLink="true">https://forum.pycom.io/topic/7712/fipy-firmware-update-results-in-no-repl-serial-response</guid><dc:creator><![CDATA[robert-hh]]></dc:creator><pubDate>Wed, 14 Sep 2022 22:48:25 GMT</pubDate></item><item><title><![CDATA[Sync Time offline - RTC]]></title><description><![CDATA[@Miguel-Moreno Thanks a lot!
Indeed currently I am syncing the RTC with the NTP server by connecting the FiPy to the internet. But sometimes I am in places with no coverage (I connected it to my phone's hotspot), and since my application is to scan for WiFi and Bluetooth outside, the internet is not always available. That's why I need to get the current time offline and not to be hard coded.
]]></description><link>https://forum.pycom.io/topic/7685/sync-time-offline-rtc</link><guid isPermaLink="true">https://forum.pycom.io/topic/7685/sync-time-offline-rtc</guid><dc:creator><![CDATA[Jana Koteich]]></dc:creator><pubDate>Thu, 25 Aug 2022 14:07:22 GMT</pubDate></item><item><title><![CDATA[Cannot connect terminal to FiPy]]></title><description><![CDATA[Update.
Going for broke, I used the fwtool to erase the flash and reset the CONFIG and NVS areas.
working, connected to REPL etc.
I don't see a pyscan DFU listed and wasn't able to grope for it. Seems to be working now after a spring clean.
R
]]></description><link>https://forum.pycom.io/topic/7681/cannot-connect-terminal-to-fipy</link><guid isPermaLink="true">https://forum.pycom.io/topic/7681/cannot-connect-terminal-to-fipy</guid><dc:creator><![CDATA[Rob Shepherd]]></dc:creator><pubDate>Wed, 24 Aug 2022 15:39:55 GMT</pubDate></item><item><title><![CDATA[FiPy wlan promiscuous, channel, packet format]]></title><description><![CDATA[@Pete-Allen-0 Hi Pete, thank you. In scanning mode (sta/promiscious), the FyPi is not attached to an access point, so it should switch to each wifi channel for a certain time and sniff the packages. The question is, how can I switch the channels in sta-mode? If channel switching is not possible, the sniff function will mis a lot of packages because it is bound to one channel.
Best regards,
Martin
]]></description><link>https://forum.pycom.io/topic/7661/fipy-wlan-promiscuous-channel-packet-format</link><guid isPermaLink="true">https://forum.pycom.io/topic/7661/fipy-wlan-promiscuous-channel-packet-format</guid><dc:creator><![CDATA[martin janssen]]></dc:creator><pubDate>Tue, 02 Aug 2022 14:44:03 GMT</pubDate></item><item><title><![CDATA[PyMesh manifest]]></title><description><![CDATA[This issue has been fixed, so mesh deployment should be working
]]></description><link>https://forum.pycom.io/topic/7655/pymesh-manifest</link><guid isPermaLink="true">https://forum.pycom.io/topic/7655/pymesh-manifest</guid><dc:creator><![CDATA[Pete Allen 0]]></dc:creator><pubDate>Thu, 28 Jul 2022 02:28:54 GMT</pubDate></item><item><title><![CDATA[PyMesh Config.json]]></title><description><![CDATA[This issue has been fixed, so mesh deployment should be working
]]></description><link>https://forum.pycom.io/topic/7652/pymesh-config-json</link><guid isPermaLink="true">https://forum.pycom.io/topic/7652/pymesh-config-json</guid><dc:creator><![CDATA[Pete Allen 0]]></dc:creator><pubDate>Wed, 27 Jul 2022 05:34:54 GMT</pubDate></item><item><title><![CDATA[Bootloader on FiPy]]></title><description><![CDATA[@jcaron Are there any list of compatible jtag that can be used with FiPy. I am trying to connect with IAR J-Link jtag but I am not able to find the Xtensa® dual–core 32–bit LX6 microprocessor.
]]></description><link>https://forum.pycom.io/topic/7608/bootloader-on-fipy</link><guid isPermaLink="true">https://forum.pycom.io/topic/7608/bootloader-on-fipy</guid><dc:creator><![CDATA[Kostas Nomikos]]></dc:creator><pubDate>Mon, 20 Jun 2022 13:15:52 GMT</pubDate></item><item><title><![CDATA[FiPy - Device busy on Pysense, unable to interact with device]]></title><description><![CDATA[I have this problem too. Latest firmware applied to PySense 1.1 and LoPy4, doesn't work on Mac (attaches to VSCode as tty. not cu. and busy as tty) and on Linux I see it as ACM0 and it's always busy.
I've tried multiple instances of PySense 1.1 and LoPy4 - I have ten units that have been sitting in storage for a few years. None working now that the old tools are all gone.
]]></description><link>https://forum.pycom.io/topic/7607/fipy-device-busy-on-pysense-unable-to-interact-with-device</link><guid isPermaLink="true">https://forum.pycom.io/topic/7607/fipy-device-busy-on-pysense-unable-to-interact-with-device</guid><dc:creator><![CDATA[Jonathan Brewer]]></dc:creator><pubDate>Sat, 18 Jun 2022 15:56:12 GMT</pubDate></item><item><title><![CDATA[FiPy Memory access]]></title><link>https://forum.pycom.io/topic/7604/fipy-memory-access</link><guid isPermaLink="true">https://forum.pycom.io/topic/7604/fipy-memory-access</guid><pubDate>Thu, 16 Jun 2022 14:52:32 GMT</pubDate></item><item><title><![CDATA[Using Pysense to Program FiPy]]></title><description><![CDATA[@Benjamin-Mirad-Gurini there are plenty, the most obvious being the the Pysense has additional sensors (accelerometer, temperature, humidity etc.) which the expansion board doesn’t have, and conversely the expansion board gives easy access to all pins and has a few jumpers.
]]></description><link>https://forum.pycom.io/topic/7583/using-pysense-to-program-fipy</link><guid isPermaLink="true">https://forum.pycom.io/topic/7583/using-pysense-to-program-fipy</guid><dc:creator><![CDATA[jcaron]]></dc:creator><pubDate>Fri, 27 May 2022 19:00:34 GMT</pubDate></item><item><title><![CDATA[FiPy WiFI not created - restarted my computer RGB no longer blinking]]></title><description><![CDATA[Also, it appears, that I have no connection when connecting with my USB to UART through PUTTY. Once again, I have done nothing to the board other than power it, as stated on the minimum recommended circuit.
I tried changing the power supply to a IPS 606D, giving it exactly 5V. Once again, it blinked for a few seconds and stopped.
]]></description><link>https://forum.pycom.io/topic/7582/fipy-wifi-not-created-restarted-my-computer-rgb-no-longer-blinking</link><guid isPermaLink="true">https://forum.pycom.io/topic/7582/fipy-wifi-not-created-restarted-my-computer-rgb-no-longer-blinking</guid><dc:creator><![CDATA[Benjamin Mirad Gurini]]></dc:creator><pubDate>Thu, 26 May 2022 18:46:29 GMT</pubDate></item><item><title><![CDATA[3D model for fipy?]]></title><link>https://forum.pycom.io/topic/7581/3d-model-for-fipy</link><guid isPermaLink="true">https://forum.pycom.io/topic/7581/3d-model-for-fipy</guid><pubDate>Thu, 26 May 2022 15:17:03 GMT</pubDate></item><item><title><![CDATA[Energy consumption in Fipy]]></title><description><![CDATA[@jcaron I do not have any problem with current it draws for now. I am just experimenting with the power_modes "Always ON" and "TX_only" but it seems to have no difference at all in power consumption in both the modes but their should be some difference as far I know. I don't know if it should be the case or I have done something wrong.
]]></description><link>https://forum.pycom.io/topic/7573/energy-consumption-in-fipy</link><guid isPermaLink="true">https://forum.pycom.io/topic/7573/energy-consumption-in-fipy</guid><dc:creator><![CDATA[muhammad Umair]]></dc:creator><pubDate>Mon, 23 May 2022 00:55:26 GMT</pubDate></item><item><title><![CDATA[LoRa Rx window timing debugging]]></title><link>https://forum.pycom.io/topic/7572/lora-rx-window-timing-debugging</link><guid isPermaLink="true">https://forum.pycom.io/topic/7572/lora-rx-window-timing-debugging</guid><pubDate>Thu, 19 May 2022 11:54:10 GMT</pubDate></item><item><title><![CDATA[Pymesh transmit data in mesh network to ubidots cloud]]></title><link>https://forum.pycom.io/topic/7567/pymesh-transmit-data-in-mesh-network-to-ubidots-cloud</link><guid isPermaLink="true">https://forum.pycom.io/topic/7567/pymesh-transmit-data-in-mesh-network-to-ubidots-cloud</guid><pubDate>Wed, 18 May 2022 08:55:42 GMT</pubDate></item></channel></rss>