SharpCap Forums

The iOptron Commander software sometimes asks the user to confirm 'normal' or "counterweight up' pointing when doing a slew to a position near the meridian. If commanded from the SharpCap sequencer, the mount waits for an answer to the normal/up question, gives up after 2 minutes and that kills the sequence.

Imagine the mount is 1 deg past the meridian. Doing a slew to the saved position should now initiate a meridian flip. This sequence often doesn't actually flip and then crashes the sequence:

GOTO SAVED COORDINATES

The way around the problem is to command a slew to a position more than 10 degs from the meridian, before doing the flip. This does work:

MOUNT OFFSET 1 0
GOTO SAVED COORDINATES

I've tested it successfully indoors, on both the north and south meridians.

Hi,

that's a neat trick - thanks for sharing.

The mount offset capability was actually added to help deal with iOptron mounts prompting for confirmation for GOTO movements near the sun - it's good to see that you have found another use for it!

I did notice the other day in iOptron commander there is an option to set how far past the meridian it is allowed to track (and what it does when it reaches the limit). You would have thought that the same option might have an effect on warning messages, but maybe not

cheers,

Robin

Just done some more testing on this issue. IOptron Commander appears to ask the counterweight up / normal question when within about 1.9 degs if the meridian. If you are 2 degs away (or more) then it doesn't. So you can command a meridian flip by just using GOTO SAVED COORDINATES as long as you are at least 2 degs from the meridian (either before or after). I've emailed iOptron tech support to confirm this.

As this behaviour comes from Commander, I would guess that it also applies to some other iOptron mounts as well.