PHD2 latest version does not show any ASCOM?

[John Mallett]

Hi,

I can see and connect to my ASCOM CMOS SSAGPRO guide camera but it does not come up in the PHD2 list??

ASCOM, EQMOD and ASCOM drivers loaded.

Any ideas?

regards,

John

[bw_msgboard]

Hi John.  The list of ASCOM cameras is built on-the-fly by PHD2 using an ASCOM utility function.  So if your camera isn’t in that list, it means its ASCOM driver is either not installed or didn’t get registered correctly.  When you say you “can see and connect” to the camera, I assume you are doing that with the native camera driver, not the camera’s ASCOM driver.  Many of these cameras have both ASCOM and proprietary software interfaces and they are installed separately.  If you want to do an independent check, you can run the ProfileExplorer tool in the Program Files(x86)\ASCOM\Platform 6\Tools directory.  It will show you a list of all the installed ASCOM devices, including cameras.  

 

Good luck,

Bruce

 

---

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[John Mallett]

This is the Diagnostic output..

16:23:01.393 Registered Device Type    Camera
16:23:01.393 Registered Devices           ASCOM.ASCOM_SSAGPro.Camera - CMOS SSAGPro Camera
16:23:01.395 DriverCompatibility            ProgID: ASCOM.ASCOM_SSAGPro.Camera, Bitness: Bits32
16:23:01.395 DriverCompatibility            Found 32bit ProgID registration
16:23:01.395 DriverCompatibility            Running on a 64bit OS, 32bit Registered: True, 64Bit Registered: False
16:23:01.395 DriverCompatibility            Found CLSID entry
16:23:01.395 DriverCompatibility            Returning: ""
16:23:01.395 Registered Devices               OK for 32bit applications
16:23:01.411 DriverCompatibility            ProgID: ASCOM.ASCOM_SSAGPro.Camera, Bitness: Bits64
16:23:01.411 DriverCompatibility            No entry in the 64bit registry, checking the 32bit registry
16:23:01.411 DriverCompatibility            Returning: "This 64bit capable driver is only registered as a 32bit COM driver.[0D][0A]Please contact the driver author and request an updated installer."
16:23:01.411 Registered Devices               This 64bit capable driver is only registered as a 32bit COM driver.[0D][0A]Please contact the driver author and request an updated installer.

[John Mallett]

[Andy Galasso]

John,

If the ASCOM camera does not show up in PHD2's camera drop-down list, then it most likely is a problem with the ASCOM driver. You can try another application like SharpCap. If the camera does not show up in SharpCap either (on the Cameras menu, under ASCOM Cameras), then you'll have good evidence that there is a problem with the ASCOM driver.  In that case reinstalling the ASCOM driver might help.

Andy

[John Mallett]

It shows up in Astroart and I can connect to both the camera and the telescope but neither show in the PHD2 windows??

John 

[Andy Galasso]

On Mon, Nov 7, 2016 at 12:57 PM, John Mallett <jo...@astro.me.uk> wrote:

It shows up in Astroart

John, In AstroArt does it show up as an ASCOM device, or as a native (non-ascom) device?   I'm not familiar with AstroArt so I can't say how AstroArt would show the difference between ASCOM/native.  If you are unsure, please try SharpCap.

I can connect to both the camera and the telescope but neither show in the PHD2 windows

Are you saying the EQMOD ASCOM does not show up in the PHD2's Mount drop-down list even though you have EQASCOM installed?

Andy

[bw_msgboard]

Hi John.  Ok, it looks like you ran the ASCOM diagnostics tool.  Could you please post the entire output log rather than just the snippet?  There is another section in the log that shows profile entries, and we’d like to see those.

 

Thanks,

Bruce

 

---

[John Mallett]

On Monday, November 7, 2016 at 6:33:31 PM UTC, Bruce Waddington wrote:

Hi John.  Ok, it looks like you ran the ASCOM diagnostics tool.  Could you please post the entire output log rather than just the snippet?  There is another section in the log that shows profile entries, and we’d like to see those.

 

Thanks,

Bruce

 

[Andy Galasso]

John,

One thing I notice from the log is that you are using an old version of the ASCOM platform.  I don't know if this is the source of the problem, but it may help if you update to the current version, ASCOM Platform 6.2.

Andy

[bw_msgboard]

Hi John, sorry for the delay.  I think we need to maybe hit the ‘reset’ button on our side of things <g>  This kind of problem is almost always something simple – the user hasn’t installed the ASCOM drivers or doesn’t understand the user interface, stuff like that.  So that’s why we offered up simple answers without asking you for details about your setup – we don’t even know what version of PHD2 you’re running.  That’s our mistake for not getting this info.  I’m not an ASCOM diagnostics expert but of course I’ve used it many times.  As Andy said, you’re running quite an old version of the ASCOM platform, so we need to get that fixed.  There’s no point in trying to debug something on an outdated platform.  The log you sent affirms what you already know – your ASCOM drivers for the mount and camera are installed and should be accessible.  This narrows things down to why the ASCOM platform doesn’t seem to include them in an enumeration of all the ASCOM drivers on your system.  This is very simple code in PHD2, been there a long time, and is central to what most users do.  If this had gotten broken, we would be deluged with problem reports and more importantly, neither Andy nor I would be able to do any imaging or PHD2 testing.  You can imagine how long we’d put up with that. <g>  So I think we’re dealing with something subtle, something to do with your OS platform, its Registry, or how you installed the ASCOM platform.  For example, your diagnostics log shows this:

 

21:16:41.049 Error                     RegistrySecurity - Subkey SOFTWARE\Wow6432Node\ASCOM does not have full access rights for BUILTIN\Users!

 

I’ve never seen this, it certainly doesn’t show up in any of my logs.  I don’t know what the implications are, if any, but I’m not very comfortable with it.  

 

Once you upgrade to the new ASCOM platform, you may get lucky and the problem will disappear.  But if not, we’re going to need a lot more info:

1. Your PHD2 debug log file
2. A fresh ASCOM diagnostics log on the ASCOM 6.2 platform
3. Whether the ASCOM camera simulators and the ASCOM mount simulators show up in the PHD2 list for cameras and mounts. The ‘mount’ list should also include things like POTH and the Pipe tool.
4. Which version of Windows you’re running and whether you are using multiple user accounts
5. Whether you have another application that provides access to the ASCOM “chooser”.  If so, whether the Chooser shows your camera and mount driver in its list.
6. If you don’t have such an app, we can build you a simple app or script that will do the job
7. Some history on the problem – we don’t know if you’re a new user and this is a problem you hit right away or something that suddenly cropped up in a functional PHD2 environment

 

I think if we just grind on this in a methodical way, we should be able to get you going.

 

Thanks,