• 0

Bluetooth Programming [C]


Question

#include <stdlib.h>
#include <stdio.h>
#include <Winsock2.h>
#include <Ws2bth.h>
#include <BluetoothAPIs.h>
#include <windows.h>

void ErrorExit(LPTSTR lpszFunction);

int main(void)
{
	BLUETOOTH_FIND_RADIO_PARAMS FirstRadio;
	HANDLE RadioHandle;
	HANDLE NextRadio;
	BOOL FoundNextRadioHandle;
	BLUETOOTH_RADIO_INFO RadioDeviceInfo;
	DWORD dw;

	BluetoothFindFirstRadio((BLUETOOTH_FIND_RADIO_PARAMS*)&FirstRadio,(HANDLE*)&RadioHandle);
	if(RadioHandle == NULL)
	{
  printf("Problems Creating Radio Handle");
	}

	FoundNextRadioHandle = BluetoothFindNextRadio((HANDLE*)&RadioHandle,(HANDLE*)&NextRadio);

	if(FoundNextRadioHandle == TRUE)
	{
  printf("Found Another Bluetooth Radio");
	}
	else
	{
  printf("Only One Bluetooth Radio Handle Present\n");
  
	}
  
	BluetoothGetRadioInfo(RadioHandle,(BLUETOOTH_RADIO_INFO*)&RadioDeviceInfo);
	dw = GetLastError();
	ErrorExit((LPTSTR)&dw);

	HBLUETOOTH_DEVICE_FIND DeviceHandle;
	BLUETOOTH_DEVICE_INFO DeviceInfo;
	BLUETOOTH_DEVICE_SEARCH_PARAMS SearchParams;

	BOOL FoundDevice; /*Return Value of FindNextDevice*/
	BLUETOOTH_DEVICE_INFO FoundDeviceInfo; /*Structure Containing Info of next Device*/

	SearchParams.dwSize = sizeof(BLUETOOTH_DEVICE_SEARCH_PARAMS);
	SearchParams.fReturnAuthenticated = TRUE;
	SearchParams.fReturnRemembered = TRUE;
	SearchParams.fReturnUnknown = TRUE;
	SearchParams.fReturnConnected = TRUE;
	SearchParams.fIssueInquiry = TRUE;
	SearchParams.cTimeoutMultiplier = 10;
	SearchParams.hRadio = RadioHandle;

	BluetoothFindFirstDevice((BLUETOOTH_DEVICE_SEARCH_PARAMS*)&SearchParams,(BLUETOOTH_DEVICE_INFO*)&DeviceInfo);
	dw = GetLastError();
	ErrorExit((LPTSTR)&dw);

	FoundDevice = BluetoothFindNextDevice((HBLUETOOTH_DEVICE_FIND*)&DeviceHandle,(BLUETOOTH_DEVICE_INFO*) &FoundDeviceInfo);
	dw = GetLastError();
	ErrorExit((LPTSTR)&dw);

	return 0;
}

void ErrorExit(LPTSTR lpszFunction) 
{ 
    TCHAR szBuf[80]; 
    LPVOID lpMsgBuf;
    DWORD dw = GetLastError(); 

    FormatMessage(
        FORMAT_MESSAGE_ALLOCATE_BUFFER | 
        FORMAT_MESSAGE_FROM_SYSTEM,
        NULL,
        dw,
        MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT),
        (LPTSTR) &lpMsgBuf,
        0, NULL );

    wsprintf(szBuf, 
        "%s failed with error %d: %s", 
        lpszFunction, dw, lpMsgBuf); 

    MessageBox(NULL, szBuf, "Error", MB_OK); 

    LocalFree(lpMsgBuf);
    ExitProcess(dw); 
}

Hi, Please could someone tell me why this program isnt working. It keeps comming up with the error :

  Quote
Error 126 : The specified module could not be found.

It needs the platform SDK installed for the bluetooth headers and such. It also doesnt find the local bluetooth dongle or my phone which is what it is intended to do.

Thanks in Advance.

Sawyer12 :)

Link to comment
https://www.neowin.net/forum/topic/275426-bluetooth-programming-c/
Share on other sites

13 answers to this question

Recommended Posts

  • 0

If a function succeeds, it is not required to set the last error to 0. You have to check what success means for each function. For example, BluetoothFindFirstDevice is supposed to return a valid handle and fails on NULL - you should check this first. If you have a NULL handle, then call GetLastError.

  • 0
  Sawyer12 said:
Can anyone tell me the difference between the functions :

BluetoothFindFirstDevice and  BluetoothFindFirstRadio ?

Which should I call first, Im basically trying to get my program to find my bluetooth phone. Any ideas?

585348297[/snapback]

I tried the code on 2 dev machines:

Machine 1: Mitsumi Bluetooth Adapter - Got an Error 126

Machine 2: Microsoft Bluetooth Keyboard/Mouse Adapter - Worked no problem

I guess it could be a driver issue.

BluetoothFindfirstDevice, this would find a device like phone, pda, keyboard etc.

BluetoothFindFirstRadio, this would find the actual bluetooth adapter.

  • 0

If you only have the 1 bluetooth adapter installed then you can have the line

 SearchParams.hRadio = NULL;

Then you can delete all the code that deals with BluetoothFindFirstRadio().

But like I said, 1 adapter worked for me, the other didn't... If you are still getting the same error it might be the adapter/api conflict.

  • 0

Here is the code that worked for me

#include "bthdef.h"
#include "BluetoothAPIs.h"
#pragma comment(lib, "irprops.lib")

	BLUETOOTH_DEVICE_SEARCH_PARAMS bdsp;
	BLUETOOTH_DEVICE_INFO bdi;
	HBLUETOOTH_DEVICE_FIND hbf;

	ZeroMemory(&bdsp, sizeof(BLUETOOTH_DEVICE_SEARCH_PARAMS));

	bdsp.dwSize = sizeof(BLUETOOTH_DEVICE_SEARCH_PARAMS);
	bdsp.fReturnAuthenticated = TRUE;
	bdsp.fReturnRemembered = TRUE;
	bdsp.fReturnUnknown = TRUE;
	bdsp.fReturnConnected = TRUE;
	bdsp.fIssueInquiry = TRUE;
	bdsp.cTimeoutMultiplier = 10;
	bdsp.hRadio = NULL;

	bdi.dwSize = sizeof(bdi);

	hbf = BluetoothFindFirstDevice(&bdsp, &bdi);
	DWORD dwErr = GetLastError();

	if (hbf != NULL)
	{
  TCHAR szDevName[MAX_PATH];

  while(1)
  {
  	memset(szDevName, 0x00, sizeof(szDevName));
  	sprintf(szDevName, _T("Name:%S"), bdi.szName);
  	MessageBox(szDevName, _T("Bluetooth Info"));

  	if (BluetoothFindNextDevice(hbf, &bdi) == FALSE)
    break;
  }

  BluetoothFindDeviceClose(hbf);
	}
	else
	{
  //No Devices Found...
	}

  • 0

I think that the Microsoft Bluetoothxxx() API functions are only to enumerate, bond, select & get info of bluetooth devices in the area. You may have to use the Winsock functions to actually communicate to the bluetooth device.

I only do WindowsCE programming, and the MS Bluetooth API functions are very different, eg. once you have bonded/selected a device it usually appears as a COM Port, then it is a simple matter of opening/closing/read/write to that port. On WIn32, I don't know.

Some devices like PDA's use OBEX to transfer files, maybe that could be used, maybe not !!!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.1.4 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.1.4 changelog: Intel: Added NPU presence detection before removing shared DLL files (these were previously left to prevent potential NPU-related issues). Intel: Added optional NPU removal Improved "Extension" driver removal process. Updated several translations. Download: Display Driver Uninstaller 18.1.1.4 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot | Forum Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • That is what I also think to a point. How is 26 necessarily different than just another iteration like 18, 19, 20, etc? At first I think it would be better for Apple to use 2026, 2027, and then maybe truncate it to just 28, 29, and so on. Granted, I also think it makes more sense to use the year when it was released (2025 or 25), not 26/2026. Maybe Apple's thinking is as stated by Aditya that the bulk of a release being the current release is during the following year (2026, for example) after it is released (2025, for example). There are other examples of these sorts of things. In the NBA, the season has always started in the Fall and ends in the Spring. When the season ends is how the season is named. So, this is the 2025 NBA season and the Pacers and Thunder are playing to be the 2025 NBA Champions. The NFL starts in the Fall and the end of the season is always in the beginning of the next year as well. The Super Bowl was played on February 9, 2025, but that was the end of the 2024 NFL season. So, contrary to the NBA, the NFL names it season based on when it starts, not when it ends. Maybe that is because more of the NFL season is played at the end of the year (2024 in the most recent example) whereas most of the NBA season is played in the first half of the following year (2025 in the current example).
    • Years ago I was at COMDEX in Las Vegas and a pit boss told me all the casino hotel staff said of the geeks "They bring one clean shirt and a $10 bill and they don't change either one all week..."
    • I really hate Capcom for cutting all that content on RE3 Remake. It could have been a masterpiece like 2 Remake was.
    • Yes. Wouldn't want to confuse anyone from 1926 or 3026 who might look at it.
  • Recent Achievements

    • Week One Done
      abortretryfail earned a badge
      Week One Done
    • First Post
      Mr bot earned a badge
      First Post
    • First Post
      Bkl211 earned a badge
      First Post
    • One Year In
      Mido gaber earned a badge
      One Year In
    • One Year In
      Vladimir Migunov earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      snowy owl
      252
    3. 3
      +FloatingFatMan
      251
    4. 4
      ATLien_0
      228
    5. 5
      +Edouard
      191
  • Tell a friend

    Love Neowin? Tell a friend!