View Issue Details

IDProjectCategoryView StatusLast Update
0002028CCdciel[All Projects] Generalpublic18-11-20 17:15
ReporterCedric RaguenaudAssigned ToPatrick Chevalley 
Status resolvedResolutionfixed 
Product Version 
Target Version1.0Fixed in Version 
Summary0002028: Suggestion: skip current plan when hitting limits
DescriptionWhen running a sequence, when the mount hits the limits defined in the ASCOM driver, cancel the current plan and move on to the next target.
TagsNo tags attached.


Patrick Chevalley

18-11-16 22:45

administrator   ~0005089

There is no Ascom function (and no Indi too) to know if the telescope reach some limit.
So as seen from CCDciel the telescope will probably stop tracking or maybe be parked, depending on how this is configured in the driver or the handpad.
What your mount do when it reach the limits?

But I think the best is to not let the mount go to the limits, this must be seen as a security feature, not an operational one.

There is function in CCDciel that help for that.
- The automatic meridian flip options manage the meridian limit a better way without interrupting an exposure.
- The horizon limit are managed by the rise/set options in the Begin/End column of the sequence. This rise/set are not at 0° of elevation, you can configure the minimum elevation in the observatory preferences, or load an horizon file to have different elevation for different azimuth.

Do your mount as other limits that can not be prevented by this options?

Cedric Raguenaud

18-11-16 22:52

reporter   ~0005092

My mount is setup to stop when a limit is reached. I didn't like the idea of going back home avec that happened.
I agree it's a safety measure. But my horizon is very irregular due to trees, the observatory, and my house. So I setup 35 degrees minimum altitude but in a few places there is a spike above that. I don't really want to increase the minimum altitude because its lose large amounts of sky.
Is fine if it's not possible.

Patrick Chevalley

18-11-17 20:46

administrator   ~0005103

Yes, that's why you can use an horizon profile that give the altitude for each azimuth. The format of the file is the same as for Cartes du Ciel, azimut in the first column, elevation in the second. When such a file is loaded in CCdciel the rise/set time are computed above this line.
Here a part of my file and in attachment how it look in CdC.
70 19
80 20.5
85 26
90 28
93 21
95 25
110 25
115 18
117 20
121 18
125 20
128 14
135 12
140 14
143 12
145 14
147 10
148 10
150 13
153 12
155 9.5
157 9.5
158 12
162 8.5
163 11.5
165 11
166 8
170 7

hotizon.png (186,958 bytes)
hotizon.png (186,958 bytes)

Patrick Chevalley

18-11-17 20:53

administrator   ~0005104

And another point.
When the target go behind the trees this produce a star lost event for PHD2. You can configure how CCDciel react to this event, how long it wait for recovery before to go to the next target, just set a smaller value for "Abort after".

Cedric Raguenaud

18-11-18 12:42

reporter   ~0005107

Ah that's great I didn't know it was used for rise/set values. That helps a lot. I'll reuse my eqmod horizon and that should take care of more issues.

Patrick Chevalley

18-11-20 17:15

administrator   ~0005115

As it is better to not reach the mount limits it is also good if the sequence can react correctly when this arise and the tracking stop.

With this change it process the next target if the tracking cannot be restarted after 1 minute.

Issue History

Date Modified Username Field Change
18-11-16 17:15 Cedric Raguenaud New Issue
18-11-16 22:45 Patrick Chevalley Assigned To => Patrick Chevalley
18-11-16 22:45 Patrick Chevalley Status new => feedback
18-11-16 22:45 Patrick Chevalley Target Version => 1.0
18-11-16 22:45 Patrick Chevalley Note Added: 0005089
18-11-16 22:52 Cedric Raguenaud Note Added: 0005092
18-11-16 22:52 Cedric Raguenaud Status feedback => assigned
18-11-17 20:46 Patrick Chevalley File Added: hotizon.png
18-11-17 20:46 Patrick Chevalley Note Added: 0005103
18-11-17 20:53 Patrick Chevalley Note Added: 0005104
18-11-18 12:42 Cedric Raguenaud Note Added: 0005107
18-11-20 17:15 Patrick Chevalley Status assigned => resolved
18-11-20 17:15 Patrick Chevalley Resolution open => fixed
18-11-20 17:15 Patrick Chevalley Note Added: 0005115