Pymakr Atom Plugin released

[Ralph]

Hi @MaSePreetz, Thanks for your feedback. At the moment there are already 2 ways to do this:

• In the Pymakr settings screen or you packages overview, you can Disable the entire plugin
• Click the 'close' button of the terminal and leave it closed. When restarting atom it'll remember this state and will not connect. The 'open' button will stay on the bottom of the screen so you can open it at any time.

Is this what you were looking for?

[MaSePreetz]

Hi @Ralph, thanks for the swift response.

You are right, i forgot about the disable button.

But the second method does not work for me when the plugin is enabled.
Atom always opens the plugin window with auto-connect when i open Atom (Atom 1.16.0 on Windows 7 64Bit),
regardless of the previous state of the plugin...

[Ralph]

@MaSePreetz You are right, the behaviour is a little less straight forward. Turns out Atom stores this state per project. So if you have one project open, close the terminal and then close atom, the terminal will still be closed when opening that same project. But when opening another project, the state will be set to 'open' again.

Considering that, it might be useful for some people to have a 'don't open on startup' setting for the plugin, so it will always stay closed by default.

[robmarkcole]

Hi @Ralph I see you have a lot on your plate, but I wonder if it will also be possible to one day program via a Jupyter notebook? This would be fantastic for rapid expolration of data generated by the board.
Of interest https://github.com/adafruit/jupyter_micropython_kernel

[tuxtof]

Same problem for me

MacOS X 10.12.4
Atom 1.16.0
Pymakr 0.9.3
Lopy FW 1.6.12.b1

any other solution to use my Lopy ?

[livius]

@tuxtof
First test if your ping reach device
show us response

ping 192.168.4.1

[tuxtof]

@livius

ping is OK
telnet is working
i can connect on the python interpreter with the default login / password

only Atom/Pymakr is not working

@pycom please help

[pwest]

@smssms Same problem on Linux Mint 17.3, Cinnamon, 64-bit

[Ralph]

@pwest @smssms If you have time, please test the code on the develop branche on github (instructions for manual installation are in the readme file on the develop branch). This code contains pre-compiled versions of the serialport lib for both mac and linux (64 bit), which should solve both of your issues.
Let me know if it works.

[cylex]

Hey there! So after testing the plugin for a few days I have to remark that debugging with the pymakr Plugin is quite hard. When it comes to an error the compiler output is often times incomplete and changes after running the same error-having code for several times... However, the compiler output is complete when I use my terminal.

[bnjroos]

On windows 10 I cannot see any package named pymakr when searching in the installation tab and when i try to install it manually i get thee following:

How to install the pymakr plugin sucessfully ?

Thanks,

[Ralph]

Hi @cylex, The same problem (in a different form) was reported in this topic and the bug was fixed (on the develop branch only, not yet released). Very likely this fix also solves your issue. You can do a manual install from the develop branch to test it if you want, or wait for the next release.

[bnjroos]

@bnjroos said in Pymakr Atom Plugin released:

On windows 10 I cannot see any package named pymakr when searching in the installation tab and when i try to install it manually i get thee following:

How to install the pymakr plugin sucessfully ?

Thanks,

Found the solution by running npm install inside the package folder.

Thanks

[Ralph]

Hi @bnjroos, Good to hear! For future reference, there is a short instruction for 'manual install' in the readme file on the develop branch

[bnjroos]

@Ralph said in Pymakr Atom Plugin released:

Hi @bnjroos, Good to hear! For future reference, there is a short instruction for 'manual install' in the readme file on the develop branch

Yes but on windows I don't have apm installed by default hehehe. Maybe a 'npm install' should be added to the manual.

[Andrea Filippini]

@bnjroos you can find apm in the Atom install location, under /bin folder

[bnjroos]

@Andrea-Filippini thank you for the info, i usually use sublime or Visual Studio Code, I am pretty new to Atom.

[Ralph]

Version 0.9.4 has been released with a few bugfixes and stability improvements:

• Include precompiled serialport libs for mac and linux
• Improved error handling and stability on sync
• Running files is now possible for unsaved files
• Bugfixes for pasting multiple lines and cmd-c/cmd-v commands.
• Fixed connection issue when using telnet to a device's access point

[obviate]

@Ralph Hi Ralph, I installed 0.9.4 and upgraded firmware on my LoPy modules to 1.6.13.b1 and now I can't sync using a serial connection. It was OK with 0.9.3 but I don't know whether to blame the firmware or the Atom plugin update. I am running Atom on a Windows 7 x64 PC.

[obviate]

@Ralph I re-built the filesystem on each LoPy and now the sync is working. All good.