No version for distro foxy. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. Known supported distros are highlighted in the buttons above.

fadecandy_driver package from fadecandy_ros repo

fadecandy_driver fadecandy_msgs

Package Summary

Tags No category tags.
Version 0.1.2
License Apache License 2.0
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/iron-ox/fadecandy_ros.git
VCS Type git
VCS Version master
Last Updated 2020-07-07
Dev Status DEVELOPED
CI status Continuous Integration : 0 / 0
Released RELEASED
Package Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

ROS driver for fadecandy LED controllers

Additional Links

No additional links.

Maintainers

  • Jon Binney

Authors

No additional authors.

Fadecandy driver

ROS node for controlling LEDs via a fadecandy board. Uses python-usb to talk directly to the board, so it doesn't need the fadecandy server - there are no dependencies on anything in the fadecandy repo. All you should need is a fadecandy board with fadecandy firmware on it.

How to run

Start the node. Depending on permissions, this may need to run as root to talk to the USB device.

rosrun fadecandy_driver fadecandy_node

To make sure everything is working, you can send a test pattern using the example client script.

rosrun fadecandy_driver example_client

Note about how the LEDs are addressed

The fadecandy board has 8 pairs of outputs, numbered 0-7 on the PCB. Each of these can control a single Neopixel LED strip of up to 64 LEDs. In the LEDArray mesage, you can specify color outputs for an arbitrary number of strips. If the "strips" array in the LEDArray has length N, those colors are applied to the first N strips, starting with strip 0 on the board. So if you wanted to provide colors for just strip 0 and strip 5, you would need to include three empty LEDStrip messages in the "strips" message between them.

Within each LEDStrip message you provide a list of color values for each LED. If colors for less than 64 LEDs are provided, the rest are set to (0,0,0) (completely off). Also, the "a" (alpha) values of the colors aren't used.

Finally, the fadecandy board doesn't have any way of knowing how many strips are attached or how long they each are. It just pushes out 64 values for each of the 8 strips.

Configuring linux device permissions

By default, access the Fadecandy USB device in linux using libusb requires running as root. To fix this, copy the rules file from the udev directory of this package into /etc/udev/rules.d.

sudo cp udev/10-fadecandy.rules /etc/udev/rules.d/

Now reload the udev rules.

sudo udevadm control --reload-rules && udevadm trigger

If you have the Fadecandy device plugged in, unplug and replug it. Then make sure that your user has been added to the dialout group. Now you should be able to run without needing root!

CHANGELOG

Changelog for package fadecandy_driver

0.1.2 (2020-07-06)

  • Merge pull request #10 from eurogroep/chore/log-io-error chore: log IO error
  • Merge pull request #9 from eurogroep/fix/rospy-shutdown fix(shutdown): Shutdown gracefully when no connection was set-up
  • Contributors: Rein Appeldoorn

0.1.1 (2020-06-03)

  • Merge pull request #7 from jonbinney/python3-fixes Fixes for python3/noetic compatibility
  • Contributors: Jon Binney

0.1.0 (2020-05-28)

  • Initial release.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged fadecandy_driver at answers.ros.org

fadecandy_driver package from fadecandy_ros repo

fadecandy_driver fadecandy_msgs

Package Summary

Tags No category tags.
Version 0.1.2
License Apache License 2.0
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/iron-ox/fadecandy_ros.git
VCS Type git
VCS Version master
Last Updated 2020-07-07
Dev Status DEVELOPED
CI status Continuous Integration : 0 / 0
Released RELEASED
Package Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

ROS driver for fadecandy LED controllers

Additional Links

No additional links.

Maintainers

  • Jon Binney

Authors

No additional authors.

Fadecandy driver

ROS node for controlling LEDs via a fadecandy board. Uses python-usb to talk directly to the board, so it doesn't need the fadecandy server - there are no dependencies on anything in the fadecandy repo. All you should need is a fadecandy board with fadecandy firmware on it.

How to run

Start the node. Depending on permissions, this may need to run as root to talk to the USB device.

rosrun fadecandy_driver fadecandy_node

To make sure everything is working, you can send a test pattern using the example client script.

rosrun fadecandy_driver example_client

Note about how the LEDs are addressed

The fadecandy board has 8 pairs of outputs, numbered 0-7 on the PCB. Each of these can control a single Neopixel LED strip of up to 64 LEDs. In the LEDArray mesage, you can specify color outputs for an arbitrary number of strips. If the "strips" array in the LEDArray has length N, those colors are applied to the first N strips, starting with strip 0 on the board. So if you wanted to provide colors for just strip 0 and strip 5, you would need to include three empty LEDStrip messages in the "strips" message between them.

Within each LEDStrip message you provide a list of color values for each LED. If colors for less than 64 LEDs are provided, the rest are set to (0,0,0) (completely off). Also, the "a" (alpha) values of the colors aren't used.

Finally, the fadecandy board doesn't have any way of knowing how many strips are attached or how long they each are. It just pushes out 64 values for each of the 8 strips.

Configuring linux device permissions

By default, access the Fadecandy USB device in linux using libusb requires running as root. To fix this, copy the rules file from the udev directory of this package into /etc/udev/rules.d.

sudo cp udev/10-fadecandy.rules /etc/udev/rules.d/

Now reload the udev rules.

sudo udevadm control --reload-rules && udevadm trigger

If you have the Fadecandy device plugged in, unplug and replug it. Then make sure that your user has been added to the dialout group. Now you should be able to run without needing root!

CHANGELOG

Changelog for package fadecandy_driver

0.1.2 (2020-07-06)

  • Merge pull request #10 from eurogroep/chore/log-io-error chore: log IO error
  • Merge pull request #9 from eurogroep/fix/rospy-shutdown fix(shutdown): Shutdown gracefully when no connection was set-up
  • Contributors: Rein Appeldoorn

0.1.1 (2020-06-03)

  • Merge pull request #7 from jonbinney/python3-fixes Fixes for python3/noetic compatibility
  • Contributors: Jon Binney

0.1.0 (2020-05-28)

  • Initial release.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged fadecandy_driver at answers.ros.org

No version for distro kinetic. Known supported distros are highlighted in the buttons above.
No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro indigo. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.