@nickb This is a standard AT command. the response tells: "scanning with unsolicited response enabled" (first 2), and "not registered, but MT is currently trying to attach or searching an operator to register to" (second 2) https://www.etsi.org/deliver/etsi_ts/127000_127099/127007/12.07.00_60/ts_127007v120700p.pdf or https://firebasestorage.googleapis.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIL0iGdl11z7Jos_jpX%2F-LKN7scqKKkb6TqB3uYO%2F-LKN82sqi_sHewyinxC5%2Fmonarch_4g-ez_lr5110_atcommands_referencemanual_rev3_noconfidential (2).pdf?generation=1534782114581269&alt=media

@dan An empty string is returned in cases, when the LTE modem takes longer than 10 seconds to respond. Sending an empty AT command (lte.send_at_command('')) may show such a late resonse.

@pmb_nl Yes it works without any problems the last few weeks so far

@jmarcelino Any update on the fn to enable LOW power LTE option?

@panda Thanks for the input. My first thought was Hologram due to lower cost to get started. Long term commitment to data plan is another issue which I am not sure of. At this point, I am going to be trying lots of different things to arrive at a configuration that works for me. In a perfect world (lots of time and money) I would try both with two different setups connecting to the same sensor network and using the same code. Since my world is far from perfect, I thought I would ask. Hearing your experience with Hologram helps... functionality is also high on the list, and it seems like it is working good for you.

@thomand1000 Have been looking at power consumption and have similar issues to what is reported here have 200mA in main program then 190 to 150 mA for 30 sec before dropping to deep sleep. In first cycle deep sleep current is 200 micro amps. In subsequent cycles the deep sleep current is 30 mA. Have tried turning everything off without change. Have same issue with LTE but don't have a SIM. Agree that things should not be instantiated by default but as required.

@nickboots Great! I'm glad you sorted it out. The project name label might be related to this issue, you should be still able to upload/run your project, it's just the label that doesn't update. FTP only works with WiFi, if you want to use the serial connection, you can use Pymakr with Atom/VSCode, or rshell.

Hello everyone, a question regarding this issue, I would like to know if someone has tried to connect a Lopy with raw Lora to a Multitech Conduit gateway as it comes from the factory or would they not be compatible?

@NickBoots , If you are connecting to an Access point from your pycom device (i.e Wifi in STA mode) disable the wifi on boot option via this command pycom.wifi_on_boot(False) reset board and try again.

@PaulM You might want to look into firmware version 1.19. At the moment it is still in beta, but it adds the option to use LittleFS instead of FAT as the primary filesystem of the internal flash. This prevents data corruption even in the case of power loss during write operations.

After >18 hours of connecting the last device finally started working with the network. I have no idea what happened, because I made no changes to anything. The only thing I can say is that the commands I have in the first post should be enough and be patient with it as it can take >24 hours to find signal and connect.

Update: Some more information... I am in the USA, and registered the SIM card on a verizon network that mentioned it was compatible with the FiPY IMEI. Below is a screenshot of some commands. Firmware is 33080, this is old...could this be the issue?, but it seems Pycom is releasing a new modem update fix soon? Do I need to set the APN manually, or is there something I am missing? I have a CATM1 modem with the same kind of SIM card and it gets signal just fine here. [image: 1534859163191-dd2f561e-2edc-4d5e-bedc-133837e0bb1b-image.png]

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

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?