Thanks to Roberto, problem is solved. Seems to be a pbm my boot.py Bad one : import os from machine import UART uart = UART(0, 115200) os.dupterm(uart) Good one : import machine import os import time uart = machine.UART(0, 115200) os.dupterm(uart)

Takachi IP67 WH Series or Camden Boss 90 Series enclosure

I was suspecting that too when I noticed I kept receiving them when the lopy was off. But that does not yet solve the issue that the message from my lopy itself is not coming through Edit: @Batilan I have also updated the firmware and both scripts still behave the same

@bartvandeenen Reply to myself!!!! The ABP lora function call does cause a hard crash, if you provide it the wrong parameter: DEV_ADDR = struct.unpack(">l", binascii.unhexlify('311...513')) And then call lora.join(activation=LoRa.ABP, auth=(DEV_ADDR, NWK_SESSKEY, APP_SESSKEY)) The problem is I forgot to take the first item from the struct.unpack array return! To be honest, it doesn't help that the documentation shows this in blue on darkgrey [image: 1479647178014-upload-8c69dd48-7ea8-47dd-aaa2-d88de272ffe3.png]

I have just found the issue in arch linux having upgraded the kernel and thus making the module for usbserial support unavailable. So not related to lopy at all, sorry for the noise!

@daniel Great! You might have to revisit this issue though, see Github. It might have been fixed in the same commit. You know that better than I do. I also opened a another issue: I would like access to the current BSSID: https://github.com/pycom/pycom-micropython/issues/13

Hi, We are actually working on improving our documentation. We'll release the first part soon, which should at least clarify if something doesn't work as expected. Our final goal is to have what @tbradshaw mentions: We'll make sure that all functions work as expected and document clearly their arguments and return values. Stay tuned :)

@MrPy Sad isn't it? Twice the price for double the frustration during development. ;-)

@Ralph No worries. It turned out those two were the same subtle bug, and my 3 letter fix was applied not only where I found it but a handful more places. Commit fc4dd58 contains that fix, and reenables a bit of pin initialization which I'm guessing was commented out because it hit the same bug.

Note that /flash and /flash/lib are in sys.path by default. If you want to put your libraries somewhere else, don't for get to add that directory to your path in boot.py. import sys sys.path.append('/flash/custom-dir')

@George FIY: Besides the passive mode, the lopy can only handle one connection at a time, which you also need to configure in FileZilla (see this chapter in the docs). I'm guessing WinSCP might have this as a default setting, making it work out of the box :)

Today i tried the examples again with the new firmware and now it is working for me.

@daniel said in Question on arithmetic: Hello, Sorry for the delay. The problem is caused by a compiler bug that Espressif has identified and a fix is on the way. Please see details here: https://github.com/espressif/esp-idf/issues/96 Cheers, Daniel Hi Daniel thanks for the info. Looking forward the fixed firmware, hope they will fix it shortly. Regards... Béla

Yes!!! This solved my problem as well. This note should be added to the official quick start documentation! Cheers, Phil

If you can comunicate between LoPy than this is "simple" Virtualize your traffic e.g. Lopy connected to computer by COM Second LoPy connected to First LoPy by e.g. WiFi, Lora, Bluetooth and to your Arduino by COM PORT. Any traffic throught COM port you transmit over WiFi(Lora,Bluetooth) and write by COM to arduino Simple :)