Add troubleshooting/restarting SITL sections #176
Conversation
|
At this point I'm comfortable floating dronekit-sitl-runner as a cross-platform alternative to the Vagrant sections. This uses precompiled binaries on S3 that are generated in a separate CI step: https://github.com/tcr3dr/dronekit-sitl-builder Three versions (3.2, 3.3-rc5, and 3.4-dev) are supported and built for Windows, OS X, and Linux. Basically, we should just outline what assurances are needed from that tool to use as a replacement for the Vagrant install (which I assume is less desirable in all circumstances). |
|
@tcr3dr if you feel like dksr (dk-sitl-runner) is the way to go we should remove all traces of sitl vagrant from the docs, lets create a new issue for this, and if this issue is now made irrelevant by that lets close this long live dronekit-sitl-runner! |
|
@tcr3dr I can't get it to work on Windows (dronekit/dronekit-sitl#9). I can't get UDP connection to work on Linux. Before replacing the vagrant stuff I would hope that we could get this working on Plane and Rover (dronekit/dronekit-sitl#3). Does this support "help" ie so people can get what versions of the binaries are available? Does this automatically set up any outputs or other defaults - ie what if you do "dronekit-sitl copter-3.4-dev" Do any other dependencies need to be added? Or are mavproxy et al pip dependencies? P.S. Excellent job! This should make things much easier for users! |
|
@tcr3dr It would be best to push this out now, while we resolve issues with the sitl runner. The work is already done and minor. |
| @@ -52,7 +52,7 @@ and Linux (though we recommend the native installations linked above). | |||
| #. Install SSH (Windows only - SSH is present by default on Linux/Mac OSX) | |||
|
|
|||
| * Download and install `Git for Windows <https://git-scm.com/download/win>`_ (or another client that comes with SSH). | |||
| 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** | |||
| 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** | |||
There was a problem hiding this comment.
I'm confused about this change, shouldn't they be backslashes?
Also I believe that can read where ssh without the c:\
|
@hamishwillee Just one comment on the change, otherwise I'll merge. |
This adds some troubleshooting when using vagrant (it is possible for the image to corrupt) and also instructions on resuming/restarting).
In addition, it adds some minor fixes to rendering of paths (backslashes) and the bullet points.