anqixu's profile - activity

Re - parameters: which parameters do you want to get? If you are referring to the warning about MONO8: http://wiki.ros.org/dynamic_reconfigure

Re - calibration: http://wiki.ros.org/camera_calibration

Re - multiple uEye cameras: if you want them to operate independently, then yes you need to duplicate the launch file, and change the node name, camera namespace, and camera ID. If you want to synchronize the exposure of both cameras, see: http://wiki.ros.org/ueye_cam#Camera_S...

uEye cameras use a proprietary communication protocol (and driver daemon), which OpenCV does not support.

Consider using a ROS dirver for uEye (I recommend ueye_cam :D), and also see https://github.com/pal-robotics/aruco...

To inspect the data coming from camera topic / camera_info in terminal:

1. rostopic echo /camera/image_raw (WARNING: possibly will generate a lot of raw ASCII)
2. rostopic echo /camera/camera_info

To visualize the data from camera: rosrun image_view image_view image:=/camera/image_raw

To subscribe to the camera: http://wiki.ros.org/image_transport/T...

The error seems to be caused by camera_calibration_parsers::writeCalibration(<dest yaml="" file="">, <cam name="">, <calib data="">), as seen in ueye_cam/src/ueye_cam_nodelet.cpp, UEyeCamNodelet::saveIntrinsicsFile().

I suspect that there is some write-permission issues / out-of-space issues with /home/rospasta/.ros/camera_info/. Please test and confirm.

It turned out that I made a mistake in MyCode.cfg and used: "from dynamic_reconfigure.parameter_generator import *" instead of "from dynamic_reconfigure.parameter_generator_catkin import *"

Technically, the answer to my question is: 0 -- use the suggested folder structure

For those that are curious, you can make the ps3 gamepad rumble, both in wired and wireless (sixad). I wrote a thin wrapper, which is based on fftest:

https://github.com/anqixu/sixad_rumble

(You will need to identify the proper /dev/input/event# handle associated to your gamepad. I use 'ls'.)

Fixed: https://github.com/anqixu/ueye_cam/co...

Are there any official / public / private websites that provide statistics or analytics regarding download patterns for Debian releases of ROS packages?

Currently there is a bug in ueye_cam's calibration parser, where it loads a yaml file, but parses the format of a Videre INI file instead. This will be fixed very soon. For the time being, you can manually modify the contents of your .yaml file according to the Videre INI specs (yuk, I know, sorry).

From the wiki page, section 2.3:

If you want to downsize the image while preserving the field of view, change one or multiple of the 'sensor_scaling' / 'binning' / 'subsampling' ROS parameters (e.g. set sensor_scaling=2 works in all uEye cameras that I've used).

If however you want to zoom digitally into a portion of the image, you can tweak the 'image_height', 'image_width', 'image_left', and 'image_right' ROS parameters.

Note that you can play with all of these parameters, and more, while running ueye_cam live, using dynamic_reconfigure.

On 12.04 LTS3, I had to do a few non-obvious steps to get the DualShock 3 controller to work in USB: A) run 'sudo apt-get install xserver-xorg-input-joystick'; B) after connecting the gamepad via USB, before or after running joy_node, I had to hold the PS button for 2 seconds to activate it.

My ROS package has been taking longer and longer to compile, so I decided to move all msg/srv/cfg into a separate package. Here's the partial folder structure:

catkin_ws
  src
    mycode_core
      cfg
        MyCode.cfg
    mycode
      src
        MyCode.cpp

The 'mycode' package lists mycode_core as both a compile-time and run-time dependency, and the CMakeLists.txt is configured correspondingly. In mycode/CMakeLists.txt, I'm currently specifying the include dir for the generated cfg headers manually:

include_directories( <...> ${mycode_core_PACKAGE_PATH}/cfg/cpp )

This seems quite inelegant. So I'm wondering if there is a better / recommended approach?

1. manually specify include dir (as described above)
2. in mycode_core/CMakeLists.txt, manually mark cfg/cpp/ headers to be installed under ${CATKIN_PACKAGE_INCLUDE_DESTINATION}
3. do not separate dynamic_reconfigure cfgs into a separate package
4. something else?

master_slaves_rgb8.launch is a special launch file, designed for a hardware-triggered synchronized multi-camera setup. Please see the wiki for additional information if interested. For non-synchronized stereo, please modify rgb8.launch to duplicate 2 instances of cameras, with different IDs.

Please make sure to source your [catkin_workspace]/devel/setup.bash file prior to compiling and running any catkin-based ROS packages, such as ueye_cam. The erroneous behaviors resulting from not sourcing this file appears to be consistent with several of the symptoms reported here.

Since your CMAKE_PREFIX_PATH does not contain the path of your workspace it looks like that you have not sourced the workspace/devel/setup.bash file. Can you make sure to do that and try again?

@Vero: hmm that's very weird. try checking out the fuerte branch and compiling (with rosbuild). Please also confirm that under the path [catkin_ws]/devel/lib, you have the files libueye_cam_nodelet.so libueye_wrapper.so

Your new run shows the correct nodelet type of ueye_cam/ueye_cam_nodelet rather than ueye_cam/include/ueye_cam_nodelet. Also, the default repo branch is for catkin, not rosmake. So either use catkin_make (groovy&up) or switch branch: git clone https://github.com/anqixu/ueye_cam.git --branch fuerte

Re. Update-2): The latest commit changed the topic name to /camera/image_raw. You need to manually edit the launch file if you would to use a different camera namespace. Also, the extended log (pastebin.com/Km2zVU0N) shows you running master_slaves_rgb8.launch. Try rgb8.launch instead.

It appears that your launch file is incorrectly trying to load a nodelet of type "ueye_cam/include/ueye_cam_nodelet" and failing, since the actual nodelet is of the type "ueye_cam/ueye_cam_nodelet" (which has been compiled successfully on your machine, if you look at the rest of the printout).

Please try updating your code from the github repo and trying again.

See: https://github.com/anqixu/ueye_cam/blob/master/launch/rgb8.launch

Hi. I would need to know a bit more info before I can help you out. Please try running rgb8.launch, [IMPORTANT!] connect to the image topic (e.g. by running "rostopic hz /UI122xLE_C/image_raw" on a separate terminal), wait for ~5 sec, and paste the entire output of the roslaunch (e.g. on pastebin.com).

Also, thank you for reporting the c++11 flag compile error; I eagerly upgraded to g++4.7, which supports c++11, and forgot to use the backward-compatible c++0x flag instead.

Edit: the extended log (pastebin.com/Km2zVU0N) shows execution log from running master_slaves_rgb8.launch. In this particular case, only slave2 had a camera connected, and it was configured (in the launch file, see "ext_trigger_mode") to be externally triggered. Assuming that nothing is wired to the camera, then it will spit out garbage images at a unpredictable rate. Please consider using rgb8.launch or bayer_rggb_image_proc.launch for single-camera usage.

It's up now (it was previously in limbo for various reasons). I can't post links, so just check the ROS wiki page.