RUI3 api.lorawan.txp.get() does not reflect the real TX power level when using ADR

RUI
#1

As the title said, RUI3 api.lorawan.txp.get() does not reflect the real TX power level when using ADR.

Using a power meter from Nordic I can see the peak current decreased after ADR goes to DR5. Which indicate ADR (should be) reducing TX power. However, api.lorawan.txp.get() still return 0, which indicate MaxEIRP. The picture below show the current consumption of the sensor.

image
image853×506 20.6 KB

#2

@carlrowan Sorry for tagging you directly but I want to confirm if this is how it was designed or is a bug?

#3

Hi @chansheunglong ,

I am sorry for missing your post 9days ago.

Whenever ADR is active, DR and TX settings are override. This means values set by ADR will be used by the module.

#4

Thanks for the replay, however, while trying the API I found that even with ADR enabled, calling api.lorawan.txp.set(0) right before queuing the packet can set the TX power (override ADR’s setting) even with ADR enable.

Is there any API to access the setting used by ADR?

The testing is as follow:

  1. Set Tx power = 0
  2. Queue packet, result: Packet send with Txpwr = 0
  3. Queue a new packet. result: Packet send with Txpwr = ADR’s setting
  4. Read Tx power, result: api.lorawan.txp.get() return 0
#5

Hi @chansheunglong ,

Unfortunately, there is no API or way to determine the configured ADR settings.

#6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.