nRF Desktop APP Direct Test Mode Wrong TX Values

Im working with:

-Windows Nordic Connect for Desktop App v5.20.

-Direct Test Mode v2.5.0

-nRF54L15 flashed with ncs v2.9.0 direct_test_mode example

There is currently an issue with the Transmit power slider in the App. Apparently, wrong values are sent. The issue got discovered when we measured different TX values as set in the App. Testing and debugging has shown following: results:

nRF Windows. Tx Power Slider Setting Register TXPOWER
8 4
7 3
6 2
5 0
4 -4
3 -8
2 -12
0 -16
-4 -22
-8 -40

What is striking is that the TX Power Slider has different values before the nRF54L15 DK gets connected. Take a look at the values before the DK gets connected and compare them to our measured values earlier:

nRF App Settings nRF Reg TXPOWER
8 -
7 -
6 -
5 -
4 4
3 3
2 2
0 0
-4 -4
-8 -8
-12 -12
-16 -16
-20 -22
-40 -40

For me, it seems like the issue lies in changing the App Tx Power Slider values when connnecting the nrF54L DK.

Parents
  • Hi Jonas, 

    We have identified a bug in the nrf connect desktop app where it encodes incorrect for the tx power. 

    The DTM app on the nrf connect for deskto (NCD)p, uses vendor specific commands to send this TX power requests, but as per latest BLE spec, the HCI has its own command 0x09 for sending commands related to TX power. The NCD team has decided that they will now change the app for future revisions to use this new command instead of vendor specific commands. The DTM sample will also adapt for it but until then this will be a known issue on our end on the NCD side. For your reference, the internal tracking number for this is NCD-1420

Reply
  • Hi Jonas, 

    We have identified a bug in the nrf connect desktop app where it encodes incorrect for the tx power. 

    The DTM app on the nrf connect for deskto (NCD)p, uses vendor specific commands to send this TX power requests, but as per latest BLE spec, the HCI has its own command 0x09 for sending commands related to TX power. The NCD team has decided that they will now change the app for future revisions to use this new command instead of vendor specific commands. The DTM sample will also adapt for it but until then this will be a known issue on our end on the NCD side. For your reference, the internal tracking number for this is NCD-1420

Children
No Data
Related