The wait is over! We are proud to introduce the next generation 3DR autopilot, Pixhawk Mini. Pixhawk Mini is an upgraded Pixhawk designed in collaboration with HobbyKing and optimized to run the Dronecode PX4 firmware stack and QGroundControl multi-platform ground station (Windows, Mac, Linux, Android, iOS).
For just $199, Pixhawk Mini includes autopilot, GPS, and all the cables and connectors needed to get started building DIY quads, planes, rovers, and boats.
What's improved over Pixhawk 1?
One third the size--dimensions reduced from 50 mm x 81.5 mm x15.5 mm to 38 mm x 43 mm x 12 mm. Smaller airframes can now operate autonomously without making sacrifices for the Pixhawk footprint.
Rev 3 STM32 processor allow for full utilization of 2MB flash memory. Pixhawk Mini operates at only 50% compute capacity, 40 percentage points lower than the original Pixhawk. There is significantly more overhead available to run custom code.
Improved sensors, including both primary and secondary IMU (MPU9250 and ICM20608, respectively), lead to much better vibration handling and increased reliability.
GPS module included--Neo M8N with quad-constellation support and upgraded HMC5983 compass.
Micro JST connectors replace DF-13. We can all breath a sigh of relief.
Integrated piezo speaker and safety switch
What's improved over Pixfalcon?
Again, improved sensors, including both primary and secondary IMU (MPU9250 and ICM20608 respectively) for much better vibration handling and increased reliability.
Dedicated CAN port for UAVCAN applications.
Includes 8-channel servo output board for planes and other vehicles requiring powered PWM output.
Includes I2C breakout board for a total of 5 I2C connections.
Pixhawk Mini features an advanced processor and sensor technology from ST Microelectronics® and a NuttX real-time operating system, delivering incredible performance, flexibility, and reliability for controlling any autonomous vehicle.
SPECIFICATIONS
Main Processor: STM32F427 Rev 3
IO Processor: STM32F103
Accel/Gyro/Mag: MPU9250
Accel/Gyro: ICM20608
Barometer: MS5611
Dimensions: 38x43x12mm
Weight: 15.8g
GPS Module: ublox Neo-M8N GPS/GLONASS receiver; integrated magnetometer HMC5983
Dimensions: 37x37x12mm
Weight: 22.4g
Interface
1 x UART Serial Port (for GPS)
Spektrum DSM/DSM2/DSM-X® Satellite Compatible RC input
Futaba S BUS® Compatible RC input
PPM Sum Signal RC Input
I2C (for digital sensors)
CAN (for digital motor control with compatible controllers)
ADC (for analog sensors)
Micro USB Port
What’s Included?
Pixhawk Mini Flight Controller
GPS with uBlox M8N module with
Concurrent reception of up to 3 GNSS (GPS, Galileo, GLONASS, BeiDou)
Industry leading –167 dBm navigation sensitivity
Security and integrity protection
Supports all satellite augmentation systems
Advanced jamming and spoofing detection
Product variants to meet performance and cost requirements
Backward compatible with NEO‑7 and NEO‑6 families
Integrated Power Module (up to 6s batteries) and power distribution board for quadcopters
8-channel servo output board for planes and other vehicles requiring powered PWM output.
Cables
4 pin I2C cable and breakout board
6 pin GPS+Compass cable
6 to 6/4 ‘Y’ adapter for additional I2C devices
4 JST to 6 DF13 cable for legacy telemetry radios
External safety switch cable
RCIN cable for PPM/SBUS input
8 channel RC output cable
6 pin power cable for included Power Distribution Board
OPTIONAL ACCESSORIES
All available here
Comments
Will there be a stable version of arduplane soon in pixhawk mini ?
Yes, it's definitely possible.
Thanks, are you saying that this problem would potentially affect pixfalcons as well? I have 5 flying out there...
Yes Hein, this really isn't a surprise at all. Certainly we've seen this problem before with people placing the beeper too close to the flight controller. I have no idea why somebody would put the beeper directly on the board. The result was inevitable.
@Hein, yes, we've seen this in logs before when people put the beeper hard up against the case of other boards. The difference here is the beeper is builtin and attached directly to the main board.
Wow thanks for picking up on that Tridge, I don't know who else would have thought of that! When a failsafe has been triggered, the beeper is continuously playing a sequence, so that might have an adverse effect or at least give you a EKF warning and I would not have suspected the beeper!
Hi Gary,
I'm not the right person to know if replacing it is feasible as that depends on a level of soldering skill I don't have.
Simple thing to do is just disable it.
I'd also note that in most flights the occasional beep from the buzzer won't cause the state estimation to go crazy, but it's not worth the risk to fly with it enabled.
Cheers, Tridge
Hi Tridge,
Thank you for setting this up, truly exceptional given the circumstances.
Would it be feasible / worthwhile to yank the buzzer off the board and perhaps attach another one with remote leads or at least a plug that could go to one?
As it stands, it definitely sounds (bad pun) as though the buzzer is not an asset.
Best Regards,
Gary
WOW.
Well, thanks for looking out for our users Tridge.
There's actually a good opportunity for a cost save here. Just remove the buzzer since it can't be used.
yes, it works with ArduPlane. I have only bench tested it not actually flown it, but it is fully functional. You need to be running master though, as I hadn't received a board when I did the last stable release so I wasn't able to add support in that release.
One thing I would suggest is disabling the buzzer with NTF_BUZZ_ENABLE=0. The buzzer on the mini is located in a really bad spot on the board, and the board has a nasty resonant frequency of around 4020Hz. The buzzer can excite that resonance even with much lower tones (from harmonics) causing extreme aliasing in one of the IMUs. Playing the right tune on the buzzer can make the state estimator think the board is upside down as aliasing causes the accelZ value to change sign. There isn't anything the software can do to properly fix this apart from not using the buzzer. Luckily it only seems to have a big effect on one of the IMUs, so the EKF will hopefully change lanes and use the other IMU when this happens, but thats not a proper fix.
Mounting a buzzer directly on the same board as an IMU is not a good idea.
Here is a graph of the first IMU accelerometer readings when playing a B+ tone on the buzzer. The tone was set to play every 2 seconds. It is the worst case of buzzer induced aliasing I have seen. As you can see, gravity goes from the correct value of -9.4m/s/s (the board is not quite level) up to +2.6m/s/s when the tone is playing.
-
5
-
6
-
7
-
8
-
9
of 16 Next