@eric73 I am just creating the file and the first row, in my mind that's belongs to initialization. But correct me if not. Okay than I just use the basic file operations. Thank you! :)

@robert-hh Awsome! Thank you

@priis You constantly use the wrong firmware images with the wrong tools. Stop panicking. If you have a WiPy3, then you have to use the Pycom tools. The pycom firmware will be downloaded by the pycom update tool on the fly. You do not have to download the firmware beforehand. The firmware updating tool is here: https://pycom.io/downloads/ The instructions are in the link I gave you earlier: https://docs.pycom.io/gettingstarted/installation/firmwaretool Please follow the instructions. You do not have to use esptool.py of firmware images from other sources.

@alexpul But if it's only about not executing boot.py and main.py on boot, you can do similar with python scripts: from machine import reset def safe_boot.py() # create a special main.py and reset f= open("no_main.py", "w") f.write('''import os\nos.remove("no_main.py")\n''') f.close() reset() and then a specific boot.py, which checks for that special main.py: import machine import os try: f = open("no_main.py") f.close() machine.main("no_main.py") except OSError: # do the previous boot.py stuff here Or something similar in you regular boot.py and main.py, which just checks for the existence of a flag for bypassing.

Hi @grideagle, Thank you for reporting that, I've reported it to GitBook. The current workaround is to use the "copy" button it the top right corner of the code section.

@binux I haven't tried upip but support for uzlib should be available in the latest development firmware.

Hello, If you want, I propose a new powerful embedded Web Server for MicroPython (and CPython) that supports route handlers, modules like WebSockets or PyhtmlTemplate and a lot of simultaneous requests. Mostly used on ESP32, Pycom WiPy, STM32 on Pyboard, ... Robust and efficient (thousands requests on CPython!) GitHub - Open Source - MIT. --> https://github.com/jczic/MicroWebSrv2 <--

@jimpower The load sensor combinator shown combines four half bridge load cells in a way, that it looks like one full bridge load cell. It is a pure passive board simplifying the wiring. The output has to be fed into a load cell amplifier and digitizer.

@xykon thanks for this note. In this case I didn't need to reflash the firmware, however I will remember your advice as I am sure to need it soon enough!

@Henning I had the same issue with the Expansionboard v3.1. The issue got solved, after using another Expansionboard v3.1 I've bought recentely..... I never used the SD-Card slot on the first one before, so I don't know, why it seems to be broken. Well, at least it works flawless with the second Expansionboard.

There are indeed enhanced libraries other contributors already shared, though it depends exactly what data you are looking for. A few links to check out: https://github.com/inmcm/micropyGPS https://github.com/andrethemac/L76GLNSV4/blob/master/L76GNSV4.py from @andrethemac

@martijnthe I have to check that again. As far I recalled, I tested the wrap-around situations.

@inverseeffect Unit testing on hardware is a little more difficult that pure software because timings can be variable and you need to have real hardware connected. It certainly is possible to create small units of code and have them run and check their results, it's no different to running your full code, just split into smaller chunks and with more checks.

@livius Hello, Thank you very much for your quick response, as am new to server and pycom, it would be great help if you could share the code from fipy side and server side with step by step procedure. Thank You

@rskoniec Thank You sir

@formica does any other ampy action work, like 'ls' or 'ls /flash'? and the usual brute force hammer on linux, running it with sudo?

@livius TYVM!!

@seb Thank you for your reply, YES true that compute module does not have wifi or BT , so only we go with UART connection, and i have connected the fipy and RPI compute module via UART. But how shall ssh to RPI compute module and access the RPI file structure. After the serial connection now i want to send data within the RPI compute module to server. How to do this?? Thank You

@xykon I just tried it and it seems to work. Thank you very much! Are the settings in examples/wifi/scan/sdkconfig in the Pycom IDF repository exactly what you are building with or do you use a modified version? Is it documented anywhere which version of the IDF was used in a particular version of MicroPython? I assume at lot of the settings in sdkconfig (for example partition table) don't really matter, because they only change the (in this case unused) bootloader and app that are also built with make all. Is this correct? I think a hint in the readme.md of the Pycom IDF would be helpful.