Date   

Re: APCC: RA limit reached while in Park 3? #APCC

Glenn
 

Howard, thank you for speaking to me on the phone today. 

For the benefit of others, I will repeat what you told me to do to attempt to solve the problem. 

  1. Park the mount (I used Park 3)
  2. Reconfigure the V2 driver to not use the APCC virtual port. I changed it back to the IP address used by my Ethernet configuration. 
  3. Configure the driver to Unpark from Park 3 and unpark the mount. 
After doing this, the mount unparked and responded to commands normally. 

I then reconfigured the driver for use with APCC Pro and tried to connect to the mount. I got this error, which is what has appeared since the beginning. 



I don't even have to connect to the driver to get this error. It appears as soon as I connect to the mount. 

Does anyone know what might be causing this?

Thank you,

Glenn


Re: Seeking CP3 Control Box with V2 Chip

Christopher Erickson
 

I don't agree. Changing CPx controllers requires that a new PEM recording takes place. There is no way for a new CPx controller to know where the old CPx controller left the worm gear positions at.

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


On Thu, Oct 7, 2021, 3:50 PM Chris White <chris.white@...> wrote:
For those interested, I spoke with Dave today and as long as the mount doesn't move it is OK to download your PEC curve, change CP's and then upload that curve to the new unit.


Re: #APCC #Mach2 - 3D viewer weird scope position while it is parked (or even while slewing sometimes) #apcc #APCC

Sébastien Doré
 

Hi, just to let people know that Roland and Team (yes, with a capital T, they deserve it !) are kindly working with me in the background on this, which is why the thread has gone silent.

Quadruple 'A' service from AP, as usual.

Clear skies,
Sébastien


Re: Seeking CP3 Control Box with V2 Chip

Chris White
 

For those interested, I spoke with Dave today and as long as the mount doesn't move it is OK to download your PEC curve, change CP's and then upload that curve to the new unit.


Re: Interesting Park using NINA

michael mccann
 

Hey Wade
I’m not in Rusty’s. But I see him a couple times a week. So I will. Are you back near Ellensburg, do I have that right? I know I was supposed to come by sometime this summer, but the summer went by too fast.

I’ll look into that. I didn’t know that was an option.

On Oct 7, 2021, at 15:30, W Hilmo <y.groups@...> wrote:

Are you at Rusty’s by chance?

If so, say hi to Dennis and Dianne for me.

Regarding the time zone issue, if your computer is 100% dedicated to the observatory, you might consider setting it up on UTC, with no DST changes.

On Oct 7, 2021, at 1:51 PM, michael mccann via groups.io <mmccawsprojects@...> wrote:

You know that might be. I’m living in New Mexico, but so close to Arizona my computer always tell me my time is an hour earlier. I’m out in the countryside where I get my time from cell/data and not a regular network. I thought I had corrected this problem on my computer because I set the display time for mountain time zone, but when you look at all the settings it shows that it thinks it’s in Pacific time zone. I tried several times to change it. Software comes back says that I don’t have permission to, and yet I’m the administrator.

So finalizing the park is best from AP ASCOM.











Re: AP1100 mount encoder and servos errors

Howard Hedlund
 

Hi Max,
Please zip and email me a log file that shows this.


Re: AP1100 mount encoder and servos errors

Roland Christen
 

Make sure all your cables are plugged in and the encoder lights are green or blue. Check the encoder cable inside the Dec axis to make sure it is seated.

Roland

-----Original Message-----
From: Max Mirot via groups.io <titansmoons@...>
To: main@ap-gto.groups.io
Sent: Thu, Oct 7, 2021 2:57 pm
Subject: [ap-gto] AP1100 mount encoder and servos errors

I am see/clearing frequent errors on the AP1100. 
I rebalance last night. It did not help.
Load is AP Honders and a camera.

Log attached

Suggestions?

Thanks 

Max Mirot

--
Roland Christen
Astro-Physics


Re: Possible bug in APCC with park?

Tom Blahovici
 

Well I disagree with always using apcc to do a park. In Voyager if you are done for the night it should park where you have set the park.
If you are automating everything, the final step will be to park.
So bottom line is I think Voyager is not always doing a park 3.
Tom


Re: Possible bug in APCC with park?

Tom Blahovici
 

Actually, I think that this is something to do with Voyager. Perhaps a new release.
When I am done at night, i select point at zenith in Voyager. It is not park. Then I stop tracking in Voyager.
Last night, I finished the flats then I selected track in Voyager and attempted the usual park. In the past it would always go to park 3. To Last night it went to the zenith again. However apcc then did the proper park to park 3.
What was different from the night before was I did not select track before I parked. 
I need to investigate why Voyager no longer parks at park 3.
Tom


Re: Possible bug in APCC with park?

Roland Christen
 

You need a remote controlled umbrella. British style, big and boisterous.

Rolando

-----Original Message-----
From: ap@... <ap@...>
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Thu, Oct 7, 2021 3:33 pm
Subject: Re: [ap-gto] Possible bug in APCC with park?

Howard Hedlund wrote:
  • Don't park with other software.  APCC is already open anyway.  Use APCC to park your mount.
I’ll add one flavor onto this.
 
I have the APCC park default set to 3, which is where I load and unload the OTA.  In park 3 though, the telescope points (somewhat) up.
 
I have the Ascom V2 driver set to park 2.  It has a separate default.  The reason for this is that if rain is detected, the safety monitor tells NINA to tell ASCOM to do a park.  Park 2 points the telescope horizontally, where less rain will hit the objective while I run outside to haul things inside, also I think most of the other devices are less vulnerable level.  Note this is a “safety” inside NINA from an ASCOM safety monitor, not the same as APCC’s safety which is related to a disconnect.
 
So I agree with what you said sort of – I always manually park from APCC. But I have the other set up for a different purpose.  It is nice that there are two defaults (actually three counting safety park in APCC).
 
FWIW.
 
Linwood
 

--
Roland Christen
Astro-Physics


Re: Interesting Park using NINA

W Hilmo
 

Are you at Rusty’s by chance?

If so, say hi to Dennis and Dianne for me.

Regarding the time zone issue, if your computer is 100% dedicated to the observatory, you might consider setting it up on UTC, with no DST changes.

On Oct 7, 2021, at 1:51 PM, michael mccann via groups.io <mmccawsprojects@...> wrote:

You know that might be. I’m living in New Mexico, but so close to Arizona my computer always tell me my time is an hour earlier. I’m out in the countryside where I get my time from cell/data and not a regular network. I thought I had corrected this problem on my computer because I set the display time for mountain time zone, but when you look at all the settings it shows that it thinks it’s in Pacific time zone. I tried several times to change it. Software comes back says that I don’t have permission to, and yet I’m the administrator.

So finalizing the park is best from AP ASCOM.





Re: Interesting Park using NINA

michael mccann
 

Come to think of it, and I forgotten until you mentioned it, NINA asks whether to sync ‘NINA to mount’ or ‘mount to NINA’ . And I know I chose ‘NINA to mount’. I guess it should be the other way around. If it’s not to cloudy tonight I’ll change that.

Cheers

On Oct 7, 2021, at 15:08, Dale Ghent <daleg@...> wrote:


What I bet *might* be happening in your case is that you have the keypad connected to your mount and it's not set for an EXT auto connect. So when your mount is powering on, the time that's configured in the keypad is immediately getting applied to the CP when the keypad initializes it. This could possibly explain some mount/PC time mismatch or wonkiness. With the Sync Time options I pointed out before, you can set the keypad to EXT in its autoconnect setting which will allow the ASCOM driver to initialize the mount when it connects.


Re: Interesting Park using NINA

Dale Ghent
 

I honestly can't explain why there's a difference between an external app such as NINA telling the driver to park, and the driver's own park button giving different results. I would think that both interfaces run the same logic underneath. Perhaps Ray can shed some light on this mechanism.

But given a correct PC and mount time and a reasonable lat/long, parking should always be successful and fine assuming your mount is properly aligned, something that can be done with a single plate solve. Time zones aren't going to have a bearing on the mount's internal clock. Like your PC, the system clock actually runs in UTC time, with whatever timezone you have configured applied to it for purposes of display.

What I bet *might* be happening in your case is that you have the keypad connected to your mount and it's not set for an EXT auto connect. So when your mount is powering on, the time that's configured in the keypad is immediately getting applied to the CP when the keypad initializes it. This could possibly explain some mount/PC time mismatch or wonkiness. With the Sync Time options I pointed out before, you can set the keypad to EXT in its autoconnect setting which will allow the ASCOM driver to initialize the mount when it connects.

On Oct 7, 2021, at 16:50, michael mccann via groups.io <mmccawsprojects@...> wrote:

You know that might be. I’m living in New Mexico, but so close to Arizona my computer always tell me my time is an hour earlier. I’m out in the countryside where I get my time from cell/data and not a regular network. I thought I had corrected this problem on my computer because I set the display time for mountain time zone, but when you look at all the settings it shows that it thinks it’s in Pacific time zone. I tried several times to change it. Software comes back says that I don’t have permission to, and yet I’m the administrator.

So finalizing the park is best from AP ASCOM.





Re: Interesting Park using NINA

michael mccann
 

You know that might be. I’m living in New Mexico, but so close to Arizona my computer always tell me my time is an hour earlier. I’m out in the countryside where I get my time from cell/data and not a regular network. I thought I had corrected this problem on my computer because I set the display time for mountain time zone, but when you look at all the settings it shows that it thinks it’s in Pacific time zone. I tried several times to change it. Software comes back says that I don’t have permission to, and yet I’m the administrator.

So finalizing the park is best from AP ASCOM.


Re: Possible bug in APCC with park?

ap@CaptivePhotons.com
 

Howard Hedlund wrote:

  • Don't park with other software.  APCC is already open anyway.  Use APCC to park your mount.

I’ll add one flavor onto this.

 

I have the APCC park default set to 3, which is where I load and unload the OTA.  In park 3 though, the telescope points (somewhat) up.

 

I have the Ascom V2 driver set to park 2.  It has a separate default.  The reason for this is that if rain is detected, the safety monitor tells NINA to tell ASCOM to do a park.  Park 2 points the telescope horizontally, where less rain will hit the objective while I run outside to haul things inside, also I think most of the other devices are less vulnerable level.  Note this is a “safety” inside NINA from an ASCOM safety monitor, not the same as APCC’s safety which is related to a disconnect.

 

So I agree with what you said sort of – I always manually park from APCC. But I have the other set up for a different purpose.  It is nice that there are two defaults (actually three counting safety park in APCC).

 

FWIW.

 

Linwood

 


Re: Possible bug in APCC with park?

Howard Hedlund
 

Hi Tom, 
Just a few brief thoughts:
  • Park is a state.  (as opposed to a State Park) 
  • Park means that the motors and their encoders are no longer energized.  Nothing more.
  • The mount can park, or can be parked in any position.  
  • For normal operation, the mount MUST remain actively connected to APCC - This is a SAFETY feature!  In APCC:
    • click the Park tab,
    • find the Safety Park group box at the upper right corner 
    • click its lovely little ?  in the corner.  You will be rewarded with some answers
  • Don't park with other software.  APCC is already open anyway.  Use APCC to park your mount.


AP1100 mount encoder and servos errors

Max Mirot
 

I am see/clearing frequent errors on the AP1100. 
I rebalance last night. It did not help.
Load is AP Honders and a camera.

Log attached

Suggestions?

Thanks 

Max Mirot


Re: Interesting Park using NINA

Dale Ghent
 


NINA just tells the ASCOM driver, essentially, "Park the mount". It's up to the driver and mount controller to get the mount into the park position that is configured in the ASCOM driver. NINA and other upper-level apps aren't aware of what the physical orientation of the park position actually is; they only know whether the mount is parked or not.

As for why your mount didn't land in the Park 3 position, looking at the AP ASCOM driver logs might help determine why. Perhaps you hit the stop button by accident. There could be a time issue at play, so make sure your PC's clock is accurate and that the "Sync mount time at initialization" and "Keep mount time synced to PC time" options are checked in the AP ASCOM driver's setup options. You can access this through the "Setip Telescope" utility or by pressing the gears icon next to the driver selection drop-down box in NINA. I'm not sure, but you may need to reinitialize your mount to get the time to sync. Of course you ought to ensure that your PC's own clock is fairly accurate and is itself synced to a time source, if possible. See the attached screenshot.



On Oct 7, 2021, at 13:59, michael mccann via groups.io <mmccawsprojects@...> wrote:

Hi
I believe the manual says try to unpark and park with AP Ascom or APCC.  Last night I started the mount and connected with NINA.  This was my first tracking session with this mount, so this a newbie making sure My process is correct. At the end of tracking M31, I used NINA to park to #3 the mount. Dec returned to correctly, RA was 10 to 15 degrees off, weights East.  So I then tried the AP Ascom to park.  The mount corrected and moved to park position #3.
So here’s the info to fill out the picture:
Software: 
NINA 1.11 - very recent version: I only used the simple sequence aspect of setting up a single target.
APCC - not installed yet 
AP ASCOM V2 - installed 
Keypad is attached and is configured for Ext.
You’ll Laugh:
Telescope: EVO50
Camera: ZWO ASI183MC 
Guiding 
ZWO MINI GUIDER w/ ASI290MM
PLATESOLVE: ASTAP
Process:
- Start mount 
- Start Nina 
- connect eqpt 
- set Nina to slew, and auto correct (platesolve)
- run a set of four settings, about 3 hours worth
- manually I used NINA to Park, in NINA park is set to position 3. 
*** this is where it didn’t fully move to park #3
This where I used the AP ASCOM V2 interface to park, which it did correctly.

So I was surprised that NINA didn’t park it correctly.  A side note, I did notice that when slewing to M31 it was several degrees out.

Any thoughts?

Cheers 







Re: Interesting Park using NINA

Roland Christen
 

When you're off by 15 degrees in RA it always means that your local time is off by 1 hour in that particular application. Could be time is wrong, could also be daylight savings is set wrong.

For every hour, RA changes by 15 degrees.

Rolando

-----Original Message-----
From: michael mccann via groups.io <mmccawsprojects@...>
To: main@ap-gto.groups.io
Sent: Thu, Oct 7, 2021 12:59 pm
Subject: [ap-gto] Interesting Park using NINA

Hi
I believe the manual says try to unpark and park with AP Ascom or APCC.  Last night I started the mount and connected with NINA.  This was my first tracking session with this mount, so this a newbie making sure My process is correct. At the end of tracking M31, I used NINA to park to #3 the mount. Dec returned to correctly, RA was 10 to 15 degrees off, weights East.  So I then tried the AP Ascom to park.  The mount corrected and moved to park position #3.
So here’s the info to fill out the picture:
Software:
NINA 1.11 - very recent version: I only used the simple sequence aspect of setting up a single target.
APCC - not installed yet
AP ASCOM V2 - installed
Keypad is attached and is configured for Ext.
You’ll Laugh:
Telescope: EVO50
Camera: ZWO ASI183MC
Guiding
ZWO MINI GUIDER w/ ASI290MM
PLATESOLVE: ASTAP
Process:
- Start mount
- Start Nina
- connect eqpt
- set Nina to slew, and auto correct (platesolve)
- run a set of four settings, about 3 hours worth
- manually I used NINA to Park, in NINA park is set to position 3.
*** this is where it didn’t fully move to park #3
This where I used the AP ASCOM V2 interface to park, which it did correctly.

So I was surprised that NINA didn’t park it correctly.  A side note, I did notice that when slewing to M31 it was several degrees out.

Any thoughts?

Cheers






--
Roland Christen
Astro-Physics


Interesting Park using NINA

michael mccann
 

Hi
I believe the manual says try to unpark and park with AP Ascom or APCC. Last night I started the mount and connected with NINA. This was my first tracking session with this mount, so this a newbie making sure My process is correct. At the end of tracking M31, I used NINA to park to #3 the mount. Dec returned to correctly, RA was 10 to 15 degrees off, weights East. So I then tried the AP Ascom to park. The mount corrected and moved to park position #3.
So here’s the info to fill out the picture:
Software:
NINA 1.11 - very recent version: I only used the simple sequence aspect of setting up a single target.
APCC - not installed yet
AP ASCOM V2 - installed
Keypad is attached and is configured for Ext.
You’ll Laugh:
Telescope: EVO50
Camera: ZWO ASI183MC
Guiding
ZWO MINI GUIDER w/ ASI290MM
PLATESOLVE: ASTAP
Process:
- Start mount
- Start Nina
- connect eqpt
- set Nina to slew, and auto correct (platesolve)
- run a set of four settings, about 3 hours worth
- manually I used NINA to Park, in NINA park is set to position 3.
*** this is where it didn’t fully move to park #3
This where I used the AP ASCOM V2 interface to park, which it did correctly.

So I was surprised that NINA didn’t park it correctly. A side note, I did notice that when slewing to M31 it was several degrees out.

Any thoughts?

Cheers

6861 - 6880 of 88774