ROS Index
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged fss_bringup at Robotics Stack Exchange
|
|
fss_bringup package from fastswarmsim repofss_bringup fss_px4_sim fss_sensing fss_time fss_time_interfaces |
ROS Distro
|
Package Summary
| Version | 0.1.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/shupx/FastSwarmSim.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-08-25 |
| Dev Status | MAINTAINED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Peixuan Shu
Authors
fss_bringup
This package provides integrated FastSwarmSim launch files. Each launch combines the PX4 or perfect-drone simulator, optional local LiDAR point-cloud sensing, the fss_time coordinator, vehicle visualization, and RViz.
# One PX4 vehicle with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_single.launch.py
# A three-vehicle PX4 swarm with LiDAR sensing and RViz.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py num_drones:=3
# Use MAVROS-compatible perfect drones instead of PX4 simulation.
ros2 launch fss_bringup sim_px4_drone_lidar_multi.launch.py \
num_drones:=5 use_perfect_drone:=true
Both launches use the FastSwarmSim coordinated clock by default. Set use_fss_sim_time:=false to disable lock-step time coordination, sensing_enable:=false to omit local LiDAR in the multi-drone launch, or enable_sensing:=false in the single-drone launch. Use rviz_enable:=false for multi-drone runs or enable_rviz:=false for single-drone runs to launch without RViz.
The multi-drone launch assigns the namespaces uav1, uav2, and so on. It accepts drones_per_row, startup_batch_size, and startup_batch_delay_ms to control formation layout and staged startup.
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| fss_px4_sim | |
| fss_sensing | |
| fss_time | |
| launch | |
| launch_ros | |
| rviz2 |