I have made the test with scan intervals and scan windows equal to 10 ms. static esp_ble_scan_params_t ble_scan_params = { .scan_type = BLE_SCAN_TYPE_ACTIVE, .own_addr_type = BLE_ADDR_TYPE_PUBLIC, .scan_filter_policy = BLE_SCAN_FILTER_ALLOW_ALL, .scan_interval = 0x10, .scan_window = 0x10 }; The results are better but still not as good as v1.20.3.b0 Beta Firmware was. With the new values, I raised up to 60% of advertisement frames catched. Always with the same conditions and 500 ms as advertisement interval.

@Gijs actually I solved my problem before seeing this , anyway it is very interesting. In particular, my problem was solved by removing if not bt.isscanning(): bt.start_scan(-1) # start scanning with no timeout print('Trying to establish connection with Nord') connection = bt.connect('ac5fea133f19') I found out these commands were not needed and they broke my code.

Hi Gijs, thank you for your answer. I am aware that the beta can be unstable but the advertisement sniffing performance on r4 release was too poor for my objectives. The performance on that regard with the beta was far more better. I will try to reproduce the Core Dump and come back to you when I found out what's exactly triggering the Core Dump and share the code with you. Best regards

@Filisia-Melissari With the pysense the pycom updater will switch the FiPy to download mode. (assuming you mean bootloader mode). besides that, you can always force bootloader mode by connecting P2 to GND and pushing the reset button on the FiPy. P2 is available on the external IO header of PySense, the middle pin in the row with the square pin, or at the FiPy itself.

Hi, From what I understand, the Fipy's LTE modem no longer responds to you in the Pysense V2 (That is what cannot determine modem state! means). You mention using different fipys and pysenses etc. Do you have multiple Fipys experiencing this issue? Only on Pysense 2.0 X, or also on Pysense 1? Are you using additional accessories on the Pysense through the expansionpins? Can you try the following for me on the Fipy that does not work. Completely wipe the Fipy flash (in the pycom firmware update tool, advanced section clear NVS, CONFIG and erase flash check marks) and update to the latest firmware 1.20.2.r1. Let me know Gijs

Updates I guess my sims aren't activated for LTE-M (they should be) but only NB-IoT. I upgraded my modem to NB1-41019 and it works now :)

@paul_tanner What's the value of net.sec in you case?

@robert-hh I see, that what I thought. then I will reuse UART1. Thanks :)

Also you might want to have a look at this thread, might be useful, since it took a lot of effort for me to be able to connect to Azure IoT Hub with my FiPy. FYI: I am using a regular phone sim-card from Telia (Scandinavian mobile provider), which is possible since they have LTE coverage in most of Northern Europe, and Germany as well i suppose. https://forum.pycom.io/topic/5713/send-data-to-azure-iothub-with-mqtt-protocol-without-using-pybytes-solved

Someone found a workaround - check out this github here: https://github.com/pycom/pycom-micropython-sigfox/issues/424

@catalin Ok, I will try the licensing then. Thank you very much.

@hayesey I am looking for a SIM card NB-IoT enabled in the UK. Could you let me know how you get your SIM card, or where I can find one please?

@naveen No clue. When it did not work for me, I could not get a hand on debugging. I only purchased another LTE NBIoT module to verify, that the service was available and the SIM worked. It did. Module type SIM7020.

@naveen I paid EUR 2.90 for the return postage.