@nervencid said in Pymakr and VSCode 'sync_all_file_types' Configuration flag: Hello to all: I'm using VSCode with PyMakr, for upload NO .py files to flash memory, the folders are created fine However the files (extension .pem) are not uploaded. I find the 'sync_file_types' flag into 'settings.mddordle' file and i set it in true but doesn't have any effect (how can i setup this on VSCode?). In atom i switch this option to true in options panel and the files seems to be uploaded to the board properly. Can PyMakr extension of The VSCode work like atom one? Thank you and sorry for the English Where do I configure this in VSCode? I found the'sync file types' value in the'settings.md' file and set it to true, but nothing changed. After setting this preference to true in Atom's settings window, the files were successfully uploaded. Is the VSCode PyMakr add-on compatible with atom?

@martinnn Found the issue with your firmware updater. If you would want to update to a dev version, you need to download the development version of the firmware updater (here). They will release it as stable soon, but not until then, use this dev version.

@jpaul Good to hear. Our tutorials don't cover auto-connect very well yet, we'll work on that!

I also could not connect to my board and solved the problem as follows: If your PC has Bluetooth, have you ever tried to turn off Bluetooth? On my PC, Bluetooth uses COM3. Pymark always tried to connect to COM3. After I turned off Bluetooth, I was able to connect to my Pycom board without any problems. Once a connection to the board has been established, the board can also reconnect successfully with Bluetooth turned on. I hope this information helps. (: In my case COM3 is used by Bluetooth and Pymark tries to connect to COM3. [image: 1630835630712-85fee3ed-fbf7-4c3a-aafa-7c2e4310b551-image.png] In this menu you can disable Bluetooth [image: 1630835590640-a2ac2595-41ee-4d30-98cf-a1336265b5ab-image.png] Connection to the board has been established successfully: [image: 1630835997595-72640caf-babc-4421-aa13-34d4d1ce8800-image.png]

Thank you @paul-thornton, I just saw the addition to the web page with the mechanicals. I'll start drawing my board ;)

Dear @Milan 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 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. [1] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/WiPy-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

@paul-thornton I seem to get the notification now, but I'm guessing it's the mentions specifically, since I turned on the "replies in topics you watch". I'm pretty sure it's not browser related since it's not in the notifications view, but I'm using google chrome Version 71.0.3578.98 I'm guessing you get the notifications because of the reply and you're watching the topic, not because of the mention. I'm going to put mentions on emails only and replies on notifications. That should send me an email when I get mentioned and a notification because there's a reply if you reply to this topic.

@nervencid With autoconnect to false, it indeed tries to connect to the address 192.168.4.1, so the output you posted is as expected. To connect you can either: connect to the devices wifi and klik connect again, or: change the auto_connect setting to true, or: set the address setting to the correct comport (you can find it using the 'list serialports' command)

when you click run just the single file your editing it sent to the board its literally as if you typed each line into the Repl. this is fine if its just your main.py script. but when libs need updating they dont get sent as you have discovered. The reason for the reset being required is to force micropython to reload its previously loaded and cached copies of libraries There are work arounds for hot reloading code, but its way easier to just reset the board during development

@graham said in lora.join does not attempt every 15 seconds in background: while not lora.has_joined(): pass I would add something like sleep(1) into the loop, giving the background tasks more time.

@gmedlicott it's not True by default, because older firmware doesn't support it. We have documentation for pymakr settings here

@shp96 That does not seem correct. Your gateway is only listening on channels 48 to 55 and 70... Can you show logs of packets received with the associated channel?

Thanks heaps @dan Its working fine for me now on VSCode 1.27.2 :-)

Hi @John-Baird I hope you (and I) find a satisfying environment to work with these devices. Another project I've come across since then is balena (which used to be called resin) https://www.balena.io/ It's a very cool project, with almost everything open source and which can be self hosted. I talked about my use case on their forum https://forums.balena.io/t/edge-node-manager-for-wipy-micropython/2549 and someone replied with this https://github.com/Bucknalla/resin-pycom-ota project which I haven't had the time yet to try out. The idea is that you have a device that acts as and "edge manager", that device runs balena and whenever you upload new code (git commit & push) the edge device will update your pycom devices.

@dan Yep I have never put anything in boot.py, have always had main.py run without intervention.

@alvaroav Good to hear it's solved. I'm still not sure if it's another plugin, because another user had this and it was gone after a window reload. Might be some edge case in button usage.