Documentation/FlyCore i225U WikiEnglish · V1
Browse documentation
Advanced User Guide

NSH Debugging

NSH is the PX4 command line debugging terminal. It can be used to view low level operating status, module status, parameters, uORB topics, and communication links. This page is…

2 min read · English documentation

NSH is the PX4 command-line debugging terminal. It can be used to view low-level operating status, module status, parameters, uORB topics, and communication links. This page is intended for advanced users with flight controller debugging experience.

Warning:

NSH commands may change parameters, actuator states, or module operating states. Before executing commands that write data, stop or restart modules, or involve motors, remove the propellers, back up the parameters, and confirm that the commands are applicable to the current PX4 build.

Accessing NSH via QGC

Prerequisites

  • QGC is successfully connected to FlyCore-FC;
  • The aircraft is in a safe, non-armable state for ground debugging;
  • If parameters need to be modified, the current parameters have been exported and their original values recorded.

Procedure

  1. In QGC, go to the Analyze page.
  2. Open MAVLink Console.
  3. Enter a read-only status command and press Enter to execute it.

Open MAVLink Console via QGC

Common Read-Only Diagnostic Commands

Diagnostic Task Command
View firmware and hardware versions ver all
View system tasks top
View system startup information dmesg
View uORB topic status uorb status
View GPS data gps status
View MAVLink links mavlink status
View sensor status sensors status

Examples of High-Risk Commands

Purpose Command
Reverse the direction of DShot motor 1 dshot reverse -m 1
Save DShot settings dshot save

After execution, restart PX4 and complete propeller-free verification for each motor as described in Actuator Configuration and Motor Testing.