DTM Command

RE: DTM Command

Håkon Alseth — Wed, 18 Dec 2019 15:23:40 GMT

Dear Manabu,

My apologies for missing this, and thank you for clarifying this.

The value is shifted down by one bit, but it still exceeds the maximum per the bluetooth spec (251 vs. 255). I will add this to the internal bug that I already created on the former issue.

Kind regards,

Håkon

RE: DTM Command

tama — Wed, 18 Dec 2019 13:48:25 GMT

Dear Håkon,

Thank you very much for your answer.

I understood the first question. Thank you again.

Regarding second question, I would like to ask again.

How is the value "0x01FE(decimal:510)"?

The value seems to be over the maximum value "251" for Parameters with names ending in "Octets"in the Bluetooth specification.

Is this value correct?

Kind Regards,

Manabu

RE: DTM Command

Håkon Alseth — Wed, 18 Dec 2019 13:04:24 GMT

Dear Manabu,

[quote user=""]bit2 and bit3 indicates these meanings. The component "ble_dtm.c" is correct?[/quote]

0x0006 is bit 1 and bit 2. Bit 0 is the status bit:

We will then return that stable modulation index is not supported.

[quote user=""][/quote]

But the component "ble_dtm.c" in the nRF52 SDK(version 15.3) returns the value "0x01FE(decimal:510)" for Parameters with names ending in "Octets" and

returns "0x4290(decimal:17040)" for Parameters with names ending in "Time".

The component "ble_dtm.c" is correct?

In case of DLE and coded PHY support, the returned value of 17040 is correct. However, when CodedPHY is not supported, it should return max. 2120.

I will report this internally.

Thank you for notifying us of this!

Kind regards,

Håkon