PHD 2.62 and AWR Tigra Astronomy Mount Connection

[John Welsh]

Not sure if this is a PHD 2.62 issues or the Ascom Driver specifically.

I have just installed PHD2.62 and on setting up and trying to connect to the hardware get the following message when trying to connect to the mount.

I am using a SX Trius 694 with SX LAO and AWR mount with Tigra Astronomy Ascom driver.

Any ideas please ?

[bw_msgboard]

Hi John.  I think the error message says it all – “ASCOM driver problem.”  <g>  Did you click on the properties button to the left of the mount connect button to see if you could get into the setup dialog for the ASCOM driver?  It looks like you might be running into some kind of file-level permission problem, something to do with how the ASCOM driver was installed or how your system is configured.  I’d recommend using the ASCOM ‘Poth’ tool to work through connection problems with the ASCOM driver.  Once you can connect to the mount with that and get valid positional info back from it,  PHD2 should have no trouble with it either.  You might be able to get help on the ASCOM-Talk forum although you will need to give them a lot more info, starting with what OS version you’re running.

 

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 Welsh]

Hi Bruce - OK I will give the POTH a go and see where that takes me later tonight - Thanks for the reply.

[John Welsh]

Sorry, I forgot to mention that, yes, I twas possible to get to the Ascom driver settings dialogue box and all seemed to be configured correctly.

On Sunday, 31 July 2016 14:25:22 UTC+1, John Welsh wrote:

[John Welsh]

I think this is now solved.

In the image in their attachment earlier in this thread you will see that that mount selected is the Ascom.AWR Telescope model.

Apparently this is incorrect and I should have chosen - "On - AO" !!

As a new user this is quite confusing. It seems that what the prompt, "Mount:" it is actually asking for is not the mount type, as per the prompt, but instead, is asking where will the mount receive it's guiding instructions from - the two being quite different.

Please advise if I have not understood this - on changing to "ON - AO" there are no more configuration errors anyway !

Regards

John

On Sunday, 31 July 2016 14:25:22 UTC+1, John Welsh wrote:

[Andy Galasso]

Hi John,

Sorry for the confusion about the mount connection, I can see how that would have been confusing. We will look into clarifying the wording of the prompt.

You may want to consider changing from On-AO to using the mount's ASCOM driver to connect to the mount. We describe the benefits of connecting to the mount with ASCOM in the Equipment Connection section of the help file.

Andy

[John Welsh]

Hi Andy, No problem, probably just me not being conversant with the correct terminology.

Yes, I would like to try to use the Ascom AWR Driver. but this thread opened with that very driver attempt and the resulting errors as you will see in the opening lines where there is also an on screen error displayed. I am not sure if this is for me to go to the guy who wrote this driver now ???

Maybe I should try to reconnect with that set up - is there a log file that will explain more as to what is going wrong when I try to do this like in the log file sent when guiding using simulators etc.

Regards

John

[Andy Galasso]

John,

Your best bet will be to check the documentation that came with the mount and/or contact the mount manufacturer or ASCOM driver author.  You'll want to make sure you have the PC connected to the mount correctly for the ASCOM driver.  Usually this is done through a USB-Serial connection, though sometimes it is direct USB or an Ethernet connection, but never through an ST-4 cable like what you are using between the AO or guide camera and the mount.  I am not familiar enough with your mount to advise how exactly to connect it for ASCOM.

The PHD2 debug log will have more details about the error from the ASCOM driver, but I am guessing it is only telling you that you have not connected your PC to the mount.  Once you confirm that you have the PC connected correctly, and if you still have trouble we can look at the debug log.

Andy

[John Welsh]

Hi Andy, I am using a USB from the SX Trius 694 camera (which links via a mini usb to the AO) direct back to the laptop. There is then a separate USB from the laptop to the mount hand controller and that a separate one from the hand controller back to the mount then goes to a dedicated CCD port on the AWR mount control box.

Recording Demo => SXAOSimJW.mp4

AWR-USB.jpg

IH-RJ45.jpg



Hope thi shelps.

John

[Andy Galasso]

Hi John,

I'm sorry to say that I do not know enough about your mount to advise how exactly to connect it for ASCOM.  Your best bet will be to ask the mount manufacturer or the ASCOM driver provider.   Your original post showed an ASCOM driver error indicating a failure of the ASCOM driver to connect to the mount. Since this error is coming from the ASCOM driver, it is definitely an issue that will need to be diagnosed by somebody who knows about the ASCOM driver.

In the past when we have seen cases with an ASCOM driver reporting "access is denied" when trying to connect is can mean a couple things:

  1. the ASCOM driver only allows a single app to connect to it at a time and you already have another app connected (like a planetarium program for example.)  The workaround for this driver limitation is to use the ASCOM POTH hub.

  2. The ASCOM driver supports multiple apps, but some app or apps are running as Administrator while other apps are not.

Those are just two examples of things that can cause that type of error, but I'm only guessing here. Somebody with specific expertise with your ASCOM driver will be in a better position to help.

Andy