none
What bluetooth service is needed to connect a remote device to a windows 10 virtual port? RRS feed

  • Question

  • Hello, 

    I am doing some bluetooth development where I have a device running a SPP service. However i cannot set up a virtual comport where with the device. Windows discovers the device in the general bluetooth tab but when looking in the browse window in: More bluetooth options -> COM ports -> Add... -> Outgoing -> Browse, I cannot find the device.

    Remote device info:

            Name: BP
            Alias: BP
            Paired: yes
            Trusted: no
            Blocked: no
            Connected: yes
            LegacyPairing: no
            UUID: RFCOMM                    (00000003-0000-1000-8000-00805f9b34fb)
            UUID: Serial Port               (00001101-0000-1000-8000-00805f9b34fb)
            UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
            UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
            RSSI: -43
            TxPower: 8

    What services are required to be able to establish a virtual comport connection with my device? Are there any special requirments on characteristics?

    SPP should be supported according to https://support.microsoft.com/en-us/help/10568/windows-10-supported-bluetooth-profiles

    /Regars Björn


    • Edited by Björn Paulström Tuesday, February 14, 2017 8:49 PM better title
    • Moved by Hart Wang Wednesday, February 15, 2017 2:14 AM
    Tuesday, February 14, 2017 8:40 PM

Answers

  • Hi Bjorn,

    Normally, the virtual com port should be created if the device reported the service during the SDP query that occurred during the pairing of the device.  It should however be noted that the virtual com port is provided more as a legacy access method for the Bluetooth protocol, it is not available in all Windows Universal App products.

    Instead, the rfcomm service can be accessed without the presence of the virtual com port using the following Api family:

    https://docs.microsoft.com/en-us/uwp/api/windows.devices.bluetooth.rfcomm

    Samples are available here:

    https://code.msdn.microsoft.com/windowsapps/Bluetooth-Rfcomm-Chat-afcee559

    Thanks!

    Wednesday, February 15, 2017 1:59 PM

All replies

  • Hi,

    Thank you for posting here.

    Since your issue is related to windows Desktop Development Windows Hardware WDK and Driver Development   

    I will move the case to there.

    Best Regards,

    Hart


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, February 15, 2017 2:13 AM
  • Hi Bjorn,

    Normally, the virtual com port should be created if the device reported the service during the SDP query that occurred during the pairing of the device.  It should however be noted that the virtual com port is provided more as a legacy access method for the Bluetooth protocol, it is not available in all Windows Universal App products.

    Instead, the rfcomm service can be accessed without the presence of the virtual com port using the following Api family:

    https://docs.microsoft.com/en-us/uwp/api/windows.devices.bluetooth.rfcomm

    Samples are available here:

    https://code.msdn.microsoft.com/windowsapps/Bluetooth-Rfcomm-Chat-afcee559

    Thanks!

    Wednesday, February 15, 2017 1:59 PM
  • Thank you for your reply, what I did not know at the time of writing this is that SPP is not supported on BLE devices. I have been trying to migrate to a HOGP service instead, since what I originally wanted to do was send mouse input.
    Friday, February 17, 2017 7:03 PM