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

pc-ble-driver, Master Emulator, Scripting, throughput

hagar

My company is developing an embedded product based on NRF52 and until now we are using Master Control Panel (MCP) to test BLE communication. MCP is a great tool but we need something similar that allow us to write some scripts that will be used to do automatic tests and to log notifications and indications.

We have a couple of NRF51 dongles here and the pc-ble-driver provided by Nordic would be suitable for this, but it seems to have data throughput limitations: (devzone.nordicsemi.com/.../)

So, I have some questions:

  1. Is there an updated version of pc-ble-driver that supports higher throughput?

  2. Is it possible to use the Master Control Panel DLL to get higher throughput? (devzone.nordicsemi.com/.../)

  3. Do you know other tool/sniffer (commercial or free) that is suitable to read BLE data (mostly notifications and indications) and write scripts to handle that data?

Any suggestion is appreciated!

Thanks

  • 0

    Hi Hagar,

    1. If you use 1mbps, it should give you better throughput. I'm not sure what would be the highest possible throughput though.

    2. You can use the Master Emulator API comes with the Master Control Panel software. It provides the same API that the Master Control Panel uses. But be aware that the Master Emulator only acts as central role, no other roles. This is different from the pc_ble_driver who can acts as peripheral, advertiser also.

    3. Our nRFSniffer can capture BLE activities and export to Wireshark format and you can use other tool to extract information you want.

    Another option I would like to suggest is to create your own central on the nRF5 instead of using our connectivity fimrware and you use your own UART protocol for your test. For example you can create a central that only connect to specific device name and only report to PC the notification the central got. What you do with the central and what to be transmitted to PC is up to you.

  • 0 in reply to Hung Bui

    Hi Hong Bui,

    It is ok. I just need a central device. It seems that pc_ble_driver has a better support as it is newer than Master Emulator, but the throughput limitation pointed on the other post is an issue to me. I will stick withthe DLL for now. Developing our firmware and UART protocol would be nice but we dont have time to develop and support it. Thats why I am searching for some library.

    Thanks for your answer!

Related