This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Howto transfer hugh bidirectional data amount?

Hi there,

I'm just beginning BT development, so sorry for my basic question:

Our application needs to transfer data from PC to our device (approx. 512 bytes) then our device will respond with approx. 512 bytes. And then the PC sends again a request with 512 bytes and our device responses again with 512 bytes. Data transfer should be as fast as possible, power consumption is not important.

A smart phone (Android) or Windows-PC (Win10) should send the requests and visualize the response data. Would be nice, if that works out of the box without installing a special driver (.sys).

Summery: We want to use Bluetooth only as bidirectional data gateway (maybe like a virtual com port over the air).

Want is the best development-board and SDK example to get started? Makes it sense to use the nrf52832 chip (I have right in my front a Taiyo Yuden Evaluation Kit EKSHCNZXZ with nrf52832).

Thanks a lot for any hint,

Mark

Parents
  • If you want to target Win8/8.1/10 only and you insist on requirement "not to install any custom driver" then you can use Windows native BLE support in UWP API, there is HRM (Heart Rate Monitor) application example by Microsoft which works out of the box with Nordic HRM peripheral example from nRF5 SDK on any nRF5x Dev Kit. From there you can move on. Probably changing HRM protocol to something like Nordic BLE UART (aka NUS) but then you need to solve two principle things: rewrite Windows app to support the protocol and implement your custom protocol layer to fragment and reassemble data because 512 is too large for normal GATT layer set-up. There are more tools and examples from Nordic which support NUS so you should have plenty of inspiration whatever platform or programming language you choose.

  • Hi Mark,

    If you don’t mind using a nRF5x-DK as the gateway, we have a Desktop library for BLE development using nRF5 called pc-ble-driver. This is used in e.g. the nRF Connect for Desktop. Source code for nRF-Connect desktop can be found here. You can also create your own custom app inside the nRF-Connect framework, see this page.

  • These examples you guys are discussing... do they assume that the PC is connected somehow physically to a Nordic device/radio?  Or can the Win PC use it's built-in Bluetooth along with your API to talk to a remote Nordic-based device?

Reply Children
Related