Hello,
The camera feed provided in RViz and rqt_image_view seems to be rotated by 90 degrees (on the photo below, I’m standing on the left side of the robot pointing forward). In the robot.yaml, the Raspicam’s position is configured as ‘upward’, as it should be. I’m using the default calibration files for the Raspberry Pi Camera 2.1. The Raspberry Pi Camera 2.1 is mounted upward and is oriented as per the instructions. I’m aware that the camera is rotated by default, but I’ve only seen a rotation of 180 degrees, not 90.
When trying to create map fiducials are displayed perpendicular to the ground level and while rotating, rviz starts to lose location of the fiducials and display them elsewhere as shown on the last picture. I’m assumng it’s due to camera rotation. Can someone help me with that?
Hmm, I think @anfederman had some similar issues recently, maybe he can help.
It definitely looks like the urdf is wrong there, but checking the extrinsics file for upward it seems to be correct at least. The rotation should start off with the ribbon cable down, camera facing forward. So the specified pitch: -1.57 and yaw: -1.57 ought to rotate it up and to the side as you have it mounted.
It may be more that the launch config is ignoring the /etc yaml file and is still using the default forward config. I think we’ve had such problems before but it should’ve been fixed at some point. I would suggest editing the default yaml file in your cloned magni_robot repo and set the value to upward there, and see if anything changes.
I forgot to mention that I’m using ROS Kinetic with Ubuntu 16.04, so I dont have any extrinsics directory or files. I added more permissions for robot.yaml and it resulted in a temporary rotation of aruco codes in rviz to the ceiling level (but tilted), but after some time the orientation suddenly changed back to the previous one. Could you give me some advice on where to find the default yamls file or extrenics file?
After launching simple_navigation.launch it says “Parametr change detected” and it worries me.
Also 2D NavGoal doesn’t work, and there is no respons from the robot, I assumed it could be fault of bad rotation of aruco codes but robot doesnt even move a little.
There is no camera rotation in configuration file and it cannot be added because it results in errors while launching simple_navigation
The easiest thing to try is using the Noetic image, but if that isn’t possible, using the upward parameters from the Noetic release.
Hmm. Well as Alan points out, it would be recommended to switch over to noetic since we can only offer limited support for kinetic (none of us are really using it anymore), but if that’s not possible for you here’s what I can think of:
First make sure that all your repos are cloned to kinetic-devel or indigo-devel, the default branches are typically noetic-devel now and are often not backwards compatible due to the python 3 migration.
There is no camera rotation in configuration file and it cannot be added because it results in errors while launching simple_navigation
The system for defining that was indeed different back then, I think you should be able to find the rotation hardcoded in one of the xacro files in magni_description. Doing a grep -r "upward" . will probably find it faster than I can look it up.
Instead of changing the default_yaml, the changes to the default need to be specified in the default_conf variable in launch_core.py script in magni_bringup.
After launching simple_navigation.launch it says “Parametr change detected” and it worries me.
I think that’s a move_basic setup message, probably just a red herring.
