@egimbernat The partition table has two firmware section, which are alternately used only if you upload the firmware with OTA. If you upload the firmware with the Pycom loader, always the first partition is used for storing the firmware. Which one is booted depends on the OTA state. If you never used OTA, the first partition is booted. Using OTA the partitions alternate, and with safe boot just the other partition will be booted. https://docs.pycom.io/chapter/gettingstarted/programming/safeboot.html P.S.: The Pinout sheets are wrong about safe boot. P.S.2: There is still a hiccup in this mechanism. If by using OTA the second partition is the boot partition, using the serial firmware loader, which will place the new image into the first partition, seems to have no effect. Still the second partition will be started. See https://github.com/pycom/pycom-micropython-sigfox/issues/81

@szyba91 You do not have to scan for a network, if you know if it exists. Just add something like the below to your main.py file: import machine from network import WLAN wlan = WLAN(mode=WLAN.STA) # Set WLAN to STA mode if not wlan.isconnected(): # change the line below to match your network ssid, security and password wlan.connect('mywifi', auth=(WLAN.WPA2, 'mywifikey'), timeout=5000) while not wlan.isconnected(): print(".", end="") machine.sleep(1) Edit: I do not know about folder structures within VSC, Atom or any other bloatware and bug hiders like that. I prefer to use simple tools where I know what I'm doing and what is happening.

It seems that the FTDI chip I was using started to brown out. I switched to external power with a DC supply and everything is back to normal. I should've tried that first. I didn't even think of it since for the first couple of weeks the FTDI chip had no issues supplying sufficient power. Regardless, thank you very much for your help @robert-hh

One of the working devices dropped connection the same day it finally connected and after a week of testing I haven't been able to reconnect it. It briefly found a signal two days ago but wasn't able to attach and has been silent since. No idea what could be the cause, are there some commands outside of the LTE example on docs I should try? Also the 'AT!="zsp0:npc 1"' always returns "command unknown".

Hi @soulsurfer, Thanks for noticing! I'll let the team know. We're using the .mpy version to save memory, so your project can take up more space. May I ask what are you missing from the documentation?

@szyba91 P12 can be pulled up directly. But using a resistor is also OK. 4.7K is a good choice. CTRL-F is to be pushed in the Terminal window, where you expect the REPL prompt. it will be caught the the serial interrupt handler.

@tuftec In fact, lorawan callback in the network operator that i have used (objenious and orange) doesn't allow dynamic downlink data setup via callback service. I have to prepare the downlink data and when (even several hours/day later) the device send an uplink message the downlink data is send to the device. So, if you know the periodicity of your uplink frame you can predict the time to send to your device on his next uplink frame and set your operator downlink frame in advance. With Sigfox, when the device send an uplink frame with download request bit (by device choice) set, there 2 choices -default call back method can send back to the device network time and some static data -you have 20 secondes to send back from your device (from your own callback service) some data and time. With NB-IOT , network time availability is not mandatory so it depend of your network provider.

Hi @sh4nnongoh, Please check this post for updates about the modem upgrades. Hope this helps!

Hi @joseph, No, not yet. I have spent a few days on it, but no progress. I keep getting Connection refused when trying to connect, so something must be wrong with my server code. Have you tried connecting it to a different device (e.g your computer)?

@marike Sometimes you have to do a hard reset with the SD card inserted to deztect the card. Also not all card brands and sizes work. And finally especially Windows does not format a clean FAT layout with a single partition.

@archana-kadam Just add micropyGPS.py to your project folder and add import micropyGPS to main.py. If you have trouble uploading the file you should read the documentation.

Hi @davargas, I have some code for MQTT as well, but nothing for Azure Client. I have added it to my list of things to research and will try to write a tutorial for it if I can make it work ;)

@stefan-1212 If someone stands between the devices, you don't have line-of-sight, so you have to count on a bounce on some nearby surface, which makes the distance longer and the loss higher, so it depends a lot on the environment. Also note that in ideal conditions your antennas should be placed to avoid having any objects within the Fresnel zone, so even on 70 meters, your antennas should be about 1.5m above ground level (if you have flat ground with nothing on it between the devices). To get to 1 km you would need to have both antennas 6 m above ground (this is very simplified, as the Fresnel zone is an ellipse).

@xykon I did that more than a week ago, but didn't get a response (PYCSD-271). I figured my chances would be better on the forum, and it turns out they are ;) . You are welcome to help me here or via the support portal, I have no preference in that respect.

@archana-kadam I looke dagain at you request. What I cannot understand is, why you do not simple set the respberry Pi to 115200 baud. Besides that, you can free UART0 from the REPL and reconfigure it to any speed you like, e.g. for 9600 baud: import uos from machine import UART uos.dupterm(None) uart0 = UART(0, 9600) Be aware, that after the "uos.dupterm(None)", the REPL and print etc. is on telnet only.

@ananda I suggest you check out https://pycom.io/where-to-buy/ and/or contact sales@pycom.io

@pmst It's not yet possible through the firmware updater tool but if you have Python3 + PySerial on your PC you can update through serial. See https://github.com/pycom/pycom-libraries/tree/master/lib/sqnsupgrade for more details. Let me know if you have any issues.