Incase anyone else has this problem I managed to solve it. The problem was with my code. boot.py was set to launch main.py but there was a problem with main.py causing the connection to time out. The solution (which I found by accident) was to ctrl+c in the terminal window to kill main.py. It connected fine after that!

@harish-kumar Well, you're not sleeping, so you shouldn't need to nvram_save/restore, but you're re-creating the LoRa object (twice!) in your loop, using two different modes (raw LoRa and LoRaWAN), and re-joining each time, so no wonder your frame counters get re-initialised. I'm really not sure you can use the current LoRa stack like this to achieve what you want. I'm quite certain it would require some extensive changes to the stack, especially if you really want to maintain true LoRaWAN compatibility (i.e. including ADR, MAC commands, etc.).

@_grunf Did you figure it out?

@hopkapi If you connect G24 aka P3 -> 7 G11 aka P4 -> 6 GND -> 8 GND Vin -> 2 (5V) and run the LoPy from USB. then the electrical conditions shoul be OK, and the device shoudl be accessible via UART 1. SOmetimes the definition of Tx and Rx are reversed, so you may swap P3 and P4. That should not cause any harm to the devices. The UART setting according to the data sheet is baud rate: 9600, databits: 8, stopbits: 1, parity: no Some test code would be like: from machine import UART uart = UART(1, 9600) # init with given baudrate uart.init(9600, bits=8, parity=None, stop=1) # init with given parameters while True: data = uart.readall() if data is not None: print(data)

Python code without proper indentation is not very useful. You should try to put it inside a code block like this: import time import machine from machine import Pin tip_num = 0 tip = (Pin('P10', mode=Pin.IN, pull=Pin.PULL_UP)) tip([1]) while tip !="": tip_num += 1 tip_value = (tip) total += tip_value tip = (Pin('P10', mode=Pin.IN, pull=Pin.PULL_UP)) print("Counter", tip_num) print("Done") Apart from that there are a lot of mistakes (e.g. tip([1])) and redundancies (e.g. wrapping everything in parenthesis) in your code. You should probably read the the MicroPython and Pin documentation first.

@robert-hh Thanks for your reply. Yeah exactly I am talking about repeater. Just let me know once they develop this part. Till then I will try to do by myself.

@harish-kumar Did you follow the guide at https://docs.pycom.io/chapter/pymakr/installation/atom.html

Hi @AlejandroReyes, I've just tried this code and managed to find my BT headphones with it. The issue could be that your devices don't use BLE, so the LoPy board couldn't find them. Currently, only BLE is supported. You can find more on this on the Bluetooth docs page. Let me know if this helped!

@researcher Nice chart, what hardware do you use on the GNURadio Side ? Software libraries ?

@xykon Thanks for your confirmation - that will save me a lot of time. I'm going to wait for the official Nano gateway support then. Already pretty excited!

@clementdecaux Not only is there no USB support directly on the LoPy (I guess you connected to the UART lines), but additionally USB is 5V while the LoPy only supports 3.3V...

@anik Without updating you may have incompatible fw versions in module and expansion boards too.

@christian_kohler Did you set Filezilla to single link/passive mode? The number of simultaneous links have to be set in the server settings submenu->transfer settings for each connection. I'm using ftp all the time, and it is pretty reliable and fast. SInce I have Firfox open all the time anyhow, I prefer the FireFTP plugin.

@re The LoPy4 has like any xxPy device a WiFI connection and starts both a FTP and Telnet server. So you can use ftp and suitbale ftp clients like FileZilla and FireFTP to manage files on the LoPy4. see the FTP section of the docs: https://docs.pycom.io/chapter/gettingstarted/programming/FTP.html You can configure both clients to donwload/upload files into the editor of your choice when you double-click them in the devices file pane.