Re: We would like to programmatically select Bluetooth device we are communicating with

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Peter Foot [MVP] (feedback_at_nospam-inthehand.com)
Date: 04/12/04


Date: Mon, 12 Apr 2004 22:33:51 +0100

The Bluetooth API required depends on the Bluetooth Stack provided on your
device. The Pocket PC 2003 SDK provides headers and documentation on
Microsoft's own stack for free however this stack is only used on a small
number of devices currently (XDAII and SPV E200 primarily). Other stacks are
available such as WidComm which requires purchase of an SDK from WidComm for
full programmatic access to the stack
(http://www.widcomm.com/Products/bluetooth_comm_software_btce.asp).

Peter

-- 
Peter Foot
Windows Embedded MVP
OpenNETCF.org Senior Advisor
www.inthehand.com | www.opennetcf.org
"Gregor" <Gregor@radioglas.com> wrote in message 
news:OTCP0d$GEHA.528@TK2MSFTNGP09.phx.gbl...
>
>
> We are looking for a solution that would allow us to integrate Bluetooth
> functions into our applications. We are using Intermec terminals running 
> on
> Pocket PC 2003 platform. Terminals have integrated Bluetooth interface +
> drivers. We are also using three other devices upgraded with Bluetooth 
> RS232
> adapters. We have already developed all our applications that communicate
> with those devices. The problem we are having is that we are unable to
> switch between the devices automatically. We would like to 
> programmatically
> select the device we are communicating with. As Serial Port Profile (SPP) 
> is
> used, the Bluetooth Manager is shown every time we open COM port and the 
> end
> user has to manually select the device. This is unacceptable. What we need
> is some
> method (using API functions or an SDK), where we could select the device
> from our application code with no user intervention. This could be
> accomplished by either selecting which device is targeted by predefined 
> COM
> port, or by assigning each device its own incoming and outgoing port 
> pairs.
> We do know the Bluetooth address and service name beforehand, so no
> discovery is needed.
>
> Thanks Grega
>
> 


Relevant Pages

  • Re: WMDC and Bluetooth, help me....
    ... You can still connect your BT Windows Mobile device to a COM port if needed, ... to get the Toshiba Stack working as it did in Beta 3 of WMDC with Vista ... Bluetooth, can we not select a Com Port. ...
    (microsoft.public.pocketpc.activesync)
  • Re: IPAQs and Bluetooth and Visual Studio 2005 beta 2
    ... Widcomm stack SDK from high-point.com - the full version is a bit expensive ... > Note that if you don't have a device running the Microsoft Bluetooth stack, ... Try searching the Pocket PC newsgroup archives at ...
    (microsoft.public.pocketpc.developer.networking)
  • Re: 6230i Bluetooth problem
    ... Bluetooth is working fine but serial port isn't. ... Windows XP SP2 introduces its own Bluetooth protocol stack. ...
    (uk.telecom.mobile)
  • Re: bluetooth application development
    ... bluetooth stack give the ... possibility to make a BT discovery, pairing and VirtualCOM port attach. ... Once you have made this association (in PocketPC outbound VCOM usually ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: bluetooth application development
    ... Bluetooth stacks and that's the franson product. ... COM port route involves device specific code since the different stacks have ... Point have a wrapper for the Broadcom/Widcomm stack. ... On the pocket pc side, ...
    (microsoft.public.dotnet.framework.compactframework)