-
Notifications
You must be signed in to change notification settings - Fork 11
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
Setup Orin & ZED Cameras #430
Comments
Some related tasks mainly since the ZED SDK has built in ways to configure the 4 ZED cameras into a single 360-degree image and depth map. Then this depth map could be used and aligned with the LIDAR and RADAR point clouds to determine the transformations that align these with the depth map. |
09/09/2024 Update:Status: Setting up the NVIDIA Jetson ORIN Next Steps:
Update:
|
09/16/2024 Update:Status: Setting up the NVIDIA Jetson ORIN Next Steps:
Update:
|
09/23/2024 Update:Status: Setting up the NVIDIA Jetson ORIN Next Steps:
Update:
|
09/31/2024 Update:Status: Completed ZED Setup and Testing on Orin Next Steps:
Update:
|
10/28/2024 Update:Status: Connecting ZED and ROS Next Steps:
Update:
|
11/4/2024 Update:Status: Connecting ZED and ROS Next Steps:
Update:
|
The new NVIDIA Orin needs to be set up and configured to aggregate images & depth images from the four ZED cameras. Stereolabs (ZED) has a ROS SDK for doing much of the calibration and aggregation from multiple cameras. We should be able to stitch together a birds-eye-view image (often used throughout the industry).
In terms of design, the Orin will receive all the ZED data - and possibly also the LIDAR and RADAR data, do any needed pre-processing (e.g., birds-eye-view image, ground plane removal for lidar, etc) and publish cleaned perception topics to the main computer. To do this, the Orin and main computer will need to be on the same local network to share ROS messages.
This task could be coordinated with a member of the HFE team or done entirely by one person. Either way there will be a lot of hands on.
The text was updated successfully, but these errors were encountered: