HC-06 Bluetooth Telemetry Works on Android QGC but Not on Mission Planner (Windows 11)

ArduCopter Copter 4.6
1

I have a microAIR AIO flight controller with an HC-06 Bluetooth module connected as a telemetry radio. When paired with my Android phone, the HC-06 connects to QGroundControl (QGC) perfectly.

However, when paired with my Windows 11 laptop, the system maps two COM ports: COM15 and COM16. I have tried connecting in Mission Planner using both ports at baud rates 115200 and 57600, but it fails to connect every time.

Strangely, I can connect successfully using the MicroConfigurator GCS. In MicroConfigurator, the HC-06 appears as a direct selectable device, and connecting via that works fine—but selecting COM15 or COM16 in the same software also fails.

This is the first time I’ve encountered this issue. I previously used this same aircraft and HC-06 module with another laptop and could connect via Mission Planner without problems. I believe the communication between the HC-06 and the flight controller is fine, but I can’t figure out why Mission Planner won’t connect.

Has anyone else run into this issue?

image
image1920Ă—1088 90.8 KB

image
image1920Ă—1076 220 KB
s

2

windows makes a pair of com port so it works differently ig, i also had hc05 for this purpose and it did not work. with bluetooth device it directly gets the uart stream so it works. what i did was took another hc05/hc06 and made it station mode with ftdi board and then used it with mission planner, and it worked but very short range it is.

3

What I did was throw all the BT radios in the junk drawer and used Wifi radios instead :slight_smile:

4

other options @xingxing that you could explore:

SiK radios - little expensive but best
ESP8266/ESP32 - As mentioned by @dkemxr
HC12 - cheap 433mhz radio that is probably better than that hc06, but has limited bandwith but can get 200-300m range, but some users, like @hossam_2025 had issues with it.

5

:sob: :sob:

@dkemxr @xingxing am try hc-12 by mission planner with work by esp32 s3 fc and it not connect

the @Ishitbh has this one

image
image225Ă—225 70.9 KB

me has this one

image
image225Ă—225 28.5 KB

it test with same as me with esp as fc and it work but my version not

@xingxing i suggest edut the discussion forum to ground control you will can get more support or suggestion from users

6

I use these

ESP-01S
ESP-01S192Ă—131 18.1 KB

7

I think you need to check what baudrate the HC06 is set to, they are usually set to 9600 out the box. set the flight controller serial port to 9600 and connect with mission planner at 9600 and it will probably work. you need to give AT commands over serial to change the baud rate of the HC06.

8

I tried using 9600 in MP, but it still didn’t work.

9

The advantage of using Bluetooth is that the computer can still connect to the Internet, allowing you to adjust parameters while looking up information.

10

Then you could do one of the following:

  1. Use another hc06 with ftdi as reciever
  2. Use hc12
  3. Write python script to map the two com ports to an tcp localhost port. You could try but might or might not work.
11

connect a usb serial to the bluetooth adapter than connect a terminal program to both the serial and bluetooth, change the baud rate until you can type data from one to the other.

12

@geofrancis, @xingxing has already successfully connected to QGC and even mission planner on another device, so I think its unlikely that he doesnt know the correct baud, but he could verify it using AT Mode by pressing the onboard button.

1 Like
13

The hc06 doesn’t come at 57600, so unless he has changed it I don’t see how it could connect at that unless the other program was doing some kind of auto baud and it just looked like 57600.

Another option is that it’s just windows doing windows stuff. Can you connect to the Bluetooth serial with a regular terminal program?

14

Most these modules come with 9600 baud so it is also possible that he changed baud in the fc configuration but 9600 baud would be little flaky for mavlink.

15

I think I changed the baud rate of this Bluetooth module before. It couldn’t connect when the module was brand new out of the factory. This device used to connect fine on my old computer, but after I got a new one and didn’t use it for a long time, I found it can’t connect anymore.