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*
  • 0
JTWaters

BUG - ASCOM Interface Through BYE Not Working - 3.1.18 RC11

Question

I decided to test the ASCOM Telescope user interface through BYE Rel 3.1.18 RC11.  The DEC slew buttons do not work.  The RA buttons work as expected.  Everything works through the standard Telescope.NET interface and the Gemini-2 HC.

  • ASCOM Rel 6.4 SP1
  • Losmandy GM811G - Gemini-2
  • ASCOM Gemini Driver 1.0.72.0

Where do you hide the log files?

 

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

The tricky part is to make sure that whatever speed is used for calls to MoveAxis is in the list of valid Axis Rates for the driver/mount being used. In a previous post, I described one approach that could be universal to accommodate drivers/mounts with one continuous range of rates, multiple split ranges of rates, multiple discrete rate values. I would suggest that Guylain consider something similar. He just needs to think about it in the context of BYE/BYN.

Share this post


Link to post
Share on other sites
  • 0

I just looked at the Driver.cs file from that github repository and the switch statement at line 1331 is where the Gemini ASCOM driver changes the slew speed.

The Gemini ASCOM driver will *ALWAYS* change the rate to either slew/center/guide according to this code below; this is a Gemini specific behavior. 

What is your ideal outcome Jim?  Is there one that you prefer the mount to be set to once the MoveAxis is complete?

 

image.png

Share this post


Link to post
Share on other sites
  • 0

When I was looking through the code I was searching for the MoveAxis commands.  I should have been looking for Slew, Center and Guide.

To answer your question, ideally the same as the Gemini Telescope.NET app.  Guide, Center and Slew.  Maybe three radial buttons - G, C, S.  I am not sure how this would impact other ASCOM mounts and how you can implement a One-Size-Fits-All interface.

http://download.ascom-standards.org/drivers/GeminiTelescopeInstaller(1.0.72.0).exe

 

Share this post


Link to post
Share on other sites
  • 0

Right now BYE displays a percentage that is changed via the up and down arrows, but the code could be modified to use a list of valid axis rate values that a user scrolls through with the up and down arrows. The displayed values would be numeric rather than descriptions like Guide, Center, and Slew (which are specific to the Gemini driver). That type of approach could work for all drivers that support MoveAxis calls, BYE would just need to figure out a few valid rates (like a slow rate, a fast rate, and an in between rate) for the user to select from.

Share this post


Link to post
Share on other sites
  • 0
2 hours ago, astroman133 said:

Right now BYE displays a percentage that is changed via the up and down arrows, but the code could be modified to use a list of valid axis rate values that a user scrolls through with the up and down arrows. The displayed values would be numeric rather than descriptions like Guide, Center, and Slew (which are specific to the Gemini driver). That type of approach could work for all drivers that support MoveAxis calls, BYE would just need to figure out a few valid rates (like a slow rate, a fast rate, and an in between rate) for the user to select from.

Rick, in your experience, does most ASCOM driver provide that list ordered by fastest to slowest speed?  Your suggestion makes sense, I just need to figure out a few things (like dithering speed) before making the call to plunge or not.  Also, what if the mount supports the move axis command but that list is empty (is that even a possibility) or only has one value?

I guess a one size fits all would be to somehow allow the user to select from that list and keep the percentage to scale that speed sort a speak.  For Jim, that would give him all 3 speeds to choose from a list, and with the percentage set to 100%, would mean the Genimi ASCOM driver would always set the Gemini slew speed to the appropriate value.   I'm I reading this right?  I'm not saying this is what I'll be doing, or even a timeline, I'm merely trying to understand the command flow at this stage so that any decision taken is an informed one.

Regards,

Share this post


Link to post
Share on other sites
  • 0

I believe that it is common for the Telescope.AxisRates method to return the rates from slowest to fastest for the requested axis, but you should expect that the rate objects could be in any order. Don't forget that each rate is actually a range of rates from a minimum value to a maximum value. In the case of the rates for the Gemini driver, the min and max values are the same. This means that only 3 rate values are valid. It is possible that the AxisRates for a given axis could be empty. This should only occur if CanMoveAxis for that axis is false. Also, 0.0 is always a valid rate, since calling Move Axis with a value of 0 returns to either sidereal tracking or not, depending on the Tracking flag.

The three rates for the Gemini mount are not slew rates; they are for MoveAxis calls, although the fastest speed may also be the rate at which the mount slews. I would be extremely surprised if setting the speed to Center (20X sidereal) would affect the speed at which the mount slewed across the sky to a new target. It does, however, make sense to do frame and focus jog moves at 20X.

I really think that it will be confusing for people choose percentage values for the MoveAxis speed when those values can map to invalid axis rates. Giving them only a selection of valid rate values seems likely to cause less confusion. Just my 2 cents.

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.


×
×
  • 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