Re: BT Stack under WM2005
- From: "Peter Foot [MVP]" <feedback@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 14 Nov 2006 08:50:03 -0000
Under WM5.0 (with the Microsoft stack) once you have paired a device you can view it's properties in Settings > Connections > Bluetooth and view the properties, if you check Serial Port and save you can then go to the COM Ports tab of the Bluetooth settings applet and map an outgoing COM port to your device. This is slightly more flexible than the BtObSerial.dll approach on older devices because you can often have more than one incoming and one outgoing port. I don't think you should be using the GPS control panel in this case, make sure this is not set to use the hardware port you have just set up.
Peter
--
Peter Foot
Device Application Development MVP
www.peterfoot.net | www.inthehand.com
"eos" <eos@xxxxxxxxxxx> wrote in message news:esz68V0BHHA.4928@xxxxxxxxxxxxxxxxxxxxxxx
Hello Peter,
thank you very much for your fast response!
I'd better tell my story from the very beginning just to make clear what I really need.
I'm using a nice and cute device called Picoplug which is capable of transmuting serial and parallel signals into BT based communication data. It's working just fine apart from a very strange problem I'm currently experiencing with this setup and my WM5 enabled PDA:
The very first connection I establish (after having paired both devices) seems to be running quite stable in most cases. Although there's always one preliminary step I have to take prior to engaging this kind of communication: I've either got to use the built-in GPS manager, which is unfortunately hidden under WM5 by default in order to map COM ports to the incoming data from Picoplug. Or I need to create a new folder under HKLM\Drivers\Active with a string entry called Name filling it with something like "COM8:". Only then it is possible to access this port from some other programme.
However, this doesn't seem to help me very much. Every time I restart a programme which is attempting to communicate with the Picoplug, connection gets established but only to break down a few seconds later.
That's why I'm seriously suspecting some kind of an incompatibility or a bug within the WM5 BT stack.
There is even another observation I made to endorse this theory. I simply took another device to test my setup against it. This time it was a similar PDA based on WM2003. Well, I almost don't need to tell you, it was a completely different experience. Everything worked just fine as it was supposed to be from the start. Under no circumstance could I reproduce the same error on this device.
Then I started analysing WM2003 comparing it to the respective items on WM5. What I've found out is the fact that WM2003 handles my connection attempts in a completely different way. First of all, there is an own device driver to serve such requests under WM2003. It is called BTOBSerial.Dll. Working with it is absolutely comfortable since I only need to pair the devices once. BTOBSerial.Dll then takes care of every single aspect of the established connection. It even creates a new COM port for me. This port can then be found by every programme. From this point on everything works absolutely fine.
Under WM5 there doesn't seem to be anything comparable to this driver. This is so annoying! I keep asking myself why an older WM version has got such a feature working out-of-the-box while WM5 is complete rubbish with respect to this special issue?
So, this is my actual trouble. That's why I've asked for help and advice. Have you ever been faced with this problem? Is there an effectual remedy you know about?
By the way, I've heared about the new upcoming WM5 Second Edition. Can you tell if it's possible to upgrade older devices with this version?
Thank you very much in advance for your help and time!
Best regards,
Witali
"Peter Foot [MVP]" <feedback@xxxxxxxxxxxxxxxxxxxx> schrieb im Newsbeitrag news:8FDFE65A-C884-4D96-BCB9-5A0E9C43D59C@xxxxxxxxxxxxxxxxIt depends what you mean by re-initialise, you can turn the Radio off and on again with BtSetMode. Some of the settings are stored in the registry, there are a number of APIs available to set some properties - these are not documented in WM5.0 SDK, you'll need to refer to the Windows CE 5.0 documentation on MSDN.
Replacing the stack is generally not possible (certainly not legal to pull widcomm files off another device for example), you get whatever the OEM has built into the ROM image.
You haven't specified whether you are using .NET or native code, but either way you may find http://32feet.net useful. The source for the project will show you the BT functions and examples of their use - if you are a .NET developer you can use the library and save a lot of time.
Peter
--
Peter Foot
Device Application Development MVP
www.peterfoot.net | www.inthehand.com
"eos" <eos@xxxxxxxxxxx> wrote in message news:uXFurWvBHHA.3560@xxxxxxxxxxxxxxxxxxxxxxxHello there!
I'm wondering if there's a nice way to quickly reinitialise the BT Stack under WM2005 programmatically?
Is it actually possible to read and write any BT related system properties? Is there any chance of replacing WM's current stack by some other?
Does someone have a code snippet to share with me?
Thank you all in advance!
.
- Follow-Ups:
- Re: BT Stack under WM2005
- From: eos
- Re: BT Stack under WM2005
- References:
- BT Stack under WM2005
- From: eos
- Re: BT Stack under WM2005
- From: Peter Foot [MVP]
- Re: BT Stack under WM2005
- From: eos
- BT Stack under WM2005
- Prev by Date: Email lose????
- Next by Date: Re: ADS
- Previous by thread: Re: BT Stack under WM2005
- Next by thread: Re: BT Stack under WM2005
- Index(es):
Relevant Pages
|
