SGP 4.0.0.700 and ASCOM 6.6

I recently installed ASCOM 6.6

I then checked all of my equipment with the new ASCOM.
iOptron CEM120 Commander worked OK. Gemini Falcon Rotator worked OK.
PHD2 with ZWO ASI290 worked OK. Optec focuser worked OK.
Gemini PowerBox worked OK.

I found that SGP 4.0.700 would not even open. When imaging I use a ZWO ASI2600 OSC.

I reinstalled ASCOM 6.4 and SGP4 opened and operated properly

Has anyone else noticed this issue? Is there a solution??

Roger

I have installed ASCOM 6.6 on a new Mini PC. I downloaded new copies of all my Astro software which included the new version of ASCOM. I had previously used ASCOM 6.5sp1. My access to the Mini PC is through MS RDP and my iMac. I have used SGP 4.0.0.700 (32-bit) and the later Beta versions e.g. SGP 4.1.0.733 (32-bit). The last paragraph summaries using them.

Perhaps not the best person to ask about SGP Pro as I’m still evaluating it in a Trial period. I initially only wanted to use the Release versions but quickly decided that the Beta versions are now perhaps more representative of how it will work at the next Release. I have switched between SGP 4.0.0.700 (32-bit) and the latest SGP 4.1.0.7XX (32-bit) Betas without ASCOM issues.

I also have a (different) ZWO camera - the ASI294MC OSC. The versions of SGP Pro have been the 32-bit version after I read that all drivers need to be 64-bit to switch to that version. My Focuser didn’t pickup the count in the 64-bit version using only the 32-bit driver. From now on it’s the 32-bit for my Mini PC. So ASCOM 6.6 with SGP 4.0.0.700 (64-bit) the results may differ? Is there a difference if the camera is unplugged before starting SGP Pro?

When I have switched between SGP versions I have stored my profiles in …/Documents/SGP/Profiles, where I have one Camera and one User profile. When switching versions I make a point of deleting the AppData for SGP Pro e.g. the folder: C:\Users\Simon\AppData\Local\SequenceGenerator because I’m never sure if different version will make the entries incompatible. I keep my profiles and reuse them because it takes effort to recreate them. So after starting SGP Pro I set the directories for Images and Profiles as the first operation. Then rearranging the Docking Modules.

I did have one issue with ASCOM 6.6 where I couldn’t connect to my Focuser overnight. I tried reverting to ASCOM 6.5sp1 but it didn’t fix the issue. I tracked the issue down to the Virtual Com Ports (VCP) used to access the Focuser through USB ports. I have two ports like this that use FTDI and Prolifics chips. I downloaded the latest versions from the chip makers websites. The problem is fixed by changing the Driver and not reverting to an earlier version of ASCOM. My new Mini PC came with Windows 11 Pro preinstalled so I was expecting some driver issues.

With Hindsight - I should not have downloaded new versions of all my Astro software and I now have a separate NAS folder with the software that I installed and know works with. Getting a new machine and all new versions of software introduces a lot of “unknown variables” across 11 software applications and drivers (and OS).

One way to find issues is to look at the Astro Gear e.g. Cameras and COM ports in the Device Manager and click the Events → “View all Events…” button. Later on, you can open the Event Viewer and for each piece of Astro Equipment there will be a list of Events - I check the Warnings and Errors carefully.

To make the statement that “SGP 4.0.0.700 (32-bit) version works with ASCOM 6.6 using a ZWO OSC OK” is not to also say that I have used this combination for too long. As far as I can tell, it works as well as the latest SGP 4.1.0.733 (32-bit) Betas which I’m using also with ASCOM 6.6. They both also work OK with ASCOM 6.5sp1. My versions of SGP Pro are the 32-bit versions and I’m on Windows 11. My camera is a ZWO and uses the common ZWO ASI Cameras driver Setup V3.17 and ZWO_ASCOM_Setup_V6.5.1.13 shared across many of their cameras.

Simon

I’m using SGP 4.0.0.700 32 bit on Windows 10 (32 bit). After ASCOM 6.6 was installed SGP .700 opened fine but the only issue was with the ZWO ASI120mm guide camera. PHD was able to connect to it but could not download a frame. After reinstalling the ZWO_ASCOM_Setup_V6.5.1.12 driver package everything works fine.
I have SGP .733 32 bit installed on my laptop running Windows 11 (64 bit) with ASCOM 6.6 and SGP operates fine. This setup is using the iOptron GEM45G mount with the internal guide camera.

Mike

Updating ASCOM will remove the old version and do a fresh install. This seems to (mostly) keep individual drivers.

Windows 11 came preinstalled on my new Beelink Mini PC even though it was listed as 10 upgradeable. Seems not to cause any issues and it’s nice to use.

I ran the ASCOM diagnostics to confirm everything is OK. SGP can’t work magic if there is anything amiss with ASCOM and the drivers - fortunately it seems OK.