New post
0

Why Can't Demo Scope Slew To An Object When Time Is Forwarded Such That The Object's Position Is Changed From Below The Horizon To Above The Horizon? (Answer: Read On!)

Skysafari pro 6,7. android, iPad. 

 Using the app. during day time.

Engaging demo telescope.

Choosing a target that is below the horizon. 

Changing  time flow to evening hours, say 22:00. The target is now above the horizon.

Performing a "go to" .

Receive this note :"The scope can't slew to the target coordinates because  they are below the horizon".

My question is why doesn't the app. comply with the new time entered in the time flow ?

Thanks

Sam

 

4 comments

  • 0
    Avatar
    Mike Atkins

    I can also repeat this using the Demo Scope.

    I've connected it and advanced the time to 10 PM. I can center on an object but cannot Go-To one that SkySafari thinks is below the horizon based on current time. The demo controls only respect what current time is, not a future time you set SS7 to.

    SkySafari Pro 7.0.5.2
    Samsung Galaxy S22 Ultra
    Android 12/OneUI 4.1

  • 0
    Avatar
    Keiron Smith

    Samuel, Mike,

    SkySafari will not slew to coordinates below the horizon because changing the time in SkySafari does not change the real position of the object.

    Demo scope is provided as an example of what you can expect when using a real scope. 

    A real scope is never going to slew to a new "time" unless you complete an alignment using that new time too.

    Thanks!

  • 0
    Avatar
    Samuel shachaf

    Thank you for your response.

    I understand your argument, but I still think that advancing the time so the object that was below horizon becomes above it, does not 

    contradict the argument. 

    If Demo would comply with the new time and not the real time, it would still "refuse" to perform a goto to a target below the "new" horizon.

    Any way, this issue can be bypassed by changing the "real time" on the tablet- an action which I wanted to avoid. 

  • 0
    Avatar
    Keiron Smith

    Right, changing the realtime on the device is the workaround.

    Thanks!

Please sign in to leave a comment.