@steve-williams , I did some power mesurements here on the same setup I mentioned in my previous post to give you a clear picture about the current consumption while the modem is trying to attach so as to help you identifying the problem , in first trial I intentionally powered off the CAT-M1 network in office and run a script on GPY trying to attach you can see that the modem current consumption increases after sending attach request and keep trying to attach periodically, you can see that the Avg.current consumption when trying to attach can reach 285mA (150mA more than normal). The following image is when CAT-M1 network is back online and attaching is successful :

@arneme Yup. Thats Correct.

@paul-thornton The timing is rather critical. Couldn't you extend the time window for updating to let's say 30s?

See also my post here https://forum.pycom.io/topic/4130/pinout-pysense-etc

@stevo52 Yes, from the distance, it sounds like a hardware problem with the board. Maybe a broken wire or a bad solder point at the P2 pin.

@robi90 I misunderstood your first post, assuming a hard crash. I just tried your example and agree, that this is not good and must be fixed, because the device locks up in an unresponsive state. I tried that with version 1.20.0.rc4. The situation is a little bit better with Ctrl-F, because then the device falls at least back to safe boot, from which it can be restarted with machine.reset(). But only from the USB port. Using telnet is only possible then, if you use the default settings for WiFi.

Ill raise this internally. seems like a good idea.

Never Mind. Saw post with info.

@robert-hh Es läuft jetzt. Ds Update ging nicht weil ich das Board für den Fipy überbrückt habe das es im batterie Modus läuft. nach entfernen des kabels ging auch das Update. Jetzt kann es weiter gehen. Danke für deine Mithilfe.

@john-baird Can you try this? https://forum.pycom.io/topic/4022/unable-to-update-gpy-modem-firmware/4