How to generate specific packets that captured from other devices?

First of all, I'm sorry for my short English skills.

I have a issue for other bt device not pairing in specific enviroment, so I need to make same issue using 52833 dk for solve that.

It seems to be cause of issue. I was tried generating packet using nrf52833 dk and nrf connect sdk with direction finding connectionless tx example.

Especially, I want to CTE data 0x ff ff ff .... in LE PKT, but captured packet from DK is as below.

I want to add specific data in LE PKT. I want know that it is correct way that using this example or should try other example(I was first of using nrf connect sdk...)?

Any help from anyone would be appreciated.

Parents
  • Hello, 

    If I have understood you correctly, you have another device that has the role of a direction finding(DF) tag. And now you want to create a nordic device that has the role of a direction finding locator. Though this doesn't work for some reason. So to investigate this you see that the default direction finding locator sample doesnt have the CTE after the CRC, which differs from the DF tag you started with, and wonder why. 

    Regards,

    Elfving

  • Hello, Thank you for your reply.

    There is an issue with BT devices not pairing in the field. My guess is that certain packets (like the first picture) are causing the problem.

    My purpose is to use the DK to generate packets that cause problems, especially if they contain CTE data. However, only packets like the second picture (generated in the DK) are being captured, and I wonder if it is possible to get the same data as the first picture (as much as possible) from the DK.

    BR.

  • So the second screenshot is from the DK, and the default NCS DF beacon sample?

    In the first screenshot you have a CTEInfo field in AUX_ADV_IND PDU, which is a bit strange. It is not allowed there. The other screenshot shows AUX_SYNC_IND (periodic advertising PDU) where CTEInfo can be present. See: BLUETOOTH CORE SPECIFICATION Version 5.4 | Vol 6, Part B 2.3.1.6 AUX_ADV_IND.

    Still a bit strange how you are not seeing the CTE, but it is supposed to be following the CRC by default. Though it is possible to set it in the payload too. When using something like the nRF sniffer it might be that the CTE would not be found, as it is no data there, just bit 1's. Though if you do find it on your other packet I find it strange that you wouldn't see it on ours.

    Regards,

    Elfving

Reply
  • So the second screenshot is from the DK, and the default NCS DF beacon sample?

    In the first screenshot you have a CTEInfo field in AUX_ADV_IND PDU, which is a bit strange. It is not allowed there. The other screenshot shows AUX_SYNC_IND (periodic advertising PDU) where CTEInfo can be present. See: BLUETOOTH CORE SPECIFICATION Version 5.4 | Vol 6, Part B 2.3.1.6 AUX_ADV_IND.

    Still a bit strange how you are not seeing the CTE, but it is supposed to be following the CRC by default. Though it is possible to set it in the payload too. When using something like the nRF sniffer it might be that the CTE would not be found, as it is no data there, just bit 1's. Though if you do find it on your other packet I find it strange that you wouldn't see it on ours.

    Regards,

    Elfving

Children
No Data
Related