D not forget LoRa as an option if it is a LoPy 4 device.

Hello, I'm working on a modbus project using the pycom controller to read a few input registers. But there I get the same error as you Sameer and I'm not able to make the code run correctly. What did you do that the code work? Regards, Jan current code: ######################### RTU SERIAL MODBUS ######################### uart_id = 0x01 modbus_obj = Serial(uart_id, pins=('P3', 'P4')) ###################### READ INPUT REGISTERS ################## slave_addr=0x01 starting_address=0x04 register_quantity=2 signed=True register_value = modbus_obj.read_input_registers(slave_addr, starting_address, register_quantity, signed) print('Input register value: ' + ' '.join('{:d}'.format(x) for x in register_value))

Hi @fasih011, The identity is needed by the server. If it's not configured on the server, just set it to some dummy string, but some value is still needed. Otherwise, you'd have to check/get the identity from the network server.

@braulio The time on air changes with the data rate. And for larger distances, the sending device may be set for lower data rates. But that does not happen by itself.

@beyonlo said in 30uA and LoRaWAN: @marcozennaro said in 30uA and LoRaWAN: @malachib it is just sending. As I use ABP I don't have to wait for an acknowledge from the gateway. Using ABP do not means that node will not waiting for a possible ACK from the Gateway. Both, ABP and OTAA always waiting a time (are two DOWNLINK slot times) after sending data, for a possible ACK from the gateway, that is standard. The difference is that OTAA needs an authentication (that will use a DOWNLINK too) before to sent any data, ABP doens't. You are missing different things. First, Gateway never send ACK, it is done by the LoRaWAN Network Server when requested by the device. ABP and OTAA are activation modes and handling encryption keys. ABP itself doesn't generate any air traffic, keys exchanged out of LoRaWAN. OTAA is a way to generate keys but it has nothing to do with authentication. Whether node will wait for downlink and when is independent of activation mode, it depends on Devics Class 'A' or 'C', 'B' is not supported by PyCom and most of other devices.

@burgeh It is definitely possible, if you use raw LoRa mode. The simple expamples from the docs would serve for LoPy. I do not know how you want to drive the RN2903.

It is hard to determine the quality of thermocouples purchased via Ebay/Amazon. It may be a great sensor, however if you need something of quality and accuracy – or even just general information, just go to [www.pyrosales.com.au](link url) CEO John S

@harish-kumar Is it a 'Class-A' device? RX window timing can be an issue.

Looks like I got it working, seems atom and pymkr plugin were not looking for the plugged in port, rather the one that was used first. Found option in the settings to get the port automatically. Andrew

@robert-hh There is a PR for that to fix the issue OK, thank you for the heads up

@shiva-shankar There is not something like a Lora connection. You only can send messages, and if you're lucky, they arrive. At most, you can ask for confirmation when sending. But confirmation messages account for the downlink budget, and that is (intended to be) limited.

Hi @james-matthews, Maybe a LoRa mesh network? (Note: it's still in development) What type of devices do you have?

Hi @abhishek2101, You can find our tutorial for OTA here: https://docs.pycom.io/chapter/tutorials/all/ota.html

@robert-hh Thank you so much for your time. I made some changes and now my program works fine.

@robert-hh Thanks, that is perfect.

hi @affoltep i tried to connect a gps to my lopy4 and use your code, but it's not working.. of course the gps led is blinking and the code is running well. this is my wired setup [image: 1533114953929-connessionelopy-resized.jpg] can you help me please?