The iccid() function only works after an attach command is attempted. Since we use the ICCID to determine the correct APN to use in the attach command, we have to do a dummy attach call, read the iccid, detach, and then correctly attach with the computed apn. Hope this helps others until this issue is resolved.
Below is the revised code that now works.
from network import LTE
lte = LTE()
iccid = lte.iccid() # does not work
lte.attach(apn='unknown') # attempt attach so iccid() will work
iccid = lte.iccid() # iccid() now works
# compute apn from iccid
lte.attach(apn=computed_apn) # attach with correct apn
Sorry Paul, I never saw your reply until today. Unfortunately our load is pretty complicated; we have one thread for each I2C bus we configure (1 or 2 depending on the system) and two threads doing socket communication (one for outgoing and one watching for incoming). We're keeping track of resets and will monitor the systems. If it doesn't improve with later firmware releases then I'll have to look at debugging the crash. Do you have instructions on how to go about that?
@protean Pymakr is indeed using the zlib.decompress() micropython function for this feature. Normal upload also still works of course, but this way is faster for large files. Let me give you some pointers on how to code it:
The zlib function on the micropython side is documented here. Pymakr is compressing the files before uploading (here using this python file), writing the compressed file to the board with os.write() like always, and then decompressing them right after that (here). It'll definitely make uploading bigger files faster. Just realise that for files under 4k, it's actually slower because the overhead of compressing/decompressing is bigger than the savings of compressing the file.
Great news @Paul-Thornton! Congratulations
I looked at the lora-alliance website put couldn't find the certification reports -- have you made them available? Obviously we would like to use your certification but need:
the certification reports
the git hashes or release number of the code which was actually certified
Also are you planning on getting AU-915 certified, as it's a supported region in your software?
The fixes to the stack and radio drivers that you mention sound great! I had an issue with the LBT in the radio (lack of filtering so that all channels could look busy) and am interested if that was addressed.
Looking forward to the certificates and associated code!
The issue is that socket.connect() and SSL handshake will not timeout also in case the socket timeout is set and hang the application forever.
@philwilkinson said in New LTE Firmware release v1.18.1.r3 & CAT-M1 firmware & modem updater:
I have just attempted to upgrade a new module to the modem firmware.
But I get the error statement, I have no idea what it refers to.
Do you know the firmware version of the modem when you started the upgrade? Which MicroPython firmware did you use? And which firmware upgrade file / method did you use to upgrade the modem?
@rskoniec said in New Firmware release v1.18.1.r1:
@mfa2214 xPy module f/w and GPy/Fipy modem f/w are separate, so GPy/Fipy module f/w doesn't contain modem f/w.
Here http://stiny.webd.pl/PYCOM/ on my VPS you have collection of CATM1/NB1 *.dup files.
Many thanks @rskoniec for sharing the files :)
More simple procedure on Linux :
start from the Linux menu "Pycom Firmware tool", quote "include dev releases"
then just choice /dev/ttyACM0 in High transfert mode
the firmware is flashed in 1.18.1.r1
Wrote 1.19 MiB from sipy.bin in 1 minute and 13.88 seconds
@xykon said in New Firmware Updater version 1.15.1:
@bmarkus Win32:Evo-gen [Susp] is a broad classification used by the Avast Behavior Monitor feature for software that exhibits suspicious behavior categorized as potentially malicious. The Behavior Monitoring feature observes the behavior of processes as they run programs.
The firmware updater connects to the Internet. That is considered "suspicious" for some anti-virus applications.
Thanks for the details. However it is a bit strange,a s I'm frequently installing programs connecting to the net during installation and have never seen such message from my AVAST.
Anyhow, I will ad it as an exception.