Skip to content

Commit bdf186e

Browse files
committed
initial documentation for flylab
1 parent 70d733e commit bdf186e

40 files changed

+205
-0
lines changed

docs/flylab/calibration.md

Lines changed: 132 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,132 @@
1+
---
2+
layout: default
3+
title: "Vicon Calibration"
4+
date: 2025-06-18
5+
math: katex
6+
parent: FlyLab
7+
nav_order: 1
8+
---
9+
10+
<style>
11+
img {
12+
max-height: 400px;
13+
width: auto;
14+
}
15+
</style>
16+
17+
18+
## Initial Steps
19+
20+
The system should always be on - never turn the Vicon off.
21+
22+
Enter the control room. Contact DASC lab for the password if the door is locked.
23+
24+
![](./images/control_room_door.png)
25+
26+
Straight ahead is the Vicon computer. If it is asleep, wake it up. Never turn this computer off. Open the Vicon software if it’s not already open.
27+
28+
![](./images/vicon_computer.png)
29+
30+
It is a good idea to recalibrate every so often since the cameras can get bumped. If a camera is bumped, it will show up with a red icon as shown in the picture in the System Settings tab on the left.
31+
32+
![alt text](./images/bumped.png)
33+
34+
## Masking
35+
36+
Ensure there are no markers visible to the system by looking at the 3D View.![alt text](./images/masking_no_markers.png)
37+
The image below shows what it looks like when there are markers in view of the cameras.
38+
![alt text](./images/masking_markers_visible.png)
39+
40+
Open the Camera Calibration tab on the left side of the screen and open the Cameras view.
41+
42+
![alt text](./images/masking_initial.png)
43+
44+
Click Mask All. You should see the dots change from light blue to dark blue. When the lights have settled like in the picture below, click Stop.
45+
46+
![alt text](./images/masking_mask_all.png)
47+
48+
Masking is now complete.
49+
50+
## Waving the Wand
51+
52+
Grab the wand on top of the computer
53+
54+
![](./images/wand_storage.png)
55+
56+
Turn it on with the switch. Ensure it is in Continuous mode.
57+
58+
![](./images/wand_switch.png)
59+
60+
If the battery is low, charge it with the cable attached to the computer before using it.
61+
62+
![](./images/charge_wand.png)
63+
64+
Now in the Camera Calibration tab, click the settings icon to check that Auto-Stop is enabled for the wand, and that the rest of the settings match the picture below. Then click Wave All.
65+
66+
![](./images/wand_settings.png)
67+
68+
The screen will now look like this:
69+
70+
![](./images/wand_initial.png)
71+
72+
Each camera needs to receive 3000 wand frames to have a robust calibration, and you will achieve this by waving the wand in the general direction of each camera. Once each camera has seen enough frames, the process will auto-stop.
73+
74+
Out in the FlyLab space, wave the wand around like you are washing a window. Make sure to wave it in the direction of each camera, until all of the lower cameras have filled their progress bars and shine a green light
75+
76+
![Lower wand](./images/lower_wand.gif)
77+
78+
Here is an example of the progress bar on this camera. The red light will turn green once the progress bar is full. By waving the wand in all 6 axes of motion (3 translational and 3 rotational), you will eventually complete the progress bar.
79+
80+
![](./images/lower_camera_progress_bar.png)
81+
82+
During this process, the computer screen will also show the status of each camera
83+
84+
![](./images/wand_in_progress.png)
85+
86+
To get the upper cameras, we attach the wand to a rope, located next to the control room door.
87+
88+
![](./images/rope.png)
89+
90+
Untie the rope from the anchor and lower the end of the rope to ground level.
91+
92+
![](./images/rope_lowered.png)
93+
94+
Then attach the wand through the 3D printed attachment and make sure it is secured.
95+
96+
![](./images/wand_attachment.png)
97+
98+
Raise the wand using the rope and shake the rope up and down to make the wand jump and spin around to get enough coverage on each upper camera.
99+
100+
![](./images/pull_rope.png)
101+
102+
<img src="./images/upper_wand.gif" alt="Upper wand" style="width:30%; max-height:none;">
103+
104+
Each upper camera will light up green once it has seen enough frames.
105+
106+
![](./images/upper_rope_green_camera.png)
107+
108+
Once all cameras have enough detections, the calibration should auto-stop and all camera lights will turn red as shown below, indicating normal operation.
109+
110+
![](./images/complete_camera.png)
111+
112+
The computer screen will look like this
113+
114+
![](./images/wand_finished.png)
115+
116+
## Setting the Origin
117+
118+
After the wand waving process, the origin of the Vicon coordinate frame needs to be set. Go back to the 3D View and you will see that the default origin has been placed at a camera.
119+
120+
![](./images/origin_initial.png)
121+
122+
Take the wand and place it in the yellow tape in the FlyLab.
123+
124+
![](./images/wand_origin.png)
125+
126+
Pan and zoom (left click and right click while moving the mouse) in the 3D View to ensure the wand markers are visible, then click Start Set Origin, then right after click Set Origin.
127+
128+
![](./images/origin_pan_zoom.png)
129+
130+
The origin has now been set at the wand's location, which you can verify in the 3D View.
131+
132+
![](./images/origin_final.png)

docs/flylab/faqs.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
layout: default
3+
title: "Troubleshooting/FAQs"
4+
date: 2025-06-18
5+
math: katex
6+
parent: FlyLab
7+
nav_order: 3
8+
---
9+
10+
<style>
11+
img {
12+
max-height: 400px;
13+
width: auto;
14+
}
15+
</style>
16+
17+
## Troubleshooting/FAQs
18+
19+
Flylab IP 192.168.0.149
20+
21+
[Crazyflie/swarm hover_launch file for IP config](https://github.com/joonlee16/Crazyflie/blob/main/crazyswarm/ros_ws/src/crazyswarm/launch/hover_swarm.launch)
22+
23+
[PX4 Config for IP config](https://github.com/dasc-lab/rover_px4_ros2_jumpstart/blob/main/colcon_ws/src/all_launch/config/config_vicon.yaml)
24+
25+
**Object not being tracked/no Vicon messages?**
26+
27+
Make sure the markers are visible on the Vicon computer.

docs/flylab/flylab.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
layout: default
3+
title: "FlyLab"
4+
date: 2025-06-18
5+
math: katex
6+
has_children: true
7+
has_toc: true
8+
nav_order: 3
9+
---
10+
11+
This guide is designed to walk you through the process of calibrating the Vicon system in the FlyLab and also how to create objects to track. At the end of this section are some common troubleshooting issues/FAQs.
7.73 MB
Loading

docs/flylab/images/bumped.png

64.1 KB
Loading

docs/flylab/images/charge_wand.png

7.08 MB
Loading
6.98 MB
Loading
5.84 MB
Loading
6.99 MB
Loading

docs/flylab/images/lower_wand.gif

8.69 MB
Loading

0 commit comments

Comments
 (0)