There is no such thing as FMUv2 or FMUv3 anymore in ArduPilot as of Copter 4. It was a horribly misused and misunderstood build target name, so things were changed to make it much more clear what build targets are for what. This is actually a great example of that problem!
There is now a build target called Pixhawk1 (replaced FMUv3), which is for the Pixhawks and clones that don’t have the 1MB flash limit. There is also a Pixhawk1-1M build (replaced FMUv2), that as the name implies, is for the 1MB flash limit boards.
If you have a Pixhawk 1 or the many clones, you should use the Pixhawk1 build. If you have one of those 1MB flash limited early pixhawks/clones, then you should use the -1M build.
I have pixhawk 2.4.8 and mission Planer by default copied version 4.0 for fmuv2. Despite the driver has 2mb I did not receive some parameters, e.g. the possibility of connecting an external parameter. after installing pixhawk 1 firmware everything was ok. I went further and manually uploaded the firmware version for Fmuv3 and everything is ok. Hex with two Gps, two barometers flying well …
Matt, I know the history of FMUv3 - the first Cube - and Philip at CubePilot fuming at the chinese clones using v3 STM32F4s creating confusion.
But someone has to go public and broadcast the changes. ;(
Yes, it’s probably a step too far to say that, “there’s no such thing as fmuv2 and fmuv3”. Instead it’s more that we recommend users pick the firmware that is a better fit for their board (i.e. Pixhawk1, CubeBlack, etc). It’s difficult for us to remove the fmuv2 and fmuv3 from the servers because many users are still using them… so it will be a (slow-ish) transition to the new, more specific firmwares.
Up until recently it’s been difficult for most users to actually chose which firmware goes on their board. It’s fairly easy to chose the version (stable, beta, older version etc) but not whether you want fmuv2 vs fmuv3 vs Pixhawk, ChibiOS, NuttX, etc, etc so we’ve been working with MichaelOborne to make a new firmware installation page on MP that lists all the possible compatible versions for the board so the user can choose.
I HATE TO BEAT A DEAD HORSE BUT IM STUMPED FELLAS.
im having the same problem. trying to config and no gps/compass is being recognized. everything is brand new from radiolink. this is for my s550 hexacoptor. now i cant figure out how to get the right firmware on the pixhawk. when i plug it in, it chimes and the buzzer makes the positive buz at the end. i go to connect and seconds after i push connect, i get connection failed “there was an unexpected error” ill attatch 2 screen shots.
i ended up buying a new gps unit. mine didnt seem to even light up. but i still am having trouble. it does detect the board. on the pull down it will usually be com port 5. i have tried to load several firmwares on it tonight thinking “thats the one” and nope, still getting no gps recognition period and this gps is displaying a blue light.
Hello, I have exactly the same problem. Pixhawk 2.4.8 Radiolink. In the older firmware, it detects the internal compass without any problems; after installing the 4.xx firmware, the internal compass is no longer detected. I have all the settings for testing by default. Interestingly, although the rover direction is not detected in version 4.1.5 of the internal compass, it is shown perfectly in the Mission Planner, but the Compass cannot be calibrated and there are problems with the “Bad Compass Health” pre-flight check. I don’t want to run an external compass on the rover when the internal compass shows so well. Did you solve this problem in any way? Thank you for every answer. Jirik.