Re: Bluetooth connectivity problems, using Microsoft API
- From: "Farooque Khan" <farooque.khan[AT]gmail[DOT]com>
- Date: Tue, 5 Aug 2008 17:49:25 +0530
I am not sure I understand your problem completely, so this may be way off.
But can't you just set the timeout on the Com port using SetCommTimeouts() ?
--
Farooque Khan
Project Manager
Infospectrum India Pvt. Ltd.
farooque@xxxxxxxxxxxxxxxxx
Phone: +91 712 229 3711
www.info-spectrum.com
This e-mail may contain confidential or proprietary information. If you are
not the intended recipient please notify the author by replying to this
e-mail and please note that use, disclosure, distribution, copying or
printing of this e-mail or its attachments is strictly prohibited and may be
unlawful. Whilst this e-mail has been checked for viruses, the sender takes
no responsibility and recipients are advised to undertake their own checks.
"Pelle" <pelle1911@xxxxxx> wrote in message
news:dfaa7f8b-11f0-41c3-9821-6fb1b774b7ec@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello all,
I've been told it's a good idea to ask this question in this forum.
Any help highly appreciated!
Thanks in advance,
Pelle.
Hello all,
we are currently in the process of developing a bluetooth interface
for one of our measurement devices including a PC software (Windows)
to access this interface.
In the process of testing and understanding the bluetooth technology
in connection with the Microsoft interface, we have run into a major
problem.
It is a common action for a bluetooth device to leave the bluetooth
send/receive range and become unavailable.
However, since Microsoft remembers the device, the associated virtual
COM-port remains available.
While using the virtual COM-port I can't access any information on
the
device outside the current communication, as for example signal
strength or simply the availability of the device. Once the device
becomes unavailable, the communication starts to hang and I have no
chance of realising this.
Even worse, I have no chance to find out if I can reconnect to the
device or not. If I try to reconnect and especially if I do so
multiple times, there's a significant chance of the virtual COM-port
to get stuck at the connection-attempt which would block me out of my
device until I reboot the machine.
Having the customer to reboot the machine upon disconnection seems
slightly ridiculous.
I hope there's a better answer to this seemingly common problem.
Looking forward to any further information,
thanks in advance,
regards,
Carsten Palleske.
.
- References:
- Prev by Date: Re: Bluetooth connectivity problems, using Microsoft API
- Next by Date: Vista home premium network password issue
- Previous by thread: Re: Bluetooth connectivity problems, using Microsoft API
- Next by thread: Vista home premium network password issue
- Index(es):
Relevant Pages
|
