After meridian flip, things go haywire


#1

I’ve not experienced this behavior until the last couple of nights. I’m currently on 3.1.0.153 of SGP. Once it flips it will solve, and in this case it was off by around 2,000 pixels, it commands a slew and the mount will slew, but then it will immediately return to the prior position (it was far enough I could see the scope move slightly back and forth). I snagged out the last solve section of the log where it says that the sync gets rejected by EQMOD. I used to be able to do meridian flips just fine. If I park the mount and then command a recenter the sequence takes off again like everything is normal.

[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] *********** SUCCESSFUL SOLVE *************
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] SOLVER: False
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] SUCCESS: True
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] CONF: 218
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] BLIND: False
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] RA: 5.63779332109193
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] DEC: -5.30881149755124
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] SCALE: 1.14963
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] FLIPPED: False
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] ANGLE (EON): 260.79
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] MSG: Valid solve.
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] ******************************************
[01/09/19 22:50:58.679][DEBUG] [Telescope Thread] Checking to see if solve might be bad…
[01/09/19 22:50:58.684][DEBUG] [Telescope Thread] Solve appears to be good…
[01/09/19 22:50:58.684][DEBUG] [Telescope Thread] Auto center validation frame solved successfully…
[01/09/19 22:50:58.684][DEBUG] [Telescope Thread] Telescope: Syncing to J2000 RA: 5.63779332109193 Dec: -5.30881149755124
[01/09/19 22:50:58.684][DEBUG] [Telescope Thread] Telescope: Sync behavior set to “Sync”…
[01/09/19 22:50:58.803][DEBUG] [Telescope Thread] ASCOM Telescope: Invalid Operation Exception in Sync : SyncToTarget() RaDec sync was rejected. (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Runtime.InteropServices.COMException: SyncToTarget() RaDec sync was rejected.
— End of inner exception stack trace —
at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, CultureInfo culture)
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 443)
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 483
at ASCOM.DriverAccess.Telescope.SyncToCoordinates(Double RightAscension, Double Declination) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Telescope.cs:line 1135
at qy.kq(Double A_0, Double A_1, Boolean A_2)


#2

I know there are some specifics in EQMOD that SGP needs to work well. Have these changed in your setup or did you recently upgrade/change your EQMOD version?

Thanks,
Jared


#3

Hi Jared,

Nothing has changed with EQMOD that I am aware of / consciously can think of. I think it’s been 2.00q since around May or June something around that timeframe. I upgraded it shortly after it was released on sourceforge.

I was hoping to get a couple more nights in to try and nail it down but the clouds have rolled in and the forecast is snow and more clouds for quite a while looks like :frowning:


www.mainsequencesoftware.com