88d623bedb
* Add vitepress tree * Update existing workflows so they dont trigger on changes in the docs path * Add nojekyll, package.json, LICENCE etc * Add crowdin docs upload/download scripts * Add docs flaw checker workflows * Used docs prefix for docs workflows * Crowdin obvious fixes * ci: docs move to self hosted runner runs on a beefy server for faster builds Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: don't run build action for docs or ci changes Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: update runners Signed-off-by: Ramon Roche <mrpollo@gmail.com> * Add docs/en * Add docs assets and scripts * Fix up editlinks to point to PX4 sources * Download just the translations that are supported * Add translation sources for zh, uk, ko * Update latest tranlsation and uorb graphs * update vitepress to latest --------- Signed-off-by: Ramon Roche <mrpollo@gmail.com> Co-authored-by: Ramon Roche <mrpollo@gmail.com>
1.3 KiB
Sensor/Topic Debugging using the Listener Command
The uORB is an asynchronous publish() / subscribe() messaging API used for
inter-thread/inter-process communication. The listener command can be used from the QGroundControl MAVLink Console to inspect topic (message) values, including the current values published by sensors.
:::tip Це потужний інструмент для відлагодження, оскільки його можна використовувати навіть тоді, коли QGC підключений через бездротове з'єднання (наприклад, коли транспортний засіб летить). :::
:::info
The listener command is also available through the System Console and the MAVLink Shell.
:::
:::tip
To check what topics are available at what rate, just use the uorb top command.
:::
The image below demonstrates QGroundControl being used to get the value of the acceleration sensor.
For more information about how to determine what topics are available and how to call listener see: uORB Messaging > Listing Topics and Listening in.