-
Notifications
You must be signed in to change notification settings - Fork 123
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
Latency when subscribing to VSLAM topics. #126
Comments
@swapnesh-wani-nvidia Any information on this? |
You are running your Real|Sense D455 camera at 30 fps as indicated here - 'depth_module.profile': '640x360x30', |
I have the same behavior using the realsense launch file so I don't think it's related to the modified launch file. Using that launch file I can confirm the same latency behavior with the following setup. In one terminal attached to the docker container on the Orin run In a second terminal attached to the docker container on the Orin run Finally, in a third terminal attached to the docker container on the Orin run Hope that clears up the "needs info". |
Please clarify if the odometry topic stays at 90fps (desired). Is this not the expected behavior you are seeing? |
The FPS drops initially then returns to 90Hz stable after several seconds. This is an issue because a variety of different ROS operations cause this drop in framerate to occur. For example, checking the frequency of realsense topics (while attached to the running container) with |
An update on this issue. Running with intra-process communication instead of separate nodes seems to fix the issue, and generally things seem to run smoother and more reliably with this setup. Launch file that is tested on the setup in my original comment:
|
Background
Hardware: Jetson Orin Nano Devkit 8Gb + Realsense d455
OS: Jetpack 5.1.2 + Isaac VSLAM Docker Image
Launch File:
Issue
I observe inconsistent performance when subscribing to certain topics indicated by the "Delta between current and previous frame [] is above threshold []" and unstable frequency of Isaac VSLAM ros topics. I can consistently trigger this latency by running the launch file above, and then running
ros2 topic hz /visual_slam/tracking/odometry
. I also (possibly not related) see "Delta between ..." messages when I move the camera around, but this is less consistent. See this video for an example of the issue latency_isaac_vslam.webm.Attempted Solutions
Enabling
jetson_clocks
. At first I thought this might be clock throttling so I tried runningsudo jetson_clocks
, and this reduced some of the "Delta between ..." messages. However, the video above was recorded with jetson clocks running so I do not think it's related to clock throttling.Switching to Cyclone DDS. As mentioned in Causes/Solutions for "Delta between current and previous frame [] is above threshold []" #120, I tried to switch to Cyclone DDS with
export RMW_IMPLEMENTATION=rmw_cyclonedds_cpp
, but found that Isaac VSLAM topics do not seem to publish anything but others do. For example,/camera/infra1/image_rect_raw
has a frequency withros2 topic hz
, but/visual_slam/tracking/odometry
has nothing.The text was updated successfully, but these errors were encountered: