-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TCP connection to simulation is one-way only #94
Comments
Hi, We also have the wish to change from the several different network libraries that we use now (python socket, QT network, multiproccessing.Connection) to just one library (zmq), which will also make it easier to provide TCP/UDP output streams (e.g., to drive HITL simulations). When we get around to this the stack command origin/destination issue will also be addressed. |
Hi @jooste I have implemented a relatively simple fix for this on a fork (which we are keeping up-to-date with this upstream repo). I'll tidy and submit a pull request in the next few days - just writing some tests currently. It may represent a useful fix for the time being. |
Please see #103 |
If I start an opengl simulation using
python BlueSky.py
, it listens on port8888
for incoming console connections.I connect using netcat and issue a command, as follows:
Both the command (as issued in lower case) and the output result of the command appear on the gui console.
I would expect the output of the command to appear on the TCP connection, and the GUI console to remain unchanged.
The text was updated successfully, but these errors were encountered: