Thanks for the replies! @robert-hh It might be that the program is not burnt onto my LoPy. I ran the uos command and this is what I got: ['main.py', 'sys', 'lib', 'cert', 'boot.py']

@juan-narvaezb95 said in Multi-hop End-Device?: listens, sends and transmits at the same time At the RF channel, the LoPy can either Receive or Send at a given moment. You can of course communicate by WiFi and Lora at the same time.

@queifaro Both WIFI and BLE work in the same frequency range, and, if not sysnchonized, will interfere. But for sending, that's the task of the driver stack. I do not know if concurrent receives are handled properly. But again, that is the job of the transport parft of the protocol stack.

@seb I notice that the cordination has abit delay first time you upload it... and it start working once you reboot it :)

@seb Hi sorry seb, because the upper part is only wifi configuration so i didnt show it. Here is the whole main.py from network import WLAN from mqtt import MQTTClient import machine import time import pycom #from machine import Pin #pin=Pin('P10',mode=Pin.IN, pull=Pin.PULL_UP) wlan = WLAN(mode=WLAN.STA) wlan.antenna(WLAN.EXT_ANT) wlan.connect("xxx", auth=(WLAN.WPA2, "xxx"), timeout=5000) while not wlan.isconnected(): machine.idle() print("Connected to Wifi\n") def settimeout(duration): pass def sub_cb(topic, msg): print(msg) client = MQTTClient(client_id="xxx", server="io.adafruit.com",user="vickyho", password="xxx", port=1883) client.settimeout=settimeout client.set_callback(sub_cb) client.connect() print("connected to broker\n") client.publish(topic="vickyho/feeds/lights",msg="False") print("Published!") time.sleep(10) client.subscribe(topic="vickyho/feeds/lights") print("Subscribed!") while True: client.check_msg() if client.subscribe(topic="vickyho/feeds/digital",msg="ON") pycom.rgbled(0xff00) print("Led ON") time.sleep(3) if client.subscribe(topic="vickyho/feeds/digital",msg="OFF") pycom.heartbeat(False) pycom.rgbled(0x0000) print("Led OFF") time.sleep(3) thanks for your reply btw!

@jcaron Rx_iq set to False. if i set it True, lopy does not receive any data. how can i set sampling rate?

For lower attenuation it would better to go with 433 MHz, even better to 169 MHz that is also an ISM band. The big problem with compost, if I remember well how is processed, it is its high water content. There are several studies that can be found about "soil" and wireless sensors networks, search for WUSN (wirelss underground sensor network) and UG2AG (underground 2 aboveground). Usually are studies made for agriculture, forestry, soil, pipelines, ... sensors deployment.

@rachelsimida this is to fast to read it in this way look at pulses_get https://docs.pycom.io/chapter/firmwareapi/pycom/pycom.html#pycompulsesgetpin-timeout sometimes is also good to dissable irq remember = disable_irq() .... enable_irq(remember)

@marcobenini @marcobenini said in Avoid LoPy to restart after deep sleep: @seb Thenk You for the useful link. There could potentially a problem with lora.nvram_save() and fast memory wear due to too high writes or I am wrong? For example: if the NVS (flash memory) is a 100k write cycles unit, use deep sleep and if I send a message every 2 minutes, than in about 140 days the 100k writes is reached. From my understanding of the esp32 forum thread linked previously the NVS is wear leveled so depending on the amount of data it would last longer but for such frequent writes, I would recommend either an SD card or some sort of external RAM that remains powered. Maybe some parameters could not be re-written, but some, like packets counters change every time a LoRa message is sent. There are functions in the firmware for this already: https://docs.pycom.io/chapter/firmwareapi/pycom/network/lora.html#loranvramsave but these also use NVS, this should only need to be done when the device is going into and out of sleep Will Pycom change the functions also to include external memory (for example I2C / SPI FRAM, ...)? There are no plans to do this at the moment, but this doesnt prevent you from adding it yourself for your application. Could the parameters that change be transferred to the microcontroller used for sleep control? I'm afraid the memory on this microcontroller is already running tight, I doubt this could be added. In LoPy4 how are managed the LoRa parameters, does them remain stored in the Semtech LoRa chip? See above I ask since I looking to put together a solution for a test project which end devices have to be battery power, collect data, but send periodically to save power.

@jmarcelino OK, i contact the owner of the gateway to see if it's possible to connect to that gateway. Thanks for all informations! we can close the post ;)

@shiva-shankar Are you sure that you are using V1.17.3.b1 on your device, together with the lastesrt copy of the nanogateway.py script? What are the responses to : import uos uos.uname() uos.listdir() uos.stat("nanogateway.py")

@juan-narvaezb95 Multi-hop is not supported by the LoRaWAN Specification.

This listing (**********) has been removed, or this item isn't available. Please check that you've entered the correct item number Listings that have ended 90 or more days ago won't be available for viewing. Remove this?

@stefan85e Having Pytrack AND Wifi, you have two sources for the time: a) a NTP server. For that you have to espablish an internet connection. Look at the documentation & examples for WiFi and Internet access, Section https://docs.pycom.io/chapter/tutorials/all/wlan.html, heading: "Connect to a router". b) GPS. This is a little bit more tricky, since easy to use examples are missing. You can at least use the examples from thy Pytrack existing library and use that to derive the time information.

@jmarcelino Hi I was trying the code on Leo Gaggl's blog page . Cheers Sean

@jmarcelino said in Send Lora message to non pycom device: You just need to come with with a common set of values for both modules and in the LoPy case set those when initializing the LoRa class Hi again, sorry for the delay in the update. So below is what I've set my LOPY to: lora = LoRa(mode=LoRa.LORA, region=LoRa.EU868, sf=12, frequency=869850000, bandwidth=LoRa.BW_125KHZ, public=True) s = socket.socket(socket.AF_LORA, socket.SOCK_RAW) Seems fairly standard, but what does the "public" parameter do? On the ERA-LORA side via the companion GUI software I have the following st: Bandplan (frequency): 869.85MHz Bandwidth: 125KHz Channel: 0 Spreading Factor: 12 This seems to be a match on both sides though I still cannot get them to communicate :( Does the LOPY use any encryption by default? Any other defaults I need to be aware of? Thanks, Paul

@livius I'm actually using this code, because I'm looking to get the blink of the meter. [image: 1522831409-sans-titre.png] Know I need to find when the led is blinking, because he send everytime the value. I want to know how to check the difference between this value and the last one.

thanks! i didn't want to damage the radio unit.

@jcaron Thank you for reply, Sorry for giving less details. I am sending 'Hello mitcoe' message from file source as well as socket using USRP hardware and GNURadio (Matt- Gr-LoRa) Parameters : Frequency: 868MHz SF: 8 Code rate: 4 BW: 250KHz Sampling Rate: 250 KHz Header: True and same parameters on LoPy LoRa node. But i receive on LoPy LoRa some things like this Received data: 1 b'\xe7\xe7+\xfa\x00MB' 2 ��+�MB 3 b'e7e72bfa004d42' Rx_cnt:1 (rx_timestamp=676924426, rssi=-98, snr=0.0, sfrx=8, sftx=0, tx_trials=0) Received data: 1 b'\xe7\xe7\xeb\xfa\x00MB' 2 ����MB 3 b'e7e7ebfa004d42' Rx_cnt:2 (rx_timestamp=677851000, rssi=-98, snr=0.0, sfrx=8, sftx=0, tx_trials=0) My LoPy code to receive data is: print("In Receive Mode") s.setblocking(False) while True: data = s.recv(64) if(data): print("Received data: "+"\n1",data) print ("2",data.decode('utf-8')) print("3",binascii.hexlify(data)) i+=1 rx2tx_data = 'Rx_cnt:'+str(i) print(rx2tx_data) print(lora.stats()) I am not able to receive what i sent. Also i am sending message multiple times but lora only receives twice or thrice.