1. Broadcom Bluetooth SDK/API and Winsock
I wrote this Bluetooth application using Microsoft's Winsock interface
which works perfectly - but only on "Microsoft compatible
dongles" (i.e. that use Microsoft's Bluetooth stack).
If I attempt to use it on a PC with Broadcom/Widcomm Bluetooth stack,
I get a return code of 10108 when it calls WSALookupServiceBegin()
which maps to WSASERVICE_NOT_FOUND.
Quick newsgroup search revealed that - duh! - Microsoft's Winsock
interface works only with Microsoft drivers ("stack"). If I want my
application to work with Broadcom's stack/dongles I need to use
Broadcom's SDK.
"Not a problem", I though, and downloaded the SDK from Broadcom's
site.
But... initial reading suggests that I cannot use sockets to access
available serial ports that are provided by the remote device.
Is this true? Am I forced to use lower level API calls to communicate
with the Bluetooth device>
After being spoiled with the simplicity and east of using Microsoft's
Winsock API for Bluetooth, it seems almost cruel to re-write
everything using Broadcom's interface.
I hope that my understanding is incorrect and that there is a way to
use some sort of socket communication to access serial ports provided
by the Broadcom stack. However, I am relatively a newbie on the
Bluetooth front and I must rely on some guidance from more experienced
folks here.
Any help you can provide would be highly appreciated.
Thanks,
John
2. Bluetooth SDK compatible with WIDCOMM stack . - Pocket PC
3. WIDCOMM Bluetooth SDK and PocketPC 2003
Hi all, I have purchased WIDCOMM SDK and currently develop Bluetooth-enabled application for PocketPC platform. PocketPC 2003 has built-in Bluetooth stack. Will my code work without changes under PocketPC 2003?
4. Need Help with Bluetooth SDK - Pocketpc Developer
5. Need Bluetooth SDK and CF that supports PPC2000,PPC2002,PPC2003 & CE.NET
Hi, I've been searching for almost 2 months after a Bluetooth SDK and CF card that supports multiple Pocketpc (at least 2000,2002,2003 and preferrably also .NET). But most only supprt 2000 & 2002 and lockes up devices with PPC2003 or don't support the xscale cpu 100%. I have and old socketcom SDK and CF cards but they no longer support their SDK for newer OS or CPU's. Most imported for the application is creating a client serial port to connect to a device or being a serial port service for connecting the PC. The deadline is comming closer and closer and I'm stuck at base. Could somebody point me to a working SDK and CF combination? Regards TheLaery
6. BTAccess bluetooth SDK available for WM5
7. 2 Questions about Bluetooth API that comes with the platform SDK
I've been searching for answers on these topics for a few hours now, but have not been able to find anything. First Question: Using the Bluetooth API's that come with the platform sdk in conjunction with the windows socket library, I have made my PC establish a connection to a remote bluetooth device. Since the PC initiates the connection, it is the Bluetooth master, while the remote device is the slave. Is there anyway for the PC to switch this around, so that the remote device is the master, and the PC is the slave? E.g. is there something in the Bluetooth APIs that will allow me to do this? I would like to be able to do this without breaking the connection. Second Question: I have noticed that when I call closesocket on the bluetooth socket, the ACL connection will hang around for about 30 seconds and then it finally closes. Is there anyway to also force the ACL connection to close too? Thanks in advance, RS