Well, the Xterm output seems clean, doesn’t seem to be any problem from that side.
Are you running this on Ubuntu 16.04 or something else?
Is the default SITL working correctly?
Please check this, after you close the sim_vehicle.py, check if the JSBSim process has been killed or not, you can use ps aux | grep JSBSim, there shouldn’t be anything else other than the grep process.
One last thing, wait for some 30secs to 1 min before again launching the simulation, the OS can take some time to free the ports. And also restart your system and try.
The main problem is that I’m not able to reproduce the error, that’s why need to do all this to see if anything can fix it
The default SITL (i.e sim_vehicle.py --map --console) works fine. The JSBSim process has been killed, I checked it with the provided command. Only the grep process appears then.
Also restarting the system did not work.
However, I noticed the following message in the xTerm output:
“Could not bind to socket for input …”
It does not appear in the same line each time I start the simulation, but it always appears. I think this is somehow the reason for the issue, some kind of connection problem between mavproxy and jsbsim…Also the terminal in which I started the sim_vehicle.py script gives the output:
Just had an idea, can try out Ardupilot with JSBSim in a 18.04 Docker container, not sure if it will work or not
Do post if you get some new info or were able to figure out what’s going on, if there’s any specific workaround required then it can be added to the Wiki
Unfortunately, there is no error message on the ardupilot side, I just see mavroxy waiting for connection, indicated by the “MAV>” prompt.
There are also no further details in the error message. I also browsed the JSBSim source code I have on my machine and could not find the string “Could not bind to socket for input…” which is the error message I get from JSBSim. However, I found out, that this string was used in the file jsbsim/src/input_output/FGfdmSocket.cpp but was replaced in a commit from 10 Mar 2018 (see https://github.com/JSBSim-Team/jsbsim/commit/69e042b95c83e5be65af7d8f0ec3b511c9c51609#diff-c02dde2575d65a6176ca38e3b18556da). Is it possible that I am somehow running an old version of JSBSim? I went into the jsbsim directory and ran git log. It showed me that the last commits are from June 9, 2019 so I am really confused where this error message comes from…
Hello there, I am still not sure what exactly the problem was, but I fixed it so I think it might be worth sharing. It is really a special case, but however maybe it might help.
I don’t know how that happened, but I somehow had an executable of JSBSim in my /usr/games/ directory. This directory was also in the PATH variable, before the ~/jsbsim directory. So every time JSBSim was executed it was the one in /usr/games/ which apparently did not wórk. After deleting this executable everything works fine now.