Servers by jDrones

Flight controller not getting recognized when updating firmware using Mission Planner

Kind of a weird issue.

  1. Updated Mission planner to latest Beta.

image

  1. This is an old Autopilot FC pulled out of an old F450 Quad. and I believe its a 2.4.8 V3.

  2. I can easily connect to the the FC, using COM9, but noticed this strange message saying “Legacy FMU”, what does that means? It currently has some older version of Quadcopter Firmware, probably a year old or more.

I want to flash this FC, with Ardu Plane. When you go through the steps, “selected FMUV3” from drop down and Latest Arduplane Firmware and then you unplug the board and plug it back in again, it gives following error message.

image

image

tried several times flushing this board but no luck,

Good day, just try flash the firmware manually with the option custom firmware… just check also you have the last drives.
In case you can update also the bootloader of your fc… but take care during this process.

Nothing is working.

I should be selecting Pxk 1 correct if I have 2.4.8 V3 chip set?

What is this new option, inside mission planner, “Install firmware Legacy”?

image

if you have pixhawk 2.4.8… yes, you must select pixhawk 1 coz is FMUv2.
with firmware legacy you can choose the fc is connected… firmware version… bootloader

1 Like

I figured out the problem.

All these issue arise with USB drivers on the computer.

I used a different laptop and I was able to flush it.

This is the 3rd time this has happened. We need a better USB driver solution for windows. As I use my laptop to test like 50 different devices each installing USB drivers, over riding new versions with old ones, makes Windows go Coco.

Servers by jDrones