Programmatically Add and Remove Bluetooth Devices

[sarp]

I created a program to test a Bluetooth enabled product.  The program will be used to test hundreds of these devices one after another.  Each time I connect a new device using the LabVIEW Bluetooth functions, Windows asks the user if it is OK to allow the device to connect.  Is there a way to tell Windows to accept all new connections without requiring any action from the user?

Since there will be thousands of these devices tested over the course of a few years, I would like to somehow have LabVIEW remove each device from the Devices and Printers list in Windows but I cannot find a way to do it.  It has been suggested that I use ActiveX or the command prompt but I haven't been able to figure out exactly how to do it.  Any help would be appreciated.  Thanks so much.

I'm using Windows 7 and LabVIEW 2015 SP1

[tolltroll]

Hi sarp,

Do you have a VI, or at least a starting point, that you can share? That way we can get a good idea of what your implementation looks like so far, and have a spot from which to make recommendations.

Thanks,

Nick

Applications Engineer

[sarp]

Hello Nick,

Thank you for your response.  My test program requires specific hardware to run so sharing my VIs would not help.  The operation that I want to automate is shown in the attached picture.  The device listed as K1224ADAD is a Bluetooth device that I want to use LabVIEW to remove from this list of devices.  Every unit that is run through my program will add a device to this list and I don't want the user to have to remove each of them manually.  I want to know if there is a way to access the Devices and Printers section of the Windows Control Panel using ActiveX or the command prompt.  Thank you.

[tolltroll]

I'm not sure this is the best forum to figure this part of the problem out. Once you know the command you need to execute in the command prompt or in ActiveX, we can certainly help you implement it in LabVIEW. But to find that particular ActiveX call is something that might be better suited for a Microsoft forum, or somewhere like StackOverflow.

Nick

Applications Engineer