-
Minor, but the very first debug listener message received after MotoROS2 connects to the Agent has an all-zeros timestamp associated with it:
```
[2023-07-14 18:14:40.488481] [192.168.255.1:61992]…
-
MoveIt 2 is non-trivial to configure.
Especially when *not* using `ros2_control`, as almost all available documentation and examples assume `ros2_control` is being used.
We give some hint(s) in …
-
Upon initiating the microros Docker client, there will always be an alarm 8014 [1]. This has been preventing proper communication with the FollowJointTrajectory Action Server though published topics f…
-
Implement a service (perhaps `motoros2_interfaces/GetActiveAlarmInfo` or similarly named) which clients could invoke to retrieve more information about active alarms/errors.
We could expose other d…
-
The topic of accessing robot variables (BIDRSP) came up today.
This is already [on our roadmap](https://github.com/Yaskawa-Global/motoros2/tree/d6f1148494fc48bb414c3b5777c9d3f282a0b765#provisional-…
-
While working on #61, @SejalBehere noticed that the year was reporting 2022. It turns out the YRC was configured with the wrong date. But, I thought `rmw_uros_epoch_nanos` was supposed to compensate f…
-
While testing the node described in #66, I ran into the following problem.
Invoking the `stop_traj_mode` service returned:
```console
user@host:~$ ros2 service call /yrc1000/stop_traj_mode std_…
-
Even when servos are off, values reported in `JointState::velocity` can fluctuate (as in: 'randomly' change).
This could be due to noise in the values reported by M+ APIs, or a conversion error on …
-
In Galactic, the default RMW has [changed from Fast DDS to Cyclone DDS](https://docs.ros.org/en/galactic/Concepts/About-Different-Middleware-Vendors.html?highlight=default).
During testing, communi…
-
The `FollowJointTrajectory` action server in `ros_control` ([joint_trajectory_controller](http://wiki.ros.org/joint_trajectory_controller)) allows clients to request trajectory execution to start at a…