Re: Bluetooth connectivity problems, using Microsoft API

Same advice as in the other NG :)
How about using sockets, not serial port emulation?

--PA


Pelle wrote:
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.


.

Relevant Pages

  • Re: Bluetooth connectivity problems, using Microsoft API
    ... we are currently in the process of developing a bluetooth interface ... In the process of testing and understanding the bluetooth technology ... I have no chance to find out if I can reconnect to the ... there's a significant chance of the virtual COM-port ...
    (microsoft.public.win32.programmer.networks)
  • Bluetooth connectivity problems, using Microsoft API
    ... we are currently in the process of developing a bluetooth interface ... In the process of testing and understanding the bluetooth technology ... I have no chance to find out if I can reconnect to the ... there's a significant chance of the virtual COM-port ...
    (microsoft.public.win32.programmer.networks)
  • Re: Implementing Multi-Interface USB Device Driver
    ... We had already developed bluetooth stack excetp USB. ... I heard USB driver is common, only we need to develop the driver with the above Interface information. ... Once an alternate setting is desired, first terminate all transactions on endpoints that correspond to that changing interface alternate setting. ... > Please do not send e-mail directly to this alias. ...
    (microsoft.public.development.device.drivers)
  • Bluetooth development chips
    ... USB adaptor). ... disposal which will provide me with a serial - bluetooth interface? ... Since I plan to interface the chip with a microcontroller, ... So which chips would allow me a bluetooth - I2C or SPI or Serial or USB ...
    (comp.arch.embedded)
  • Re: Smart Paper & TrafPol tickets
    ... > Not being transmitted via a custom version of Bluetooth called Brunsteeth, by any chance? ...
    (uk.rec.motorcycles)
Loading