01-10-2019 01:53 AM
In a project it is my task to supervisory control different types of robots to do predefined operations like cleaning or taking measurements. The robots have no camera, should avoid delicate objects, work in sync next to other robots and not enter forbidden area. That is why the motion-patterns are planned beforehand (position, time) like in an orchestration. In an accurate positionable waterspraying robot application for a cheese-factory I did earlier, this works well (8 bots).
The problem I have is that one of the slave robots is running ROS and as I understand it ROS solutions are not really designed to be treated as a slave. Besides, it runs obstacle prevention algo’s by going around unknown obstacles and it does sensor-fusion to get a better estimate of the position.
ROS for LabVIEW seems like a good starting-point and I am glad to find a possible solution of getting live data.
Do you have any tips/ideas for me on supervisory controlling this slave ROS robot?
01-11-2019 02:49 AM
I'm now looking at the option of sniffing the communication of the ROS robot. This appears to be possible in LabVIEW thanks to http://www.ni.com/example/27660/en/. This would give me the option of logging and displaying data without extra loading the master, but takes some message decoding.
Besides supervisory control, status and data presentation/logging is one of the other tasks the sw. should do.
01-20-2019 09:30 AM
I somehow expected a reaction. Sometimes one expects just too much.