• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 17 subscribers
  • Views 332 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2642R:Ping execution by BTool

Shigehiro Oba
Prodigy 20 points
Part Number: CC2642R


I am using the sample source of "simplelink_cc13xx_cc26xx_sdk_5_40_00_40".

I want to measure the latency between Central and Peripheral with BTool.
I think it can be measured by using Ping, but what should I do to execute Ping with BTool?

Please let me know if there is another way to measure latency with BTool.

  • 0
    TI__Mastermind 25810 points

    Hey Shigehiro,

    BTOOL does print timestamps when it sends TXs to the peripheral as well as receives messages from the peripheral. Can you not use this to measure the latency?

    Additionally, this information can easily be obtained if you have an Ellisys or Frontline Bluetooth LE sniffer.

  • 0 in reply to Ammar N
    Prodigy 20 points

    Hi Ammar,

    Thank you for your reply.

    On our side, packets are transmitted unilaterally at regular intervals from Peripheral to Central.

    I understand your suggestion to calculate the latency from the difference between the transmission cycle and the timestamp.
    I will consider it.

    It would have been best if there was a way to check the latency from the log output by BTool, just by using BTool functions (commands) without modifying Central or Peripheral processing.

    Best regards,

  • 0 in reply to Shigehiro Oba
    TI__Mastermind 25810 points

    Hey Shigehiro,

    I'm not sure such a function exists with the HCI api's available. The latency will mostly be a function of the connection interval chosen, at a minimum.

    I hope the timestamps printed in BTool suffice for your testing. Another method of testing could be to place a GPIO toggle in the application when a command is received (let's say you write to a characteristic), and also placing a separate GPIO to toggle in the application that writes the characteristic. This can be done with minimal modifications to simple_central and simple_peripheral and you can measure the time between both GPIO toggles. This is similar to using the timestamps, it is more precise but is also more effort.

  • 0 in reply to Ammar N
    Prodigy 20 points

    Hi Ammar,

    Thank you very much for your suggestions.
    I will discuss it with the members of the company.

    Best regards,

    Shigehiro