ASCOM DriverException v1.0.2.4

[catlover-forever]

I'm trying to use OATControl against my newly built OAT, using an MKS Gen L v2.1 board with two MEMA 17 0.9º steppers connected. In OATControl I press Connect which leads me to Available Connections, where the option ASCOM:OpenAstroTracker appears. The Setup button works fine but when I click the connection option, followed by Next, I get the message Connecting to OAT on ASCOM:OpenAstroTracker and then nothing more happens. The Cancel button still works, where I can display the log files. Each of these actions generate a new exception report as shown below:

[00:00:00.256] [01]: Mount: Initialization starting... [00:00:00.256] [01]: Mount: Initializing communication handler factory... [00:00:00.256] [01]: Mount: Checking whether ASCOM driver is present... [00:00:00.256] [01]: Mount: Loading ASCOM driver ... [00:00:00.303] [01]: Mount: ASCOM driver successfully added... [00:00:00.303] [01]: Mount: Initiating communication device discovery... [00:00:00.303] [01]: COMMFACTORY: Device Discovery initiated. [00:00:00.303] [01]: SERIAL: Checking Serial ports.... [00:00:00.303] [01]: SERIAL: Found Serial port [COM3] [00:00:00.303] [01]: COMMFACTORY: Device found: Serial: COM3 [00:00:00.303] [01]: COMMFACTORY: Device found: ASCOM: OpenAstroTracker [00:00:00.303] [01]: Mount: Device discovery started... [00:00:00.318] [01]: Mount: Attempting to read Point of Interest from C:\Program Files (x86)\OATControl\PointsOfInterest.xml... [00:00:00.334] [01]: Mount: Successfully read 37 Points of Interest. [00:00:00.334] [01]: Mount: Initialization of OATControl 1.0.2.4 complete... [00:00:05.408] [01]: Mount: Connect to OAT requested [00:00:05.470] [01]: Mount: Showing OAT comms Chooser Wizard [00:00:05.528] [05]: COMMFACTORY: Device Discovery initiated. [00:00:05.528] [05]: SERIAL: Checking Serial ports.... [00:00:05.528] [05]: SERIAL: Found Serial port [COM3] [00:00:05.528] [05]: COMMFACTORY: Device found: Serial: COM3 [00:00:05.543] [05]: COMMFACTORY: Device found: ASCOM: OpenAstroTracker [00:00:11.203] [01]: COMMFACTORY: Attempting to connect to device ASCOM: OpenAstroTracker@19200... [00:00:11.312] [01]: COMMFACTORY: Creating ASCOM handler for OpenAstroTracker ... [00:00:12.257] [01]: COMMFACTORY: ASCOM handler supported action: Telescope:getFirmwareVer ... [00:00:12.257] [01]: COMMFACTORY: ASCOM handler supported action: Utility:JNowtoJ2000 ... [00:00:12.257] [01]: COMMFACTORY: ASCOM handler supported action: Serial:PassThroughCommand ... [00:00:12.304] [01]: EXCPTN: Entered AppDispatcherUnhandledException handler. Exception: ASCOM.DriverException: CheckDotNetExceptions ASCOM.OpenAstroTracker.Telescope Action System.IndexOutOfRangeException: Índice fuera de los límites de la matriz. (See Inner Exception for details) ---> System.IndexOutOfRangeException: Índice fuera de los límites de la matriz. --- Fin del seguimiento de la pila de la excepción interna --- en ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) en C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:línea 629 en ASCOM.DriverAccess.MemberFactory.MethodTargetInvocationExceptionHandler(String memberName, Exception e) en C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:línea 677 en ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) en C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:línea 486 en ASCOM.DriverAccess.AscomDriver.Action(String ActionName, String ActionParameters) en C:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:línea 399 en OATCommunications.CommunicationHandlers.ASCOMCommunicationHandler..ctor(String device) en OATCommunications.CommunicationHandlers.ASCOMCommunicationHandler.CreateHandler(String device) en OATCommunications.WPF.CommunicationHandlers.CommunicationHandlerFactory.ConnectToDevice(String device) en OATControl.ViewModels.MountVM.d192.MoveNext() --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción --- en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) en OATControl.DlgChooseOat.d89.MoveNext() --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción --- en System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.b__6_0(Object state) en System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Stacktrace: en ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) en C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:línea 629 en ASCOM.DriverAccess.MemberFactory.MethodTargetInvocationExceptionHandler(String memberName, Exception e) en C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:línea 677 en ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) en C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:línea 486 en ASCOM.DriverAccess.AscomDriver.Action(String ActionName, String ActionParameters) en C:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:línea 399 en OATCommunications.CommunicationHandlers.ASCOMCommunicationHandler..ctor(String device) en OATCommunications.CommunicationHandlers.ASCOMCommunicationHandler.CreateHandler(String device) en OATCommunications.WPF.CommunicationHandlers.CommunicationHandlerFactory.ConnectToDevice(String device) en OATControl.ViewModels.MountVM.d192.MoveNext() --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción --- en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) en OATControl.DlgChooseOat.d89.MoveNext() --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción --- en System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.b__6_0(Object state) en System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) [00:00:12.304] [01]: Shutdown logging. Maximum of 28 lines buffered.

[ClutchplateDude]

Does OATControl connect on COM3 directly? What does the logfile for that look like?

[catlover-forever]

Where would I be able to find this log file? (Sorry, I'm a newbie to all this.)

El dom, 25 jul 2021 a las 19:12, Lutz @.***>) escribió:

Does OATControl connect on COM3 directly? What does the logfile for that look like?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/OpenAstroTech/OpenAstroTracker-Desktop/issues/33#issuecomment-886231778, or unsubscribe https://github.com/notifications/unsubscribe-auth/AU65VYLK27S5E76LRYYRUDLTZRAZRANCNFSM5A6TSF5Q .

[catlover-forever]

And yes, I presume OATControl connects directly to COM3, as it appears on the Available Connections screen.

[catlover-forever]

Maybe I should also mention that there is nothing else but the two steppers connected to the MKS board (but will be).

[ClutchplateDude]

Please use our Discord for troubleshooting help. This is not the place for support. There isn't an actual issue at this point.