What is the interest level in an MP implementation? There are many things to be taken care of besides just the Hub connection (DPS, Twin, etc).

@eric73 said in joining OTAA on specific channels: @abhishek2101 it's depend in which region you work. If it's EU868 documentation say to use lora.add_channel(index=0, frequency=868000000, dr_min=5, dr_max=6) lora.add_channel(index=1, frequency=868000000, dr_min=5, dr_max=6) lora.add_channel(index=2, frequency=868000000, dr_min=5, dr_max=6) and join will use 868000000 for TX and RX1 (RX2 is always same frequency in lorawan) You cannot choice the channel used by the stack but as the 3 mandatory channel are in same freq.... Not it is just an example, in practice there are no such channel used as 868.0 MHz!

@asb During my testing, changing the spread factor has a huge impact on reliability and receiption distance.

@mraj By hardware or by software? By Software: if you have a communication defined, you can define a command which leads the Lopy to do execute machine.reset(). By Hardware: You need extra hardware, which depending on what you need either toggle the reset pin or power off/on the device. A separate small micro could do that, maybe even the PIC which now resides on the various expansion/ensor boards. There a subtle (unintended I guess) differences between machine.reset(), pulling the reset pin and power cycling the device.

hi @catalin, thank you very much! This answers my question. I would like to evaluate the mesh networking functions for a project at our university. The devices are energy constrained and expected to consume as little energy as possible. For this usecase I would like to use a Sleepy End Device or at least a Minimal End Device. I will use the CLI in combination with disabling the router role for a first evaluation.

@matt3526 Thingsboard has nice documented tracking use-case: https://thingsboard.io/fleet-tracking/

Hi, I tried via ftp and it works perfectly. Regards

@robert-hh Thanks What I want here is to simulate some users doing 1 of 3 things, so: >>> print(uos.urandom(1)[0] %3) 0 >>> print(uos.urandom(1)[0] %3) 0 >>> print(uos.urandom(1)[0] %3) 1 >>> >>> print(uos.urandom(1)[0] %3) 2 >>> print(uos.urandom(1)[0] %3) 2 simplifies my code and will be OK. Regarding Micropython, I've 'hacked' a bit of other code at times and this is the first time I'm having to find the functions I need, so little things like 'dir(os)' are gems. Dave

@jcaron Yes, I got several each press, hence the query on de-bouncing. As for software de-bouncing, it's just that I try not to re-invent the wheel. e.g. I'm sure the micro:bit has a 'button' type for button A and B and since the Exp3 has a user button I guess I expected something from pycom. Hardware wise I tried a couple of different capacitors across the pushbutton (relying on the PULLUP) with little success. I may give it some more testing. Dave

hello, I think we are talking about the same problem in another post. Regards,

Big Thanks for the hint! I compiled the firmware with a buffer_len of 4096 instead of 512 and it seems to be working now. At least it says it reads the correct number of bytes. I still have to verify the data ;)

@shariq I have the code below in main.py, which sets up the device for connecting to my router with a fixed IP, which you then can use to access the device. WIFI_IP = "aa.bb.cc.ss" ROUTER_IP = "aa.bb.cc.rr") WIFI_SSID = "your AP SSID" WIFI_PASS = "your AP Password" def do_connect(): import network import time wlan = network.WLAN(mode=network.WLAN.STA) # create station interface if not wlan.isconnected(): # check if the station is connected to an AP wlan.ifconfig(config=(WIFI_IP, "255.255.255.0", ROUTER_IP, ROUTER_IP)) wlan.connect(ssid=WIFI_SSID, auth=(network.WLAN.WPA2, WIFI_PASSWD)) for _ in range(100): if wlan.isconnected(): # check if the station is connected to an AP break print('.', end='') time.sleep_ms(200) else: print("Connect attempt timed out\n") return print('\nnetwork config:', wlan.ifconfig()) do_connect()

@bmarkus said in About LoRa: Can’t implement for UDP protocol used by Nano GW. Why not using UDP ? A modified version of Pycom LoRaWan nano-gateway software able to resend cached packets to TTN (for example) after WiFi was down.

@robert-hh but i dont see the mqtt integration in my console ?

@cmisztur Forgot to add... using 2 x Lopy4, Fipy, and ESP (Huzzah from Adafruit). Lopy4's and Fipy are on Expansion Board 3. Huzzah's float (literally... they are just hanging in the air in various locations to test distance vs speed).

@abhishek2101 I've got some Lopy4 acting as a class C, and it works fine (mine are always powered) but you need a server capable of sending downlink of course. I'm sorry I can't share any code but looks like something LoRa(mode=LoRa.LORAWAN, public=True, tx_retries=3, device_class=LoRa.CLASS_C) while (not lora.has_joined()): time.sleep(0.1) lsock = socket.socket(socket.AF_LORA, socket.SOCK_RAW) lsock.setsockopt(socket.SOL_LORA, socket.SO_DR, 5) lsock.setsockopt(socket.SOL_LORA, socket.SO_CONFIRMED, False) lsock.setblocking(False) while true: data, port = self.lsock.recvfrom(32) lg = len (data) if lg > 0: print("Downlink Port={:d} Size={:d} Payload={}".format(port, lg, hexlify(data).upper()) ) time.sleep(0.1)

@dan Thank you!

@justin-binda the low side is the signal pin on the 3.3V side (the ESP32 / Pycom module), the high side is signal pin on the 5V side (the sensor). I think that sensor actually has two signal pins, one for trigger (MCU -> sensor) and the other for echo (sensor -> MCU) so you would need two level shifters.