@bettina Hi Bettina,
I am based in Australia and developing a remote flood monitoring solution using LoPy4 (soon to be FiPy).
I have plans to work with Vodafone locally and wish to get a proof of concept together using NB-IoT.
Can you share information about the outcomes of the NB-IoT workshop to help get me started.
I have systems working with Sigfox and LoRaWAN. Now just want to adapt to test with NB-IoT.
Cheers
Peter.
@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```
EDIT: This issue should now be fixed in the latest version 1.14.2 but I'm leaving these instructions here for now in case the issue is still not 100% resolved.
If you are prompted for a Pybytes token even though you selected "stable" as the firmware type:
Please post your OS type (Mac, Windows (32/64bit), Linux) and exact version here.
Then please use the following firmware updater:
MacOS
Windows
Linux
Please ignore the message about an upgrade being available.
@bmarkus After removing all files and directories left over by ATOM uninstall on WIN10 and reinstalled it works and at first time at least for me upload and download also works. It's the time to restart using LoPy.
@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.
@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.
@ralph
when i press download into new folder (pymakr VS configured on COM port)
all files are downloaded but 3 of them cannot be downloaded
tried many times with reset, disconnect ...
Downloading 3 files...
[1/3] Reading lib/sensor.py
Failed to download lib/sensor.py
[2/3] Reading lib/konfig.py
Failed to download lib/konfig.py
[3/3] Reading lib/GPS2.py
Failed to download lib/GPS2.py
this is how it looks like in Filezilla:
Do you have any concept what can be wrong? - because e.g. file sensory.py is quite small
name is also in lower letters without numbers - nothing special.
konfig.py is really small file 696 bytes...
I can of course do this by Filezilla but..
@eric24 Aha... ok. Longer term eg 6 months horizon, Pycom will be offering connectivity services. For obvious reasons I cannot go into detail at this stage but we will make announcements soon.
In the meant time, I take onboard your requirements and will ensure we publish some practical steps for short term supply.
Leave that with me...
Thanks Fred
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
@fred said in When is the Deep Sleep Shield required?:
Ultra Low Power mode is available on the devices straight out of the box.
It's probably also worth mentioning that it doesn't work...
