@iotGeek There is a new Pymakr plugin update (v0.1.4) that resolved the issues with the new update (August 2017) if VSC. Try installing it and good luck!

Not sure what operating system you are using... If you have Windows you could try VS Code instead of Atom. If you are on Windows, you should try using Atom version 1.18 with the Pymakr plugin. More about Atom and Pymakr plugin issues on Github HERE More info if you are using Windows 10: The easiest way to fix this for Windows 10 is to downgrade to Atom 1.18, you can download it from here: https://github.com/atom/atom/releases?after=v1.19.0-beta5 half way down the page is version 1.18, I downloaded the AtomSetup.exe file for windows10. Make sure you don't upgrade to 1.19 or above until the Pymakr plugin is fixed. Also Atom is by default set to auto update so as soon as you open it, go to menu >>> help >>> about atom Then un-check the "Automatically download updates" Then install the Pymakr package. From Menu >>> Packages >>> Settings View >>> Install Packages In the Install Packages search box, type in pymakr, it's down a couple in the search, press 'Install' I had to remove the pymakr package manually because I had Atom previously installed. It's located something like c:\users\yourusername.atom\packages I have it all working, now dealing with a serial port connection issue. Can't connect with all the default settings and the correct com port (com6 port etc... )

@daniel Yes, I used readfrom_mem() and writeto_mem(). Thanks a lot for your solution proposal, this approach works for me well :)

@livius os.uname()                                                                                                           (sysname='WiPy', nodename='WiPy', release='1.7.5.b2', version='v1.8.6-694-g25826866 on 2017-06-29', machine='WiPy with E SP32') pytrack firmware: pytrack_0.0.3.dfu yes I git-pulled the lastest library

I have to add some information: I can't use the lastest firmware because the modules are spread and so out of my reach :( I flashed all LoPy modules in April so that's the latest firmware I'm currently using. While searching the web for my problem I found this: https://github.com/Lora-net/LoRaMac-node/issues/104 It says that there is a bug in the SX1276 driver and so maybe in the SX1272, too. It misses a division by 4of the SNR value... And thats the factor I need. So: Does anyone know if this bug was a thing in the LoPy's too and had been fixed in the last weeks after my last update? I can't find anything about it in the last changelogs...

Is there a fix to this? Im running the latest 1.18.2.r2 and im having this exact issue only the write_readinto() work around doesnt seem to work.

Hi @lebucur, The only difference between the LoPy and the WiPy 3.0 is the LoRa stack only. All of the underlying firmware is identical!

Same here. Sync does not work reliably with pymakr and the plugin. It says sync finished and then when i opent the device with filezilla main.py is 0 bytes.

@jmarcelino that fixed it. I can now upload my own firmware. Your fix of increasing the stack and putting listining mode in PASSIVE doesn't help though :-(. I'll see if I can go deeper into the scanning part. thanks for all the help Rolf

@jmarcelino Because we want preserve the Pycom WiPy firmware ad edit it with some frozen files and custom API C (like SSL and BT that have some problems).

@Andrea-Filippini You are welcome :-)

@danielm said in Issue with pin interrupt?: Did referencing of the handler help to prevent those issues? Actually I don't remember the outcome of this test. But it must have been unsatisfying. Anyway, just found the following commit in github: https://github.com/danicampora/pycom-micropython-sigfox/commit/d78bec2191358e3392f878392a19b1d9e3f002bc Looks like this is exactly about the issue I ecountered. Going to compile this myself and test...

if the error code changes it certainly is another error. No clue what -1 means, sorry.

@robert-hh Unfortunately deep sleep hasn't been implemented in the latest version I can use (1.6.3). I will try to implement it myself later today though.

The upgrade worked in a sense, but bricked my WiPy. I have opened a new thread here: https://forum.pycom.io/topic/1053/wipy-2-0-bricked-after-firmware-update

The latest firmware, 1.6.12.b1 has fixed this issue for machine.reset(). Typing CTRL-D in Pymakr still causes a crash but that is manageable by testing for machine.SOFT_RESET before attempting to set up Sigfox and if true, do a machine.reset() or machine.deepsleep(1) first.

@beyonlo I found the solution with wireshark. I was testing the web page with chrome. Chrome is a litle bit buggy to test single threaded web servers. It does a pre-connection without sending any data in order to be ready for next request.

@peter Thanks for your detailed report, we had heard about it before, but there was no description on how to reproduce the issue. We'll add this to our list of bugfixes for the next release.

@peter Thanks a lot for your detailed bug report. We will try to reproduce it, and fix it for the next release.