nros C API
Lightweight ROS 2 client for embedded real-time systems
Loading...
Searching...
No Matches
Data Fields
rclc_action_endpoint_hashes_t Struct Reference

#include <nros_generated.h>

Data Fields

const char * cancel_goal
 
const char * feedback
 
const char * get_result
 
const char * send_goal
 
const char * status
 

Detailed Description

Issue 1913 — the hash each of an action's five endpoints is keyed on.

An Iron+ rmw_zenoh_cpp peer keys every endpoint on its OWN type (the SendGoal / GetResult services, action_msgs/srv/CancelGoal, the FeedbackMessage, action_msgs/msg/GoalStatusArray), so the single type_hash an action carried matched none of them. A NULL member means "use `type_hash`", which is what C generated by an older nros gets: designated initializers zero this trailing field. Members must point at strings with STATIC storage — the generated type support's literals — because a server or client keeps the pointers from init until it registers.

Field Documentation

◆ cancel_goal

const char* rclc_action_endpoint_hashes_t::cancel_goal

action_msgs/srv/CancelGoal service hash.

◆ feedback

const char* rclc_action_endpoint_hashes_t::feedback

<Action>_FeedbackMessage hash.

◆ get_result

const char* rclc_action_endpoint_hashes_t::get_result

<Action>_GetResult service hash.

◆ send_goal

const char* rclc_action_endpoint_hashes_t::send_goal

<Action>_SendGoal service hash.

◆ status

const char* rclc_action_endpoint_hashes_t::status

action_msgs/msg/GoalStatusArray hash.


The documentation for this struct was generated from the following file: