ros_amr_interop
ros_amr_interop copied to clipboard
inorbit-ai
Before fix, ```bash $ ros2 launch vda5050_connector mqtt_bridge.launch.py [INFO] [launch]: All log files can be found below /home/damon/.ros/log/2024-02-17-22-52-36-339557-damon-lenovo-46076 [INFO] [launch]: Default logging verbosity is set to INFO [INFO] [mqtt_bridge.py-1]: process...
State message include information part and this key name is not correct in the script Correct name of the key is not **informations** it is **information** 
As mentioned in the issue ticket, object key conversions have been changed to camelCase as stated in the documentation. https://github.com/inorbit-ai/ros_amr_interop/issues/48
Addresses #44 The connector looks through the order that is accepted. If there are multiple released nodes that can be traversed without stopping (No HARD or SOFT actions) then the...
Actually when I looked vda5050 documentation it is really clear, **All field names are in camelCase** Old version of the repo it was camelCase but then with updates why it...
Release the `massrobotics_amr_sender` package for ROS Noetic (`noetic-devel`). [Here](http://wiki.ros.org/bloom/Tutorials/FirstTimeRelease) are the steps to do it with Bloom. Take into account that the [ROS1 to ROS2 migration guide](https://docs.ros.org/en/foxy/How-To-Guides/Releasing-a-ROS-2-package-with-bloom.html#procedure) recommends using different...
if there are a sequence of nodes in an order: node_1, node_2, node_3(with HARD action), node_4, node_5(with HARD action); on the loop of "_on_active_order", each time it will trigger "_process_next_edge"...
Hello, I've been using the VDA5050 Controller with openTCS' VDA5050 Master Controller found [here](https://github.com/openTCS/opentcs-commadapter-vda5050/tree/master) As I've been doing so I've noticed that there are some inconsistencies with the VDA5050 version...
Is there any plan to enable navigation through VDA5050 nodes & edges? Perhaps the NavigateToNode action could be updated to include a list of Nodes and Edges that are released...
The new `noetic-devel` branch doesn't have any test for the code. We could start by migrating [the existing tests in `foxy-devel`](https://github.com/inorbit-ai/ros_amr_interop/tree/foxy-devel/massrobotics_amr_sender_py/test) to ROS1 and then adding extra tests if needed.