Skip to content
This repository was archived by the owner on May 13, 2025. It is now read-only.

Commit 4e2fc0e

Browse files
authored
Merge pull request #21 from synfinatic/lx200-st
Add Set Time support for LX200 protocol
2 parents de1c6e0 + 5657b80 commit 4e2fc0e

File tree

5 files changed

+213
-40
lines changed

5 files changed

+213
-40
lines changed

CHANGELOG.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,21 @@
22

33
## Unreleased
44

5+
## v1.0.0 - 2021-01-23
6+
57
Added:
68

79
- Support for Nexstar tracking commands: t and T
10+
- Add date/time processing for LX200 GPS
11+
12+
Fixed:
13+
814
- Fix crash when setting Lat/Long due to index out of range
9-
- Clean up Nexstar cmd processing
15+
16+
Changed:
17+
18+
- Clean up NexStar cmd processing to be cleaner
19+
- Huge update to README.md
1020

1121
## v0.0.5 - 2021-01-17
1222

Makefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ endif
99
BUILDINFOSDET ?=
1010
PROGRAM_ARGS ?=
1111

12-
PROJECT_VERSION := 0.0.6
12+
PROJECT_VERSION := 1.0.0
1313
DOCKER_REPO := synfinatic
1414
PROJECT_NAME := alpacascope
1515
PROJECT_TAG := $(shell git describe --tags 2>/dev/null $(git rev-list --tags --max-count=1))

README.md

Lines changed: 59 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,12 @@ and Sequence Generator Pro's [WiFi Scope](https://www.sequencegeneratorpro.com/d
99
The difference is that instead of using a special device you have to buy to control
1010
your telescope, you can use your Windows computer. AlpacaScope controls your
1111
telescope via [ASCOM](https://ascom-standards.org) and [ASCOM Remote Server](
12-
https://github.com/ASCOMInitiative/ASCOMRemote).
12+
https://github.com/ASCOMInitiative/ASCOMRemote) or via [Alpaca](
13+
https://ascom-standards.org/Developer/Alpaca.htm) directly.
1314

14-
WiFi Scope is probably the closest thing to AlpacaScope- it also runs on Windows and
15-
ASCOM. Unfortunately, I've found WiFi Scope buggy (it crashes a lot for me)
16-
which is why I ended up writing this. Now AlpacaScope has more features
15+
WiFi Scope is probably the closest thing to AlpacaScope- it also runs on Windows
16+
and uses ASCOM. Unfortunately, I've found WiFi Scope buggy (it crashes a lot
17+
for me) which is why I ended up writing this. Now AlpacaScope has more features
1718
than WiFi Scope.
1819

1920
## Why?
@@ -40,7 +41,8 @@ https://ascom-standards.org/Developer/Alpaca.htm) which via
4041
exposes the ASCOM API via REST. Of course, SkySafari doesn't support this (yet)
4142
so I decided to write a service which emulates a telescope SkySafari supports
4243
and talks to Alpaca Remote Server. The result is that SkySafari can now control
43-
my Celestron Evolution mount, or any mount that supports the ASCOM standard.
44+
my Celestron Evolution mount, or any mount that supports the ASCOM or
45+
Alpaca standards.
4446

4547
## Install
4648

@@ -62,8 +64,8 @@ box as ASCOM & the Alpaca Remote Server) and run it. It will automatically find
6264
the ASCOM Remote Server running on your network and connect to it.
6365

6466
Configure SkySafari or other remote control software to connect to AlpacaScope on port
65-
4030 using the Celestron Nexstar (I use the Nexstar/Advanced GT) or Meade LX200
66-
protocol. AlpacaScope supports both, but defaults to Nexstar.
67+
4030 using the Celestron NexStar (I use the NexStar/Advanced GT) or Meade LX200 GPS
68+
protocol. AlpacaScope supports both, but defaults to NexStar.
6769

6870
Note that AlpacaScope now supports the "Auto-Detect SkyFi" feature in SkySafari
6971
so you should no longer need to enter the IP address of AlpacaScope.
@@ -83,19 +85,31 @@ flag.
8385

8486
## FAQ
8587

88+
#### Does this only work with NexStar and LX200 series telescopes?
89+
90+
No! AlpacaScope works with any telescope / mount supported by Alpaca or
91+
ASCOM. The LX200 and NexStar protocols are only for communicating with software
92+
like SkySafari. You can even use the LX200 protocol with your Celestron scope
93+
if you want because AlpacaScope does all the translating between the different
94+
protocols.
95+
8696
#### What do I need at minimum?
8797

88-
1. A telescope connected to a Windows machine
89-
2. ASCOM installed an configured for your mount
90-
3. ASCOM Remote Server installed, configured & running
91-
4. AlpacaScope installed and running
92-
5. Some kind astronomy software which talks the LX200 or Celestron Nexstar protocols
98+
1. A telescope mount with an ASCOM or Alpaca driver.
99+
1. The ASCOM/Alpaca driver configured on a computer.
100+
1. If your mount only has an ASCOM driver, you will need ASCOM Remote Server installed, configured & running
101+
1. AlpacaScope installed and running
102+
1. Some kind astronomy software which talks the LX200 or Celestron NexStar protocols
93103
(SkySafari, etc)
94104

95-
#### Does this support SkySafari on Mac, iPad, Windows, Android, etc?
105+
#### Does this support SkySafari on Mac, iPad, Android, etc?
96106
Yes, this supports all versions of SkySafari which allow for controlling telescopes.
97107
Typically this is SkySafari Plus and Pro.
98108

109+
#### What about other astronomy software?
110+
Yep, anything that can do Celestron NexStar or LX200 protocols over TCP/IP
111+
should work.
112+
99113
#### Why do I get a virus warning for alpacascope?
100114
Unfortunately, this is a [known issue with GoLang programs](
101115
https://golang.org/doc/faq#virus). A few anti-virus programs incorrectly
@@ -109,30 +123,44 @@ with 71 different AV engines via Google VirusTotal and as you can see, only
109123
For the record, I build all the release binaries on a Mac- so the chances of
110124
a Windows virus infecting the binaries is pretty much zero.
111125

112-
#### What about other astronomy software?
113-
Yep, anything that can do Celestron Nexstar or LX200 protocols over TCP/IP
114-
should work.
115-
116-
#### What features work?
126+
#### What features work with SkySafari?
117127

118128
* Manual slewing
119129
* Controlling slew speed
120130
* Goto a target
121-
* Align on target (maybe?)
131+
* Align on target
132+
* Set time and location of observing site
133+
134+
#### I'm using something other than SkySafari and it has more feature than that?
135+
AlpacaScope can support any command supported by both the [Alpaca API](
136+
https://ascom-standards.org/api/?urls.primaryName=ASCOM%20Alpaca%20Device%20API#/)
137+
and the LX200/NexStar command sets. If you have a need for another command,
138+
please open a feature request on GitHub.
139+
140+
#### What about focuser, filter wheel, etc support?
141+
The NexStar and LX200 protocols don't support that.
122142

123143
#### Does AlpacaScope support [INDI](https://www.indilib.org)?
124-
No it doesn't. There's probably no reason it can't support INDI, but CWPI
125-
doesn't support INDI so I have no easy way of developing/testing the code.
144+
No it doesn't. There's probably no reason it can't support INDI since I believe
145+
it is cross-platform, but I haven't looked into it yet.
126146

127-
#### Does AlpacaScope need to run on the same computer as CWPI/ASCOM?
147+
#### Does AlpacaScope need to run on the same computer as Alpaca or ASCOM Remote?
128148
No, but that is probably the most common solution. AlpacaScope just needs
129149
to be able to talk to the ASCOM Remote Server running on the same computer as the
130150
ASCOM driver connected to your telescope mount.
131151

132-
#### My software only supports the Meade LX200 protocol. Can I use that?
133-
Yes! Slewing and GoTo works. Be sure to specify `--mode lx200`.
134-
I believe align/sync should work but it doesn't seem to work with my mount/CWPI.
135-
Not sure if it's a bug on my end or a limitation with CWPI?
152+
#### My telescope mount has an Alpaca driver. Can I use that instead of going through ASCOM?
153+
Yes! Over time I expect more telescope mounts to have native Alpaca support
154+
and not require using ASCOM and ASCOM Remote.
155+
156+
#### For the LX200 protocol should I select "LX200 Classic" or "LX200 GPS"?
157+
SkySafari users should use "LX200 GPS/ACF LX600" as there seems to be at least
158+
[one issue](https://github.com/synfinatic/alpacascope/issues/20)
159+
with using LX200 Classic mode.
160+
161+
#### For the NexStar protocol, which scope type should I select?
162+
SkySafari users should probably use "Celestron NexStar/Advanced GT" as that's
163+
what I've done most of my testing.
136164

137165
#### How to build on Windows?
138166
If you wish to build your own binary on Windows, you'll need to do:
@@ -156,18 +184,18 @@ If you wish to build your own binary on Windows, you'll need to do:
156184
1. Clone this repoistory onto your computer using Git or just downloading the
157185
Zip file from Github.
158186
1. Run `make` (or `gmake`) to build a binary for your OS.
159-
1. Run `make help` to get a list of other OS targets you can build. Note that
187+
1. Run `make help` to get a list of other OS targets you can build. Note that
160188
GoLang makes cross-compiling easy so no problems building a Windows binary
161189
on Linux or MacOS binary on a RaspberryPi. :)
162190

163191
#### What is the purpose of the --mount-type flag?
164192

165-
The Celestron Nexstar protocol supports the concept of different tracking modes:
166-
AltAz, EQ North, EQ South and Off. Typically this would be used with a AltAz
167-
fork mount which can optionally have a wedge. The result is the mount must be
193+
The Celestron NexStar protocol supports the concept of different tracking modes:
194+
AltAz, EQ North, EQ South and Off. Typically this would be used with a AltAz
195+
fork mount which can optionally have a wedge. The result is the mount must be
168196
told to change it's tracking mode.
169197

170-
However, Alpaca/ASCOM does not support this- it only allows you to turn on &
198+
However, Alpaca/ASCOM does not support this- it only allows you to turn on &
171199
off tracking. Hence, AlpacaScope allows you to specify the mount type at startup,
172200
and then when SkySafari/etc queries the current tracking mode it will get the
173201
correct answer.

0 commit comments

Comments
 (0)