Ask Your Question

bwolfe's profile - activity

2019-05-13 08:31:51 -0500 received badge  Notable Question (source)
2019-02-20 09:35:26 -0500 commented question Visual Studios 2017 project with ROS2 components

In my original post I mentioned doing just that (i.e., create VS proj from cmake files), but what parts of the ros2 sour

2019-02-19 13:37:14 -0500 commented question Visual Studios 2017 project with ROS2 components

Dirk, you tell me it can be done, yet don't say how. I get compile errors with VS2017 by simply adding #include "rclcpp

2019-02-15 17:37:59 -0500 received badge  Popular Question (source)
2019-02-13 14:41:08 -0500 asked a question Visual Studios 2017 project with ROS2 components

Visual Studios 2017 project with ROS2 components I'm trying to build a VS2017 application (specifically an Unreal Engine

2019-02-06 10:21:04 -0500 commented question Connect windows and linux with ROS2

I ran the ros2 multicast test and can see comm between two separate windows cmd prompts, between two separate WSL prompt

2018-04-27 15:31:06 -0500 received badge  Famous Question (source)
2017-04-03 13:40:02 -0500 received badge  Student (source)
2017-04-03 13:39:10 -0500 received badge  Popular Question (source)
2017-04-03 13:39:10 -0500 received badge  Notable Question (source)
2017-02-02 11:06:53 -0500 commented question rqt: Fatal IO error when exporting x window to Windows 10 machine

Heh, actually tried that for developing ROS code, but could never get roscore to run due to networking limitations that can presumably only be fixed by getting early builds through the Windows insider program. Wonder if anybody has gotten ROS working under WSL, but that's a different topic.

2017-02-02 10:27:48 -0500 commented question rqt: Fatal IO error when exporting x window to Windows 10 machine

X11 forwarding is just a feature PuTTY provides to set the X11 parameters (through ssh) so I don't have to do it manually on the remote system. PuTTY sets DISPLAY to localhost:10.0. Couldn't get any x windows to work without it.

2017-02-02 09:46:51 -0500 asked a question rqt: Fatal IO error when exporting x window to Windows 10 machine

I am trying to run rqt on an embedded computer that has no display attached. As such, I use PuTTY on a Windows 10.1 computer to ssh in, with Xming on the Windows machine to display X windows content. I have X11 forwarding set up in PuTTY with all the comensurate xauth settings to allow the remote system to export to my Windows machine. I can run xclock and even rviz without errors. However, when I run rqt, I get "rqt: Fatal IO error: client killed". I've seen previous posts to this forum from many years ago with no definitive answers, so thought it worthwhile to see if there is some new knowledge about how to fix this problem.

Running with rosdistro indigo v1.11.20. Rviz says it's version 1.11.14 compiled against Qt version 4.8.6.

Running rqt -v gives following spew

QtBindingHelper using pyqt
PluginManager._discover() using cached plugin discovery information
RospkgPluginProvider._find_plugins() crawling for plugins of type 'qt_gui'
RospkgPluginProvider._find_plugins() crawling for plugins of type 'qt_gui'
PerspectiveManager.switch_perspective() switching to perspective "Default"
MainWindow.restore_settings()
PluginManager.restore_settings()
PluginManager.restore_settings() loading 1 plugins
RosPyPluginProvider._init_node() initialize ROS node "rqt_gui_py_node_6247"
PluginManager._load_plugin(rqt_joint_trajectory_controller/JointTrajectoryController#1) successful
PluginManager.restore_settings() all missing plugins loaded
PluginHandler.restore_settings()
PluginHandler.emit_restore_settings_completed()
PluginManager.restore_settings() all plugin settings restored
MainWindow.restore_state()
rqt: Fatal IO error: client killed