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
<!-- GAZEBO config
[gazebo-1] [Msg] Connected to gazebo master @ http://127.0.0.1:11345
[gazebo-1] [Msg] Publicized address: 172.31.159.229
-->
<!-- ROS2-web-bridge
$ node bin/rosbridge.js
ros2-web-bridge: ROS2 node started +0ms
ros2-web-bridge: Starting server on port 9090 +1ms
Websocket started on ws://localhost:9090 -->
<script>
let ros = new ROSLIB.Ros();
let bridgeHost = window.location.hostname;
let bridgePort = 9090;
// monitor the connection
// listener for a connection event to the ros object.
// two blocks following do the same for error and close events.
ros.on('connection', function() {
console.log('bridge connected');
});
ros.on('error', function(error) {
console.log('Error connecting to websocket server: ', error);
});
ros.on('close', function() {
console.log('Connection to websocket server closed.');
});
ros.connect('ws://' + bridgeHost + ':' + bridgePort);
</script>
<iframe id="iframeGazebo" src="http://172.31.159.229:11345"></iframe>
The text was updated successfully, but these errors were encountered:
I never try to combine them together, my first thought is that as ROSLIB doesn't aware if backed by ROS 1 or ROS 2, it seems feasible to interact gzweb with ros2-web-bridge by the ROSLIB.
Please validate if ros2-web-bridge supports deploying a ROS2 Foxy 20.04 Focal simulation via gzclient11 to a Web browser (gzweb is still ROS1)
<title>Gazebo11 Web Bridge v 0.0.1</title>The text was updated successfully, but these errors were encountered: