tommyo's profile - activity

Some packages were held back by the package manager. Now everything seems to be up to date but some transforms are missing.

The package version is 0.6.4-0trusty-20160110-105926-0800, and the parameter files seems to be there.

Can anybody shine some light on this error?

Exception in thread "main" org.ros.exception.RosRuntimeException: Unable to instantiate node: TestNode at org.ros.RosRun.main(RosRun.java:60) Caused by: java.lang.IllegalAccessException: Class org.ros.internal.loader.CommandLineLoader can not access a member of class TestNode with modifiers "" at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:95) at java.lang.Class.newInstance0(Class.java:366) at java.lang.Class.newInstance(Class.java:325) at org.ros.internal.loader.CommandLineLoader.loadClass(CommandLineLoader.java:240) at org.ros.RosRun.main(RosRun.java:54)

Edit: Apparently roslaunch needs the class(es) to have public visibility.

I get the following error when building rosjava after I pulled just now:

:rosjava_bootstrap:jar
:rosjava_messages:generateSources
:rosjava_messages:compileJava
/home/tommy/my_workspace/rosjava_core/rosjava_messages/build/generated-src/test_rosjava_jni/TestDataTypes.java:52: getByte() is already defined in test_rosjava_jni.TestDataTypes
  std_msgs.Byte getByte();
                ^
/home/tommy/my_workspace/rosjava_core/rosjava_messages/build/generated-src/test_rosjava_jni/TestDataTypes.java:54: getByteV() is already defined in test_rosjava_jni.TestDataTypes
  java.util.List<std_msgs.Byte> getByteV();

Is there something I'm not seeing or is this a bug?

Hi, I am trying to get the cob_bringup package to work on ubuntu 10.04. I have installed the system according to the instructions found here http://www.ros.org/wiki/Robots/Care-O-bot/electric. Additional packages are installed from apt or cloned/checked out from their repositories.

When running $ roslaunch cob_bringup_sim robot.launch a bunch of includes fail due to the absence of .../ros/... in some of the paths. I was able to get around this but if fails with this error msg:

parent link 'arm_7_link' of joint 'sdh_palm_joint' not found.  The Boxturtle urdf parser used to automatically add this link for you, but this is not valid according to the URDF spec. Every link you refer to from a joint needs to be explicitly defined in the robot description. To fix this problem you can either remove this joint from your urdf file, or add "<link name="arm_7_link" />" to your urdf file

(Note that is does not specify any path)

Is there some better way of getting the system up and running? We have tried installing from source but every time that ends up much worse. The same goes for newer versions of ubuntu (among others).

Thanks.

Now I get it, and it works fine. Thank you!

Sorry, I am kind of lost when it comes to visualization and the like. What is the simplest thing that could pass as a valid frame? At this point the scanner is just sitting on the desk with no odometry or maps available. Is it possible visualize the environment around a fixed scanner?

I'm not sure what you're getting at, but i found this in the output: frame_id: '' The publishing node a bridge between another system and ROS so if something needs to be added I'm open to that. Thanks.

Is it possible to visualize a topic of type sensor_msgs/LaserScan using rviz? Currently it complains about not having any frame (which is true, I just have the scan data)... Is there a better way?

Thanks in advance.

Hi, we seem to be having some problems with the emergency stops.

This is our conclusion after some trail and error:

• The red switch must be set to '0'. The wireless emergency stop is now active. On '1' the emergency stop remains triggerd and unreleasable.

• The button emergency stop cannot be reset using the key. We need to activate the wireless emergency stop and then reset it on the remote. The base is now able to initiatialize again.

As far as we can remember this is not the way it was demonstrated. We would really appreciate it if anyone could shine some light on this.

Thanks in advance!

Hi, we are having some problems with the rob@work (care-o-bot base) platform. The base is not moving.

When all wheels report as ok after/during init they all homes fine, but the only response to input from the joystick is a approx. 90 degree turn of the wheels (steering-wise). Then they are dead. There are no movement at all on the drive motor.

This happens at times, other times some motors will report 'failure latched' or 'undervoltage'. We have tried multiple times with both battery packs fully charged, but we always get the same kind of errors.

Thanks for any input.

I am currently trying to get the msg definition from a running ros system. My current solution consists of recursively examining the ROS_PACKAGE_PATH and reading all the .msg files. Not pretty.

Is there any special reason one cannot get at the (private) TopicDescription in the TopicDeclarations accessible through the MasterStateClient? Or is this just not a feature yet?

Is there a better way to do it?