You may have just blown the DC/DC converter. Maybe Pycom can tell us which one it is, I'd love to know more detailed specs on it too. It is s tiny tiny part you'll need some advanced soldering skills and a hot air station at a minimum

@jmarcelino It's possible to send peer-to-peer with two LoPy's. Pycom have supplied a tutorial on that in the documentation. The range I get between two LoPy's is about 400-500 meters in urban area, which is not particullary good though

OK, Thanks~ update: It works at version "1.5.0.b2" os.uname() (sysname='LoPy', nodename='LoPy', release='1.5.0.b2', version='v1.8.6-412-gf55ba50 on 2017-01-28', machine='LoPy with ESP32')

@daniel if you look at my post https://forum.pycom.io/post/3254 it looks same as @Jiemde problem i have also malformed files - look for line oryginal file in my post

Is there some other interrupts that are running in the background?

@livius Sorry my explanation wasn't correct. I mean I first tried the updater. That gave me a failure. The log was: connecting... Failure! then I tried to find the issue by other another tool, but i cant find the issue.

Hello @nurquhar , Indeed the problem is that the person that had the LoPy before you already loaded scripts to connect to a certain LoPy network. What you need to do is to use the safe boot mode, connect via ftp and erase main.py and boot.py, then reset the board. This will cause the original main and boot files to be restored. After that please perform a firmware update using our update tool: https://forum.pycom.io/topic/522/new-firmware-release-1-4-0-b1 After that follow our getting started and the WLAN step by step on the docs, which also include examples to connect the LoPy to your wireless router and be able to telnet/ftp while keeping your laptop connected to internet. https://docs.pycom.io/pycom_esp32/pycom_esp32/tutorial/includes/wlan.html It is possible to transfer the files to the board via serial using Pymakr, just by pressing the sync button. Cheers, Daniel

@ThatStudentGuy Yes, that's right, if you want to communicate between LoPy boards use "raw" LoRa ( mode=LoRa.LORA ) and set the boards up with the same parameters in LoRa.init(...) If you want the LoPy to participate in LoRaWAN networks (with a real gateway like the Kerlink) then use mode=LoRa.LORAWAN which doesn't have parameters, those are defined by the region you're in. LoPy as a pseudo-LoRaWAN single channel gateway is coming but it is a bit of a hack more for development and internal testing where users are aware of the limitations and shouldn't be a replacement for a real LoRaWAN gateway.

Yes I have, sucessfully! I have used the ABP code sample from the docs. Worked as is.

By private blockchain, I mean a local blockchain for all my devices to exchange the data in an application following defined smart contracts, no needs to interact with the global ledger. Geth Ethereum is one of the possibilities, and what I am looking for is the installation/implementation of Geth in Lopy if someone has done that before ?

@livius thank you so much, I too was banging my head with the same issue, FTP is much better and reliable, I'm using tera term to see the console. thanks Cheers

@livius said in Run script on boot for LopY: @gouao as you can see your boot file was run - because you have repl did you try my advice from second post - to put code not to boot.py only inside main.py and see if you do not got script error? Only the COM commection argumens in the boot.py, and the script in main.py. What the sync is really doing on the project ?

The send packet is 7 bytes long and the ack is 2 bytes. On the data rate I didn't set so whatever the default is. Power consumption is a good point on how to tell if it's busy but I want a software method. If we could tie a specific exception type to this cause then I could do something special in the exception handler.

sorry for the confusion yes it is an ic880a not multitech yes i'm checking back all the cables again and see if this helps