Resolved Ascom Drivers

Hi Neil,

Sorry I didn't get back to you sooner—I didn't see the notification it was assigned to me.
It looks like the driver failed to register on install. Are you familiar with the process for registering DLLs for COM interop? If not, I'd be happy to jump on via TeamViewer and see if I can resolve this for you.

Cheers,
-Adam

 

Neil - there is a QuickSupport version of TeamViewer - just download and run, no need to install.
We pay the license on our end.
https://download.teamviewer.com/download/TeamViewerQS.exe

 

Let's try to go the TeamViewerQS route. It shouldn't require any extra effort/purchases on your end.
If for some reason it gives you trouble, we can go another route (either Zoom or RemotePC, which I've never used)
If you can send me a private message with your TeamViewerQS ID and password, I'll jump on and collect a baseline.

 

Perfect! I'll keep an eye out for your message then.

 

Actually, I messed up my timezone conversion and I've got another support session booked for 9am MST. I don't expect it to run very long, but it may be better if we aim for 10am MST. Is that too late for you?

 

Excellent. Send me a private message with your connection details around then, and I'll log on when I get them.

 

The issue in question here was that Neil was trying to run N.I.N.A. (x64) and access the DLImaging ASCOM Drivers from that. There is a known issue accessing the DLImaging ASCOM drivers via an x64 process, so I've advised he temporarily use the x86 version until we can get the ASCOM driver sorted with x64 processes.

 

Sure! hit me up with your connection details and I'll try and resolve it.

 

OK, so I was able to configure and connect to/control the filter wheel in both ASCOM Diagnostic and MaxIm DL 6. I did see that NINA was able to connect to the Filter Wheel, but an out-of-range exception was causing weird behavior in the program. I was trying to get additional ASCOM driver logs to diagnose the error, but NINA has a hanging ghost process I'm not able to kill.

I think NINA is doing something incorrect in its initialization procedure, but I can't tell for sure. If you're able to collect some form of a log from NINA to tell me what it's doing when it opens a connection to the camera I'll be able to investigate further.