Skip to content
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

Roboclaw _node process has died. #13

Open
raess1 opened this issue Nov 13, 2017 · 4 comments
Open

Roboclaw _node process has died. #13

raess1 opened this issue Nov 13, 2017 · 4 comments

Comments

@raess1
Copy link

raess1 commented Nov 13, 2017

HI,
I am trying out the roboclaw with ros and i have sucessfully made it work with teleop_twist_keyboard and joy_teleop. The problem is that the Roboclaw_node dies after a while when i have the button "pressed in" or the joystick pressed in.

I get the following error:

process[rosout-1]: started with pid [14545]
started core service [/rosout]
process[roboclaw_node-2]: started with pid [14562]
process[diagnostic_aggregator-3]: started with pid [14563]
Traceback (most recent call last):
File "/home/nvidia/rfbot/src/roboclaw_ros/roboclaw_node/nodes/roboclaw_node.py", line 305, in
node.run()
File "/home/nvidia/rfbot/src/roboclaw_ros/roboclaw_node/nodes/roboclaw_node.py", line 232, in run
rospy.logdebug(" Encoders %d %d" % (enc1, enc2))
TypeError: %d format: a number is required, not NoneType
[roboclaw_node-2] process has died [pid 14562, exit code 1, cmd /home/nvidia/rfbot/src/roboclaw_ros/roboclaw_node/nodes/roboclaw_node.py __name:=roboclaw_node __log:=/home/nvidia/.ros/log/ae2a0626-c880-11e7-8a40-00044b8cfad9/roboclaw_node-2.log].
log file: /home/nvidia/.ros/log/ae2a0626-c880-11e7-8a40-00044b8cfad9/roboclaw_node-2*.log

any suggestions how to fix this?

@vishu2287
Copy link

@raess1 . I am facing same issue. could you fix it? if so please help me to overcome this issue

@raess1
Copy link
Author

raess1 commented Jan 26, 2018

I changed to this instead https://github.com/doisyg/roboclaw_ros

@vishu2287
Copy link

hi @raess1 .
Thank you for your response. i have cloned it and compiled.
there is no error which mentioned about. though there is no response in motor movements. I have also changed odometry ticks and checked under /odom topic. i moved robot manually for meter and found the values are correct.
apart from changes in odometry ticks, is there any thing to do?
I have tested in windows ionstudio. it is working well.

thank you
vishu

@Rafcin
Copy link

Rafcin commented Mar 16, 2019

This Doisyg node you posted also fails to work. It has trouble reading data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants