Lorawan and ADR problem. #104

atoy40 · 2017-12-06T13:48:31Z

Hello

I'm using :
(sysname='LoPy', nodename='LoPy', release='1.10.2.b1', version='v1.8.6-849-g0af003a4 on 2017-11-24', machine='LoPy with ESP32', lorawan='1.0.0')

I'm trying to use Lorawan with ADR. here is a piece of code :

lora = LoRa(mode=LoRa.LORAWAN, adr=True, public=True, tx_retries=1)
lora.power_mode(LoRa.ALWAYS_ON)
lora.callback(trigger=(LoRa.RX_PACKET_EVENT | LoRa.TX_PACKET_EVENT), handler=lora_cb)

# OTAA code not shown here

s = socket.socket(socket.AF_LORA, socket.SOCK_RAW)
s.bind(3)
# default rate to SF12
s.setsockopt(socket.SOL_LORA, socket.SO_DR, 0)
s.setsockopt(socket.SOL_LORA, socket.SO_CONFIRMED, True)

i = 0
while True:
    count = s.send(data)
    print('Sent %s bytes' % count)
    pycom.rgbled(green)
    time.sleep(0.1)
    pycom.rgbled(off)
    time.sleep(9.9 + os.urandom(1)[0]%5)
    i += 1

It seems to work "on the wire" because TX packet has ADR bit set, and RX packet (ack in my case) contains a mac command (LinkADRReq) telling the device to set DR4/SF8 (by default I've setup the socket to DR0/SF12)

The problem seems to be in the lora socket code (modlora.c), because it always ask the Semtech stack to send using the datarate defined in the socket, and it never check the current ChannelsDataRate value stored in the Semtech stack MIB after an ADR LinkADRReq is received.

Thanks for help.
Anthony.

Juanma24- · 2018-02-09T10:05:08Z

Firstly, thanks for noticing this. I am having the same problem.
I think you are right. In modlora.c, lora_socket_setsockoptand lora_socket_socket`set always data rate to a value selected by user in the first case and to DR_5 in the second, ignoring ADR. I think I could have solve it but I have not tested it yet. Here it is my workaround:

lora_socket_socket FUNCTION:
Change -> LORAWAN_SOCKET_SET_DR(s->sock_base.u.sd, DR_5);
BY ->

LoRaMacParams_t *LoRaMacParams = LoRaMacGetMacParams();
    if (lora_validate_data_rate(LoRaMacParams->ChannelsDatarate)) {
         LORAWAN_SOCKET_SET_DR(s->sock_base.u.sd, LoRaMacParams->ChannelsDatarate);
    }else{
         LORAWAN_SOCKET_SET_DR(s->sock_base.u.sd, DR_5);
    }

lora_socket_setsockopt FUNCTION:
Change -> LORAWAN_SOCKET_SET_DR(s->sock_base.u.sd, *(uint8_t *)optval);
By ->

LoRaMacParams_t *LoRaMacParams = LoRaMacGetMacParams();

        if (lora_validate_data_rate(LoRaMacParams->ChannelsDatarate)) {
        		LORAWAN_SOCKET_SET_DR(s->sock_base.u.sd, LoRaMacParams->ChannelsDatarate);
        }else{
        		LORAWAN_SOCKET_SET_DR(s->sock_base.u.sd, *(uint8_t *)optval);
        }

I repeate I have not tested it, but I think it has to be on the right way. If everything works fine, I will make a pull request.

JuanMa

this way it is easier to run this script standalone

danspndl added the LoRa Issues related to LoRa label Sep 3, 2018

peter-pycom added a commit that referenced this issue Feb 28, 2020

default path and make executable (#104)

9fb2548

this way it is easier to run this script standalone

amotl pushed a commit to daq-tools/pycom-micropython that referenced this issue Mar 6, 2020

default path and make executable (pycom#104)

ef947be

this way it is easier to run this script standalone

X-Ryl669 pushed a commit to X-Ryl669/pycom-micropython-sigfox that referenced this issue May 12, 2023

default path and make executable (pycom#104)

1170e88

this way it is easier to run this script standalone

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Lorawan and ADR problem. #104

Lorawan and ADR problem. #104

Uh oh!

Lorawan and ADR problem. #104

Lorawan and ADR problem. #104

Comments

Uh oh!

Uh oh!

Uh oh!