Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

have you tired grabbing the latest version of RosAria today? A fix has recently been applied. If so and you still are having problems, post the output of rosrun rosaria RosAria and I'll see what I can do for you. :)

have Have you tired grabbing the latest version of RosAria from github today? A fix has recently been applied. applied for this kind of issue: https://github.com/amor-ros-pkg/rosaria

If so and you are still are having problems, post the output of rosrun rosaria RosAria and I'll see what I can do for you. :):)

Have you tired grabbing the latest version of RosAria from github today? A fix has recently been applied for this kind of issue: https://github.com/amor-ros-pkg/rosaria

There are a couple ways to set the TicksMM: * dynamic_reconfigure * launch file * @launch _TicksMM:=XXX * There is a tool that lets you change the value in the robot's EEPROM from adept (I dont remember what it's called but you can find it on their wiki)

If you are still are having problems, post the output of rosrun rosaria RosAria and I'll see what I can do for you. :)

Have you tired grabbing the latest version of RosAria from github today? A fix has recently been applied for this kind of issue: https://github.com/amor-ros-pkg/rosaria

There are a couple ways to set the TicksMM: * dynamic_reconfigure * TicksMM:

  • dynamic_reconfigure
  • launch file * file
  • @launch _TicksMM:=XXX * _TicksMM:=XXX
  • There is a tool that lets you change the value in the robot's EEPROM from adept (I dont remember what it's called but you can find it on their wiki)

If you are still are having problems, post the output of rosrun rosaria RosAria and I'll see what I can do for you. :)

Have you tired grabbing the latest version of RosAria from github today? A fix has recently been applied for this kind of issue: https://github.com/amor-ros-pkg/rosaria

There are a couple ways to set the TicksMM:

  • dynamic_reconfigure
  • launch file
  • @launch via _TicksMM:=XXX
  • There is a tool that lets you change the value in the robot's EEPROM from adept (I dont remember what it's called but you can find it on their wiki)

If you are still are having problems, post the output of rosrun rosaria RosAria and I'll see what I can do for you. :)

Have you tired grabbing the latest version of RosAria from github today? A fix has recently been applied for this kind of issue: https://github.com/amor-ros-pkg/rosaria

There are a couple ways to set the TicksMM:

  • dynamic_reconfigure
  • launch file
  • @launch via _TicksMM:=XXX
  • There is a tool that lets you change the value in the robot's EEPROM from adept (I dont remember what it's called but you can find it on their wiki)

When rosaria launches, it will set TicksMM et al from the ROS parameter server iif those parameters exist (such as being set by hand or from a launch file). If the parameters are unset when rosaria starts up, it will read the values from the robot's EEPROM. The parameters should persist between launches of rosaria, as long as roscore is not shut down.

If you are still are having problems, post the output of rosrun rosaria RosAria and I'll see what I can do for you. :)

Update RosAria

Have you tired grabbing the latest version of RosAria from github today? A fix has recently been applied for this kind of issue: https://github.com/amor-ros-pkg/rosaria

There are a couple ways to set the TicksMM:Set TicksMM et al:

  • dynamic_reconfigure
  • launch file
  • @launch via _TicksMM:=XXX
  • There is a tool that lets you change the value in the robot's EEPROM from adept (I dont remember what it's called but you can find it on their wiki)

When rosaria launches, it will set TicksMM et al from the ROS parameter server iif those parameters exist (such as being set by hand or from a launch file). If the parameters are unset when rosaria starts up, it will read the values from the robot's EEPROM. The parameters should persist between launches of rosaria, as long as roscore is not shut down.

Test robot motion with:

$ rostopic pub -1 /RosAria/cmd_vel geometry_msgs/Twist '{linear:  {x: 0.05, y: 0.0, z: 0.0}, angular: {x: 0.0, y: 0.0, z: 0.0}}'

If you are still are having problems, post the output of rosrun rosaria RosAria and I'll see what I can do for you. :)

Update RosAria

Have you tired grabbing the latest version of RosAria from github today? A fix has recently been applied for this kind of issue: https://github.com/amor-ros-pkg/rosaria

Set Launch RosAria

In a terminal, run the ROS master server:

$ roscore

In another terminal, run the robot driver (RosAria):

$ rosrun rosaria RosAria

In another terminal, verify topics are being published:

$ rostopic list

If you don't see any topics listed, something is wrong with your ROS Environment settings. http://wiki.ros.org/ROS/Tutorials/InstallingandConfiguringROSEnvironment

TicksMM et al:

When rosaria launches, it will set TicksMM et al from the ROS parameter server iif they are set. If the parameters are not set, it will read the values from the robot's EEPROM and set them. There are a few ways to tune them if needed:

  • dynamic_reconfigure
  • launch file
  • @launch via _TicksMM:=XXX
  • There is a tool that lets you change the value in the robot's EEPROM from adept (I dont remember what it's called but you can find it on their wiki)

When rosaria launches, it will set TicksMM et al from the ROS parameter server iif those parameters exist (such as being set by hand or from a launch file). If the parameters are unset when rosaria starts up, it will read the values from the robot's EEPROM. The parameters should persist between launches of rosaria, as long as roscore is not shut down.

Test robot motion with:

$ rostopic pub -1 /RosAria/cmd_vel geometry_msgs/Twist '{linear:  {x: 0.05, y: 0.0, z: 0.0}, angular: {x: 0.0, y: 0.0, z: 0.0}}'

* Still having problems? *

If you are still are having problems, post the output of rosrun rosaria RosAria and I'll see what I can do for you. :)