Julian Oes
e80d3940a6
jmavsim_run.sh: enable SDK UDP port
...
We forgot to add the option -s for jmavsim_run.sh which starts jMAVSim
with the UDP port connecting to the SDK (port 14540).
2019-05-09 18:27:14 +02:00
Beat Küng
898664d919
jmavsim: fix HIL, don't add -lockstep by default
2019-03-15 08:54:42 +01:00
Julian Oes
18f7ee2d50
jMAVSim: update submodule, use -lockstep CLI arg
...
This updates the jMAVSim submodule which includes a fix for HITL.
In order to fix HITL, a CLI argument `-lockstep` was required to enable
lockstep. This has now been added to the command in jmavsim_run.sh.
2019-02-18 20:25:50 +00:00
Julian Oes
b436f3dd56
ROMFS/Tools: switch to TCP connection for SITL
...
This switches from UDP to TCP to connect to jMAVSim.
2018-12-22 10:32:18 +01:00
Julian Oes
82a88d6a53
jMAVSim: update submodule for new -f argument
...
This adds the argument -f for a speed factor to speed up the simulation.
2018-12-22 10:32:18 +01:00
Julian Oes
9f7f30a166
jmavsim_run.sh: fall back to Java 9 on macOS
...
This checks if we are on macOS and if we have Java 8 installed. If yes,
it falls back to Java 8 by setting JAVA_HOME.
This avoids https://github.com/PX4/jMAVSim/issues/81
2018-09-16 17:40:27 -04:00
Julian Oes
fec3422f54
jmavsim_run.sh: fix shebang and exit on error
2018-09-16 17:40:27 -04:00
Beat Küng
44839208f7
jmavsim_run.sh: add more aggressive GC option
...
This reduces memory usage by roughly 100MB on my laptop
2017-10-27 10:43:45 +02:00
Beat Küng
541e53fdcf
jmavsim_run.sh: add -i to specify the IP
2017-03-10 09:00:24 +01:00
Beat Küng
b2d47adf56
jmavsim_run.sh: add -r option to set the update rate
...
currently jmavsim uses a default rate of 500 Hz which is too much.
2017-03-04 05:59:10 +08:00
Beat Küng
0002e86b6f
jmavsim_run.sh: add additional arguments for HITL
2016-10-20 18:54:47 +02:00
Beat Küng
a51d1bc5dc
jmavsim_run.sh: add optional -p <port> argument
2016-09-30 13:50:51 +02:00
Beat Küng
e7afecb544
Tools: add separate jmavsim_run.sh script
...
It is useful to run jmavsim separately, for example when debugging mainapp
separately, or running some other external tool on mainapp (like heap
analysis)
2016-09-13 11:30:38 +02:00
