LabView Bluetooth Low Energy (HM-10)

[User002]

Hello folks,

I built a sensor array that sends data to an HM-10 BLE module (based off the Ti CC2541). I have confirmed the data stream on iOS, Android, and Windows independently (see figures 1 and 2) and am currently working on pulling this data stream into LabView.

Using the LabVIEW Bluetooth Low Energy (BLE) Instrument Drivers with LabView 17 (64-Bit) on Windows 10, I queried available devices and verified that the same services and characteristics can be accessed (see figure 3 and 4). Based on details I found on this forum, I developed a workflow that can retrieve the Device Name and MAC address consistently.

Although I can subscribe to channel 11 successfully (figure 5.), I cannot subscribe to notifications on this channel that can be accessed (figure 2. is proof of concept).  I have attached my LabView VI to this post (figure 6 is a preview).

Any and all advice is welcome, I would like to be able to use these inexpensive, low power radios in more projects without the need for additional dongles or radios.

Thank you,

Ken

Referneces:

Microsoft: GATT Client

LabView Forums: Previous Discussion, similar unresolved issues.

Further Reading on BLE and GATT

FIGURES

Figure 1.

 Figure 2.

Figure 3. 

Figure 4. 

Figure 5.

Figure 6.

[abalma21]

Hi Ken,

For inquiries regarding the LabVIEW Bluetooth Low Energy (BLE), troubleshooting, and feature requests please refer to this LabVIEW Bluetooth Low Energy Support Discussion NI Community forum for BLE.

At present, this toolkit is experimental, unsupported, and not recommended for production applications, and has no warranty.

Kind Regards

Alejandro Balma

[User002]

Thanks for the links,

I based my work on materials I found on that discussion.  I was hoping to source additional community resources on this tool as this may be an example where I, a novice in RF design and programming, do not know how to use the tool i have equipped myself with.

I'll keep this open in the hopes that someone might be able to shed more light on the subject.

[endeavor]

Hi Ken,

not sure if your question is still valid but I was having a similar issue and it looks like I was able to workaround it.

It appears that happens because handle IDs provided by the toolkit web service are incorrect. In my case message (notification) characteristic was mixed up with a command characteristic therefore attempts to subscribe to notifications was causing the same error. So the solution for me was to use handles provided by Bluetooth LE Lab, e.g. you need to use 17, not 11.

Hope this helps,

Tatiana

[User002]

Hi Tatiana,

I also developed a work-around for the problem. I paired two BLE radios, configured them to send and receive UART TX/RX over the air.  Data from the sensor array and on-board processing is passed to the BLE radio via UART, the same UART TX/RX is received by the paired radio which is connected to a USB Serial Adapter.

I wrote a VISA function to parse the serial data into a cluster and array for display and post processing.

Thank you for your note, I will check if the characteristic I was using was not correctly addressed.

Best,

Ken