implement robot state publishers (charge, etc) #2

Closed
opened 2021-05-14 14:04:04 +02:00 by wkwolek · 1 comment
Owner
  • /PIONIER6/RosAria/battery_recharge_state [std_msgs/Int8]
  • /PIONIER6/RosAria/battery_state_of_charge [std_msgs/Float32]
  • check what is the recharge state
  • figure out latching for recharge state
  • /PIONIER6/RosAria/robot_info [rosaria_msgs/RobotInfoMsg]
- [x] /PIONIER6/RosAria/battery_recharge_state [std_msgs/Int8] - [x] /PIONIER6/RosAria/battery_state_of_charge [std_msgs/Float32] - [ ] check what is the recharge state - [ ] figure out latching for recharge state - [x] /PIONIER6/RosAria/robot_info [rosaria_msgs/RobotInfoMsg]
wkwolek added this to the reimplement ros1 functionality project 2021-05-14 14:04:05 +02:00
Author
Owner

latching is not directly supported in ROS2, I think it can be emulated by modifying the QoS settings but I couldn't get that to work. I assume it's not that big of a problem if we publish this state continuously instead of once per change and latching, as we only actually publish it when there's a subscriber connected.

latching is not directly supported in ROS2, I think it can be emulated by modifying the QoS settings but I couldn't get that to work. I assume it's not that big of a problem if we publish this state continuously instead of once per change and latching, as we only actually publish it when there's a subscriber connected.
wkwolek referenced this issue from a commit 2021-06-17 13:54:40 +02:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: L1.5/ros2aria#2
No description provided.