Rein Appeldoorn

@Rayman , we are not actively using this package anymore so if you would like to maintain both packages; you are more than welcome. Also, I am not able to...

Feel free to add a README that describes the working principle and all parameters.

IMO this is desired behavior. You can use the published diagnostics for monitoring the health of the driver.

I;m also interested in this

Still in latest version: ``` [robot_73981][INFO] 2023-10-19 16:15:28,219: what(): vector::_M_range_check: __n (which is 18446744073709551615) >= this->size() (which is 0) ``` I will try to reproduce this in a `DEBUG` build

@yannickdehoop fyi

@rlamarche , did you have a chance to work on this? @facontidavide , I think you meant ROS to JSON is straight forward since you already implemented [this](https://github.com/facontidavide/ros_msg_parser/blob/f874a6f98e0d1ed72e6d23f3671d26ed96a49986/include/ros_msg_parser/ros_parser.hpp#L160) ;)

Sure, we have two reasons for this: - When running a gazebo instance in a hardware in the loop set-up, some other nodes in the ros2 graph require real timestamps...

Any thoughts @azeey ?

Thanks for your reply @azeey , I don't think we can and I don't think we should modify the default node behavior: https://github.com/ros2/rclcpp/blob/343b29b617b163ad72b9fe3f6441dd4ed3d3af09/rclcpp/src/rclcpp/time_source.cpp#L257 Here the parameter is set to `false`...