Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
PLEASE READ ==> If you get a StructureMap or EdsInitializeSDK() error please RE-INSTALL before posting in the forum <==
  • 0
Sign in to follow this  
gfunkernator

CPWI ASCOM control in BYE issues

Question

When BYE is connected to CPWI via ASCOM and I have selected an object to track in CPWI, if I press any of the slew arrows in BYE, tracking stops.  Is this normal?  I'd like to use the slew functions in BYE instead of always having the CPWI slew window open.  I also noticed that while that slew window is open, if my celestron focuser is connected via USB in BYE and I press any of the focus controls, either BYE will freeze, or I get an error message that allows me to continue, but CPWI stops responding.

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0

Have you tried the Unified Celestron driver, instead of the CPWI driver? The latest version will also control the Celestron Focuser. It is available for download from the ASCOM-Standards web site.

Oh, and by the way the chevron buttons in BYE jog the scope. Jogging movement occurs as long as the button is pressed. Slewing is movement to a target. When a jog button is released, the scope should return to the tracking state (on or off) prior to the jogging movement. This is part of the ASCOM standard that the CPWI driver must implement to be compliant.

Share this post


Link to post
Share on other sites
  • 0

Don't know the version number off the top.  It is the latest version (trial).

 

I am using the unified Celestron driver.  When I press those jog buttons, tracking stops.  Even the status that usually says tracking changes to stationary after I press the jog buttons.  

 

As far as the Focuser is concerned, I had an idea I've yet to try.  I am going to connect it via USB to my Surface and not connect the ST4 cable to the mount.  I think that when CPWI connects through the hand controller it also steals the I/O path to the Focuser.  I will test when I get a chance and report back.

Share this post


Link to post
Share on other sites
  • 0

Sorry, can't really help without the version number has things have changed recently with ASCOM.

Start the APP and the version number will be in the title bar.

Share this post


Link to post
Share on other sites
  • 0

I am confused. Your original post said that you are using the CPWI driver. Then in your most recent post you said that you are using the unified Celestron driver. These are two different drivers that both support Celestron mounts.

So, what is the friendly name of the driver that you select from the ASCOM Chooser?

Also, I don't understand what connecting the focuser to your Surface has to do with the ST4 cable. The ST4 cable would normally be connected between the guide camera and the mount. It would have nothing to do with the focuser.

Both the CPWI driver and the Unified Celestron driver can control both the mount and the focuser at the same time, as long as they are cabled correctly. This does not involve the use of the ST4 (Autoguide) port. It uses the Aux port.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use