mirror of
https://github.com/CopterExpress/clover.git
synced 2026-05-26 11:43:25 +00:00
* builder: Use 64-bit Raspberry Pi OS * travis: Use 64-bit builder * builder: Don't try to install Melodic packages on Noetic * clover: Use package version 3, update dependencies * travis: Enable Noetic build * standalone_install: Auto-select Python, ROS distro * builder: Use variable substitution for ROS_DISTRO * builder: Add Noetic package definitions * builder: Use variable substitution for validation * aruco_pose, clover: Allow compiling against OpenCV 3 and 4 * builder: Add proper Noetic repository * builder: Don't force Tornado version Assume rosbridge_suite depends on the right one. * builder: Install packages for Python 3 * builder/test: Use Python3 interpreter for ROS tests TODO (?): add tests for Python2? * builder: Use Python 3 syntax for Python 3 tests * builder: Install rpi_ws281x for Python3 * standalone_install: Use proper Python for pytest * builder: Install espeak for python3 * builder: Use proper path for roscore * builder: Install rosdep, etc. for python3 * builder: Run Clever/Clover test with Python3 * builder: Use Python3 for Clever compat layer * builder: Enable OpenCV 4.2 repository * builder: Force versions for ROS packages that use OpenCV Also, hold their versions so that they don't get updated for no reason. * aruco_pose/draw: Replace OpenCV projection code with a rewrite * builder: Don't try to install compressed_transport twice * clover: Fix importing urllib for Python3 * aruco_pose, clover: Expose Python scripts through CMake * clover/selfcheck: Be more python3-compatible This is basically commita01d199890from buster-python3, not sure if it aged well. * roswww_static: Add python script installation * clover_blocks: Use Python3 syntax for exec * aruco_pose: Remove unused code * Melodic => Noetic in some docs * docs: add 0.22 migration article * docs: remove unneeded comment * docs: python 3 updates * docs: python 3 update in auto_setup article * docs: add ROS Noetic transition note * aruco.launch: add placement, length and map arguments * genmap.py: add -o argument for output file name * docs: use -o argument of genmap.py * simple_offboard: correctly check manual control timeout, separate it from kill switch check * blocks: force led_leds index to int * docs: update and fix 0.22 migration articles * blocks: fix set_leds with color-typed argument * aruco_gen: Open file in binary mode for Python3 compatibility * clover: Use proper variable in aruco.launch * led: change default number of leds to 72 * aruco_pose: Make sure there are no undefined symbols Also, compile in apriltag_quad_thresh.cpp - it contains some of the functions referenced in aruco.cpp, which would otherwise be undefined. * aruco_pose: Make vendored library compatible with older OpenCVs * aruco_pose, clover: Reduce the amount of OpenCV libs requested * aruco_pose, clover: Move subscriptions to the end of init * aruco_pose: Don't expose vendored library symbols * aruco_pose: Simplify dynamic parameter callback setting * builder: Build with debug symbols * clover: Attempt to respawn dying nodelets * Change Raspberry Pi OS to latest armhf, use packages.coex.tech as a source * Add CRYPTOGRAPHY_DONT_BUILD_RUST=1 * Fix Node.js installation * image: use older CMake (3.13.4-1) Fixing https://travis-ci.org/github/CopterExpress/clover/jobs/764367665#L6984 * image: update Raspberry Pi OS to 2021-03-04 * image: bring back moving ld.so.preload out of the way while building * Fix pthreads ld error * Try to fix pthreads ld error * Another attempt to fix pthreads ld error * Yet another attempt to fix pthreads ld error * Try to fix * Be verbose * Temporarily disable rc and camera_markers building * Fix standalone-install * Revert "Temporarily disable rc and camera_markers building" This reverts commite119220e91. * Try to fix * Try to fix * Revert "image: use older CMake (3.13.4-1)" This reverts commitdf28da0060. * Revert "Revert "image: use older CMake (3.13.4-1)"" This reverts commita28c774e8f. * Verbosity * Debugging * More debugging * Display all CMake variables * Try to fix * Another try to fix * Revert "Another try to fix" This reverts commit5a4c3a0da7. * Another try to fix * And another * And yet another * Continue... * Cleanup * Sources lists cleanup * More cleanup * Restore .git directory in clover repo * Fix building documentation * Fix documentation building in image * Trigger build to update ws281x package * Test * Disable unneeded hack * Disable hack * image: add cmake-modules package * www: add viewing clover.err file from web interface * Remove hacks * Show nodelet version * docs: add packages article * image: add image-view package for recording video from topics * Minor fix * CI: add Docker authentication on image build * CI: fix Bash syntax * CI: fix authentication in Docker * CI: move Melodic build and editorconfig-lint to GitHub Actions (#331) * Create main.yml * Update main.yml * Disable native Melodic build in Travis * Run editorconfig-lint in Actions * Let wget be less verbose * Test * Test ok * Disable editorconfig-lint in Travis * docs: add links to hardware sources * CI: move image building to GitHub actions (#335) * Start working on building image in GitHub actions * Trigger GitHub on push to any branch * Fix TRAVIS_TAG * Add compress image step * Disable image build in Travis * Add upload image step * Fix compress image * Fix * Fix * Minor fix * Trigger build on tag * Show images sizes not in human format * Upload only built image * Make prerelease * Upload assets on release not on tags * readme: change build badge to GitHub Actions * readme: add support chat badge * CI: move documentation building to GitHub Actions (#337) * CI: change docs target branch to actions * CI: change docs target branch to master * CI: use gh-pages target branch for docs * CI: split up to several workflows * CI: remove .travis.yml * CI: change apt to apt-get * CI: push documentation site to the main repo * builder: less verbosity * CI: add new key for apt Fixing https://github.com/CopterExpress/clover/runs/2700356960#step:3:74 * Add Noetic building to CI * Add test for QR recognition * Fix * Move QR recognition test to a separate file * Fix QR recognition code for Python 3 * Import SetLEDs, LEDStateArray, LEDState in tests * Add more imports to tests (from documentation) * Fix permissions * Fix standalone-install for Python 2 * Fix QR recognition test * Don’t use ROS for QR recognition test * docs: remove non-working example * Make v4l2 device file an argument in main_camera.launch * Wait for v4l2 device before launching the camera driver * Use exec in waitfile * Transfer main camera nodelet manager to main_camera.launch * Update cv_camera version to 0.5.1 * docs: minor fix * Revert cv_camera to 0.5.0 * Update Raspberry Pi OS to 2021-05-07 * docs: add link to the last ROS Melodic version. Co-authored-by: Alexey Rogachevskiy <sfalexrog@gmail.com>
166 lines
5.8 KiB
Markdown
166 lines
5.8 KiB
Markdown
# Working with the camera
|
|
|
|
> **Note** In the image version **0.20** `clever` package was renamed to `clover`. See [previous version of the article](https://github.com/CopterExpress/clover/blob/v0.19/docs/en/camera.md) for older images.
|
|
|
|
Make sure the camera is enabled in the `~/catkin_ws/src/clover/clover/launch/clover.launch` file:
|
|
|
|
```xml
|
|
<arg name="main_camera" default="true"/>
|
|
```
|
|
|
|
Also make sure that [position and orientation of the camera](camera_setup.md) is correct.
|
|
|
|
The `clover` service must be restarted after the launch-file has been edited:
|
|
|
|
```(bash)
|
|
sudo systemctl restart clover
|
|
```
|
|
|
|
You may use rqt or [web_video_server](web_video_server.md) to view the camera stream.
|
|
|
|
## Troubleshooting
|
|
|
|
If the camera stream is missing, try using the [`raspistill`](https://www.raspberrypi.org/documentation/usage/camera/raspicam/raspistill.md) utility to check whether the camera works.
|
|
|
|
First, stop the `clover` service:
|
|
|
|
```bash
|
|
sudo systemctl stop clover
|
|
```
|
|
|
|
Then use `raspistill` to capture an image from the camera:
|
|
|
|
```bash
|
|
raspistill -o test.jpg
|
|
```
|
|
|
|
If it doesn't work, check the camera cable connections and the cable itself. Replace the cable if it is damaged. Also, make sure the camera screws don't touch any components on the camera board.
|
|
|
|
## Camera parameters
|
|
|
|
Some camera parameters, such as image size, FPS cap, and exposure, may be configured in the `main_camera.launch` file. The list of supported parameters can be found [in the cv_camera repository](https://github.com/OTL/cv_camera#parameters).
|
|
|
|
Additionally you can specify an arbitrary capture parameter using its [OpenCV code](https://docs.opencv.org/3.3.1/d4/d15/group__videoio__flags__base.html). For example, add the following parameters to the camera node to set exposition manually:
|
|
|
|
```xml
|
|
<param name="property_0_code" value="21"/> <!-- property code 21 is CAP_PROP_AUTO_EXPOSURE -->
|
|
<param name="property_0_value" value="0.25"/> <!-- property values are normalized as per OpenCV specs, even for "menu" controls; 0.25 means "use manual exposure" -->
|
|
<param name="cv_cap_prop_exposure" value="0.3"/> <!-- set exposure to 30% of maximum value -->
|
|
```
|
|
|
|
## Computer vision
|
|
|
|
The [SD card image](image.md) comes with a preinstalled [OpenCV](https://opencv.org) library, which is commonly used for various computer vision-related tasks. Additional libraries for converting from ROS messages to OpenCV images and back are preinstalled as well.
|
|
|
|
### Python
|
|
|
|
Main article: http://wiki.ros.org/cv_bridge/Tutorials/ConvertingBetweenROSImagesAndOpenCVImagesPython.
|
|
|
|
An example of creating a subscriber for a topic with an image from the main camera for processing with OpenCV:
|
|
|
|
```python
|
|
import rospy
|
|
import cv2
|
|
from sensor_msgs.msg import Image
|
|
from cv_bridge import CvBridge
|
|
|
|
rospy.init_node('computer_vision_sample')
|
|
bridge = CvBridge()
|
|
|
|
def image_callback(data):
|
|
cv_image = bridge.imgmsg_to_cv2(data, 'bgr8') # OpenCV image
|
|
# Do any image processing with cv2...
|
|
|
|
image_sub = rospy.Subscriber('main_camera/image_raw', Image, image_callback)
|
|
|
|
rospy.spin()
|
|
```
|
|
|
|
To debug image processing, you can publish a separate topic with the processed image:
|
|
|
|
```python
|
|
image_pub = rospy.Publisher('~debug', Image)
|
|
```
|
|
|
|
Publishing the processed image (at the end of the image_callback function):
|
|
|
|
```python
|
|
image_pub.publish(bridge.cv2_to_imgmsg(cv_image, 'bgr8'))
|
|
```
|
|
|
|
The obtained images can be viewed using [web_video_server](web_video_server.md).
|
|
|
|
#### Retrieving one frame
|
|
|
|
It's possibly to retrieve one camera frame at a time. This method works slower than normal topic subscribing and should not be used when it's necessary to process camera images continuously.
|
|
|
|
```python
|
|
import rospy
|
|
from sensor_msgs.msg import Image
|
|
from cv_bridge import CvBridge
|
|
|
|
rospy.init_node('computer_vision_sample')
|
|
bridge = CvBridge()
|
|
|
|
# ...
|
|
|
|
# Retrieve a frame:
|
|
img = bridge.imgmsg_to_cv2(rospy.wait_for_message('main_camera/image_raw', Image), 'bgr8')
|
|
```
|
|
|
|
### Examples
|
|
|
|
#### Working with QR codes
|
|
|
|
> **Hint** For high-speed recognition and positioning, it is better to use [ArUco markers](aruco.md).
|
|
|
|
To program actions of the copter for the detection of [QR codes](https://en.wikipedia.org/wiki/QR_code) you can use the [pyZBar](https://pypi.org/project/pyzbar/). This lib is installed in the last image for Raspberry Pi.
|
|
|
|
QR codes recognition in Python:
|
|
|
|
```python
|
|
import rospy
|
|
from pyzbar import pyzbar
|
|
from cv_bridge import CvBridge
|
|
from sensor_msgs.msg import Image
|
|
|
|
bridge = CvBridge()
|
|
|
|
rospy.init_node('barcode_test')
|
|
|
|
# Image subscriber callback function
|
|
def image_callback(data):
|
|
cv_image = bridge.imgmsg_to_cv2(data, 'bgr8') # OpenCV image
|
|
barcodes = pyzbar.decode(cv_image)
|
|
for barcode in barcodes:
|
|
b_data = barcode.data.decode("utf-8")
|
|
b_type = barcode.type
|
|
(x, y, w, h) = barcode.rect
|
|
xc = x + w/2
|
|
yc = y + h/2
|
|
print("Found {} with data {} with center at x={}, y={}".format(b_type, b_data, xc, yc))
|
|
|
|
image_sub = rospy.Subscriber('main_camera/image_raw', Image, image_callback, queue_size=1)
|
|
|
|
rospy.spin()
|
|
```
|
|
|
|
The script will take up to 100% CPU capacity. To slow down the script artificially, you can use [throttling](http://wiki.ros.org/topic_tools/throttle) of frames from the camera, for example, at 5 Hz (`main_camera.launch`):
|
|
|
|
```xml
|
|
<node pkg="topic_tools" name="cam_throttle" type="throttle"
|
|
args="messages main_camera/image_raw 5.0 main_camera/image_raw_throttled"/>
|
|
```
|
|
|
|
The topic for the subscriber in this case should be changed for `main_camera/image_raw_throttled`.
|
|
|
|
## Video recording
|
|
|
|
To record a video you can use [`video_recorder`](http://wiki.ros.org/image_view#image_view.2Fdiamondback.video_recorder) node from `image_view` package:
|
|
|
|
```bash
|
|
rosrun image_view video_recorder image:=/main_camera/image_raw
|
|
```
|
|
|
|
The video file will be saved to a file `output.avi`. The `image` argument contains the name of the topic to record.
|