• State Verified Answer
  • Replies 12 replies
  • Subscribers 88 subscribers
  • Views 2495 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 254068
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Zigbee TXPOWER change issue.

embedded_noob

Hi,

I am trying to change the tx power of Zigbee using the following APIs : 

1) zb_set_tx_power(0x32);
2) nrf_radio_txpower_set(NRF_RADIO_TXPOWER_NEG12DBM);
3) nrf_802154_tx_power_set(NRF_RADIO_TXPOWER_NEG12DBM);

None of this API makes a significant change in the TXPOWER CPU register and similarly I cannot see any change in the Wireshark RSS. Can you suggest a proper API to see the changes in TXPOWER.

Thanks

Parents
  • +1

    The RSS should start at the effect that you set, but naturally, the signal strength will drop when the packet is received, because of noise and effect loss both at the transmitting antenna, receiving antenna, and the distance between the devices. However, if you set the output power to -40, you should never see the RSS of -35, because it is not possible that the signal strength has increased over the air. Again, can you double check that the extended device address is actually the device that you changed the TX power on, and that it is not another node routing the message to the receiver? The extended network address is part of the packet. If you still claim that it is not changing, do you have a project where it doesn't work, and I can replicate it? Because I tried it in the light bulb example, and it worked there.

    Best regards,

    Edvin

Reply
  • +1

    The RSS should start at the effect that you set, but naturally, the signal strength will drop when the packet is received, because of noise and effect loss both at the transmitting antenna, receiving antenna, and the distance between the devices. However, if you set the output power to -40, you should never see the RSS of -35, because it is not possible that the signal strength has increased over the air. Again, can you double check that the extended device address is actually the device that you changed the TX power on, and that it is not another node routing the message to the receiver? The extended network address is part of the packet. If you still claim that it is not changing, do you have a project where it doesn't work, and I can replicate it? Because I tried it in the light bulb example, and it worked there.

    Best regards,

    Edvin

Children
No Data
Related