[Documentation] [TitleIndex] [WordIndex

  Show EOL distros: 

cob_driver: cob_base_drive_chain | cob_camera_sensors | cob_canopen_motor | cob_generic_can | cob_head_axis | cob_hokuyo | cob_hwboard | cob_light | cob_phidgets | cob_relayboard | cob_sick_lms1xx | cob_sick_s300 | cob_sound | cob_undercarriage_ctrl | cob_utilities | cob_voltage_control

Package Summary

cob_phidgets

  • Maintainer status: developed
  • Maintainer: Benjamin Maidel <benjamin.maidel AT ipa.fraunhofer DOT de>
  • Author: Florian Weisshardt
  • License: LGPL
  • Source: git https://github.com/ipa320/cob_driver.git (branch: hydro_release_candidate)
cob_driver: cob_base_drive_chain | cob_bms_driver | cob_canopen_motor | cob_elmo_homing | cob_generic_can | cob_light | cob_mimic | cob_phidgets | cob_relayboard | cob_scan_unifier | cob_sick_lms1xx | cob_sick_s300 | cob_sound | cob_undercarriage_ctrl | cob_utilities | cob_voltage_control

Package Summary

cob_phidgets

  • Maintainer status: developed
  • Maintainer: Benjamin Maidel <benjamin.maidel AT mojin-robotics DOT de>
  • Author: Florian Weisshardt
  • License: Apache 2.0
  • Source: git https://github.com/ipa320/cob_driver.git (branch: kinetic_release_candidate)

Hardware Check

After installation of the phidgets board execute following steps:

  1. login on the PC which is connected to the phidgets board
  2. run "lsusb" in the console

  3. if you find something with phidgets in the printed list follow step 6.
  4. if not unplug and plug in the phidgets board
  5. run "dmesg" and look at the last lines (end)

  6. start roscore

  7. run "relaunch cob_bringup tray_sensors.launch"

  8. check output with "rostopic echo /tray_sensors/range_1"

Error Handling

If you get a message like "operation not permitted" you have probably not the right to open the USB device. Therefore, add an udev rule with:

sudo echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="06c2", MODE="0666", GROUP="dialout"' >>  /etc/udev/rules.d/10-persistent-usb.rules && sudo chmod a+r /etc/udev/rules.d/10-persistent-usb.rules && sudo udevadm control --reload-rules 

Make sure your user is in the group "dialout" with groups.


2024-03-16 12:30