1. main@ap-gto.groups.io
  2. Messages
   Date   
Re: slewing issues trying to create meridian limits

Ray Gralak
 

Hi Eric,

APCC will always slew the RA axis first, but the counterweight should be down before the declination slew. Are you saying that it is possible for your scope to hit the pier in some counterweight down positions when declination is slewing?

12. Clicked "Next Position".
13. >> The mount slewed to counterweights level, paused for a moment, went back slightly, then started slewing
With a GTOCP4 there can be a double slew to the meridian, once with APCC and once for save slewing in the CP4. This will be fixed in the next release of APCC, which will be available soon.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, October 20, 2018 2:03 PM
To: ap-gto@...
Subject: [ap-gto] slewing issues trying to create meridian limits



I tried creating a new meridian limit twice and both times had problems with my Mach 1 mount trying to slew into the
pier. I'm running the v11 CP4 firmware and APCC v1.6.0.3.

Here are the steps I took:

1. Mount at park 3.
2. Started APCC. Initialized from previous position (which was park 3).
3. Clicked on "Edit" in the Meridian tab.
4. Clicked on "Reset all points".
5. Clicked "EAST". Dec Increment set to 10. Meridian Inclination set to 0.
6. Clicked "Go to Meridian".
7. >> The mount slewed the OTA to the east in RA only until the counterweights were horizontal, then started
slewing in DEC. I had to Emergency Stop it to avoid having the camera hit the tray on the side of the pier. Doesn't
it normally slew in RA and DEC when the counterweights are down?

8. Manually slewed with keypad close to meridian so the DEC slew would miss the pier.
9. Clicked "Go to Meridian" again" and it properly slewed to the meridian with the OTA on east side, pointing
south, counterweights level.
10. Clicked "Add Point" then "Next Position". It worked fine. OTA now at 10 degrees up.
11. Slewed with keypad to the horizon and clicked "Add Point".
12. Clicked "Next Position".
13. >> The mount slewed to counterweights level, paused for a moment, went back slightly, then started slewing
in RA and DEC to put the OTA on the WEST side. I had to Emergency Stop to keep the camera from hitting the
pier. Shouldn't it have simply slewed in RA until the counterweights were level, then slewed in DEC another 10
degrees up?

I gave up and disconnected the mount and closed APCC.
My log file is in the "EricC" file folder and is called "ApccZip-Eric_Claeys-2018-10-20-144613.zip"
slewing issues trying to create meridian limits

Eric Claeys
 

I tried creating a new meridian limit twice and both times had problems with my Mach 1 mount trying to slew into the pier.  I'm running the v11 CP4 firmware and APCC v1.6.0.3.
Here are the steps I took:
  1. Mount at park 3.
  2. Started APCC.  Initialized from previous position (which was park 3).
  3. Clicked on "Edit" in the Meridian tab.
  4. Clicked on "Reset all points".
  5. Clicked "EAST".  Dec Increment set to 10.  Meridian Inclination set to 0.
  6. Clicked "Go to Meridian".
  7. >> The mount slewed the OTA to the east in RA only until the counterweights were horizontal, then started slewing in DEC.  I had to Emergency Stop it to avoid having the camera hit the tray on the side of the pier.   Doesn't it normally slew in RA and DEC when the counterweights are down?
  8. Manually slewed with keypad close to meridian so the DEC slew would miss the pier.
  9. Clicked "Go to Meridian" again" and it properly slewed to the meridian with the OTA on east side, pointing south, counterweights level.
  10. Clicked "Add Point" then "Next Position".  It worked fine.  OTA now at 10 degrees up.
  11. Slewed with keypad to the horizon and clicked "Add Point".
  12. Clicked "Next Position".
  13. >> The mount slewed to counterweights level, paused for a moment, went back slightly, then started slewing in RA and DEC to put the OTA on the WEST side.  I had to Emergency Stop to keep the camera from hitting the pier.  Shouldn't it have simply slewed in RA until the counterweights were level, then slewed in DEC another 10 degrees up?
I gave up and disconnected the mount and closed APCC.
My log file is in the "EricC" file folder and is called "ApccZip-Eric_Claeys-2018-10-20-144613.zip"
Re: ascom driver question

Ray Gralak
 

Dan,

A google check of the time now in Longmont, Co the time is 2:10 PM but GMT is 8:10 PM.

That's -6 hours difference, right?

I think -7 is correct for your location *without* Daylight Saving Time because Longmont is still on DST. So, I think the time offset is correct in the driver.

Best regards,

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, October 20, 2018 12:14 PM
To: ap-gto@...
Subject: [ap-gto] Re: ascom driver question



Hello Ray and thanks for responding. I have a new mach1gto mount and I've recently (last two months)
downloaded all the software I'm using including skyx pro and ascom v2 driver v 5.10.02



the 1st pic (sorry for lame pics but best I can do atm) is when I go into Input and click on location within skyx pro.
Time zone is listed as -7 which is what is should be for me here in longmont CO.



<http://www.bisque.com/sc/cfs-
file.ashx/__key/CommunityServer.Discussions.Components.Files/84/3364.IMG_5F00_3328.JPG>



I noticed last night that when this screen opens as seen below from ascom, it shows -6 for TZ. Knowing how little
things can create big problems, I was reaching out to see if this is an issue and how do I fix it? I can't seem to find
how to go back and fix the TZ in ascom as I thought I input that info correctly during the initial setup. The time
shown just above TZ is correct.

<http://www.bisque.com/sc/cfs-
file.ashx/__key/CommunityServer.Discussions.Components.Files/84/6406.IMG_5F00_3329.JPG>



I checked my computer settings and it's set for time and zone automatically and the time zone is listed on my
computer as UTC-07:00 Mountain Time (US and Canada)




Thanks for your help!

dan
Re: ascom driver question

Stuart Heggie <stuart.j.heggie@...>
 

Dan, I have to think you have DST turned on in one software and off in the other. Is that possible?

Stuart

On Sat, 20 Oct 2018 at 15:15, orionsway16@... [ap-gto] <ap-gto@...> wrote:
 

Ray, also I am not running APCC.


dan



--

Re: ascom driver question

Dan Goetz
 

Ray, also I am not running APCC.

dan
Re: ascom driver question

Dan Goetz
 

Hello Ray and thanks for responding.  I have a new mach1gto mount and I've recently (last two months) downloaded all the software I'm using including skyx pro and ascom v2 driver v 5.10.02

 

the 1st pic (sorry for lame pics but best I can do atm) is when I go into Input and click on location within skyx pro.  Time zone is listed as -7 which is what is should be for me here in longmont CO.

 

 

 I noticed last night that when this screen opens as seen below from ascom, it shows -6 for TZ.  Knowing how little things can create big problems, I was reaching out to see if this is an issue and how do I fix it?  I can't seem to find how to go back and fix the TZ in ascom as I thought I input that info correctly during the initial setup.  The time shown just above TZ is correct.

 

I checked my computer settings and it's set for time and zone automatically and the time zone is listed on my computer as UTC-07:00 Mountain Time (US and Canada)


Thanks for your help!

dan
Re: ascom driver question

Ray Gralak
 

Hi Dan,

If this isn't the place to ask a question about ascom, my apologies.
Yes, this is the place you can ask AP V2 ASCOM driver questions.

The driver's time zone information is read from your computer if you have the option selected to match the time to the computer.

Are you also running APCC?

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, October 20, 2018 8:36 AM
To: ap-gto@...
Subject: [ap-gto] ascom driver question



If this isn't the place to ask a question about ascom, my apologies. Otherwise, here's my question.




When I downloaded the ascom driver I had at one point needed to input my location info. In there I put the correct
coordinates as well as the time offset which for me in longmont CO is -7. When I downloaded skyx pro at some
point I did the same thing - correct coordinates and the offset of -7. When I was playing last night I noticed that the
ascom driver now has my offset as -6 while skyx pro still has it at -7. I tried going back to ascom to fix the offset but
I can't seem to find how to change it at this point. Where I'm looking at the ascom driver is the page that wil pop up
when you are connected to your mount and it lists data in a column on the left of that little ascom page which
includes "TZ", time zone. That's where I noticed -6.

Is this something I need to fix and, if so, how?




thx!!

dan
Re: RAPAS question

Dan Goetz
 

And, right after I send my comment that this wasn't explained in my documentation I of course now find exactly where it's explained in my documentation.  Page 6 under "focusing Procedure".  Maybe I need to focus my own eyes first!!

Apologies and thanks!

dan
Re: RAPAS question

Dan Goetz
 

Rolando, thank you.  Ok, I understand now that the focus on the RAPAS is only for the reticle.  Makes sense.

Aha, ok so the RAPAS barrel is what moves for the focus!  I just played with it following your directions and now I see how it works.  Thank you!  

Just a heads up, that explanation isn't in my directions on how to use the RAPAS.  I have a new mach1gto and a new rapas (purchased in the last few months).
Re: RAPAS question

Roland Christen
 


Did I miss a step somewhere or is there something I can do with the RAPAS as it relates to focus?
With every RAPAS we send out detailed instruction sheet that shows how to set the infinity focus for your eyes. Please refer to the instruction sheet if my previous post is not clear.

Rolando


-----Original Message-----
From: orionsway16@... [ap-gto]
To: ap-gto
Sent: Sat, Oct 20, 2018 9:09 am
Subject: [ap-gto] RAPAS question



Had my first chance to use the RAPAS last night and found that I can't focus in on polaris.  So, I turned the focus to the right but that was causing polaris to blurr. Ok, great.  So I need to turn the focus the opposite direction and polaris was starting to come into focus.  However, it only makes it so far until I run out of the ability to turn the focus anymore but the image is still a blurr....a small blur, but definitely not a dot that I can work with but rather an out-of-focus star that was hard to work with.

Did I miss a step somewhere or is there something I can do with the RAPAS as it relates to focus?

thx!

dan
Re: RAPAS question

Roland Christen
 

Joe, I know you're trying to be helpful, but he is focusing the wrong thing.

Rolando



-----Original Message-----
From: 'Joseph Zeglinski' J.Zeglinski@... [ap-gto]
To: ap-gto
Sent: Sat, Oct 20, 2018 10:50 am
Subject: Re: [ap-gto] RAPAS question



    Since you have RAPAS problems with your MACH-1, depending on the serial number/year
– If yours is older than 2014, do you have the “special”  RAPAS ADAPTER PLATE  attached for it? The only mount not needing one was the old AP-900, all, others did.
That might explain why you don’t have enough back space to reach focus.
Mach1GTO - All mounts shipped beginning in 2014 (serial number M10670 and later) will have the adapter for the Right-Angle Polar Alignment Scope “built in”. Mounts shipped in prior years must purchase the Right-Angle Polar Alignment Scope Adapter for Mach1GTO (RAPM1), - separately.
HTH,
Joe Z.
Re: RAPAS question

Roland Christen
 


I had a clear line of sight to polaris, and no wiring in the mach1gto polar axis.  Without the scope I was able to do a rough alignment.  With the RAPAS, I could see polaris, but it was way big.  I used the focuser on the RAPAS and when I went "in", the blur got bigger.  When I turned "out", polaris started to come into focus but I ran out of, well, the ability to continue turning the focus "out".  The focus reached it's end but polaris wasn't in focus yet.  I needed maybe another turn or two to get there but, as I said, it was at the end of it's ability to continue turning.

any thoughts?
Yes, you are focusing the wrong thing. See my previous post.

Rolando


-----Original Message-----
From: orionsway16@... [ap-gto]
To: ap-gto
Sent: Sat, Oct 20, 2018 10:24 am
Subject: Re: [ap-gto] RAPAS question



I had a clear line of sight to polaris, and no wiring in the mach1gto polar axis.  Without the scope I was able to do a rough alignment.  With the RAPAS, I could see polaris, but it was way big.  I used the focuser on the RAPAS and when I went "in", the blur got bigger.  When I turned "out", polaris started to come into focus but I ran out of, well, the ability to continue turning the focus "out".  The focus reached it's end but polaris wasn't in focus yet.  I needed maybe another turn or two to get there but, as I said, it was at the end of it's ability to continue turning.

any thoughts?
Re: RAPAS question

Joe Zeglinski
 

    Since you have RAPAS problems with your MACH-1, depending on the serial number/year
– If yours is older than 2014, do you have the “special”  RAPAS ADAPTER PLATE  attached for it? The only mount not needing one was the old AP-900, all, others did.
That might explain why you don’t have enough back space to reach focus.
Mach1GTO - All mounts shipped beginning in 2014 (serial number M10670 and later) will have the adapter for the Right-Angle Polar Alignment Scope “built in”. Mounts shipped in prior years must purchase the Right-Angle Polar Alignment Scope Adapter for Mach1GTO (RAPM1), - separately.
HTH,
Joe Z.
Re: RAPAS question

Roland Christen
 


Had my first chance to use the RAPAS last night and found that I can't focus in on polaris.  So, I turned the focus to the right but that was causing polaris to blurr.
It may seem that the eyepiece focus is used to bring the stars into focus, but that's really not correct. The eyepiece focus is strictly to bring the reticle into sharp focus.

Step1: Focus the eyepiece on the reticle. Do this in the daytime and don't change the eyepiece focus.
Step2: Aim the scope to a very distant object, loosen the retaining ring on the rear of the scope barrel. This will allow you to move the scope focus in and out by simply turning the barrel clockwise or counterclockwise. Turn the barrel until a distant object is in sharp focus. Now you have both reticle and infinity focus in the same place.

Rolando


-----Original Message-----
From: orionsway16@... [ap-gto]
To: ap-gto
Sent: Sat, Oct 20, 2018 9:09 am
Subject: [ap-gto] RAPAS question



Had my first chance to use the RAPAS last night and found that I can't focus in on polaris.  So, I turned the focus to the right but that was causing polaris to blurr. Ok, great.  So I need to turn the focus the opposite direction and polaris was starting to come into focus.  However, it only makes it so far until I run out of the ability to turn the focus anymore but the image is still a blurr....a small blur, but definitely not a dot that I can work with but rather an out-of-focus star that was hard to work with.

Did I miss a step somewhere or is there something I can do with the RAPAS as it relates to focus?

thx!

dan
ascom driver question

Dan Goetz
 

If this isn't the place to ask a question about ascom, my apologies.  Otherwise, here's my question.


When I downloaded the ascom driver I had at one point needed to input my location info.  In there I put the correct coordinates as well as the time offset which for me in longmont CO is -7.  When I downloaded skyx pro at some point I did the same thing - correct coordinates and the offset of -7.  When I was playing last night I noticed that the ascom driver now has my offset as -6 while skyx pro still has it at -7.  I tried going back to ascom to fix the offset but I can't seem to find how to change it at this point.  Where I'm looking at the ascom driver is the page that wil pop up when you are connected to your mount and it lists data in a column on the left of that little ascom page which includes "TZ", time zone.  That's where I noticed -6.

Is this something I need to fix and, if so, how?


thx!!

dan
Re: RAPAS question

Dan Goetz
 

I had a clear line of sight to polaris, and no wiring in the mach1gto polar axis.  Without the scope I was able to do a rough alignment.  With the RAPAS, I could see polaris, but it was way big.  I used the focuser on the RAPAS and when I went "in", the blur got bigger.  When I turned "out", polaris started to come into focus but I ran out of, well, the ability to continue turning the focus "out".  The focus reached it's end but polaris wasn't in focus yet.  I needed maybe another turn or two to get there but, as I said, it was at the end of it's ability to continue turning.

any thoughts?
Re: RAPAS question

Joel Short
 

You should be able to get pinpoint focus on Polaris with the RAPAS.  Is something blocking the hole, or blocking polaris?
joel

On Sat, Oct 20, 2018 at 9:36 AM orionsway16@... [ap-gto] <ap-gto@...> wrote:
 

Had my first chance to use the RAPAS last night and found that I can't focus in on polaris.  So, I turned the focus to the right but that was causing polaris to blurr. Ok, great.  So I need to turn the focus the opposite direction and polaris was starting to come into focus.  However, it only makes it so far until I run out of the ability to turn the focus anymore but the image is still a blurr....a small blur, but definitely not a dot that I can work with but rather an out-of-focus star that was hard to work with.


Did I miss a step somewhere or is there something I can do with the RAPAS as it relates to focus?


thx!


dan
RAPAS question

Dan Goetz
 

Had my first chance to use the RAPAS last night and found that I can't focus in on polaris.  So, I turned the focus to the right but that was causing polaris to blurr. Ok, great.  So I need to turn the focus the opposite direction and polaris was starting to come into focus.  However, it only makes it so far until I run out of the ability to turn the focus anymore but the image is still a blurr....a small blur, but definitely not a dot that I can work with but rather an out-of-focus star that was hard to work with.


Did I miss a step somewhere or is there something I can do with the RAPAS as it relates to focus?


thx!


dan
Re: APCC unable to find GPS COM port

Ray Gralak
 

Hi Dale,

The Fix: uninstall all ublox drivers. Hah.
Wow, that was some really nice detective work. I am impressed!

Best regards,

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, October 20, 2018 12:09 AM
To: ap-gto@...
Subject: Re: [ap-gto] APCC unable to find GPS COM port





On Oct 20, 2018, at 1:00 AM, Dale Ghent daleg@... [ap-gto] <ap-gto@...> wrote:

And I have an answer. It is a problem with .net and interacting with this VCP driver. According to ublox:

The .Net 'SerialPort' class does not recognise the COM port created by this driver as real COM port, hence this
class cannot be used to communicate with this driver.

I have no idea why it worked before under ACPP; perhaps it was a recent update which changed things. I guess
this means that the other program I was using to connect to the VCP is certainly not .net if it works fine.

Alright, so this is purely a problem that I need to solve for myself for now. Sorry for taking your attention.
And problem solved. I figure I'd close the loop by posting my findings here in the even someone else runs into this
situation.

I took a look at the datasheet for the GPS controller chip used in this receiver and noted that it implements a basic
UART mode as its default mode on the USB bus. Long story short, if the ublox device driver *does not* attach to the
controller, it's not put in the non-UART mode and will instead be enumerated as a regular serial interface and
assigned a COM port by Windows. Because it now looks like an actual hardware serial device instead of one
emulated via VCP driver, .Net apps such as APCC now have no problem talking to it via the SerialPort class.

The Fix: uninstall all ublox drivers. Hah.

http://i.imgur.com/7AVZxSw.png

I must say that this was the first time I had to *uninstall* the drivers for something in order to get it to work.

/dale
Re: APCC unable to find GPS COM port

Christopher Erickson
 

Excellent sleuthing!

Well done!


-Christopher Erickson
Observatory engineer
Summit Kinetics
Waikoloa, HI 96738
www.summitkinetics.com

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Friday, October 19, 2018 9:09 PM
To: ap-gto@...
Subject: Re: [ap-gto] APCC unable to find GPS COM port



On Oct 20, 2018, at 1:00 AM, Dale Ghent daleg@... [ap-gto]
<ap-gto@...> wrote:

And I have an answer. It is a problem with .net and interacting with this
VCP driver. According to ublox:

The .Net 'SerialPort' class does not recognise the COM port created by
this driver as real COM port, hence this class cannot be used to communicate
with this driver.

I have no idea why it worked before under ACPP; perhaps it was a recent
update which changed things. I guess this means that the other program I was
using to connect to the VCP is certainly not .net if it works fine.

Alright, so this is purely a problem that I need to solve for myself for
now. Sorry for taking your attention.

And problem solved. I figure I'd close the loop by posting my findings here
in the even someone else runs into this situation.

I took a look at the datasheet for the GPS controller chip used in this
receiver and noted that it implements a basic UART mode as its default mode
on the USB bus. Long story short, if the ublox device driver *does not*
attach to the controller, it's not put in the non-UART mode and will instead
be enumerated as a regular serial interface and assigned a COM port by
Windows. Because it now looks like an actual hardware serial device instead
of one emulated via VCP driver, .Net apps such as APCC now have no problem
talking to it via the SerialPort class.

The Fix: uninstall all ublox drivers. Hah.

http://i.imgur.com/7AVZxSw.png

I must say that this was the first time I had to *uninstall* the drivers for
something in order to get it to work.

/dale

------------------------------------
Posted by: Dale Ghent <daleg@...>
------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list see
http://groups.yahoo.com/group/ap-gto
------------------------------------

Yahoo Groups Links




---
This email has been checked for viruses by AVG.
https://www.avg.com
24901 - 24920 of 88314