mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-04-14 10:07:39 +08:00
702 lines
18 KiB
Markdown
702 lines
18 KiB
Markdown
# 모듈 참조: 명령
|
|
|
|
## bl_update
|
|
|
|
Source: [systemcmds/actuator_test](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/actuator_test)
|
|
|
|
파일에서 부트로더를 플래시하는 유틸리티
|
|
|
|
WARNING: remove all props before using this command.
|
|
|
|
### Usage {#actuator_test_usage}
|
|
|
|
```
|
|
actuator_test <command> [arguments...]
|
|
Commands:
|
|
set Set an actuator to a specific output value
|
|
|
|
The actuator can be specified by motor, servo or function directly:
|
|
[-m <val>] Motor to test (1...8)
|
|
[-s <val>] Servo to test (1...8)
|
|
[-f <val>] Specify function directly
|
|
-v <val> value (-1...1)
|
|
[-t <val>] Timeout in seconds (run interactive if not set)
|
|
default: 0
|
|
|
|
iterate-motors Iterate all motors starting and stopping one after the other
|
|
|
|
iterate-servos Iterate all servos deflecting one after the other
|
|
```
|
|
|
|
## bl_update
|
|
|
|
Source: [systemcmds/bl_update](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/bl_update)
|
|
|
|
Utility to flash the bootloader from a file
|
|
|
|
### Usage {#bl_update_usage}
|
|
|
|
```
|
|
bl_update [arguments...]
|
|
setopt Set option bits to unlock the FLASH (only needed if in locked
|
|
state)
|
|
|
|
<file> Bootloader bin file
|
|
```
|
|
|
|
## bsondump
|
|
|
|
Source: [systemcmds/bsondump](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/bsondump)
|
|
|
|
Utility to read BSON from a file and print or output document size.
|
|
|
|
### Usage {#bsondump_usage}
|
|
|
|
```
|
|
bsondump [arguments...]
|
|
<file> The BSON file to decode and print.
|
|
```
|
|
|
|
## dumpfile
|
|
|
|
Source: [systemcmds/dumpfile](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/dumpfile)
|
|
|
|
Dump file utility. Prints file size and contents in binary mode (don't replace LF with CR LF) to stdout.
|
|
|
|
### Usage {#dumpfile_usage}
|
|
|
|
```
|
|
dumpfile [arguments...]
|
|
<file> File to dump
|
|
```
|
|
|
|
## dyn
|
|
|
|
Source: [systemcmds/dyn](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/dyn)
|
|
|
|
### 설명
|
|
|
|
Load and run a dynamic PX4 module, which was not compiled into the PX4 binary.
|
|
|
|
### Example
|
|
|
|
```
|
|
dyn ./hello.px4mod start
|
|
```
|
|
|
|
### Usage {#dyn_usage}
|
|
|
|
```
|
|
dyn [arguments...]
|
|
<file> File containing the module
|
|
[arguments...] Arguments to the module
|
|
```
|
|
|
|
## failure
|
|
|
|
Source: [systemcmds/failure](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/failure)
|
|
|
|
### 설명
|
|
|
|
Inject failures into system.
|
|
|
|
### 구현
|
|
|
|
This system command sends a vehicle command over uORB to trigger failure.
|
|
|
|
### 예
|
|
|
|
Test the GPS failsafe by stopping GPS:
|
|
|
|
failure gps off
|
|
|
|
### Usage {#failure_usage}
|
|
|
|
```
|
|
failure [arguments...]
|
|
help Show this help text
|
|
|
|
gps|... Specify component
|
|
|
|
ok|off|... Specify failure type
|
|
[-i <val>] sensor instance (0=all)
|
|
default: 0
|
|
```
|
|
|
|
## gpio
|
|
|
|
Source: [systemcmds/gpio](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/gpio)
|
|
|
|
### 설명
|
|
|
|
This command is used to read and write GPIOs
|
|
|
|
```
|
|
gpio read <PORT><PIN>/<DEVICE> [PULLDOWN|PULLUP] [--force]
|
|
gpio write <PORT><PIN>/<DEVICE> <VALUE> [PUSHPULL|OPENDRAIN] [--force]
|
|
```
|
|
|
|
### 예
|
|
|
|
Read the value on port H pin 4 configured as pullup, and it is high
|
|
|
|
```
|
|
gpio read H4 PULLUP
|
|
```
|
|
|
|
1 OK
|
|
|
|
Set the output value on Port E pin 7 to high
|
|
|
|
```
|
|
gpio write E7 1 --force
|
|
```
|
|
|
|
Set the output value on device /dev/gpio1 to high
|
|
|
|
```
|
|
gpio write /dev/gpio1 1
|
|
```
|
|
|
|
### Usage {#gpio_usage}
|
|
|
|
```
|
|
gpio [arguments...]
|
|
read
|
|
<PORT><PIN>/<DEVICE> GPIO port and pin or device
|
|
[PULLDOWN|PULLUP] Pulldown/Pullup
|
|
[--force] Force (ignore board gpio list)
|
|
|
|
write
|
|
<PORT> <PIN> GPIO port and pin
|
|
<VALUE> Value to write
|
|
[PUSHPULL|OPENDRAIN] Pushpull/Opendrain
|
|
[--force] Force (ignore board gpio list)
|
|
```
|
|
|
|
## hardfault_log
|
|
|
|
Source: [systemcmds/hardfault_log](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/hardfault_log)
|
|
|
|
Hardfault utility
|
|
|
|
Used in startup scripts to handle hardfaults
|
|
|
|
### Usage {#hardfault_log_usage}
|
|
|
|
```
|
|
hardfault_log <command> [arguments...]
|
|
Commands:
|
|
check Check if there's an uncommitted hardfault
|
|
|
|
rearm Drop an uncommitted hardfault
|
|
|
|
fault Generate a hardfault (this command crashes the system :)
|
|
[0|1|2|3] Hardfault type: 0=divide by 0, 1=Assertion, 2=jump to 0x0,
|
|
3=write to 0x0 (default=0)
|
|
|
|
commit Write uncommitted hardfault to /fs/microsd/fault_%i.txt (and
|
|
rearm, but don't reset)
|
|
|
|
count Read the reboot counter, counts the number of reboots of an
|
|
uncommitted hardfault (returned as the exit code of the
|
|
program)
|
|
|
|
reset Reset the reboot counter
|
|
```
|
|
|
|
## hist
|
|
|
|
Source: [systemcmds/hist](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/hist)
|
|
|
|
Command-line tool to show the px4 message history. There are no arguments.
|
|
|
|
### Usage {#hist_usage}
|
|
|
|
```
|
|
hist [arguments...]
|
|
```
|
|
|
|
## i2cdetect
|
|
|
|
Source: [systemcmds/i2cdetect](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/i2cdetect)
|
|
|
|
Utility to scan for I2C devices on a particular bus.
|
|
|
|
### Usage {#i2cdetect_usage}
|
|
|
|
```
|
|
i2cdetect [arguments...]
|
|
[-b <val>] I2C bus
|
|
default: 1
|
|
```
|
|
|
|
## led_control
|
|
|
|
Source: [systemcmds/led_control](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/led_control)
|
|
|
|
### 설명
|
|
|
|
Command-line tool to control & test the (external) LED's.
|
|
|
|
To use it make sure there's a driver running, which handles the led_control uorb topic.
|
|
|
|
There are different priorities, such that for example one module can set a color with low priority, and another
|
|
module can blink N times with high priority, and the LED's automatically return to the lower priority state
|
|
after the blinking. The `reset` command can also be used to return to a lower priority.
|
|
|
|
### 예
|
|
|
|
Blink the first LED 5 times in blue:
|
|
|
|
```
|
|
led_control blink -c blue -l 0 -n 5
|
|
```
|
|
|
|
### Usage {#led_control_usage}
|
|
|
|
```
|
|
led_control <command> [arguments...]
|
|
Commands:
|
|
test Run a test pattern
|
|
|
|
on Turn LED on
|
|
|
|
off Turn LED off
|
|
|
|
reset Reset LED priority
|
|
|
|
blink Blink LED N times
|
|
[-n <val>] Number of blinks
|
|
default: 3
|
|
[-s <val>] Set blinking speed
|
|
values: fast|normal|slow, default: normal
|
|
|
|
breathe Continuously fade LED in & out
|
|
|
|
flash Two fast blinks and then off with frequency of 1Hz
|
|
|
|
The following arguments apply to all of the above commands except for 'test':
|
|
[-c <val>] color
|
|
values: red|blue|green|yellow|purple|amber|cyan|white, default:
|
|
white
|
|
[-l <val>] Which LED to control: 0, 1, 2, ... (default=all)
|
|
[-p <val>] Priority
|
|
default: 2
|
|
```
|
|
|
|
## listener
|
|
|
|
Source: [systemcmds/topic_listener](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/topic_listener)
|
|
|
|
Utility to listen on uORB topics and print the data to the console.
|
|
|
|
The listener can be exited any time by pressing Ctrl+C, Esc, or Q.
|
|
|
|
### Usage {#listener_usage}
|
|
|
|
```
|
|
listener <command> [arguments...]
|
|
Commands:
|
|
<topic_name> uORB topic name
|
|
[-i <val>] Topic instance
|
|
default: 0
|
|
[-n <val>] Number of messages
|
|
default: 1
|
|
[-r <val>] Subscription rate (unlimited if 0)
|
|
default: 0
|
|
```
|
|
|
|
## mfd
|
|
|
|
Source: [systemcmds/mft](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/mft)
|
|
|
|
Utility interact with the manifest
|
|
|
|
### Usage {#mfd_usage}
|
|
|
|
```
|
|
mfd <command> [arguments...]
|
|
Commands:
|
|
query Returns true if not existed
|
|
```
|
|
|
|
## mft_cfg
|
|
|
|
Source: [systemcmds/mft_cfg](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/mft_cfg)
|
|
|
|
Tool to set and get manifest configuration
|
|
|
|
### Usage {#mft_cfg_usage}
|
|
|
|
```
|
|
mft_cfg <command> [arguments...]
|
|
Commands:
|
|
get get manifest configuration
|
|
|
|
set set manifest configuration
|
|
|
|
reset reset manifest configuration
|
|
hwver|hwrev Select type: MTD_MTF_VER|MTD_MTF_REV
|
|
-i <val> argument to set extended hardware id (id == version for
|
|
<hwver>, id == revision for <hwrev> )
|
|
```
|
|
|
|
## mtd
|
|
|
|
Source: [systemcmds/mtd](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/mtd)
|
|
|
|
Utility to mount and test partitions (based on FRAM/EEPROM storage as defined by the board)
|
|
|
|
### Usage {#mtd_usage}
|
|
|
|
```
|
|
mtd <command> [arguments...]
|
|
Commands:
|
|
status Print status information
|
|
|
|
readtest Perform read test
|
|
|
|
rwtest Perform read-write test
|
|
|
|
erase Erase partition(s)
|
|
|
|
The commands 'readtest' and 'rwtest' have an optional instance index:
|
|
[-i <val>] storage index (if the board has multiple storages)
|
|
default: 0
|
|
|
|
The commands 'readtest', 'rwtest' and 'erase' have an optional parameter:
|
|
[<partition_name1> [<partition_name2> ...]] Partition names (eg.
|
|
/fs/mtd_params), use system default if not provided
|
|
```
|
|
|
|
## nshterm
|
|
|
|
Source: [systemcmds/nshterm](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/nshterm)
|
|
|
|
Start an NSH shell on a given port.
|
|
|
|
This was previously used to start a shell on the USB serial port.
|
|
Now there runs mavlink, and it is possible to use a shell over mavlink.
|
|
|
|
### Usage {#nshterm_usage}
|
|
|
|
```
|
|
nshterm [arguments...]
|
|
<file:dev> Device on which to start the shell (eg. /dev/ttyACM0)
|
|
```
|
|
|
|
## param
|
|
|
|
Source: [systemcmds/param](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/param)
|
|
|
|
### 설명
|
|
|
|
Command to access and manipulate parameters via shell or script.
|
|
|
|
This is used for example in the startup script to set airframe-specific parameters.
|
|
|
|
Parameters are automatically saved when changed, eg. with `param set`. They are typically stored to FRAM
|
|
or to the SD card. `param select` can be used to change the storage location for subsequent saves (this will
|
|
need to be (re-)configured on every boot).
|
|
|
|
If the FLASH-based backend is enabled (which is done at compile time, e.g. for the Intel Aero or Omnibus),
|
|
`param select` has no effect and the default is always the FLASH backend. However `param save/load <file>`
|
|
can still be used to write to/read from files.
|
|
|
|
Each parameter has a 'used' flag, which is set when it's read during boot. It is used to only show relevant
|
|
parameters to a ground control station.
|
|
|
|
### 예
|
|
|
|
Change the airframe and make sure the airframe's default parameters are loaded:
|
|
|
|
```
|
|
param set SYS_AUTOSTART 4001
|
|
param set SYS_AUTOCONFIG 1
|
|
reboot
|
|
```
|
|
|
|
### Usage {#param_usage}
|
|
|
|
```
|
|
param <command> [arguments...]
|
|
Commands:
|
|
load Load params from a file (overwrite all)
|
|
[<file>] File name (use default if not given)
|
|
|
|
import Import params from a file
|
|
[<file>] File name (use default if not given)
|
|
|
|
save Save params to a file
|
|
[<file>] File name (use default if not given)
|
|
|
|
select Select default file
|
|
[<file>] File name
|
|
|
|
select-backup Select default file
|
|
[<file>] File name
|
|
|
|
show Show parameter values
|
|
[-a] Show all parameters (not just used)
|
|
[-c] Show only changed params (unused too)
|
|
[-q] quiet mode, print only param value (name needs to be exact)
|
|
[<filter>] Filter by param name (wildcard at end allowed, eg. sys_*)
|
|
|
|
show-for-airframe Show changed params for airframe config
|
|
|
|
status Print status of parameter system
|
|
|
|
set Set parameter to a value
|
|
<param_name> <value> Parameter name and value to set
|
|
[fail] If provided, let the command fail if param is not found
|
|
|
|
set-default Set parameter default to a value
|
|
[-s] If provided, silent errors if parameter doesn't exists
|
|
<param_name> <value> Parameter name and value to set
|
|
[fail] If provided, let the command fail if param is not found
|
|
|
|
compare Compare a param with a value. Command will succeed if equal
|
|
[-s] If provided, silent errors if parameter doesn't exists
|
|
<param_name> <value> Parameter name and value to compare
|
|
|
|
greater Compare a param with a value. Command will succeed if param is
|
|
greater than the value
|
|
[-s] If provided, silent errors if parameter doesn't exists
|
|
<param_name> <value> Parameter name and value to compare
|
|
<param_name> <value> Parameter name and value to compare
|
|
|
|
touch Mark a parameter as used
|
|
[<param_name1> [<param_name2>]] Parameter name (one or more)
|
|
|
|
reset Reset only specified params to default
|
|
[<param1> [<param2>]] Parameter names to reset (wildcard at end allowed)
|
|
|
|
reset_all Reset all params to default
|
|
[<exclude1> [<exclude2>]] Do not reset matching params (wildcard at end
|
|
allowed)
|
|
|
|
index Show param for a given index
|
|
<index> Index: an integer >= 0
|
|
|
|
index_used Show used param for a given index
|
|
<index> Index: an integer >= 0
|
|
|
|
find Show index of a param
|
|
<param> param name
|
|
```
|
|
|
|
## payload_deliverer
|
|
|
|
Source: [modules/payload_deliverer](https://github.com/PX4/PX4-Autopilot/tree/main/src/modules/payload_deliverer)
|
|
|
|
### 설명
|
|
|
|
Handles payload delivery with either Gripper or a Winch with an appropriate timeout / feedback sensor setting,
|
|
and communicates back the delivery result as an acknowledgement internally
|
|
|
|
### Usage {#payload_deliverer_usage}
|
|
|
|
```
|
|
payload_deliverer <command> [arguments...]
|
|
Commands:
|
|
start
|
|
|
|
gripper_test Tests the Gripper's release & grabbing sequence
|
|
|
|
gripper_open Opens the gripper
|
|
|
|
gripper_close Closes the gripper
|
|
|
|
stop
|
|
|
|
status print status info
|
|
```
|
|
|
|
## perf
|
|
|
|
Source: [systemcmds/perf](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/perf)
|
|
|
|
Tool to print performance counters
|
|
|
|
### Usage {#perf_usage}
|
|
|
|
```
|
|
perf [arguments...]
|
|
reset Reset all counters
|
|
|
|
latency Print HRT timer latency histogram
|
|
|
|
Prints all performance counters if no arguments given
|
|
```
|
|
|
|
## reboot
|
|
|
|
Source: [systemcmds/reboot](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/reboot)
|
|
|
|
Reboot the system
|
|
|
|
### Usage {#reboot_usage}
|
|
|
|
```
|
|
reboot [arguments...]
|
|
[-b] Reboot into bootloader
|
|
[-i] Reboot into ISP (1st stage bootloader)
|
|
[lock|unlock] Take/release the shutdown lock (for testing)
|
|
```
|
|
|
|
## sd_bench
|
|
|
|
Source: [systemcmds/sd_bench](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/sd_bench)
|
|
|
|
Test the speed of an SD Card
|
|
|
|
### Usage {#sd_bench_usage}
|
|
|
|
```
|
|
sd_bench [arguments...]
|
|
[-b <val>] Block size for each read/write
|
|
default: 4096
|
|
[-r <val>] Number of runs
|
|
default: 5
|
|
[-d <val>] Duration of a run in ms
|
|
default: 2000
|
|
[-k] Keep the test file
|
|
[-s] Call fsync after each block (default=at end of each run)
|
|
[-u] Test performance with unaligned data
|
|
[-U] Test performance with forced byte unaligned data
|
|
[-v] Verify data and block number
|
|
```
|
|
|
|
## sd_stress
|
|
|
|
Source: [systemcmds/sd_stress](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/sd_stress)
|
|
|
|
Test operations on an SD Card
|
|
|
|
### Usage {#sd_stress_usage}
|
|
|
|
```
|
|
sd_stress [arguments...]
|
|
[-r <val>] Number of runs
|
|
default: 5
|
|
[-b <val>] Number of bytes
|
|
default: 100
|
|
```
|
|
|
|
## serial_passthru
|
|
|
|
Source: [systemcmds/serial_passthru](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/serial_passthru)
|
|
|
|
Pass data from one device to another.
|
|
|
|
This can be used to use u-center connected to USB with a GPS on a serial port.
|
|
|
|
### Usage {#serial_passthru_usage}
|
|
|
|
```
|
|
serial_passthru [arguments...]
|
|
-e <val> External device path
|
|
values: <file:dev>
|
|
-d <val> Internal device path
|
|
values: <file:dev>
|
|
[-b <val>] Baudrate
|
|
default: 115200
|
|
[-t] Track the External devices baudrate on internal device
|
|
```
|
|
|
|
## system_time
|
|
|
|
Source: [systemcmds/system_time](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/system_time)
|
|
|
|
### 설명
|
|
|
|
Command-line tool to set and get system time.
|
|
|
|
### 예
|
|
|
|
Set the system time and read it back
|
|
|
|
```
|
|
system_time set 1600775044
|
|
system_time get
|
|
```
|
|
|
|
### Usage {#system_time_usage}
|
|
|
|
```
|
|
system_time <command> [arguments...]
|
|
Commands:
|
|
set Set the system time, provide time in unix epoch time format
|
|
|
|
get Get the system time
|
|
```
|
|
|
|
## top
|
|
|
|
Source: [systemcmds/top](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/top)
|
|
|
|
Monitor running processes and their CPU, stack usage, priority and state
|
|
|
|
### Usage {#top_usage}
|
|
|
|
```
|
|
top [arguments...]
|
|
once print load only once
|
|
```
|
|
|
|
## usb_connected
|
|
|
|
Source: [systemcmds/usb_connected](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/usb_connected)
|
|
|
|
Utility to check if USB is connected. Was previously used in startup scripts.
|
|
A return value of 0 means USB is connected, 1 otherwise.
|
|
|
|
### Usage {#usb_connected_usage}
|
|
|
|
```
|
|
usb_connected [arguments...]
|
|
```
|
|
|
|
## ver
|
|
|
|
Source: [systemcmds/ver](https://github.com/PX4/PX4-Autopilot/tree/main/src/systemcmds/ver)
|
|
|
|
Tool to print various version information
|
|
|
|
### Usage {#ver_usage}
|
|
|
|
```
|
|
ver <command> [arguments...]
|
|
Commands:
|
|
hw Hardware architecture
|
|
|
|
mcu MCU info
|
|
|
|
git git version information
|
|
|
|
bdate Build date and time
|
|
|
|
gcc Compiler info
|
|
|
|
bdate Build date and time
|
|
|
|
px4guid PX4 GUID
|
|
|
|
uri Build URI
|
|
|
|
all Print all versions
|
|
|
|
hwcmp Compare hardware version (returns 0 on match)
|
|
<hw> [<hw2>] Hardware to compare against (eg. PX4_FMU_V4). An OR comparison
|
|
is used if multiple are specified
|
|
|
|
hwtypecmp Compare hardware type (returns 0 on match)
|
|
<hwtype> [<hwtype2>] Hardware type to compare against (eg. V2). An OR
|
|
comparison is used if multiple are specified
|
|
|
|
hwbasecmp Compare hardware base (returns 0 on match)
|
|
<hwbase> [<hwbase2>] Hardware type to compare against (eg. V2). An OR
|
|
comparison is used if multiple are specified
|
|
```
|