Jimmy McElwain
Jimmy McElwain
In reference to #37 and #192. Now the error message and error codes match the reasons that the motion start failed.
I added 2 extra settings to the `motoros2_config.yaml` file, `userlan_debug_broadcast_enabled` and `userlan_debug_broadcast_port`. By default, it broadcasts to all enabled ports, but the user can choose a specific port if they...
Changes start_traj_mode and start_point_queue_mode services so that they properly report the reasons for failure in case motion cannot be started. This addresses many of the concerns brought up in the...
This is needed to move the Init_Trajectory_Status enum and response strings to motoros2_interfaces. In response to #67. Requires Yaskawa-Global/motoros2_interfaces#26 to be merged, and will require messages to be rebuilt.
Fix for #128. RCL(C) API errors get reported to the user now. It just notifies the user that an RCL(C) API error occurred and gives the integer value of the...
This has ended up being less straightforward than I was expecting, so I'm putting this out there as a draft and will make any requested modifications, clean everything up, and...
Context #405 This is not the primary bug discussed there, but was mentioned near the end of https://github.com/Yaskawa-Global/motoros2/discussions/405#discussion-8157061 > As a side note, I also noticed that in the Feedback...
See https://github.com/Yaskawa-Global/motoros2/discussions/374#discussioncomment-12332137 Port numbers with 5 or more digits get truncated when trying to connect. If I have a valid port in the config file 16510, I would have to...
In reference to #268. I am going to make this a draft because I definitely want feedback and expect that I will have to make changes. The second most recent...