@ahelllycan I think we would need to see code, or general overview of your process. At the moment we are guessing. But @jcaron is right. You should have a call back on message receive and you choose when to send messages based on other criteria. The rest of the time you will be sleeping or waiting.

@seb Thanks. Did the trick. Remove directory, reinstall and rebuild the package Thx, Geert

We are aware of this issue, expect and update very soon to resolve this.

@u0452047: I think you should put it in the categories Bug/Issues

HI @smbunn, thanks for reporting, sorry for not having this issue fixed yet. We spent some time today re-compiling the serialport-lib that's in Pymakr for Atom 1.25. It hasn't succeeded yet for all operating systems. There is a new release of pymakr v1.2.10 which contains new precompiles for osx and win64, but the latter still has issues. Bear with us on this, we'll be sure to fix it in the next days. And there's always VSCode to fall back to for a few days. I'll keep you up to date.

@jmarcelino In the board, I have a custom code running, and it shows what it should on the console, but whenever I try to upload a project, it fails. It had worked until I updated the plugin to the last version.

Could you try deleting C:\Users\Stefan\.atom\packages\pymakr\ and re-install the pymakr plugin

Have you tried using something other than pymakr? maybe screen or minicom. Also its worth checking if your user has permissions for the serial port. The procedure to do this varies by linux distro but on most you can add your user to the dialout group and when you reboot that user will have permissions to use serial ports sudo usermod -a -G dialout $USER

Hi, At this time the plans to make a sublime text plugin have been cancelled, I will remove this from the documentation

@seb thanks... I look at that but I cant understand how I should do it spend alot of time with it :( and I cant get to a solution...

Connect a jumper between P12 and 3.3V and press the reset button, this will cause the onboard LED to flash orange, when you see this please remove the jumper. This puts the device into "safe boot", in this mode it will not run the boot.py and main.py files and drop you straight into the interactive REPL terminal

@robert-hh Thank you, that worked perfectly.

@seb Same reaction here... I think however there are cases when Ctrl-C will not interrupt the currently running code right away, but have an effect only once the current call is finished or something, maybe that's related? We don't quite know what code was running... Or maybe... @pierrot10, had you actually deleted the console in Atom (clicked on the bottom part of the window) before hitting Ctrl-C?

It looks like it needs a double scan to find the rom. After inserting ow1 = OneWire(Pin('P4')) print('found devices:', ow1.scan()) Even if the print is an empty array ('found devices:[]') then the temperature reading is working with appropriate rom... Anyone can get why? Maxi

@goldfishalpha No, I just moved the txt-files outside the project folder. That is good enough for me. Johan

Thank you. Everything works now. I hope that pymakr will be fixed as well.

We've just uploaded a new version (0.1.6) that works on windows x64. Try it out and let me know if your problem is fixed.

@soren Sorry for the late reply. Atom currently always copies the top option in the list. If there is an actual Pycom serial detected, it will place that one at the top. Anyway, this is just a result of your issue, not the cause. So just to be sure, after rebooting your mac, you are able to connect to your device? Then when switching out to a different lopy, the comport disappears from the list of serials, even when closing the connection during the swap? Do you switch expansionboards, or just the lopy? You could even hot-swap your lopy while keeping the expansion board connected, see if that helps.

OK now works! I changed the device address in the global settings to the correct Com port and rebooted Atom and it picked it up fine. Thanks again, @seb, rather strange this has only just started to happen!

Hi @seb Thanks that clears things up a lot! I didn't know I could list the methods in each module either, useful to know... That would be fantastic if you could add this sort of extra detail in the documentation, I'm sure that will save me a lot of time! Thanks again.