pc-ble-driver-py failure with Queue.Empty

RE: pc-ble-driver-py failure with Queue.Empty

Christian Warren — Fri, 12 Jan 2018 18:44:24 GMT

Yes, I did install it using PyPi (so the version installed is v0.11.3)

I got ensnared in several issues trying to compile pc-ble-driver from source, too, so I've switched to using bluez / hcitool / gatttool to talk to the heartrate app (which seems to work well). Thanks for taking the time to help, though.

RE: pc-ble-driver-py failure with Queue.Empty

Jørgen Holmefjord — Fri, 12 Jan 2018 07:40:16 GMT

Yes, you are correct. Which version of pc-ble-driver-py are you using? Did you install it using PyPi?

RE: pc-ble-driver-py failure with Queue.Empty

Christian Warren — Thu, 11 Jan 2018 17:15:44 GMT

Thanks, Jørgen.

So if I'm understanding #2 correctly, when the script says 'INFO:pc_ble_driver_py.ble_driver:Flashing board with firmware', it's not re-flashing the nRF52 device, it's reflashing the board itself - because the board is going to act as a BLE adapter for the PC to communicate with the nRF52 device. Is that right?

I've retried with the 1m baudrate hex file now, and am still encountering the same issue unfortunately. I'm going to try building pc_ble_driver from scratch and see if that changes anything.

RE: pc-ble-driver-py failure with Queue.Empty

Jørgen Holmefjord — Thu, 11 Jan 2018 16:40:39 GMT

Hi,

Have you tried with the 1M baudrate connectivity HEX-file? This is the default baudrate used by the driver.
The purpose of the pc-ble-driver is to provide a softdevice serialization library for use on the computer. The devkit will be used as a "BLE adapter" for the PC, that allows you to connect to external devices. The BLE API in PC's have only recently allowed you to create native PC applications that can talk to BLE devices.
You can find instructions for how to build the connectivity fimware on this page. Only HCI is supported as transport layer.

Best regards,

Jørgen