-
 
No version for distro humble. Known supported distros are highlighted in the buttons above.
No version for distro iron. Known supported distros are highlighted in the buttons above.
No version for distro jazzy. 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.0
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 2024-07-03
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

The astrobee package provides system launch functionality.

Additional Links

No additional links.

Maintainers

  • Astrobee Flight Software

Authors

  • Astrobee Flight Software

\page signal Signal behavior

Astrobee has 44 individually addressable LEDs on each PMC. To control the LEDs, patterns specified by the LightFlow programming language are interpreted into messages containing the RGB value of each LED. These messages are sent over ROS to a hardware driver that formats the message into a buffer, which is sent over I2C.

Internal behavior

After receiving a ff_msgs::SignalState message, the behavior node will first process the ID to make sure that it has knowledge of the corresponding LightFlow pattern (the class that holds the patterns is called LightFlowStorage inside of the lightflow_storage.py file). Once the pattern is confirmed to exist and there is not a pattern running, the behavior node begins to interpret the LightFlow and send messages in real time. To send messages at a constant update rate, the behavior node determines the time at which each message needs to be sent. The behavior node then figures out the correct color for each LED, waits until the correct time to send the message, and sends it.

CHANGELOG
No CHANGELOG found.

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

No known dependants.

Launch files

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

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged light_flow at Robotics Stack Exchange

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

Package Summary

Tags No category tags.
Version 0.0.0
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 2024-07-03
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

The astrobee package provides system launch functionality.

Additional Links

No additional links.

Maintainers

  • Astrobee Flight Software

Authors

  • Astrobee Flight Software

\page signal Signal behavior

Astrobee has 44 individually addressable LEDs on each PMC. To control the LEDs, patterns specified by the LightFlow programming language are interpreted into messages containing the RGB value of each LED. These messages are sent over ROS to a hardware driver that formats the message into a buffer, which is sent over I2C.

Internal behavior

After receiving a ff_msgs::SignalState message, the behavior node will first process the ID to make sure that it has knowledge of the corresponding LightFlow pattern (the class that holds the patterns is called LightFlowStorage inside of the lightflow_storage.py file). Once the pattern is confirmed to exist and there is not a pattern running, the behavior node begins to interpret the LightFlow and send messages in real time. To send messages at a constant update rate, the behavior node determines the time at which each message needs to be sent. The behavior node then figures out the correct color for each LED, waits until the correct time to send the message, and sends it.

CHANGELOG
No CHANGELOG found.

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

No known dependants.

Launch files

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

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged light_flow at Robotics Stack Exchange