@helalbr I used both. But after the devices had been authenticated by OTAA once, I copied the credentials from the TTN console into the ABP script. ABP starts faster.

@seb ok. good to know :)

I've queried our firmware team about this and the response was: The IDF had a bug there at the beginning, so we disabled it He is welcome to enable it and submit a pull request

@robert-hh Thanks, that did it! I had to do the P12 to 3.3V for the 7-9s to load the factory firmware. I retested a firmware update and it went back to the unresponsive mode. So I then reformatted the /flash area by running: import os os.mkfs('/flash') A firmware update then worked ok. Thanks again.

@danielm Thanks! Anything about band support?

@daniel Hi, i have a LoPy4 with firmware 1.17.3.b1 attached to a Expansionboard v2.1A. I have a code that worked fine on SiPy, but after transfer to LoPy4 i get this error. Note: this error comes with or without any pins connected to the expansionboard. If you want the main.py, please provide me with a mail i can sent to. Thank you UPDATE: This is solved by disable wifi on boot pycom.wifi_on_boot(False) See topic: https://forum.pycom.io/topic/3217/lopy4-guru-meditation-error Guru Meditation Error: Core 0 panic'ed (InstrFetchProhibited) . Exception was unhandled. Register dump: PC : 0x00000000 PS : 0x00060630 A0 : 0x8011855d A1 : 0x3ffbd650 A2 : 0x00000000 A3 : 0x00000037 A4 : 0xffffffa2 A5 : 0x3fbc0af0 A6 : 0x00000008 A7 : 0x00000000 A8 : 0x8012382c A9 : 0x3ffbd640 A10 : 0x3fbc0b0c A11 : 0x00000037 A12 : 0xffffffa2 A13 : 0x3ffbd6e4 A14 : 0x7777395d A15 : 0x7777395d SAR : 0x00000010 EXCCAUSE: 0x00000014 EXCVADDR: 0x00000000 LBEG : 0x4009b351 LEND : 0x4009b385 LCOUNT : 0xffffffff Backtrace: 0x00000000:0x3ffbd650 0x4011855a:0x3ffbd670 0x40119567:0x3ffbd740 0x4012faf5:0x3ffbd760 0x40131657:0x3ffbd7b0```

Hi, The hardware version of the board can be found written on the silk screen (either 1.0 or 1.1), The firmware version of the pysense can be found by using the read_fw_version() function in pycoproc.py which can be found here. Finally in regards to what library version you are using, you can see that at the top of the .py file e.g: __version__ = '0.0.2'

@ssmith I would agree with your assessment. I am endeavoring to use GPY & FiPY to monitor a number of devices in a commercial setting (between 50 and 150 high value devices) which implies that many pycom boards. The package, functionality (LTE, sigfox, gps) etc.. all go together to make it an ideal platform. However not being able to get LTE to work, finding a way to repeatably hang device in latest firmware doesn't instill a great deal of confidence. I have a little bit of time up my sleeve however if I have no traction resolving LTE in the next few weeks, then I must look to another solution.

@stefan85e That is correct, the 1.17.0.b1 upgrade is for the LoPy. You do not need to ever upgrade firmware for the expansion board 2

@emmecilab I have only managed to see this when I've done something like put the module in the wrong way round or I'm using a usb cable that makes a bad physical connection. Im sure you already have but could you try removing/reseating the module in the expansion board and trying again. Same with the USB. If its still failing. drop a ticket to support@pycom.io or pm me on here and I'll help get this sorted.

@robert-hh Okay yeah that is a fair point, there is a known bug in this ones firmware with sending RST signals or something. I'll throw it in the bin and try a different one with a FTDI chip.

Hi, @daniel is currently working on this feature, I cannot provide an exact timeline at this stage.

@Xykon , it is now the second time you save my day :)) Successfully updated! You can mark this as solved! Just wanted to point that the command tool didn't work this time, but the python did. Anyway, next step try to connect it to my LoRa AP! Thank you for your help. Regards, (I was using a expansion board)

@misterlisty Youj can dowload images, like https://software.pycom.io/downloads/WiPy-1.15.0.b1.tar.gz or https://software.pycom.io/downloads/LoPy-1.16.0.b1.tar.gz This archives contain a file called appimg.bin, which you have to use for OTA. The files system is kept during OTA, including boot.py and main.py

The command line updater failed (Debian) with this error: "Something failed trying to connect to the device." After this step: "Connecting to the device to get it's information, please wait." Also saw this error message: "Exception: Failed to connect to ESP32: Timed out waiting for packet header, on line 351" With the gui version everything worked fine. I had to install python-qt4 to get the gui version working. Edit: same issue as below

@seb Thanks! Someone should fix this in doc. I'm running the latest stable firmware on wipy3, SPI device is hooked to default pins (as in pinout diagram) and it wasn't working until I've explicitly passed them in pins during SPI initialization. Most of the day yesterday I was struggling to make it work.

@pynew ....support Arduino too