What are the advantages and disadvantages or each?
The PX4 looks like the very old days when APM had many boards and no case. Just looking at the advertisement I have no idea why I would want to trade in my APM 2.5+ for a PX4?
.
You need to be a member of diydrones to add comments!
Replies
APM is out of eeprom
APM is out of ram
APM is out of cpu cycles
APM is not even on their new flagship "IRIS"
Hmm...
If you are judging an autopilot by how pretty it looks or put off by being able to see the circuit board, perhaps take up knitting instead...
All jokes aside...
A simple comparison and understanding of specs will give you a pretty good indication that PX4 hardware is far more superior, however I would reserve final judgement on what firmware is loaded onto the autopilot and how well it is taking advantage of the available hardware architecture,
If your requirements or interests don't exceed APM then I would say stick with that, for now :)
I actually have my F330 / PX4 flying very nicely in stabilize as of today.
I had motors 3 and 4 reversed which resulted in a lovely takeoff back flip.
I checked by holding the copter at low throttle and testing for it working against your tilting it and it worked in two directions but did the opposite in the other 2 immediately indicating 2 motor servo connections reversed.
I have really good cheap GemFan carbon props and did it on grass anyway so no harm done.
Possibly better to check first next time though.
By the way the little pre arm button with the green LED that comes with the PX4 system is a real asset.
I was doing some handheld motion testing as above when my undercharged transmitter gave out and it was running at medium throttle at the time.
Pressing the pre-arm button for 3 seconds shut it down.
It would have been a genuine problem if that hadn't been there.
I really like the pre arm button as an extra safety step required before take off too.
There is no mistaking it.
If the green LED is blinking continuously and evenly it is not pre armed and cannot be armed with the throttle.
If it is blinking twice with a longer pause between each pair it is pre-armed and can be armed with the throttle.
For all interested in flashing Firmware conveniently, there is a new tool called QUpgrade in the Downloads Area. It allows to flash the PX4 default or APM Plane / Copter / Rover Firmware on Windows, Mac OS and Linux with a graphical user interface in a single click. In particular for APM @ PX4 early adopters it may be interesting, since new builds can be flashed with a single click by browsing the Firmware page.
Hello everyone,
I still have problems with PX4 board.
1. I can not calibrate acc level with MissionPlaner. It only success via CLI.
2. I have enabled IMU logs but can not download any logs from the board. It tells me Error opening com port.
Does anyone have success with it?
Ok guys, I have a simple question.
If I get PX4 and use Arduplane firmware, what will I miss? What functions won't work?
Thanks
The DIYD APM and PX4 Firmware upload site is now directly linked in the Appendix of the ArduCopter and ArduPlane Wikis.
Hi again all, PX4 is Up and running in both modes.
Two entries in Wiki:
PX4FMU Only is here: https://code.google.com/p/arducopter/wiki/PX4_First
And PX4FMU plus PX4IO board is here: https://code.google.com/p/arducopter/wiki/PX4FMU_PX4IO_First
Please, get in there, kick the tires and give me feedback.
Hi All PX4 fans,
I think we've done it.
My problem turns out to have been the way the fmu_only file name was written.
Windows 7 FAT32 (File Allocation Table) structure couldn't recognize it.
Spent a couple hours G+ Hangout with screen sharing with Andrew Tridgell last night.
Really nice, really smart guy, my brain fried, but problem solved and more importantly, the PX4 is looking pretty much like its going to basically work for everybody so interested in doing so now.
I'm sure there will still be problems, but at least, basic operational capability looks good.
There had been a need for a small file called fmu_only on the SD card to indicate that you were using the PX4FMU board alone, without the stacking PX4IO board.
Didn't matter what was in the file, only that it was there.
Andrew solved the problem in what I am sure is typical Andrew fashion; he just eliminated the need for it.
Now, the software will determine whether the IO board is present or not and behave accordingly.
I also found out how to do the firmware loading and setup procedure much more simply without need ing to use Eclipse.
It is going to take me a few days to rewrite the Wiki about all of this, but basically we are good to go.
-
1
-
2
-
3
-
4
-
5
of 5 Next