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.

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

add interface for warning, error and report #13

Closed

Conversation

mamueluth
Copy link
Member

@mamueluth mamueluth commented Jan 11, 2024

Add report interfaces for emergency stop, error and warning:

  • The available report interfaces are: EMERGENCY_STOP_SIGNAL, ERROR_SIGNAL, ERROR_SIGNAL_MESSAGE,WARNING_SIGNAL and WARNING_SIGNAL_MESSAGE

The component interface (actuator_inteface, sensor_intefrace, system_inteface) creates and stores them locally. The interfaces are named like <hardware_name>/<report_interface_type>. E.g. if hardware is called rrbot -> interface for WARNING_SIGNAL is called: rrbot/WARNING_SIGNAL. Later with variant support the interfaces will hold following datatypes:

  • Emergency Stop (bool)
  • Error Code (vector(32))
  • Warning Code (vector(32))
  • Error Message (vector<string(128)>(32)
  • Warning Message (vector<string(128)>(32)

Where the <error/warn>message_interfaces holds the error/warn message at position X for the <error/warn>interface's error signal at position X .

Copy link
Member

@destogl destogl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are proposing to go with variants immediately. This is OK, but then we should do it properly. Variant support should be anyway done separately.

That is the reason why I would not go with variants at first, but map everything to doubles.

Also, I am missing tests here to see how this actually works.

@mamueluth mamueluth closed this Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants