Can't connect to flight controller

I shut down last night everything was running well. Today, I cannot connect via Mission Planner nor via the TX16S controller.

Mission Planner does not show a Com 8 but Windows (11) does.

Powering up the flight controller if I move it, the servos react. Motors beep when power is connected but do not arm (have a switch set) or via moving the rudder stick.

Any ideas appreciated. Thanks.

Show our complete setup.
List all hardware and software components. What was the last thing you did when everything was working?

Spun motors on ports 7,8 & 9

Activated servos

Heewing FX-405 Flight Controller

Heewing FX-405 PMU

Flysky FS-IA10B receiver

Beitian BE-250Q GPS

MG90S Micro servo (2)

40 amp esc

GForce E400 2212 1400kv 4s

Cannot connect to Mission Planner (no com 8)

Moving FC activates servos

Motors will not arm

What shows Windows on the com port?
Which Firmware you are using?
You are sitting in front of your system, others can only know what you are writing

2 Likes

Using Ardupilot 4.3.7 which I believe is a custom firmware

I don’t know about custom, there is the latest Stable version of Arduplane in the repository for that flight controller.
In device manager it should probably say Ardupilot (COMx)

Is this screenshot with connected FC to PC?
Is it changing when connect or disconnect the FC?
Are there some other devices connetcted to the PC via Comports?

Is the firmware the origanally delivered FW with this FC or did you changed it in the past?

Firmware came installed on the FC. I have not changed anything on the firmware versioning.

The device manager screenshot is with the device plugged into the computer. Obviously, no connection exists. Another image for this issue from Mission Planner. No COM(X)

Manually added COM8 to Windows. Still it does not show up in Mission Planner.

This happens often on both Mac and Win machines, even if you use a USB cable and not Wifi or Bluetooth. It usually fixes itself for me by rebooting the machine (shut down and then restart). Also reboot the FC, disconnect USB wire, remove battery. Plug things FC and USB wire in again after your machine has booted up.
Doesn’t hurt to try.

1 Like

When power is applied, could you explain the status of the FC or GPS?
It would be even better if there are photos.

GPS continues to function and is recording in Mission Planner. Flight Controller never connects. Originally COM8 (ARDUPILOT) but no longer able to select COM8 from the Mission Planner and no COM8 in device manager.

What happens on Device Manager if you unplug the FC?
What happens on Device Manager when you again plugin your FC?
What are the devices shown in the Device Manger, do you identified all of them?
How you know that GPS is recording to Mission Planner?

It’s all greyed out so it’s not connected, try other cable.
Install windows lsusb replacement like https://usbdeview.com/ and check what happens when you connect the cable, do it appear anywhere?

Removing / replugging the FC makes no difference.

The GPS is showing up in Mission Planner, even showing a view of my home.

All other devices in device manager known.

Also ran same on 3 separate Windows computers and 1 Linux (Ubuntu) desktop with same results. I am convinced the issue is with the instance or Ardupilot in the FC. No way to flash that I know of if a computer cannot access the FC.

All I got from that site was a bunch of spam wanting me to install a bunch of stuff I didn’t need or want.

Have you tried QGC? Long shot, but a couple of times it’s installed the driver or whatever missing bit I’ve needed to connect new hardware.

Thanks for the thoughts. Could not get a connection to the FC. It does not show up under device manager or Ardupilot/QGC.

I still believe the Ardupilot image on the FC got corrupted and I cannot find a way in. Hoping Heewing will reflash it for me otherwise I’m not sure what to do.