Csr Csr8510 A10 Bluetooth Dongle 5.0 Original Cd Drivers Setup
Rosham Rosebure
However. When I pair them with my laptop using an Avantree bluetooth dongle, with generic Windows drivers as per manufacturer recommendation, I get stuttering and bad quality sound. Also, the media controls (back/forward) don't work except for pause. (I also have onboard Bluetooth on the wireless card which I disable). This is true for another CSR dongle as well.
csr csr8510 a10 bluetooth dongle 5.0 original cd drivers setup
Download File ○ https://shurll.com/2zw9JB
I have scoured the internet from end to end. I've tried reinstalling/uninstalling/turning off bluetooth, sound and wireless drivers. I've turned handfree telephony/audio enhancements on and off in every possible way known to humanity.
Now media controls. The default Windows 10 drivers don't work, either with the dongles or onboard bluetooth. Only by using an old driver for one of the dongles (there is no Windows 10 driver for the other), can I get the media controls to work. I would prefer not to have to use a bulky, outdated software/driver package if Windows can be made to work.
It appears that the problem was a USB hub I have on my laptop. Apparently, some USB 3.0 devices can cause interference. Plugging it in would result in stuttering some of the time, but not when unplugged. Moving the dongle to the other side of the laptop, away from the USB hub, appears to have fixed the stuttering.
This document exists to help users make decisions as to which usb devices to purchase to extend their NI Linux RT hardware. This list should be updated by the community and refreshed as kernel changes occur. NI makes no guarantee that a specifc usb device will work. There is no substitution for actual engineering and investigation.
National Instruments is not responsible for the information in this list. Claims that these devices will work out of the box should be considered speculative. Please look at the provided links to ensure that the devices work in the way you expect them to. This list is merely for convenience and organization purposes.
Realistically speaking, it depends somewhat on what you want to do with the module. You can put together as simple or as complex a framework to scan, connect, and interact with hardware as you want in any language supported on the controller that supports interacting with bluetooth.
This can be bash-scripting or python coding accessed through the System Exec.vi through to a library written in C/C++ and accessed through the Call Library Function Node. Depending on the interface provided by the bluetooth interface libraries, you may be able to install and interact with the libraries directly from LabVIEW CLFNs.
Can you expand on what you mean when you say "We are looking for a bluetooth device which has [...] compatability with Linux RT"? How do you intend on using the BT device, from LabVIEW (the Bluetooth palette is not available on LabVIEW RT targets), or from the actual Linux OS itself (scripts/code separate from LabVIEW)?
In either case, the version of the OS on your hardware also has a bearing since Bluetooth support in the kernel was only enabled in 2016 kernels (comes with LabVIEW RT 2016 or RIO 2016 installations), before that the needed protocol bits in the kernel were missing and you'd have to manually create BT packets in userspace and pass them directly to a raw USB device.
Finally, now that I've filled in some background let's return to your original question. I am unaware if anyone has tested or successfully use a Cirago BT device with NI devices. It should work but has not been tested to my knowledge.
I have tested several CSR8510 based USB BT 4.0 dongles and can make them work correctly at the OS / utility level. We don't have a nice (NI Labs) LV API that Windows 10 has though, and there's a few barriers that you will encounter. I'll follow up with direct message. At this point we're still trying to figure out how customers would like to use Bluetooth Low Energy, and what problems they are trying to solve.
I have been trying to pair the puck with my laptop. Though I can see the puck in the list of devices the pairing always fails with the message : "Connection failed becuase an incorrect code was entered"
Hi
I have just received a puck.js and am running windows 10.
I have not seen the "Connection failed becuase an incorrect code was entered" myself.
You downloaded the Web IDE and are using it locally?
What is the exact type of dongle?
For some reason I dont see the puck on the list of devices in the "Manage Bluetooth devices" window, like the one you show above. I can however, see it in CSR bluetooth device list. I'll post some pics later, unless you have already an idea why I cant see it on my "Manage Bluetooth devices" windows.
As you're using an external CSR dongle you might need to try and get some Windows 10 drivers for it? It's possible that if you installed older driver/software the CSR tools don't make it available using the Windows 10 APIs.
I am not too sure if the reference Gordon made to the Windows instructions is to what I tried:
ie. I tried to use Zadig installed river with the native app: did not work for me with my Intel Bluetooth adapter
ie I would say remove all extra CSR tools and remove the driver (delete driver) and install adapter and make sure the Windows 10 finds the driver (basically what Gordon was stateing in part of his reply)
If necessary supply the inf files by reference to any driver disk that is available from CSR
If you can find some Windows 10 compatible drivers for the CSR dongle, that would be ideal as it'd mean that when Web Bluetooth finally makes its way into Chrome, it'd work for you fine. However it might be that your computer already has built-in non-BLE Bluetooth, and that's what Windows is using instead of your CSR adaptor. I guess you may have to disable the built-in bluetooth adaptor to make it work.
If you don't want to mess with your internal Bluetooth then I'd suggest my original instructions. @OwenBrotherwood they may not work with your Intel card, but the Zadig instructions should definitely work with @Icarus's external CSR Bluetooth dongle.
@OwenBrotherwood if you're willing to mess around with the internal of the noble library, there are a bunch of USB PID/VIDs in there - you might find that by adding your Intel adaptor into that list you can make it work - if so it'd make a good pull request for Noble
e59dfda104