using_mount_control_software.html
27.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>First steps with the Mount Control Software — Mount Control Software 1.0.0 documentation</title>
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<link rel="stylesheet" href="_static/classic.css" type="text/css" />
<link rel="stylesheet" type="text/css" href="_static/graphviz.css" />
<script id="documentation_options" data-url_root="./" src="_static/documentation_options.js"></script>
<script src="_static/jquery.js"></script>
<script src="_static/underscore.js"></script>
<script src="_static/doctools.js"></script>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="Communication protocols for astromecca mounts" href="communication_langage_protocol.html" />
<link rel="prev" title="Welcome in the AstroMeCCA software documentation" href="index.html" />
</head><body>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="communication_langage_protocol.html" title="Communication protocols for astromecca mounts"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="index.html" title="Welcome in the AstroMeCCA software documentation"
accesskey="P">previous</a> |</li>
<li class="nav-item nav-item-0"><a href="index.html">Mount Control Software 1.0.0 documentation</a> »</li>
<li class="nav-item nav-item-this"><a href="">First steps with the Mount Control Software</a></li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<div class="section" id="first-steps-with-the-mount-control-software">
<h1>First steps with the Mount Control Software<a class="headerlink" href="#first-steps-with-the-mount-control-software" title="Permalink to this headline">¶</a></h1>
<p>The Mount Control Software (MCS) is the program
that makes the link between astronomers and the
hardware of the mount. MCS is installed aboard the computer
linked to the mount hardware controlers.</p>
<p>MCS is running as a service as soon as the raspberry is booted.
It allows a connection with any astronomy software using ASCOM
protocol via serial port RS232 (driver astromecca, 115200 bauds).
We named <em>astronomy software</em> any software that communicates
with MCS (Cartes du Ciel, Prism, MaxIm DL, AudeLA, etc.).</p>
<p>If the ASCOM connection failed you must check if the
MCS is running as service.</p>
<div class="section" id="check-if-mcs-is-running-as-service">
<h2>Check if MCS is running as service<a class="headerlink" href="#check-if-mcs-is-running-as-service" title="Permalink to this headline">¶</a></h2>
<p>In case of ASCOM no connection you must check the
MCS state. To verify if MCS is running, in a Linux console:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">ps</span> <span class="o">-</span><span class="n">edf</span> <span class="o">|</span> <span class="n">grep</span> <span class="n">mount</span>
</pre></div>
</div>
<p>The answer may seems to be:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>root 569 1 1 16:47 ? 00:00:16 /usr/bin/python3 /home/pi/astromecca/mount_control_software.py -config_path /home/pi/astromecca/ -server -langage ASCOM -transport SERIAL -port /dev/ttySC1
pi 1195 1161 0 17:05 pts/1 00:00:00 grep --color=auto mount
</pre></div>
</div>
<p>What is important is the first line indicating the mount_control_software.py
script is run by python3. Note the PID (process identifier) is 569. It should
be different for your session.</p>
<p>If the mount_control_software.py appears in <em>ps -edf</em>
it means the possibility to drive the mount using a astronomy
software using the ASCOM protocol. The check is OK.</p>
<p>If the mount_control_software.py does not appear in the <em>ps -edf</em>
command, the check is not OK and you should check the error
log file. In a Linux console:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">more</span> <span class="o">/</span><span class="n">tmp</span><span class="o">/</span><span class="n">mcs_err</span><span class="o">.</span><span class="n">txt</span>
</pre></div>
</div>
<p>According the contents of the file mcs_err.txt, contact the manufacturer.</p>
<p>Moreover, the log file can help to identify some problems.
To check the log of MCS, in a Linux console:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">tail</span> <span class="o">-</span><span class="n">n30</span> <span class="o">/</span><span class="n">tmp</span><span class="o">/</span><span class="n">mcs_log</span><span class="o">.</span><span class="n">txt</span>
</pre></div>
</div>
<p>If you want to change the running service configuration,
read the
<a class="reference external" href="#change-the-mcs-configuration-for-running-as-service">section to change the configuration for running as service</a>.</p>
</div>
</div>
<div class="section" id="use-the-pad-of-the-mount-control-software">
<h1>Use the pad of the Mount Control Software<a class="headerlink" href="#use-the-pad-of-the-mount-control-software" title="Permalink to this headline">¶</a></h1>
<p>If the astronomer wants to drive manually the mount, it is
possible to launch MCS in another way than a service. By
this way it is possible to use the virtual pad of the MCS.</p>
<p>First you have to kill the current instance of mount_control_system.py
(i.e. that is running as service). To kill a running MCS,
in a Linux console:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">sudo</span> <span class="n">kill</span> <span class="o">-</span><span class="mi">9</span> <span class="mi">569</span>
</pre></div>
</div>
<p>569 is the PID previously noticed in <em>ps -edf</em> list (replace 569
by the PID of your session).
Once kill done, verify the MCS has disapeared of the <em>ps -edf</em> list.</p>
<p>Then you can launch manually an instance of mount_control_system.py</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="nb">cd</span> ~/astromecca
python3 mount_control_software.py -config_mount config_mcs_default.py -mount_real -pad <span class="p">&</span>
</pre></div>
</div>
<p>In the command line, the file name config_mcs_default.py provides
a simulator only. For a real mount you have to replace the file
name config_mcs_default.py by the file name delivered for your
specific mount (contact the vendor if not present in the folder).</p>
<p>After MCS launch the virtual pad must appears on the desktop.
The pad is a window divided in tabs.</p>
<blockquote>
<div><ul class="simple">
<li><p><strong>Drive the mount</strong> tab is used to drive the mount for astronomical observations.</p></li>
<li><p><strong>Calibrations</strong> tab is to help the polar alignment.</p></li>
<li><p><strong>Configuration</strong> tab displays the configuration parameters.</p></li>
</ul>
</div></blockquote>
<div class="section" id="drive-the-mount">
<h2>Drive the mount<a class="headerlink" href="#drive-the-mount" title="Permalink to this headline">¶</a></h2>
<p>The first tab is used to drive the mount.
It is possible to enter equatorial coordinates (J2000)
and the side of the tube. Then push the button GOTO to start pointing.
Note the side of the tube is <em>Regular</em> or <em>Fliped</em> for fork mounts and
is <em>Tube West</em> or <em>Tube East</em> for German mounts.
The telescope will track in sideral motion after pointing.</p>
<p>It is possible to move the pointed position using the N, E, S, W buttons.
The moving velocity is set changing the number (1 deg/sec by default)
in the center of the buttons. When buttons are released the motion
return to the previous motion state (tracking or stoped).</p>
<p>The button STOP stops any motion of the mount (slew or track).
The button Synchro records the RA, Dec, Side of pointing as the
pointed coordinates. Use the button Synchro after having pointed and
centered a bright star for instance.
The button Park is used to park the mount.
The button Quit exits the pad.</p>
<div class="figure align-default" id="id1">
<span id="fig-pad1"></span><a class="reference internal image-reference" href="_images/pad1.png"><img alt="_images/pad1.png" src="_images/pad1.png" style="height: 450px;" /></a>
<p class="caption"><span class="caption-number">Fig. 2 </span><span class="caption-text">Pad tab to drive the mount.</span><a class="headerlink" href="#id1" title="Permalink to this image">¶</a></p>
</div>
</div>
<div class="section" id="help-for-polar-aligment">
<h2>Help for polar aligment<a class="headerlink" href="#help-for-polar-aligment" title="Permalink to this headline">¶</a></h2>
<p>The second tab is for advanced users.
It is possible to enter local equatorial coordinates (equinox at the date)
and the side of the tube. H.A. means <em>hour angle</em>.
Then push the button GOTO to start pointing.
The telescope will not drift after pointing.</p>
<p>It is possible to move the pointed position using the N, E, S, W buttons.
The moving velocity is set changing the number (1 deg/sec by default)
in the center of the buttons. After release the direction buttons the
telescope is stoped (i.e. no tracking).</p>
<div class="figure align-default" id="id2">
<span id="fig-pad2"></span><a class="reference internal image-reference" href="_images/pad2.png"><img alt="_images/pad2.png" src="_images/pad2.png" style="height: 450px;" /></a>
<p class="caption"><span class="caption-number">Fig. 3 </span><span class="caption-text">Pad tab to help the polar aligment.</span><a class="headerlink" href="#id2" title="Permalink to this image">¶</a></p>
</div>
<p>The buttons <em>Lim E</em>, <em>Lim W</em> and the <em>Declination inc0</em> value are used to
fit the mechanical pole in the center of images.
The buttons <em>Lim E</em>, <em>Lom W</em> allow to slew the mount
around the hour angle axis in order to obtain images of stars as circles.</p>
<div class="figure align-default" id="id3">
<span id="fig-rotpole1"></span><a class="reference internal image-reference" href="_images/rotpole1.png"><img alt="_images/rotpole1.png" src="_images/rotpole1.png" style="height: 350px;" /></a>
<p class="caption"><span class="caption-number">Fig. 4 </span><span class="caption-text">Image taken during the rotation from <em>Lim E</em> to <em>Lim W</em>.</span><a class="headerlink" href="#id3" title="Permalink to this image">¶</a></p>
</div>
<p>One can deduce the center of rotation.
The goal is to fit the center of star circles exactly in the center of the image.
One axis of offcentring depends on the value of inc0 of the declination axis:</p>
<blockquote>
<div><ul class="simple">
<li><p>First: Push the <em>Lim E</em> button to put the mount in the eastern position.</p></li>
<li><p>Second: Change the inc0 value and push the button <em>VALID and GOTO pole</em>.</p></li>
<li><p>Third: Start an image exposure.</p></li>
<li><p>Fourth: Push the <em>Lim W</em> button to put the mount in the western position.</p></li>
<li><p>Fifth: Display the image and return to the first step and iterate until reaching star circles centered on the image center (see <a class="reference internal" href="#fig-rotpole1"><span class="std std-numref">Fig. 4</span></a>).</p></li>
</ul>
</div></blockquote>
<p>This setting must be done before any procedure
of <a class="reference external" href="https://en.wikipedia.org/wiki/Polar_alignment">polar alignment</a> (see the dedicated documentation align the pole).</p>
</div>
<div class="section" id="mount-configuration">
<h2>Mount configuration<a class="headerlink" href="#mount-configuration" title="Permalink to this headline">¶</a></h2>
<p>The third tab display the configuration paramters.</p>
<div class="figure align-default" id="id4">
<span id="fig-pad3"></span><a class="reference internal image-reference" href="_images/pad3.png"><img alt="_images/pad3.png" src="_images/pad3.png" style="height: 450px;" /></a>
<p class="caption"><span class="caption-number">Fig. 5 </span><span class="caption-text">Pad tab to display the mount configuration.</span><a class="headerlink" href="#id4" title="Permalink to this image">¶</a></p>
</div>
</div>
</div>
<div class="section" id="mount-control-software-for-experimented-users">
<h1>Mount Control Software for experimented users<a class="headerlink" href="#mount-control-software-for-experimented-users" title="Permalink to this headline">¶</a></h1>
<p>All the fonctionalities described now imply to kill
all the MCS instances (using kill -9 described above)
before launching a new one.</p>
<p>It is possible to launch manually mount_control_software.py
via Spyder IDE instead of the command line. We let users
chosing what they prefer.</p>
<p>There are many options to adapt MCS for your needs.
Especially it is possible to choose the protocols for
astronomy programs.</p>
<div class="section" id="change-the-mcs-configuration-of-the-command-line">
<h2>Change the MCS configuration of the command line<a class="headerlink" href="#change-the-mcs-configuration-of-the-command-line" title="Permalink to this headline">¶</a></h2>
<p>There are many options to fit the needs. The help of the software is displayed as the following procedure:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>pi@raspberrypi:~/astromecca $ python3 mount_control_software.py -h
usage: mount_control_software.py [-h] [-config_path CONFIG_PATH]
[-config_mount CONFIG_MOUNT] [-mount_real]
[-mount_port MOUNT_PORT] [-server]
[-langage LANGAGE] [-transport TRANSPORT]
[-port PORT] [-client]
[-client_port CLIENT_PORT] [-pad]
Launch MCS
optional arguments:
-h, --help show this help message and exit
-config_path CONFIG_PATH
Path where configuration files will be read.
-config_mount CONFIG_MOUNT
Configuration files for the mount.
-mount_real Connect to a real mount controller. You must specify
the -mount_port.
-mount_port MOUNT_PORT
Port identifier for the connection with a real mount
controller -mount_real.
-server To activate a server. You must specify the -langage,
-transport, -port.
-langage LANGAGE Server langage protocol (LX200, ASCOM, ASTROMECCA).
-transport TRANSPORT Server transport protocol (SERIAL, TCP).
-port PORT Port identifier for the server to listen a client.
-client To test a client. You must specify the -client_port
-client_port CLIENT_PORT
Port identifier for the client to dialog with a
server.
-pad Display the virtual pad.
</pre></div>
</div>
<p>MCS codes are installed in the folder /home/pi/astromecca.
Codes are written in Python and consist of two Python modules, files and folders:</p>
<blockquote>
<div><ul class="simple">
<li><p>Module <strong>mounastro</strong>: Contains Python classes to drive the mount.</p></li>
<li><p>Module <strong>celme</strong>: Contains Python classes to perform calculations of celestial mechanics.</p></li>
<li><p>File <strong>mount_control_software.py</strong>: The Python code of MCS. It uses modules mountastro and celme.</p></li>
<li><p>Folder <strong>catalogues</strong>: Contains catalogs of astronomical sources used by the mountastro module.</p></li>
<li><p>Folder <strong>doc_html</strong>: Contains this documentation in HTML format (index.html).</p></li>
<li><p>Folder <strong>doc_pdf</strong>: Contains this documentation in PDF format (index.html).</p></li>
<li><p>Folder <strong>doc_rst</strong>: Contains this documentation in RST format (source of the documentation).</p></li>
</ul>
</div></blockquote>
<p>For example, if you want to launch MCS with the server MCS protocol over TCP port 1111:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">cd</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">pi</span><span class="o">/</span><span class="n">astromecca</span><span class="o">/</span>
<span class="n">python3</span> <span class="n">mount_control_software</span><span class="o">.</span><span class="n">py</span> <span class="o">-</span><span class="n">pad</span> <span class="o">-</span><span class="n">server</span> <span class="o">-</span><span class="n">langage</span> <span class="n">MCS</span> <span class="o">-</span><span class="n">transport</span> <span class="n">TCP</span> <span class="o">-</span><span class="n">port</span> <span class="mi">1111</span>
</pre></div>
</div>
<p>If you want to launch MCS with the server ASCOM protocol over serial port /dev/ttySC1:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">cd</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">pi</span><span class="o">/</span><span class="n">astromecca</span><span class="o">/</span>
<span class="n">python3</span> <span class="n">mount_control_software</span><span class="o">.</span><span class="n">py</span> <span class="o">-</span><span class="n">pad</span> <span class="o">-</span><span class="n">server</span> <span class="o">-</span><span class="n">langage</span> <span class="n">ASCOM</span> <span class="o">-</span><span class="n">transport</span> <span class="n">SERIAL</span> <span class="o">-</span><span class="n">port</span> <span class="o">/</span><span class="n">dev</span><span class="o">/</span><span class="n">ttySC1</span>
</pre></div>
</div>
</div>
<div class="section" id="change-the-mcs-configuration-for-running-as-service">
<h2>Change the MCS configuration for running as service<a class="headerlink" href="#change-the-mcs-configuration-for-running-as-service" title="Permalink to this headline">¶</a></h2>
<p>For AstroMECCA mounts, MCS is installed in a Raspberry computer.
When the computer is booting, MCS is automatically launched
according the configuration of the /etc/rc.local file.
To read or change the configuration:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>sudo geany /etc/rc.local
</pre></div>
</div>
<p>The following line is the code must be found in the rc.local file to launch MCS during
the boot of the Raspberry:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">nohup</span> <span class="o">/</span><span class="n">usr</span><span class="o">/</span><span class="nb">bin</span><span class="o">/</span><span class="n">python3</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">pi</span><span class="o">/</span><span class="n">astromecca</span><span class="o">/</span><span class="n">mount_control_software</span><span class="o">.</span><span class="n">py</span> <span class="o">-</span><span class="n">config_path</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">pi</span><span class="o">/</span><span class="n">astromecca</span><span class="o">/</span> <span class="o">-</span><span class="n">server</span> <span class="o">-</span><span class="n">langage</span> <span class="n">ASCOM</span> <span class="o">-</span><span class="n">transport</span> <span class="n">SERIAL</span> <span class="o">-</span><span class="n">port</span> <span class="o">/</span><span class="n">dev</span><span class="o">/</span><span class="n">ttySC1</span> <span class="mi">1</span><span class="o">>/</span><span class="n">tmp</span><span class="o">/</span><span class="n">mcs_log</span><span class="o">.</span><span class="n">txt</span> <span class="mi">2</span><span class="o">>/</span><span class="n">tmp</span><span class="o">/</span><span class="n">mcs_err</span><span class="o">.</span><span class="n">txt</span> <span class="o">&</span>
</pre></div>
</div>
<p>If you want to start the service with the MCS protocol over TCP port 1111:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">nohup</span> <span class="o">/</span><span class="n">usr</span><span class="o">/</span><span class="nb">bin</span><span class="o">/</span><span class="n">python3</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">pi</span><span class="o">/</span><span class="n">astromecca</span><span class="o">/</span><span class="n">mount_control_software</span><span class="o">.</span><span class="n">py</span> <span class="o">-</span><span class="n">config_path</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">pi</span><span class="o">/</span><span class="n">astromecca</span><span class="o">/</span> <span class="o">-</span><span class="n">server</span> <span class="o">-</span><span class="n">langage</span> <span class="n">MCS</span> <span class="o">-</span><span class="n">transport</span> <span class="n">TCP</span> <span class="o">-</span><span class="n">port</span> <span class="mi">1111</span> <span class="mi">1</span><span class="o">>/</span><span class="n">tmp</span><span class="o">/</span><span class="n">mcs_log</span><span class="o">.</span><span class="n">txt</span> <span class="mi">2</span><span class="o">>/</span><span class="n">tmp</span><span class="o">/</span><span class="n">mcs_err</span><span class="o">.</span><span class="n">txt</span> <span class="o">&</span>
</pre></div>
</div>
<p>If you want to start the service another configuration file (e.g. myconf.py)
placed in the folder /home/pi/astromecca:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">nohup</span> <span class="o">/</span><span class="n">usr</span><span class="o">/</span><span class="nb">bin</span><span class="o">/</span><span class="n">python3</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">pi</span><span class="o">/</span><span class="n">astromecca</span><span class="o">/</span><span class="n">mount_control_software</span><span class="o">.</span><span class="n">py</span> <span class="o">-</span><span class="n">config_path</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">pi</span><span class="o">/</span><span class="n">astromecca</span><span class="o">/</span> <span class="o">-</span><span class="n">config_mount</span> <span class="n">myconf</span><span class="o">.</span><span class="n">py</span> <span class="o">-</span><span class="n">server</span> <span class="o">-</span><span class="n">langage</span> <span class="n">MCS</span> <span class="o">-</span><span class="n">transport</span> <span class="n">TCP</span> <span class="o">-</span><span class="n">port</span> <span class="mi">1111</span> <span class="mi">1</span><span class="o">>/</span><span class="n">tmp</span><span class="o">/</span><span class="n">mcs_log</span><span class="o">.</span><span class="n">txt</span> <span class="mi">2</span><span class="o">>/</span><span class="n">tmp</span><span class="o">/</span><span class="n">mcs_err</span><span class="o">.</span><span class="n">txt</span> <span class="o">&</span>
</pre></div>
</div>
<p>Do not forget to reboot the Raspberry to start the service:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">sudo</span> <span class="n">reboot</span>
</pre></div>
</div>
</div>
</div>
<div class="clearer"></div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<h3><a href="index.html">Table of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">First steps with the Mount Control Software</a><ul>
<li><a class="reference internal" href="#check-if-mcs-is-running-as-service">Check if MCS is running as service</a></li>
</ul>
</li>
<li><a class="reference internal" href="#use-the-pad-of-the-mount-control-software">Use the pad of the Mount Control Software</a><ul>
<li><a class="reference internal" href="#drive-the-mount">Drive the mount</a></li>
<li><a class="reference internal" href="#help-for-polar-aligment">Help for polar aligment</a></li>
<li><a class="reference internal" href="#mount-configuration">Mount configuration</a></li>
</ul>
</li>
<li><a class="reference internal" href="#mount-control-software-for-experimented-users">Mount Control Software for experimented users</a><ul>
<li><a class="reference internal" href="#change-the-mcs-configuration-of-the-command-line">Change the MCS configuration of the command line</a></li>
<li><a class="reference internal" href="#change-the-mcs-configuration-for-running-as-service">Change the MCS configuration for running as service</a></li>
</ul>
</li>
</ul>
<h4>Previous topic</h4>
<p class="topless"><a href="index.html"
title="previous chapter">Welcome in the AstroMeCCA software documentation</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="communication_langage_protocol.html"
title="next chapter">Communication protocols for astromecca mounts</a></p>
<div role="note" aria-label="source link">
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="_sources/using_mount_control_software.rst.txt"
rel="nofollow">Show Source</a></li>
</ul>
</div>
<div id="searchbox" style="display: none" role="search">
<h3 id="searchlabel">Quick search</h3>
<div class="searchformwrapper">
<form class="search" action="search.html" method="get">
<input type="text" name="q" aria-labelledby="searchlabel" />
<input type="submit" value="Go" />
</form>
</div>
</div>
<script>$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
>index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="communication_langage_protocol.html" title="Communication protocols for astromecca mounts"
>next</a> |</li>
<li class="right" >
<a href="index.html" title="Welcome in the AstroMeCCA software documentation"
>previous</a> |</li>
<li class="nav-item nav-item-0"><a href="index.html">Mount Control Software 1.0.0 documentation</a> »</li>
<li class="nav-item nav-item-this"><a href="">First steps with the Mount Control Software</a></li>
</ul>
</div>
<div class="footer" role="contentinfo">
© Copyright 2021, astromecca.
Created using <a href="https://www.sphinx-doc.org/">Sphinx</a> 3.4.0.
</div>
</body>
</html>