Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add throttled/debug logs to AP_DDS and AP_ExternalControl that won't flood the GCS link #28671

Open
Ryanf55 opened this issue Nov 18, 2024 · 0 comments
Open

Add throttled/debug logs to AP_DDS and AP_ExternalControl that won't flood the GCS link #28671

Ryanf55 opened this issue Nov 18, 2024 · 0 comments
Labels
Enhancement ROS

Comments

@Ryanf55
Copy link
Collaborator

Ryanf55 commented Nov 18, 2024 •
edited
Loading

Feature request

Is your feature request related to a problem? Please describe.

We can't communicate errors to a user in ROS without potentially flooding the GCS link.

Motivation: #28429 (comment)

Right now, if external control is rejected (or other errors), you need to find it using GDB, which is hard for flying vehicles.

Describe the solution you'd like

Add either

  • Throttled logs
  • compile-time enabled debug logs that default to off - perhaps AP_DDS_DEBUG_LOGGING_ENABLED

Describe alternatives you've considered

  • no logging (current approach)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement ROS
Projects
DDS/ROS2
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Ryanf55