1

Here's the setup: I have two bluetooth devices paired with a single PC. Both are SPP, intended to be used with separate virtual COM ports. One device is assigned COM9, the other is assigned COM11. If I open the COM9 port, it 'sees' the data from the COM11-paired device, even though I didn't open the COM11 port.

It looks as if any data from a paired device, regardless of which COM port it is paired with, will be received on whatever COM port has been opened. I would have expected that data from the device paired with COM9 would only be received if I opened the COM9 virtual port, etc.

Can anyone tell me why the paired ports aren't behaving uniquely? Any way to force them to be unique?

pnuts
  • 58,317
  • 11
  • 87
  • 139
Norm Bernstein
  • 11
  • 1
  • 2
  • Is the PC/Bluetooth Dongle just using the standard Microsoft Bluetooth stack or is it using Widcomm/Broadcom, BlueSOleil, etc? – alanjmcf Nov 04 '10 at 14:21
  • even am experiencing the same issue as mentioned above .any solutions so far ? – HRG Feb 17 '16 at 09:45

2 Answers2

1

I have observed a similar behaviour on Windows 7 and Windows 8. I have paired two SPP Bluetooth devices. Thus Windows has created four virtual COM ports: one incoming and one outgoing for each device. I then opened the two incoming ports. Nevertheless, I could not connect both devices simultaneously. The first one gets connected to whatever incoming port and the second one cannot connect as long as the first is connected. It looks as if Windows can accept only one incoming connection, on whatever incoming virtual COM port.

cfoucher
  • 11
  • 3
1

typically I have seen 2 com ports (incoming and outgoing) that gets assigned to a single device, are you sure com 9 and 11 in your care are not the incoming and outgoing port to the same device ?

Dennis Mathews
  • 6,897
  • 2
  • 26
  • 39
  • You're right, each device is assigned both an incoming and outgoing COM port. One device is assigned COM8 outgoing, COM9 incoming, and the other device is assigned COM10 outgoing, and COM11 incoming... since our device initiates data transfer, we only use the incoming port assignment. – Norm Bernstein Nov 05 '10 at 15:24
  • Also, this is working with the standard Microsoft Bluetooth stack.... all other stacks are removed, or were not installed. When we open a port on the PC in anticipation of communications, we specify which port (and presumably, which device) we want to communicate with.... yet, when we operate the device assigned to the non-opened port, it responds on the opened port. – Norm Bernstein Nov 05 '10 at 15:27
  • I get the feeling that, for some reason, the Microsoft Bluetooth stack is not maintaining separate queues for each defined virtual COM port... any ideas? – Norm Bernstein Nov 05 '10 at 15:27