You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to try to test wireless network performance with inverted pendulum, I believe it could be intuitive perception and understanding in case that the controller signal coming into pendulum would be come from sever side, let's say cloud.
So I am looking for the way to let controller node the other location but in the same network at the moment, for this time making the problem be simple.
how to make it to launch controller node in the host computer A, the other nodes in the host computer B ?
I hope this description can be clear to you and help me.
Thanks
Sean,
The text was updated successfully, but these errors were encountered:
Hi @swgu931, you could do this by running each executable in separate processes. Instead of using the pendulum demo bringup or the ros2 run pendulum_demo pendulum_demo command you will have to run the standalone driver and controller executables. For example, you can run the controller in host computer A as follows:
Aside from this work, I did two docker images for controller and model to be isolated, it works perfectly because the one built with ROS2 packages excluded the other, for example, model image don't include controller packages.
I will test more then I will uploaded into docker hub and brief manual.
I want to try to test wireless network performance with inverted pendulum, I believe it could be intuitive perception and understanding in case that the controller signal coming into pendulum would be come from sever side, let's say cloud.
So I am looking for the way to let controller node the other location but in the same network at the moment, for this time making the problem be simple.
how to make it to launch controller node in the host computer A, the other nodes in the host computer B ?
I hope this description can be clear to you and help me.
Thanks
Sean,
The text was updated successfully, but these errors were encountered: