My laptop is about 20m from the inverter, and through 3 walls (one at about 20 degree angle to the path between the laptop and inverter, another lined with kitchen cupboards), yet each time I've connected it's had a steady 80% signal. Incidentally, my dongle cost $6.81 delivered (supposedly from Au stock), and is specified as having a 20 to 50m range. So if I want to connect with both the inverter and phone, it seems I'll need another Bluetooth dongle! Though I then tried to pair my phone (as it had been successfully when the CSR drivers were installed) but although it can see the phone, it won't pair. but upon opening Sunny Explorer, it promptly found the inverter and after ensuring the IDnet was correctly set at 1, and using the '0000' password, it successfully connected. After this I could not find the inverter via normal 'search for Bluetooth devices'. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub. Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet. ADAPTERS will not support - see kernel regression bug and Kernel Bug 60824. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub. and it chose to load the Microsoft generic drivers. lsusb listing it as Bus xxx Device yyy: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode). I un-installed the Cambridge Silicon Radio driver software, and with the CSR mini disk still in the laptop, removed and reinstalled the dongle. I managed to get my Bluetooth dongle working. It starts successfully but dont get available devices to pair. Some more info in event you haven't solved your issues. I have a bluetooth dongle Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode). Mine works fine with my phone (Samsung Galaxy S4), but I'd purchased it to connect to my SMA inverter using SMA's 'Sunny Explorer'. rootmaiko-cce-lin: lsusb grep Bluetooth Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) It rarely works, and when I do get it to work it stops working when I reboot. I have found that just upgrading to Kernel 5.13.4 fixes the Fake Bluetooth CSR 0100 issue. I don't know it the correct driver may be found here, but it's a start! I've just performed a basic search and found. If not, try contacting the supplier, who may be able to email you a zipped driver stack, or a link from where you can download it.Īlternatively, try searching the key words (e.g. If yours also came with a disk, I'd un-install the generic driver, and install from the disk. I also recently purchased a similar (or same) device (CSR v4.0 bluetooth dongle), and have a laptop with a Windows7 Home Premium 64bit operating system.Īlthough a 'plug and play', it still required installing the driver software from the mini-disk that came with it, which contained the Cambridge Silicon Radio Ltd. Hi, experts, I have just purchased a new bluetooth v4.0 dongle (brand should be cambridge silicon radio).Īfter I plugged to my labtop (win7 home premium 64bit), windows 7 detects it as generic bluetooth radio.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |