Skip to content

Commit 9e05e85

Browse files
committed
Add troubleshooting/restarting SITL sections
1 parent ce8de35 commit 9e05e85

File tree

1 file changed

+38
-2
lines changed

1 file changed

+38
-2
lines changed

docs/guide/sitl_setup.rst

Lines changed: 38 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ and Linux (though we recommend the native installations linked above).
5252
#. Install SSH (Windows only - SSH is present by default on Linux/Mac OSX)
5353

5454
* Download and install `Git for Windows <https://git-scm.com/download/win>`_ (or another client that comes with SSH).
55-
After installing you can locate the file using the command ``C:\where ssh`` (normally it is installed to **C:\Program Files (x86)\Git\bin\ssh.exe**
55+
After installing you can locate the file using the command ``C:\where ssh`` (normally it is installed to **C:/Program Files (x86)/Git/bin/ssh.exe**
5656
* Add the ssh.exe location to the *Path* (**System Properties | Advanced tab | Environment Variables | Path**)
5757

5858
#. Create a new directory where you will run *Vagrant*, and open a command prompt/terminal in it:
@@ -88,7 +88,7 @@ and Linux (though we recommend the native installations linked above).
8888
8989
.. _disable-arming-checks:
9090

91-
#. Load a default set of parameters and disable the arming check:
91+
7. Load a default set of parameters and disable the arming check:
9292

9393
.. code:: bash
9494
@@ -102,6 +102,42 @@ and Linux (though we recommend the native installations linked above).
102102

103103
You should never disable the arming check in a script or on a real vehicle.
104104

105+
106+
Restarting
107+
----------
108+
109+
When you've finished using the simulation you can suspend the virtual machine with the command
110+
``vagrant suspend`` and later restart it using ``vagrant resume``. Alternatively you can power-down
111+
the machine using the `halt <http://docs.vagrantup.com/v2/cli/halt.html>`_ command
112+
and later restart it using ``vagrant up``:
113+
114+
.. code-block:: bash
115+
116+
vagrant halt
117+
vagrant up
118+
119+
120+
121+
122+
Troubleshooting
123+
---------------
124+
125+
In most cases problems can be fixed by halting and restarting vagrant:
126+
127+
.. code-block:: bash
128+
129+
vagrant halt
130+
vagrant up
131+
132+
If this does not work then the "nuclear option" is to destroy and restart the environment:
133+
134+
.. code-block:: bash
135+
136+
vagrant destroy
137+
vagrant up
138+
139+
140+
105141
106142
.. _viewing_uav_on_map:
107143

0 commit comments

Comments
 (0)