Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix rendering issues #514

Merged
merged 2 commits into from
Jun 13, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions docs2/usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -155,10 +155,11 @@ Onboard positioning
The Crazyflie also supports several alternative positioning systems that provide direct onboard position or pose estimation.
In this case you do not need to receive positioning from an external system like with MoCap.

Instructions per positioning system.:
* The `Loco positioning system <https://www.bitcraze.io/documentation/system/positioning/loco-positioning-system/>`_ - Follow Bitcraze's tutorial `here <https://www.bitcraze.io/documentation/tutorials/getting-started-with-loco-positioning-system/>`.
* The `Lighthouse positioning system <https://www.bitcraze.io/documentation/system/positioning/lighthouse/>`_ - Follow Bitcraze's tutorial `here <https://www.bitcraze.io/documentation/tutorials/getting-started-with-lighthouse-positioning-system/>`. Make sure to review the system management for saving and loading a system config, such that you don't have to redo the basestation geometry estimation for each crazyflie.
* The `Flow deck <https://www.bitcraze.io/products/flow-deck-v2/>`_ - Follow Bitcraze's tutorial `here <https://www.bitcraze.io/documentation/tutorials/getting-started-with-flow-deck/>`. Note that the flow deck provides an relative positoing estimate and might conflict when you are flying with crazyswarm2 if you are flying with absolute coordinates instead of relative ones.
Instructions per positioning system:

* The `Loco positioning system <https://www.bitcraze.io/documentation/system/positioning/loco-positioning-system/>`_ - `Follow Bitcraze's tutorial on LPS here <https://www.bitcraze.io/documentation/tutorials/getting-started-with-loco-positioning-system/>`_.
* The `Lighthouse positioning system <https://www.bitcraze.io/documentation/system/positioning/lighthouse/>`_ - `Follow Bitcraze's tutorial on Lighthouse here <https://www.bitcraze.io/documentation/tutorials/getting-started-with-lighthouse-positioning-system/>`_. Make sure to review the system management for saving and loading a system config, such that you don't have to redo the basestation geometry estimation for each crazyflie.
* The `Flow deck <https://www.bitcraze.io/products/flow-deck-v2/>`_ - `Follow Bitcraze's tutorial on the flowdeck here <https://www.bitcraze.io/documentation/tutorials/getting-started-with-flow-deck/>`_. Note that the flow deck provides an relative positoing estimate and might conflict when you are flying with crazyswarm2 if you are flying with absolute coordinates instead of relative ones.

Also in this case, make sure that motion_capture is disabled in the crazyflies.yaml file:

Expand Down Expand Up @@ -238,4 +239,4 @@ Swarm Management
The launch file will also start a swarm management tool that is a ROS node and web-based GUI.
In the upper pane is the location of the drone visualized in a 3D window, similar to rviz.
In the lower pane, the status as well as log messages are visible (tabbed per drone).
In the future, we are planning to add support for rebooting and other actions.
In the future, we are planning to add support for rebooting and other actions.
Loading