@Julia-Steiwer As you should have noticed, Pycom Inc ceased it's operation, and there is no service any more for Pycom products, be it hardware or software like Pymakr. The latter should still work with the older VSCode versions. So if you want to use PyMakr, you have to stick with an working combo of an older VSCode version and PyMakr.

I think I finally found an answer on how to properly reset the modem in case it just won't attach to a network. Reset the modem by sending following AT-command: lte.send_at_cmd('AT+SQNSFACTORYRESET=?') Unlike lte.factory_reset() - which seems to use AT-command AT+SQNSFACTORYRESET - this command will successfully reset the modem to factory state. A reboot of the device is necessary to finalize the reset! After this process the modem should attach to the network without any issues! Also, for further information see: AT Commands Reference Manual, 15.1 Device Reset to Factory State

@Benjamin-Mirad-Gurini there are plenty, the most obvious being the the Pysense has additional sensors (accelerometer, temperature, humidity etc.) which the expansion board doesn’t have, and conversely the expansion board gives easy access to all pins and has a few jumpers.

Hi @ahmadelmasri, Thanks for your answer. I'm using the one from Pycom (Vodafone). Ok, I will also send an email to pybytes@pycom.io.

Hi, I'm running a gPy device on LTE against pybytes.pycom.io. The device has never been connected via wifi and is working fine. Things I have done: attached an external antenna replaced the LTE-controller firmware with one suitable for my region / provider

Hi, This is indeed not directly built into the micropython firmware. You could implement it in C using the ESP-IDF, but we cannot give you in-depth support for that. There do exist some examples over on the espressif esp-idf repository on github that you can look at

@Chandan-Verma can you clarify which example you are using, which region you are in, and where exactly the error happens (the full log/trace would be useful)?

@tttadam said in LTE init error: lte = LTE(debug=True) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: extra keyword arguments given Concerning this error, please update to the latest stable firmware (1.20.2.r4) as the 'debug' keyword is not supported in the version you're using. Let me know if it happens again, generally the issue is solved by either machine.reset() or a power cycle

@robert-hh Thank you

@jcaron Thanks for the info!

I tried the legacy firmware without the pybytes stuff. It is works all right with that fw.

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.

I never managed to reproduce the Core Dump but I found this : https://github.com/pycom/pycom-micropython-sigfox/commit/3f690a5733d31ff938aad6219c498f7d1bf98346 A bug fix, the issue was not resolved in the version I used. This issue could explain the core dump I encountered. The issue is fixed in the last beta version (v1.20.3.b3) and in the last release (1.20.2.r4) of the firmware.