-
Stéphane Yang authored
Moved unit test script to a "example" folder to avoid confusion with "navigation" folder which is the actual implementation Update readmes
Stéphane Yang authoredMoved unit test script to a "example" folder to avoid confusion with "navigation" folder which is the actual implementation Update readmes
Promethe scripts for the drone
Here you can find some Promethe programs to control the drone with the joystick, simulate NN ...
You could also find some hardware files (.hwc, .hwj, etc), those are the different hardwares setup such as the camera or the joystick.
Note: Between cam_usb.hwc and cam_pc.hwc, you have to chose only one on the .dev file (if the script has it). Make sure to comment what you don't want and uncomment what you want.
The programs in "examples" are (the list may be not comprehensive):
- cam_f_out: sends camera input (or any capture device opened in /dev/video*) to f_out (shared memory)
- drone_joyRemote: reads and updates the shared memory according to joystick inputs and checkboxes (added plot for altitude and compass heading control)
- drone_test: using checkboxes, updates the shared memory for several drone actions
- drone_flot: reads input image in f_in, adds a visual control of the drone using optical flow, through shared memory
The main programs are (the list may be not comprehensive):
- navigation: contains multiples scripts that are working together, it reuses cam_f_out, drone_joyRemote and drone_flot (go to the navigation folder for more info)
To modify/compile (coeos) and/or to simulate (promethe) a script, run the right command files (.sh) if they exist. Otherwise, run the following commands:
Coeos
cd <path_to_the_script>
coeos <name_of_the_script>.symb
Promethe (.dev is required if it uses the camera, .gcd is optional)
cd <path_to_the_script>
promethe <name_of_the_script>.{script,res,config,gcd}