I have the same opinion as @jcaron . MTU size is something that has to be configurable. We should be able to set MTU size of Pycom. Changing is not going to break anything in case of good implementation (I've already tried it with Pycom). @Emmanuel-Florent the reason I've started this topic is that I've experience with ESP32-DevKitC and BLE MTU size changing, on that size everything worked fine, so I'm just requesting the same functionality on Pycom if possible.

a web service protocol stack is a protocol stack that is used to define,locate implement, and make web services interact with each other .

Heya, Take a look at our own pybytes: http://pybytes.pycom.io/

@ingframin Did you manage to modify the firmware? I would like to have a Wi-Fi advertising per 100 milliseconds; default LoPy-4 seem to send an advertising only if requested by a station.

@geoff-white : guess we'll find out.

Hi there, we learned only recently that native code generation indeed would be coming to MicroPython for ESP32 [1]. After MicroPython 1.12 arrived a few weeks ago, this even became a real thing: The esp32 port has the following new features: native code generation [2] However, Pycom just upgraded to MicroPython 1.11 a few months ago so we will probably have to wait a bit to see the upgrade to MicroPython 1.12. With kind regards, Andreas. [1] https://community.hiveeyes.org/t/native-modules-in-micropython/2709/2 [2] https://github.com/micropython/micropython/releases/tag/v1.12

in this section, there was only : #terminal { background: #000; padding-left: 2px; } I have added the line : font-size: 16px; and that is better to read , thanks !

@calvinblock44 Sigfox enforces that the devices that consume their service need to be registered manufacturers, the Pycom's Sigfox native library contains sensitive information and code that need to be packed and secured (As more as possible). From there you have two options, construct your wifi sniffing functionality over the official firmware or select a more appropriate hardware that fit your needs. Be aware also that if you are planning to create a final product using certified boards your are not allowed to modify the RF code because is highly possible to void the certification if the code modify the way of signal emission.

Dear @tanmay07 and @Martinnn, if you feel lucky, you might want to try our custom build just released on [1]. More background about this is available through [2]. Please be aware that when upgrading from a lower firmware version to this custom build based on 1.20.1.r1, you will have to erase your device completely before flashing in order to keep things straight. You will find respective references to this on the forum. Hint: Use pycom-fwtool-cli --port /dev/ttyUSB0 erase_all, see also [3]. With kind regards, Andreas. [1a] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/GPy-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz [1b] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/FiPy-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz [2] https://community.hiveeyes.org/t/investigating-random-core-panics-on-pycom-esp32-devices/2480 [3] https://community.hiveeyes.org/t/installing-the-recent-pycom-firmware-1-20-1-r1-requires-erasing-the-flash-memory-completely/2688

@seb Yes I meant copying single files. I installed mpfshell and this can do the job for me. I did use an FTP toool for this, bud when using the WiFi radio in my app I constntly had to switch between IP addresses. Thanks again.

@robert-hh Thanks! I tried this and it works great! I tried also the new update with the freezing the _main.py which also solves the problem.

This is the correct procedure. It works 100%. I really appreciate your quick and accurate response. THANKS !!!