Pymakr Atom Plugin released

[obviate]

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

[Ralph]

V1.0.0 has just been released. A few problems concerning the synchronize feature using a serial connection are now solved and some new features have been added:

• Added project specific settings
• Added serial port detection (in sub-navigation under the 'more' button)
• Multiple bug fixes for synchronization over serial
• Terminal height now resizable by dragging the top edge
• Fixed 'failed to connect' bug when reconnecting on telnet

The project specific settings might need some explanation:
When clicking the new 'project settings' option, a config file is created inside your project folder. Any settings changed inside this file will override the global settings. This can be useful when you are using different project for different devices or when each project has a different folder that has to be synchronized.
Remove the settings from this file that you don't want to override.

[mcook]

@Ralph

Hi,

Maybe I am doing something dumb. When I set up the Atom plugin, by going to Atom > Preferences > Packages > Pymakr, all I see is the PyMakr Readme.

This is what I see... I don't see a place to configure the IP Address of the LoPy.

Any idea what I am doing incorrectly?

Thanks,
Mike

[bucknall]

Hi @mcook,

If you look at the bottom of the Atom window, you'll see a new bar with a button that says '^ Open'. If you click this, you will see the new terminal interface.

[RobTuDelft]

With one of the previous versions I encountered a serious error, Atom wouldn't even start anymore. So I deinstalled Pymakr.
However when I now install it again (tried multiple times) it won't show up anymore. Toggle console does nothing. I can see Pymakr in the packages menu (top menu bar) and I also see it in the Installed Packages menu, where you can change the port etc.

Atom is updated to the latest version. Maybe I need to clear some old files?

[mcook]

@bucknall

Thanks. I see what the issue is.... there is a small red bug in the bottom right corner of the screen. When clicking on it, it indicates that there is an issue with my serial library. It has a "rebuild" link. After clicking on it, and restarting Atom, it now works.

Mike

[RobTuDelft]

Clicking on that bug also gave me some hints: Some installed packages could not be loaded because they contain native modules that were compiled for an earlier version of Atom.Rebuild Packages and clicking rebuild: The system cannot find the path specified, it fails.

edit: third time it worked!

[amartinez]

I' m always having problems to sync with the boards, specially while connecting by WiFi it's almost impossible to sync or run a program.

I have everything updated and using Windows10, am I the only one? Or is it "normal"? What do you recommend me to sync easier? Is it possible to connect with Putty by Wifi?

[Ralph]

A small patch has just been released under v1.0.2. It contains some fixes that will help pytrack/pysense users, for example when the board goes into sleep. The serial will now handle a loss and recovery of the serial port when the board goes to sleep.

• Added timeout and reconnect logic on serial connection (useful for pysense/pytrack sleep)
• Pysense/pytrack serialport detection
• Bugfix related to project settings not refreshing (issue #23)
• Ignoring hidden and empty subfolders during synchronize

[Ralph]

This morning a patch has been released under v1.0.3.

It fixes issues with serialport library on windows32 and problems in newer atom versions (1.17.2 and 1.18). If you had any installation issues before, this update should to resolve it.

[ozeta]

@Ralph I have atom 1.18 and before pymakr 1.0.3 all worked fine. after last update I get: "Failed to load the Pymakr package" ... stacktrace.... then: The error was thrown from the Pymakr package. This issue has already been reported.
View Issue ( https://github.com/pycom/pymakr-atom/issues/1 )

is it possible to revert to 1.0.2?

[Manuel]

@ozeta I have the same problem in 2 windows 10 machines (64 bits).

Using this https://forum.pycom.io/topic/1137/downgrade-atom-pymkr-plugin should fix the problem.

Try with "apm install Pymakr@1.0.2" in cmd or PowerShell (if you are using windows). It worked for me.

[Ralph]

@Manuel That works, but if you want to use 1.0.3, you can completely uninstall and then re install the plugin to make it work. There is an issue with a few files that fail to update to the new code in the folder, for unknown reasons. Only happens on windows it seems. We're working on a permanent solution.

[Manuel]

@Ralph Thank you. It works.

[amartinez]

@Ralph I' m getting this error when I try to install Pymakr plugin 1.0.3 (I' ve tried to update from 1.0.2 and it crashed, so I' ve unistalled to reinstall it).

[Ralph]

V1.1.0 update. Includes a big refactor round that gets the code in line with the VSCode plugin. This has very little effect on the UI and features, except for a new config option 'open_on_start' that can be used to hide the plugin by default. All problems with the serialport should also be resolved (bindings file not found and serialport version mismatch errors), as long as you are on the latest atom version (1.19 or higher)

• Big refactor to get a shared base code with the VSCode plugin
• Added 'open_on_start' config
• Fixes issues with serialport lib for newer versions of atom
• Bugfix in the run feature on linux.
• More relaxed keep-alive protocol on telnet (ping has to fail twice before connection break)

[Colateral]

On my Mac I installed last ver of Atom (1.20.0 x64) and pymakr plugin (1.0.3). I'm connected to LoPy through serial.
After I created a simple file test.py containing this:

import uos
uos.uname()

Sync &Running the project with Atom raise errors. Do I have to configure something to run a simple python file?

>>>
>>
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
NameError: name 'null' is not defined
>
MicroPython 8a4f37d-dirty on 2017-09-17; LoPy with ESP32
Type "help()" for more information.

[danielm]

On Windows 7 with Atom 1.20.1x64 only Pymakr version 1.0.3 is offered as latest compatible version.

Then the package fails to be loaded anyway:

[MJ]

@danielm Hi, i am new here. I also facing the same problem as you. May i know how can we fix it?

[Ralph]

@mj @danielm I see your issue. To explain: from pymakr 1.1.0 on we added a version limit to the plugin (<=1.20.0), with the goal to make sure that when a new version of atom comes out, we can test it before we release the plugin for it as well. The problem is that if you are on an old pymakr version before this limiter, but update straight to a new release (1.20.1 was released last week) you'll be stuck with an incompatible version.

I'll test pymakr with the latest Atom and will release 1.1.2 very soon. A quick fix would be to downgrade to atom 1.20.0, then update pymakr to 1.1.1