I am using a Baader Steel drive focuser and recently updated my laptop to Windows 10. I previously had no issues to using this focuser for auto focus. I would first open the driver, set the USB port and position of the focuser and then open SGP and SGP would know where it was and autofocus worked fine.
Now it “hangs” saying focuser moving to next position. This can happen after one point, or after 4-5 points, or it might work sometimes. When it does not work I cancel and it tries again or I do it manually until it works.
The driver I was using was several years old and I did update this after the problem started, but it has continued. Not sure if SGP still thinks it’s the old driver or if it is a cable or USB issue.
Your focuser connection id definitely the issue here:
[10/03/24 02:54:50.837][DEBUG][Sequence Thread][SQ;BC;] BlockUntilFocuserMovementDone: Timeout! Focuser trying to get to 5889, but reports it is at 5959!
Even with several retry attempts it won’t budge. I can’t speak to the driver, but it seems like you may have multiple drivers installed. I would first start by removing (not reinstalling) all focuser drivers and then only re-install the one you intend to use.
It is more likely though that Windows 10 USB drivers are to blame here and, if using a USB hub, try to temporarily bypass it to see if the issue clears up.
Makes sense. I did check the compatibility of the old driver and it appears incompatible with Windows 10. It looks like it is no longer supported by Baader - I have started an email exchange with them to see if they know of a driver for Windows 10. Otherwise I hope I can find simply a generic ASCOM driver that I can use? I have also emailed Orion UK who were the original manufacturers.
Unfortunately, unless Baader implements the RoboFocus standard, likely not. It’s the only “open” standard I know of that multiple different controllers actually use.
So I had the USB port on the Baader Focus Motor repaired and removed the USB Hub that it was going through. Still seems to be an issue. I am now wondering if there is a conflict in the drivers that I have on my computer. I am selecting the ASCOM driver and the port in SGP and it seems to run most of the time.
[01/31/25 01:15:58.433][ERROR][Camera Thread][SQ;AF;BC;] Error in auto focus! Focuser failed to move to the requested position (7117). Focuser reports it is at 7162. : Error in auto focus! Focuser failed to move to the requested position (7117). Focuser reports it is at 7162.
at q3.a(AutoFocusData A_0, tb& A_1, tb A_2)
[01/31/25 01:15:58.434][DEBUG][Main Thread][SQ;AF;BC;] Adding sequence level notification: Error in auto focus! Focuser failed to move to the requested position (7117). Focuser reports it is at 7162.
[01/31/25 01:15:58.485][DEBUG][Camera Thread][SQ;AF;BC;] Sending Notification: Error - Error in auto focus! Focuser failed to move to the requested position (7117). Focuser reports it is at 7162.
[01/31/25 01:15:58.485][DEBUG][Camera Thread][SQ;AF;BC;] MoveFocuserAbs: Start, move to 6847…
[01/31/25 01:15:58.485][DEBUG][Camera Thread][SQ;AF;BC;] ASCOM Focuser: MoveSync - start…
[01/31/25 01:15:58.485][DEBUG][Camera Thread][SQ;AF;BC;] Focuser moving to 6847
[01/31/25 01:15:58.536][DEBUG][Camera Thread][SQ;AF;BC;] Focuser move call complete
[01/31/25 01:15:58.536][DEBUG][Move Monitor Thread][SQ;AF;BC;] ASCOM Focuser: Move monitor thread is started…
[01/31/25 01:17:58.648][DEBUG][Camera Thread][SQ;AF;BC;] ASCOM Focuser: Timeout! Focuser trying to get to 6847, reports it is at 6847. Focuser move complete reports: False
[01/31/25 01:17:58.700][DEBUG][Camera Thread][SQ;AF;BC;] MoveFocuserAbs: End, move complete, at 6847…
[01/31/25 01:17:58.700][DEBUG][Camera Thread][SQ;AF;BC;] Auto focus (finally): closing dialog…
[01/31/25 01:18:09.394][DEBUG][Camera Thread][SQ;AF;BC;] Auto focus complete…
[01/31/25 01:18:09.401][DEBUG][Camera Thread][SQ;BC;] SGM_FOCUSER_AUTO_FOCUS complete…
[01/31/25 01:18:09.401][DEBUG][Camera Thread][SQ;BC;] Camera thread is IDLE…
[01/31/25 01:19:09.654][DEBUG][Sequence Thread][SQ;BC;] BlockUntilFocuserMovementDone: Timeout! Focuser trying to get to 6847, but reports it is at 6847!
Not sure if this is related to anything I have set in the backlash settings.
SGPro 3.2 is quite old so you’re challenging my memory, but from the log snippet I seem to recall that there was an old bug that could sometimes do this (say it couldn’t get to a position when it was already there) in SGPro 3 and it was corrected years ago in SGPro 4.
Thanks Ken - would using an older version assist me here? Is there an issue with trying that as the program worked extremely well for many years - I have just upgraded to a new Laptop and Windows 11 howver. Alternatively I am happy to upgrade to the latest version but would like to trial it for 30 days to ensure it works. Let me know if a trial is possible or if I can user an older version. Thank you!
Sorry, I honestly can’t remember anything about the issue… it was many years ago at this point. You are, as you note, free to give SGPro 4 a shot. There is an update subscription attached, but it’s not required (and you’ll still be able to use SGPro 4 forever, just like v3)
So I have upgraded to the latest version of SGP 4 Pro.
One of the immediate things I have run into is that the ASCOM OMNI Simulator is activated when I open SGP and when I open the Equipment Profile Manager. I then get a series of errors and I cannot save changes that I have made to my equipment with the error saying “The RPC Server is unavailable”.
The issues I think started when I installed some of the plate solving software
So looks like the classic Firewall and Anti Virus blocking the App, Just going through this now to let the Firewall and Anti Virus run the software properly
So unfortunately I am back to square one. SGP Pro 4 worked for a little while and then again started getting the same messages. Seems to all be the issue with the ALPACA Simulator Devices I think and access to the local host 32323 hich I cannot access. I have tried to create a new equiment profile and still no joy.
Have reinstalled SGP 3 and this has no issues.
I have posted on my local FB Astronomy group and hopefully someone that is using SGP Pro 4 with Windows 11 can help.
So first focus run testing tonight. Did get a focuser moving to new position hanging message and a dowloading imaging hanging error on another run stuck at 87% (screen shot attached)
I then turned off backlash compensation for my focuser and also disabled fast downloads.
After more than nearly 10-15 focus runs no issues - will try again tommorow evening.
Have you made sure to grab the latest focuser drivers? Happy to take a look. There are a bunch of reasons a focuser can timeout after a request to move and we can help narrow it down with you. SGPro has built in issue reporting tools you can use to send us the logs showing the event.
It’s an onld focuser and driver by Baader and they no longer have any drivers - it is the original Baader Steel Drive. Perhaps someone somewhere has an updated ASCOM driver?
