Dab acronyms
Jeff Moe
parent
db6abff149
commit
afb4ec1004
|
|
@ -12,7 +12,7 @@
|
|||
\section{Overview of Operation}
|
||||
\label{sec:overview-operation}
|
||||
\index{operation}
|
||||
Below shows how to run a SatNOGS Optical \gls{ground-station},
|
||||
Below shows how to run a SatNOGS Optical \gls{ground-station},
|
||||
after it has been set up and configured.
|
||||
|
||||
\section{Setup with \texttt{stvid}}
|
||||
|
|
|
|||
|
|
@ -17,14 +17,14 @@
|
|||
This is a description of \gls{satellite} detection processes.
|
||||
To detect \gls{satellite} in a \gls{FITS} file using the stvid toolchain,
|
||||
run \texttt{process.py} or, if it exists, the \texttt{process\_new.py}
|
||||
Python script.
|
||||
\gls{Python} script.
|
||||
|
||||
Note the \texttt{stvid} application's \texttt{process.py} and \texttt{process\_new.py}
|
||||
will perform both the detection and identification steps.
|
||||
\index{identify}
|
||||
|
||||
\subsection{\texttt{process\_new.py} Usage}
|
||||
\index{process}
|
||||
\index{process}\index{stvid}
|
||||
|
||||
This assumes you have installed \texttt{stvid} as shown in section \ref{sec:stvid-setup}
|
||||
\pageref{sec:stvid-setup}.
|
||||
|
|
@ -39,6 +39,7 @@ cd stvid/
|
|||
\end{minted}
|
||||
|
||||
\subsection{\texttt{process.py} Usage}
|
||||
\index{stvid}
|
||||
If there is no \texttt{process\_new.py} it has likely been merged into
|
||||
\texttt{process.py}. Or perhaps, to use the ``older'' script it would
|
||||
be run as shown below. Note, the old and new configuration files
|
||||
|
|
|
|||
|
|
@ -148,6 +148,7 @@
|
|||
\newacronym[description={Comma Separated Value.}]{CSV}{CSV}{Comma Separated Value}
|
||||
\newacronym[description={Network Time Protocol.}]{NTP}{NTP}{Network Time Protocol}
|
||||
\newacronym[description={Internet Protocol.}]{IP}{IP}{Internet Protocol}
|
||||
\newacronym[description={Internet Protocol version 6.}]{IPv6}{IPv6}{Internet Protocol version 6}
|
||||
\newacronym[description={International Space Station.}]{ISS}{ISS}{International Space Station}
|
||||
\newacronym[description={Low Earth Orbit.}]{LEO}{LEO}{Low Earth Orbit}
|
||||
\newacronym[description={Geostationary orbit.}]{GEO}{GEO}{Geostationary orbit}
|
||||
|
|
@ -163,6 +164,21 @@
|
|||
\newacronym[description={All Sky Monitor.}]{ASM}{ASM}{All Sky Monitor}
|
||||
\newacronym[description={Pan-tilt-zoom.}]{PTZ}{PTZ}{Pan-tilt-zoom}
|
||||
\newacronym[description={Pulse per second.}]{PPS}{PPS}{Pulse per second}
|
||||
\newacronym[description={Universal Serial Bus.}]{USB}{USB}{Pulse per second}
|
||||
\newacronym[description={Next Unit of Computing.}]{NUC}{NUC}{Pulse per second}
|
||||
\newacronym[description={Volt.}]{V}{V}{Volt}
|
||||
\newacronym[description={Direct current.}]{DC}{DC}{Direct current}
|
||||
\newacronym[description={Equatorial.}]{EQ}{EQ}{equatorial}
|
||||
\newacronym[description={I don't know.}]{IDK}{IDK}{I don't know}
|
||||
\newacronym[description={Database.}]{DB}{DB}{Database}
|
||||
\newacronym[description={USB video device class.}]{UVC}{UVC}{USB video device class}
|
||||
\newacronym[description={Computer vision.}]{CV}{CV}{Computer vision}
|
||||
\newacronym[description={Package Installer for Python.}]{PIP}{PIP}{Package Installer for Python}
|
||||
\newacronym[description={Random-access memory.}]{RAM}{RAM}{Random-access memory}
|
||||
\newacronym[description={Global Navigation Satellite System.}]{GLONASS}{GLONASS}{Global Navigation Satellite System}
|
||||
\newacronym[description={BeiDou Navigation Satellite System.}]{BDS}{BDS}{BeiDou Navigation Satellite System}
|
||||
% POSIX
|
||||
% INDIGO
|
||||
|
||||
|
||||
%%%%%%%%%%%
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
\index{ground station}\index{SDR}\index{antenna}\index{camera}
|
||||
\index{receiver}\index{antenna}
|
||||
\Glspl{ground-station} are a setup of equipment such as computers, cameras,
|
||||
\glspl{SDR}, antennas, and receivers, located on Earth, observing space.
|
||||
\glspl{SDR}, \glspl{antenna}, and receivers, located on Earth, observing space.
|
||||
|
||||
|
||||
\section{SatNOGS Ground Stations}
|
||||
|
|
@ -41,7 +41,7 @@ It shows a \gls{SatNOGS} \gls{ground-station} with \gls{VHF} (right) and \gls{UH
|
|||
\end{center}
|
||||
\end{figure}
|
||||
|
||||
Ground stations can be viewed on the SatNOGS network website, such as
|
||||
Ground stations can be viewed on the \gls{SatNOGS} network website, such as
|
||||
as the example in figure \ref{fig:satnogs-ground-station-web}, page \pageref{fig:satnogs-ground-station-web}.%
|
||||
\footnote{\url{https://network.satnogs.org/stations/2733/}}
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
\index{hardware}
|
||||
Hardware considerations for a \gls{SatNOGS-Optical} \gls{ground-station}.
|
||||
|
||||
Main hardware components in an optical ground station:
|
||||
Main hardware components in an optical \gls{ground-station}:
|
||||
|
||||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{itemize}
|
||||
|
|
@ -29,7 +29,7 @@ Other components:
|
|||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{itemize}
|
||||
\item Ethernet cable. \index{ethernet}
|
||||
\item USB cable. \index{USB}
|
||||
\item \gls{USB} cable. \index{USB}
|
||||
\item Enclosure. \index{enclosure}
|
||||
\item Power supply. \index{power supply}
|
||||
\item Tripod. \index{tripod}
|
||||
|
|
@ -92,7 +92,7 @@ Embedded computers, such as Raspberry Pi, that can be used.
|
|||
\item [Odroid M1] --- Testing.
|
||||
\item [Raspberry Pi 3] --- ? \index{Raspberry Pi}
|
||||
\item [Raspberry Pi 4] --- ? \index{Raspberry Pi}
|
||||
\item [Intel NUC] --- ? \index{Intel}
|
||||
\item [Intel \gls{NUC}] --- ? \index{Intel}
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
|
||||
|
|
@ -107,11 +107,11 @@ Comparing embedded computers for \gls{SatNOGS-Optical}.
|
|||
\hspace*{-1.5cm}
|
||||
\begin{tabularx}{250pt}{|c|c|c|c|c|}
|
||||
\hline
|
||||
Make & Model & Architecture & Max RAM & eMMC \\
|
||||
Make & Model & Architecture & Max RAM & eMMC\\
|
||||
\hline
|
||||
Odroid & N2 & ARM64 & 4 GB & Yes \\
|
||||
Odroid & N2 & ARM64 & 4 GB & Yes\\
|
||||
\hline
|
||||
Odroid & M1 & ARM64 & 8 GB & Yes \\
|
||||
Odroid & M1 & ARM64 & 8 GB & Yes\\
|
||||
\hline
|
||||
\end{tabularx}
|
||||
\caption{Comparison of embedded computers}
|
||||
|
|
@ -123,7 +123,7 @@ Comparing embedded computers for \gls{SatNOGS-Optical}.
|
|||
\index{Odroid}\index{ARM64}\index{eMMC}
|
||||
|
||||
|
||||
\section{Example Optical Ground Station wtih Tracking}
|
||||
\section{Example Optical Ground Station with Tracking}
|
||||
\label{sec:hardware-tracking-ground-station}
|
||||
\index{ground station}\index{mount}\index{tracking}
|
||||
\index{tripod}
|
||||
|
|
@ -141,7 +141,7 @@ a Bosch \gls{PoE} camera enclosure,
|
|||
and through the glass the camera lens.
|
||||
\index{Sky-Watcher}\index{telescope}\index{mount}\index{Bosch}\index{PoE}\index{camera}
|
||||
\index{lens}
|
||||
In the background is a white antenna for \gls{GNSS} (\gls{GPS}) and a solar power setup.
|
||||
In the background is a white \gls{antenna} for \gls{GNSS} (\gls{GPS}) and a solar power setup.
|
||||
\index{GNSS}\index{GPS}\index{solar power}
|
||||
|
||||
\begin{figure}[p!]
|
||||
|
|
@ -230,14 +230,14 @@ is:
|
|||
\item Camera mounting screws, M6x25 (?).
|
||||
\item Ethernet cable, internal, short white (came with Bosch enclosure). \index{ethernet}
|
||||
\item \gls{PoE} ethernet cable, external, plugged into \gls{PoE} switch for data and power. \index{PoE}
|
||||
\item USB 3 cable, internal, way too long, needs replacing, from Odroid to camera. XXX flat connector
|
||||
\item USB 3 cable, external, from Odroid to telescope mount. XXX large rectangle connector \index{USB}
|
||||
\item ``Custom'' 12V DC power cable from Bosch \gls{PoE} to Odroid.
|
||||
\item \gls{USB} 3 cable, internal, way too long, needs replacing, from Odroid to camera. XXX flat connector
|
||||
\item \gls{USB} 3 cable, external, from Odroid to telescope mount. XXX large rectangle connector \index{USB}
|
||||
\item ``Custom'' 12\gls{V} \gls{DC} power cable from Bosch \gls{PoE} to Odroid.
|
||||
\item Assorted nuts, bolts, and washers for an ad-hoc standoff height.
|
||||
\end{itemize}
|
||||
\end{mdframed}
|
||||
\index{camera}\index{Kowa}\index{The Imaging Source}\index{Odroid}\index{Debian}
|
||||
\index{fan}\index{power cable}\index{mount plate}\index{Bosh}
|
||||
\index{fan}\index{power cable}\index{mount plate}\index{Bosch}
|
||||
\index{ethernet cable}\index{PoE}\index{USB}\index{power cable}
|
||||
|
||||
\begin{sidewaysfigure}[p!]
|
||||
|
|
@ -287,7 +287,7 @@ Tripod and similar options include:
|
|||
\item [Telescope Tripod] --- Similar to photography tripods, but typically heavier weight.
|
||||
\item [Telescope Portable Pier] --- Similar to a telescope tripod, but much heavier, typically
|
||||
with a larger center pier post. Still movable, and folds up similar to a photography tripod.
|
||||
\item [Telescope Pier] --- A wide variety, such as making a ~1.5 meter permanent cement post.
|
||||
\item [Telescope Pier] --- A wide variety, such as making a roughly 1.5 meter permanent cement post.
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\index{pier}
|
||||
|
|
@ -320,8 +320,8 @@ Tracking mount options to consider include:
|
|||
|
||||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{description}
|
||||
\item [Sky-Watcher EQ6-R Pro] --- Telescope mount using {INDI}.
|
||||
\item [Celestron] --- Wide variety of telescope mounts using {INDI}.
|
||||
\item [Sky-Watcher EQ6-R Pro] --- Telescope mount using \gls{INDI}.
|
||||
\item [Celestron] --- Wide variety of telescope mounts using \gls{INDI}.
|
||||
\item [iOptron] --- Telescope mount with (untested) satellite tracking.
|
||||
\item [INDI Telescope Mounts] --- A wide variety of other \gls{INDI} compatible telescope mounts.
|
||||
\item [Yaesu G-5500] --- Antenna \gls{rotator}.
|
||||
|
|
@ -360,7 +360,7 @@ For tracking, there a few different ways to track:
|
|||
|
||||
\subsection{Sidereal Tracking Mounts}
|
||||
Sidereal tracking (``telescope tracking'') is what \gls{COTS} tracking ``GOTO''
|
||||
\glspl{telescope} from Celestron or Sky-Watcher do, for example. They tracks
|
||||
\glspl{telescope} from Celestron or Sky-Watcher do, for example. They track
|
||||
the stars, countering the rotation of the Earth to keep the same view
|
||||
of the sky in the camera's \gls{FOV}. Stars remain as points, even after multi-minute
|
||||
or multi-hour imaging. This is what is used for ``pretty'' pictures
|
||||
|
|
@ -368,19 +368,17 @@ of stars, nebula, galaxies, etc.
|
|||
This is the most common tracking set up, as it has been widely used in
|
||||
astronomy communities for decades.
|
||||
|
||||
|
||||
Within sidereal tracking mounts, there are yet more options:
|
||||
|
||||
|
||||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{description}
|
||||
\item [Fork] --- Fork mount.
|
||||
\item [EQ fork] --- Fork on EQ mount.
|
||||
\item [German EQ] --- Most common EQ mount.
|
||||
\item [\gls{EQ} fork] --- Fork on \gls{EQ} mount.
|
||||
\item [German \gls{EQ}] --- Most common \gls{EQ} mount.
|
||||
\item [More] --- Endless variety of available telescope mounts.
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\index{German EQ}\index{fork} %XXX
|
||||
\index{German \gls{EQ}}\index{fork} %XXX
|
||||
\index{mount}\index{track}
|
||||
|
||||
Also related to sidereal tracking is lunar and planetary
|
||||
|
|
@ -407,7 +405,7 @@ It requires, such as:
|
|||
\begin{description}
|
||||
\item [Time] --- Accurate time, such as from \gls{GNSS}.
|
||||
\item [Location] --- Accurate location, also available from \gls{GNSS}.
|
||||
\item [TLE] --- Need to know the \glspl{satellite}' orbit (accurately!).
|
||||
\item [\gls{TLE}] --- Need to know the \glspl{satellite}' orbit (accurately!).
|
||||
\item [Variable speed tracking] --- \Glspl{satellite} are moving at different
|
||||
speeds above, the mount needs to be capable of that.
|
||||
\item [Human guided] --- Some skilled amateurs track by hand.
|
||||
|
|
@ -430,7 +428,7 @@ and leave star trails. The speed the mount moves needs to be calculated
|
|||
based upon a recent orbit calcuation, such as from a \gls{TLE}.
|
||||
|
||||
There are highly skilled amateur astronomers that have captured detailed
|
||||
pictures of artificial satellites, such as the ISS and astronauts doing
|
||||
pictures of artificial satellites, such as the \gls{ISS} and astronauts doing
|
||||
space walks, using hand guided telescopes with low cost \gls{CCD} imagers.
|
||||
\index{CCD}\index{ISS}
|
||||
% XXX ref
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ My fork is here:
|
|||
\index{satid}\index{sattools}\index{identify}
|
||||
\index{C}\index{Giza}
|
||||
|
||||
The deprecated C application, \texttt{satid} from the \texttt{\gls{sattools}}
|
||||
The deprecated \gls{C} application, \texttt{satid} from the \texttt{\gls{sattools}}
|
||||
package can help identify \glspl{satellite}.
|
||||
See figure \ref{fig:satid-giza-3}, page \pageref{fig:satid-giza-3}
|
||||
for output from my Giza port of \texttt{\gls{satid}}.%
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ A cursory review of \glspl{satellite} and existing \gls{RF} ground stations
|
|||
will be followed by a big picture view of acquiring and processing
|
||||
images of \glspl{satellite}. Hardware is reviewed, then software to run
|
||||
on it, with many options, including what is best. Finally,
|
||||
what to do with the data (idk!).
|
||||
what to do with the data (\gls{IDK}!).
|
||||
The chapters that follow are listed below.
|
||||
\index{RF}
|
||||
|
||||
|
|
@ -64,7 +64,7 @@ The chapters that follow are listed below.
|
|||
\end{mdframed}
|
||||
\index{ground station}\index{process}\index{hardware}\index{software}
|
||||
\index{acquire}\index{solve}\index{detect}\index{identify}\index{upload}
|
||||
\index{support}
|
||||
\index{support}\index{plate sover}
|
||||
|
||||
|
||||
\section{Libre Space Foundation}
|
||||
|
|
|
|||
|
|
@ -83,11 +83,11 @@ Examples of motion video camera sources that could be used:
|
|||
High quality cameras, believed to be usable following \gls{DFSG}.
|
||||
\item [ZWO ASI based on IMX174] --- Known to work. Not \gls{DFSG} compatible.
|
||||
Uses proprietary SDK. Currently in prototype development.
|
||||
\item [UVC/Video4Linux2] --- ``Any'' video camera that works with the \gls{Linux} kernel.
|
||||
\item [\gls{UVC}/\gls{V4L2}] --- ``Any'' video camera that works with the \gls{Linux} kernel.
|
||||
Typically, the device will appear similar to \texttt{/dev/video0}. A camera
|
||||
that works with the software isn't necessarily sensitive enough to detect
|
||||
satellites, however, as most are designed for brighter environments.
|
||||
\item [OpenCV] --- Devices that work with OpenCV can be used, same as UVC.
|
||||
\item [OpenCV] --- \gls{CV} devices (cameras) that work with OpenCV can be used, same as \gls{UVC}.
|
||||
To work well, they need to be sensitive.
|
||||
\item [Raspberry Pi] --- The PiCamera can be used. A good lower cost option.
|
||||
Recommended. Many non-Raspberry Pi devices, such as Odroid are also compatible with the Pi
|
||||
|
|
@ -137,7 +137,7 @@ There are also broader ``paths'' that need to be considered:
|
|||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{description}
|
||||
\item [\gls{sattools}] --- Deprecated because it is in \gls{C}, and the
|
||||
decision was made to move forward with applications primarily
|
||||
decision by upstream and the \gls{LSF} was made to move forward with applications primarily
|
||||
written in \gls{Python}. \Gls{sattools} is the most complete toolkit,
|
||||
however, so no matter what path is chosen, some parts of it will likely
|
||||
be used for now. It can be used with motion video cameras and
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ antention to ones using amateur \gls{RF} bands.
|
|||
\section{SatNOGS DB}
|
||||
\label{sec:satnogs-db}
|
||||
|
||||
The \gls{SatNOGS DB} is a database that lists \glspl{satellite},
|
||||
The SatNOGS \gls{DB} is a database that lists \glspl{satellite},
|
||||
many of which can be tracked by ground station operators on the
|
||||
\gls{SatNOGS} network.
|
||||
|
||||
|
|
@ -107,8 +107,8 @@ for a example list of observations of the RamSat \Gls{cubesat}.%
|
|||
|
||||
Individual \gls{RF} observations are uploaded to the SatNOGS network,
|
||||
as can be seen in the example observation of the RamSat by SatNOGS
|
||||
ground station ``2380 - Piszkesteto UHF'' run by volunteer bcsak (username).
|
||||
\index{RF}\index{RamSat}
|
||||
ground station ``2380 - Piszkesteto \gls{UHF}'' run by volunteer bcsak (username).
|
||||
\index{RF}\index{RamSat}\index{UHF}\index{bcsak}
|
||||
|
||||
\begin{figure}[h!]
|
||||
\begin{framed}
|
||||
|
|
|
|||
|
|
@ -92,7 +92,7 @@ git clone https://spacecruft.org/spacecruft/stvid
|
|||
#git clone https://github.com/cbassa/stvid
|
||||
\end{minted}
|
||||
|
||||
Optionally, set up a \gls{Python} virtual environment:
|
||||
Optionally, set up a \gls{Python} virtual environment and use \gls{PIP}:
|
||||
\index{Python}\index{virtualenv}
|
||||
|
||||
\begin{minted}{sh}
|
||||
|
|
@ -179,7 +179,7 @@ export ST_LOGIN="identity=foo@no:pass"
|
|||
\end{minted}
|
||||
\index{sattools}\index{TLE}
|
||||
|
||||
Set \texttt{astrometry.net} to run in parallel, assuming you have enough RAM:
|
||||
Set \texttt{astrometry.net} to run in parallel, assuming you have enough \gls{RAM}:
|
||||
(This doesn't appear to work? Breaks?).
|
||||
\index{astrometry.net}
|
||||
|
||||
|
|
@ -261,7 +261,7 @@ sudo make uninstall
|
|||
\end{minted}
|
||||
|
||||
See below for \gls{skymap} (fork) usage:
|
||||
\index{TLE}
|
||||
\index{TLE}\index{skymap}
|
||||
|
||||
\begin{minted}{sh}
|
||||
tleupdate
|
||||
|
|
@ -315,7 +315,7 @@ software:
|
|||
\begin{description}
|
||||
\item [Telescope] --- Controlling \glspl{telescope} remotely.
|
||||
\item [Antenna] --- Controlling \glspl{antenna} remotely with hamlib.
|
||||
\item [Cameras] --- Controlling PTZ cameras remotely.
|
||||
\item [Cameras] --- Controlling \gls{PTZ} cameras remotely.
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\index{telescope}\index{antenna}
|
||||
|
|
@ -326,13 +326,13 @@ Software that can be used with telescope tracking mounts:
|
|||
|
||||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{description}
|
||||
\item [INDI] --- Main client/server used by other applications.
|
||||
\item [KStars] --- Sky charts, INDI control.
|
||||
\item [\gls{INDI}] --- Main client/server used by other applications.
|
||||
\item [KStars] --- Sky charts, \gls{INDI} control.
|
||||
\item [Ekos] --- Application used within KStars for remote control
|
||||
of \glspl{telescope} and related hardware via \gls{INDI}.
|
||||
\item [Stellarium] --- Sky charts, has \gls{INDI} plugin.
|
||||
\item [Other INDI] --- Many more applications work with \gls{INDI}.
|
||||
\item [INDIGO] --- Positions itself as a next-generation INDI (?).
|
||||
\item [Other \gls{INDI}] --- Many more applications work with \gls{INDI}.
|
||||
\item [INDIGO] --- Positions itself as a next-generation \gls{INDI} (?).
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\index{telescope}\index{INDI}\index{KStars}\index{Ekos}\index{Stellarium}
|
||||
|
|
@ -363,12 +363,12 @@ be steady enough.
|
|||
|
||||
|
||||
\subsection{Camera Tracking Software}
|
||||
There are applications for using PTZ control of cameras, such as used in
|
||||
There are applications for using \gls{PTZ} control of cameras, such as used in
|
||||
``security'' cameras.
|
||||
|
||||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{description}
|
||||
\item [motion] --- PTZ camera control. XXX check
|
||||
\item [motion] --- \gls{PTZ} camera control. XXX check
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
|
||||
|
|
@ -385,17 +385,17 @@ at present.
|
|||
accurately determining the location of the observation.
|
||||
|
||||
\gls{GNSS} collectively includes the USA \gls{GPS}, Europe's Galileo,
|
||||
Russia's GLONASS, and China's Beidou, as well as other
|
||||
Russia's \gls{GLONASS}, and China's \gls{BDS}, as well as other
|
||||
regional systems.
|
||||
\index{GPS}\index{Galileo}\index{GLONASS}\index{Beidou}
|
||||
|
||||
A basic, widely available \gls{COTS} USB \gls{GNSS} device
|
||||
A basic, widely available \gls{COTS} \gls{USB} \gls{GNSS} device
|
||||
with a basic (or no!) \gls{antenna} plugged into the embedded
|
||||
computer can get time and location accurate enough for the
|
||||
purposes here. See various U-Blox devices, for example.
|
||||
\index{COTS}\index{USB}\index{U-Blox}
|
||||
|
||||
In \gls{Debian} \gls{GNSS} service with a USB device can be provided
|
||||
In \gls{Debian} \gls{GNSS} service with a \gls{USB} device can be provided
|
||||
by the \texttt{gpsd} application.
|
||||
\index{Debian}
|
||||
|
||||
|
|
@ -423,7 +423,7 @@ used in that case:
|
|||
DEVICES="/dev/serial/by-id/usb-u-blox_AG_-_www.u-blox.com_u-blox_GNSS_receiver-if00"
|
||||
\end{minted}
|
||||
|
||||
Even with \texttt{gpsd} configuration listening on all IPs,
|
||||
Even with \texttt{gpsd} configuration listening on all \glspl{IP},
|
||||
don't think \texttt{systemd} won't do what it likes. So
|
||||
you may have to do:
|
||||
|
||||
|
|
@ -431,7 +431,7 @@ you may have to do:
|
|||
systemctl edit --full gpsd.socket
|
||||
\end{minted}
|
||||
|
||||
And create a configuration like this (I have IPv6 disabled, in this case):
|
||||
And create a configuration like this (I have \gls{IPv6} disabled, in this case):
|
||||
|
||||
\begin{minted}{sh}
|
||||
[Unit]
|
||||
|
|
@ -505,16 +505,16 @@ See below for sample output from \texttt{cgps}.
|
|||
\index{NTP}
|
||||
With all the above, time still needs to be configured.
|
||||
Configuring \texttt{gpsd} isn't enough for correct system time.
|
||||
The main system on the Internet used for time synchronization is NTP.
|
||||
In \gls{Debian} there are a few options for NTP.
|
||||
The best is to use a hardware GPS, with PPS for improved
|
||||
accuracy. The easiest is to just use NTP.
|
||||
\index{PPS}
|
||||
The main system on the Internet used for time synchronization is \gls{NTP}.
|
||||
In \gls{Debian} there are a few options for \gls{NTP}.
|
||||
The best is to use a hardware \gls{GNSS} (\gls{GPS}), with \gls{PPS} for improved
|
||||
accuracy. The easiest is to just use \gls{NTP}.
|
||||
\index{PPS}\index{Debian}\index{GNSS}
|
||||
|
||||
All systems in the chain need to have the correct time and
|
||||
location. It is best if they all pull from the same NTP
|
||||
location. It is best if they all pull from the same \gls{NTP}
|
||||
server, or even better than best if they all run \gls{GNSS}
|
||||
hardware with PPS enabled.
|
||||
hardware with \gls{PPS} enabled.
|
||||
|
||||
Some quick and dirty time synchronization commands.
|
||||
The \texttt{ntpd} daemon can have slow startup synchronization
|
||||
|
|
@ -551,7 +551,7 @@ One main use is to control a telescope tracking mount, such as the
|
|||
hardware described in section \ref{sec:hardware-mounts}, page \pageref{sec:hardware-mounts}.
|
||||
|
||||
For the purposes here, described below will be using KStars with a
|
||||
Sky-Watcher tracking mount with INDI and Ekos.
|
||||
Sky-Watcher tracking mount with \gls{INDI} and Ekos.
|
||||
See figure \ref{fig:video-enclosure-mount-tripod}, page \pageref{fig:video-enclosure-mount-tripod}
|
||||
for a photo of the setup used with KStars below.
|
||||
|
||||
|
|
@ -563,12 +563,13 @@ Sidereal is the ``standard'' tracking mode of \glspl{telescope}.
|
|||
\index{Sky-Watcher}\index{INDI}\index{Ekos}
|
||||
|
||||
KStars is the ``main'' application, but it depends on other key parts.
|
||||
\gls{INDI} is the protocol that KStars uses for telescope control.
|
||||
\gls{INDI} is the protocol that KStars uses for \gls{telescope} control.
|
||||
\gls{INDI} itself is a collection of applications.
|
||||
While KStars has the main sky chart and Ekos is launched within it,
|
||||
the actual mount control is done with the Ekos application.
|
||||
While it may sound complex, all of this is set up pretty easily in
|
||||
\gls{Debian}.
|
||||
\index{INDI}\index{Debian}
|
||||
|
||||
\begin{minted}{sh}
|
||||
# Quick and dirty from memory, something like:
|
||||
|
|
@ -595,7 +596,7 @@ A brief overview of steps:
|
|||
\item Physically mount all hardware.
|
||||
\item Plug in and power everything up.
|
||||
\item Confirm all hardware looks ok (e.g. \texttt{lsusb}).
|
||||
\item Confirm GNSS time and location are ok (e.g. \texttt{cgps -u m}).
|
||||
\item Confirm \gls{GNSS} time and location are ok (e.g. \texttt{cgps -u m}).
|
||||
See section \ref{sec:software-gnss}, page \pageref{sec:software-gnss}.
|
||||
\item Confirm time is correct on all systems in toolchain (e.g. \texttt{date}).
|
||||
See section \ref{sec:software-ntp}, page \pageref{sec:software-ntp}.
|
||||
|
|
@ -604,16 +605,16 @@ A brief overview of steps:
|
|||
include a camera (such as \texttt{indi\_v4l2\_ccd}.
|
||||
\item Start KStars on the workstation.
|
||||
\item Launch Ekos within KStars, under \texttt{Tools}.
|
||||
\item In Ekos, select a configuration with the EQ Mount for the Sky-Watcher,
|
||||
and \texttt{V4L2} for the CCD, which will work with The Imaging Source
|
||||
\item In Ekos, select a configuration with the \gls{EQ} Mount for the Sky-Watcher,
|
||||
and \texttt{\gls{V4L2}} for the \gls{CCD}, which will work with The Imaging Source
|
||||
camera used in this example. Alternatively, the ZWO ASI could be used with a similar configuration.
|
||||
\item The Ekos configuration should also be set to use the remote \texttt{indiserver}
|
||||
IP address of the embedded computer USB connected to the Sky-Watcher mount.
|
||||
\item Hit the start button to start Ekos/INDI.
|
||||
\gls{IP} address of the embedded computer \gls{USB} connected to the Sky-Watcher mount.
|
||||
\item Hit the start button to start Ekos/\gls{INDI}.
|
||||
\item On the screen that pops up, confirm all the tabs are good.
|
||||
\item Check the last configuration tab for the camera, it often
|
||||
resets the size.
|
||||
\item Hit close on the screen with the INDI devices.
|
||||
\item Hit close on the screen with the \gls{INDI} devices.
|
||||
\item Click the mount icon, and start tracking.
|
||||
\item Perhaps do some focusing... XXX
|
||||
\item Click the solver icon.
|
||||
|
|
@ -625,9 +626,9 @@ A brief overview of steps:
|
|||
\item Stop the \texttt{indiserver} running on the embedded computer.
|
||||
\item Start the \texttt{indiserver} on the embedded computer, but without using a camera
|
||||
(e.g. remove \texttt{indi\_v4l2\_ccd}.
|
||||
\item Select the INDI configuration with a remote \texttt{indiserver},
|
||||
the EQ Mount, and the Simulated \gls{CCD}.
|
||||
\item Hit start in Ekos to get INDI connections going.
|
||||
\item Select the \gls{INDI} configuration with a remote \texttt{indiserver},
|
||||
the \gls{EQ} Mount, and the Simulated \gls{CCD}.
|
||||
\item Hit start in Ekos to get \gls{INDI} connections going.
|
||||
\item Confirm all is ok in hardware tabs, then hit close.
|
||||
\item Now in the KStars sky chart window there is control of the mount without
|
||||
interfering with the camera.
|
||||
|
|
|
|||
Loading…
Reference in New Issue