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
unable to check for odometry and telemetry data #3
Comments
Yes this will all be apart of the C++ driver as soon as my classes slow down a bit lol. As for as the /odom you should be seeing that. Could you send me any configuration data you have such as your launch file and the topics. |
Hi for now I’m just testing the node you wrote and when I use rostopic echo /odom no data is displayed, I'm just starting to learn ROS :( sorry good luck with you classes Henry Date: Tue, 12 Apr 2016 06:02:27 -0700 Yes this will all be apart of the C++ driver as soon as my classes slow down a bit lol. As for as the /odom you should be seeing that. Could you send me any configuration data you have such as your launch file and the topics. — |
Well welcome to ROS and the community. It can be a bit daunting at first but you will catch on quick. Here are a few things that might help you in the future.
As for your problem. You need to figure out if any data is being read by the encoders. Run the ION MC software and see that the encoders are working and recording a change in position. If that is working then place rospy.loginfo statements in the code to print out the raw values of the encoders. If that does not just keep placing the rospy.loginfo statements until you see where things are not working. Now you know where things stop working. At this point let me know what you find, this could be a bug I don't know about. FYI you will be changing this file. |
HI me first timer with python and after not developing for more than 15 years, took me long time trying to get this . anyway :), so I had add rospy.loginfo and rospy.logdebug, across all functions and classes definitions funtions, then I ran rqt_console, and I couldn’t see any indication of those being used. the only part I can see are vr_ticks:%d vl_ticks: %d on line 274, and I got the impression that the function publish_odom is not used, I also introduced an error in the class definition function def update and at running time this was not block the program I'm not sure if this make sense :) Thanks Date: Wed, 13 Apr 2016 07:11:16 -0700 Well welcome to ROS and the community. It can be a bit daunting at first but you will catch on quick. Here are a few things that might help you in the future. This is a cheat sheet that is good to have, make sure and download the catkin version https://github.com/ros/cheatsheet/releases/tag/0.0.1 I really liked this book. And of course the tutorials. http://wiki.ros.org/ROS/Tutorials As for your problem. You need to figure out if any data is being read by the encoders. Run the ION MC software and see that the encoders are working and recording a change in position. If that is working then place rospy.loginfo statements in the code to print out the raw values of the encoders. If that does not just keep placing the rospy.loginfo statements until you see where things are not working. Now you know where things stop working. At this point let me know what you find, this could be a bug I don't know about. FYI you will be changing this file. https://github.com/sonyccd/roboclaw_ros/blob/master/roboclaw_node/nodes/roboclaw_node.py — |
All functions are used. Add output="screen" to line 12 before the > in file That will print all the messages to the screen for you to see. |
yes, I can see the output messages, like this one [INFO] [WallTime: 1460728452.287377] Did not get comand for 1 second, stopping I had add the log_level=rospy.DEBUG on line 156 add load of rospy.loginfo("message",data to log) (i.e rospy.loginfo("Encoder left ticks",left_ticks)) but still no see where things break, I starting to debug line by line, so I'm in the quest :) Thanks All functions are used. Add output="screen" to line 12 before the > in file https://github.com/sonyccd/roboclaw_ros/blob/master/roboclaw_node/launch/roboclaw.launch That will print all the messages to the screen for you to see. — |
Ok let me know if you find where it is stoping. I broke my roboclaw and won't have the new one for a week. When I get it I will see if I can find where this problem is coming from. |
I got some debugging done on the def cmd_vel_callback(self, twist) can't get logs messages Date: Wed, 20 Apr 2016 05:24:45 -0700 Ok let me know if you find where it is stoping. I broke my roboclaw and won't have the new one for a week. When I get it I will see if I can find where this problem is coming from. — |
Like you see no messages from ros log at all? |
that is correct, no ros logs Date: Fri, 29 Apr 2016 05:40:16 -0700 Like you see no messages from ros log at all? — |
Please send me your ros launch file. |
Date: Fri, 29 Apr 2016 06:21:31 -0700 Please send me your ros launch file. — |
I mean paste it in the response lol |
oops sorry I'm using the launch file you created
I mean paste it in the response lol — |
Ok can you figure out that point when the logs stopped, everything here looks fine. |
can we do a skype session, i think will be more efficient :) |
Can I finish exams first lol |
sure, good luck on your exams :) Date: Mon, 2 May 2016 07:09:03 -0700 Can I finish exams first lol — |
There is a typo in roboclaw_node.py line 180: "tick_per_meter" must be "ticks_per_meter" and I realized that code is not reaching to line 232. I cannot get odom messages. So I changed the line 231 to this: I'm not an python expert but I couldn't understand what this line is supposed to do? Hope this helps, it works for me. |
Ok I am back in the loop of things. Thanks for catching that I will fix that now. ! If that fixes the problem please close the issue or lets keep talking. |
Hi, I can confirm that the changes on line 232 solves the issue I got odometry data now :) Thank you |
Will push changes tonightish |
Were these change pushed? I have the same issues... |
I'm unable to see the /odom data when using the node, also it is not possible to see other status conditions from the controller (i.e battery status and Voltage, temperature) and to set up an E-stop signal
The text was updated successfully, but these errors were encountered: