No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro foxy. Known supported distros are highlighted in the buttons above.
No version for distro rolling. Known supported distros are highlighted in the buttons above.

Package Summary

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

Repository Summary

Checkout URI https://github.com/nasa/astrobee.git
VCS Type git
VCS Version master
Last Updated 2021-10-01
Dev Status UNMAINTAINED
CI status No Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Package to control the signal lights

Additional Links

No additional links.

Maintainers

  • Astrobee Flight Software

Authors

  • Astrobee Flight Software

\page signal_lights Signal light driver

The signal_lights driver controls the signal lights on the port and starboard PMC. Since the exact behavior of the signal lights is a work-in-progress, this proof of concept driver just illustrates full stack control of the lights.

Like many other drivers, the signal lights are controlled by a proxy library, called 'signal_lights' which acts as an intermediary between high level calls and i2c transactions.

The current ICD supports 5 programs, two of which are implemented:

  • 0: Not available yet
  • 1: Not available yet
  • 2: Not available yet
  • 3: Turn on all pixels to a specified color.
  • 4: Not available yet
  • 5: Turn on a single light at the index.

Using the commandline tool

The color of the light is specified with the red (-r), green (-g) and blue (-b) switches. Acceptable indexes (-d) run from 0 - 43 inclusive. The program is selected with -p and the mode is selected with -m. The mode should always be the default value of 1 unless s shutdown is required.

To turn all lights blue, type the following

rosrun signal_lights signal_lights_tool -r 0 -g 0 -b 128 -p 3

To turn the light at index 5 (the sixth LED) type the following

rosrun signal_lights signal_lights_tool -r 0 -g 128 -b 0 -p 5 -d 5

Using the ROS interface

The signal_lights nodelet provides a single service-based interface for control, located at /hw/sig/config. It takes the same arguments as the commandline tool, where the -d switch maps to the 'arg' message variable.

For example, this turns LED at index 4 to white:

rosservice call /hw/sig/config "{mode: 1, program: 5, brightness: 0, red: 128, green: 128, 
  blue: 128, arg: 4}" 
CHANGELOG
No CHANGELOG found.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

Launch files

  • launch/signal_lights.launch
    • Copyright (c) 2017, United States Government, as represented by the
      • name [default: signal_lights]
      • manager [default: ]

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged signal_lights at answers.ros.org

Package Summary

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

Repository Summary

Checkout URI https://github.com/nasa/astrobee.git
VCS Type git
VCS Version master
Last Updated 2021-10-01
Dev Status UNMAINTAINED
CI status No Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Package to control the signal lights

Additional Links

No additional links.

Maintainers

  • Astrobee Flight Software

Authors

  • Astrobee Flight Software

\page signal_lights Signal light driver

The signal_lights driver controls the signal lights on the port and starboard PMC. Since the exact behavior of the signal lights is a work-in-progress, this proof of concept driver just illustrates full stack control of the lights.

Like many other drivers, the signal lights are controlled by a proxy library, called 'signal_lights' which acts as an intermediary between high level calls and i2c transactions.

The current ICD supports 5 programs, two of which are implemented:

  • 0: Not available yet
  • 1: Not available yet
  • 2: Not available yet
  • 3: Turn on all pixels to a specified color.
  • 4: Not available yet
  • 5: Turn on a single light at the index.

Using the commandline tool

The color of the light is specified with the red (-r), green (-g) and blue (-b) switches. Acceptable indexes (-d) run from 0 - 43 inclusive. The program is selected with -p and the mode is selected with -m. The mode should always be the default value of 1 unless s shutdown is required.

To turn all lights blue, type the following

rosrun signal_lights signal_lights_tool -r 0 -g 0 -b 128 -p 3

To turn the light at index 5 (the sixth LED) type the following

rosrun signal_lights signal_lights_tool -r 0 -g 128 -b 0 -p 5 -d 5

Using the ROS interface

The signal_lights nodelet provides a single service-based interface for control, located at /hw/sig/config. It takes the same arguments as the commandline tool, where the -d switch maps to the 'arg' message variable.

For example, this turns LED at index 4 to white:

rosservice call /hw/sig/config "{mode: 1, program: 5, brightness: 0, red: 128, green: 128, 
  blue: 128, arg: 4}" 
CHANGELOG
No CHANGELOG found.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

Launch files

  • launch/signal_lights.launch
    • Copyright (c) 2017, United States Government, as represented by the
      • name [default: signal_lights]
      • manager [default: ]

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged signal_lights at answers.ros.org

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 eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. 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.
No version for distro kinetic. Known supported distros are highlighted in the buttons above.