500a1c808d
* Lists ROMFS files explicity instead of using GLOB_RECURSE
Previously, when ROMFS files that were not airframes were touched, the ROMFS
would not be rebuilt. The ROMFS files are now specified explicityl in a
CMakeLists.txt file that is located in the root ROMFS directory.
Now when one of the ROMFS files is touched the whole ROMFS is rebuilt.
When new files are added to the ROMFS, they need to be explicity added to
the CMakeLists in the ROMFS root directory.
* ROMFS: adds individual CMakeLists files in each subdirectory
Also moves the temporary ROMFS build directory to ${PX4_BINARY_DIR}/ROMFS/genromfs
so that the cmake_install.cmake files and the CMakeFiles directories (generated whenever
are not add_subdirectory() is called) are not generated in the temporary ROMFS directory
from which the ROMFS binary is created.
* cmake ROMFS generate add px4_add_romfs_files function
* ROMFS CMakeLists: adds explanatory comment to px4_add_romfs_files function
* ROMFS CMakeLists: updates copyright headers
|
||
|---|---|---|
| .. | ||
| AAERTWF.main.mix | ||
| AAVVTWFF.main.mix | ||
| AERT.main.mix | ||
| AETRFG.main.mix | ||
| CCPM.main.mix | ||
| CMakeLists.txt | ||
| FMU_pass.mix | ||
| FX79.main.mix | ||
| IO_pass.main.mix | ||
| README.md | ||
| Viper.main.mix | ||
| bebop.main.mix | ||
| blade130.main.mix | ||
| caipi.main.mix | ||
| caipirinha_vtol.main.mix | ||
| claire.aux.mix | ||
| claire.main.mix | ||
| coax.main.mix | ||
| delta.main.mix | ||
| deltaquad.main.mix | ||
| dodeca_bottom_cox.aux.mix | ||
| dodeca_top_cox.main.mix | ||
| firefly6.aux.mix | ||
| firefly6.main.mix | ||
| fw_generic_wing.main.mix | ||
| hexa_+.main.mix | ||
| hexa_cox.main.mix | ||
| hexa_x.main.mix | ||
| mount.aux.mix | ||
| mount_legs.aux.mix | ||
| ocpoc_quad_x.main.mix | ||
| octo_+.main.mix | ||
| octo_cox.main.mix | ||
| octo_cox_w.main.mix | ||
| octo_x.main.mix | ||
| pass.aux.mix | ||
| phantom.main.mix | ||
| quad_+.main.mix | ||
| quad_+_vtol.main.mix | ||
| quad_dc.main.mix | ||
| quad_h.main.mix | ||
| quad_s250aq.main.mix | ||
| quad_w.main.mix | ||
| quad_x.main.mix | ||
| quad_x_can.main.mix | ||
| quad_x_vtol.main.mix | ||
| quad_x_vtol_sim.main.mix | ||
| stampede.main.mix | ||
| tri_y_yaw+.main.mix | ||
| tri_y_yaw-.main.mix | ||
| ugv_generic.main.mix | ||
| vtol_AAERT.aux.mix | ||
| vtol_AAVVT.aux.mix | ||
| vtol_convergence.main.mix | ||
| vtol_delta.aux.mix | ||
| wingwing.main.mix | ||
| zmr250.main.mix | ||
README.md
PX4 mixer definitions
Files in this directory implement example mixers that can be used as a basis for customisation, or for general testing purposes.
For a detailed description of the mixing architecture and examples see: http://px4.io/dev/mixing
Syntax
Mixer definitions are text files; lines beginning with a single capital letter followed by a colon are significant. All other lines are ignored, meaning that explanatory text can be freely mixed with the definitions.
Each file may define more than one mixer; the allocation of mixers to actuators is specific to the device reading the mixer definition, and the number of actuator outputs generated by a mixer is specific to the mixer.
For example: each simple or null mixer is assigned to outputs 1 to x in the order they appear in the mixer file.
A mixer begins with a line of the form
<tag>: <mixer arguments>
The tag selects the mixer type; 'M' for a simple summing mixer, 'R' for a multirotor mixer, etc.
Null Mixer
A null mixer consumes no controls and generates a single actuator output whose value is always zero. Typically a null mixer is used as a placeholder in a collection of mixers in order to achieve a specific pattern of actuator outputs.
The null mixer definition has the form:
Z:
Simple Mixer
A simple mixer combines zero or more control inputs into a single actuator output. Inputs are scaled, and the mixing function sums the result before applying an output scaler.
A simple mixer definition begins with:
M: <control count>
O: <-ve scale> <+ve scale> <offset> <lower limit> <upper limit>
If is zero, the sum is effectively zero and the mixer will output a fixed value that is constrained by and .
The second line defines the output scaler with scaler parameters as discussed above. Whilst the calculations are performed as floating-point operations, the values stored in the definition file are scaled by a factor of 10000; i.e. an offset of -0.5 is encoded as -5000.
The definition continues with entries describing the control inputs and their scaling, in the form:
S: <group> <index> <-ve scale> <+ve scale> <offset> <lower limit> <upper limit>
The value identifies the control group from which the scaler will read, and the value an offset within that group. These values are specific to the device reading the mixer definition.
When used to mix vehicle controls, mixer group zero is the vehicle attitude control group, and index values zero through three are normally roll, pitch, yaw and thrust respectively.
The remaining fields on the line configure the control scaler with parameters as discussed above. Whilst the calculations are performed as floating-point operations, the values stored in the definition file are scaled by a factor of 10000; i.e. an offset of -0.5 is encoded as -5000.
Multirotor Mixer
The multirotor mixer combines four control inputs (roll, pitch, yaw, thrust) into a set of actuator outputs intended to drive motor speed controllers.
The mixer definition is a single line of the form:
R: <geometry> <roll scale> <pitch scale> <yaw scale> <deadband>
The supported geometries include:
- 4x - quadrotor in X configuration
- 4+ - quadrotor in + configuration
- 6x - hexcopter in X configuration
- 6+ - hexcopter in + configuration
- 8x - octocopter in X configuration
- 8+ - octocopter in + configuration
Each of the roll, pitch and yaw scale values determine scaling of the roll, pitch and yaw controls relative to the thrust control. Whilst the calculations are performed as floating-point operations, the values stored in the definition file are scaled by a factor of 10000; i.e. an factor of 0.5 is encoded as 5000.
Roll, pitch and yaw inputs are expected to range from -1.0 to 1.0, whilst the thrust input ranges from 0.0 to 1.0. Output for each actuator is in the range -1.0 to 1.0.
In the case where an actuator saturates, all actuator values are rescaled so that the saturating actuator is limited to 1.0.