IMRCLab / IMRCLab/motion_capture_tracking

Errors with rviz when running motion capture tracking. (ROS2 Foxy + Vicon)

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
83
Forks
44
PR merge metrics
No merged PRs in 30d

Description

I am currently using Vicon and ROS2 Foxy. When I attempt to launch motion_capture_tracking, I get the following error

[INFO] [launch]: All log files can be found below /home/csanchez5/.ros/log/2024-06-04-04-51-40-492812-lnx-me001.ecn.uiowa.edu-1321991
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [motion_capture_tracking_node-1]: process started with pid [1321993]
[INFO] [rviz2-2]: process started with pid [1321995]
[motion_capture_tracking_node-1] logClouds=0
[rviz2-2] [INFO] [1717494701.597764147] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] [INFO] [1717494701.597950942] [rviz2]: OpenGl version: 4.6 (GLSL 4.6)
[rviz2-2] [INFO] [1717494701.713982917] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] [ERROR] [1717494701.775150896] [rviz2]: PluginlibFactory: The plugin for class 'rviz_common/Time' failed to load. Error: According to the loaded plugin descriptions the class rviz_common/Time with base class type rviz_common::Panel does not exist. Declared types are

I do not receive any data from Vicon, RViz does not show any markers or frames and states Frame [world] does not exist, and no /poses topics are created. The hostname/ip in the config file should be correct, as we used to use ros2-vicon-receiver for our tracking.

I have read on other threads that this is because ROS2 Foxy does not support the rviz_common/Time panel. I have tried removing the following lines from the rviz.rviz file in the config folder to resolve this, but had no luck.

- Class: rviz_common/Time
Experimental: false
Name: Time
SyncMode: 0
SyncSource: PointCloud2

Does anyone know how to resolve this? Any information would be appreciated.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the motion_capture_tracking launch on ROS2 Foxy with Vicon and inspect the rviz2 PluginlibFactory error for rviz_common/Time. Review the rviz.rviz file in the config folder, then check whether Vicon data arrives and whether the expected /poses topics and world frame are created. Done means the launch completes without the reported RViz plugin failure and tracking data is visible.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
robotics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.