Date   

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


Re: Possible bug in APCC with park?

Ray Gralak
 

Hi Tom,

I guess Voyager could have set a new park position but then why wouldn't apcc park at 3 like I requested?
My guess is that the mount was already parked in position near the zenith, so Voyager, seeing the mount was already parked, didn't try to park again. The mount could have parked itself at its current position near the zenith if you had shut down APCC for more than a minute.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Tom Blahovici
Sent: Wednesday, October 6, 2021 1:19 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] Possible bug in APCC with park?

Last night from Voyager, I did a move to the zenith and stopped tracking so I could do flats. When they were
finished I attempted to park the scope. It reported it was parked. My usual location is park 3.
I closed out Voyager completely, and attempted to start tracking again.
Apcc reported the mount as parked. Pointing at the zenith.
I then did an unpark and tried a park 3 at the point. It went back to the zenith.
I had to use apcc, and then reopen it. Then. I could do a park 3.
I guess Voyager could have set a new park position but then why wouldn't apcc park at 3 like I requested?
Thanks


Re: APCC - APPM - and ASTAP

Ron Kramer
 

PNG files won't have the data (RA DEC) that FITS headers contain. 
Yes ASTAP is best and fastest.  Yes works with NINA and APPM.
I had some hiccups - I think bin2 was the answer.  APPM model is the best thing I've done for my Mach1. I no longer have to guide at all.  Tested up to 1000 second exposures.  I use to get trails or elongated stars over 40 seconds. 


On Mon, Oct 4, 2021 at 2:29 PM Jack Huerkamp <Mallincamusa@...> wrote:

I was not running the mount at all.  I was inside my house running ASTAP in stand alone mode on my home computer to become familiar with it.  According to the ASTAP site, it is possible to solve images by feeding them directly into the program.  That is what I was trying to do, and no matter what image I fed into the program, it failed to solve.  That is when I contacted Han at hnsky.org and he provided things to try to get the images to solve – and they did. 

 

Once I am out in the observatory and running ASTAP with APPM on my mount, scope and camera, hopefully all will work as designed.

 

Yours truly,

 

Jack

 

Jack Huerkamp

Jack's Astro Accessories, LLC

38388 Pine Street

Pearl River, LA 70452-5192

985-445-5063

mallincamusa@...

www.mallincamusa.com

30.37N  89.76W

 

All of us get lost in the darkness.
Dreamers learn to steer by the stars.

………………………………….Neil Peart

 

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@...
Sent: Monday, October 04, 2021 12:24 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC - APPM - and ASTAP

 

Jack Huerkamp wrote:

 

  • Mainly image scale, but putting a rough RA and Dec into the boxes so that the program did not have to search the entire sky helped a lot.  I assume that when running APPM with ASTAP, I will see the target RA and Dec and then I will be able to input them into ASTAP to help refine the plate solving.  I will find out once the skies clear here in SE Louisiana.

 

No,  you should not need to, the RA/DEC should be provided by the connection to your mount and/or by the FITS headers (not completely sure which, they both provide it).

 

If you were doing this running the simulator you should also connect to the same simulator in APPM and NINA.  Both NINA and APPM should have a connection to the (same) mount.

 


Virus-free. www.avg.com




Re: Seeking CP3 Control Box with V2 Chip

Chris White
 

I would be interested to know the answer, however you are correct... a pempro curve is not too tough to generate... and fun. 😀


Re: RA and DEC stiff after loosing Clutches AP1100

Max Mirot
 

Sure that makes sense.

I read the manual a year and a half ago. 
That how long I have been using this configuration without change to the scope or camera.

You saved me again Roland.

Thanks

Max


Re: RA and DEC stiff after loosing Clutches AP1100

Roland Christen
 

Yes, that's by design. For fine balance you need to use the gear lever to disengage the gears. But please read the manual! It is important to always release the gears ONLY at Park 3 position.

Roland

-----Original Message-----
From: Max Mirot via groups.io <titansmoons@...>
To: main@ap-gto.groups.io
Sent: Wed, Oct 6, 2021 5:58 pm
Subject: [ap-gto] RA and DEC stiff after loosing Clutches AP1100

Both my RA and Dec no longer turn freely after loosing the clutches on my AP1100.
Another word it takes a little force or some lbs of misbalance for them to turn

What am I missing ? 

Max

--
Roland Christen
Astro-Physics


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

Ray Gralak
 

APCC reads the mount’s mechanical position in both axes and returns that relative to each axis’ offset value to the 3DViewer. The axis offset value is what gets saved when the 3D viewer is synced. It’s incredibly straightforward and works the same way for ALL mounts. Nothing is different for the Mach 2.

 

An incorrect 3D position can arise if you move the scope manually and sync/recal the mount, or possibly when you home the mount. The solution is to resync the 3D Viewer after homing, moving the scope manually,  or unparking from one of the Park positions instead of the last-parked position.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Seb@stro
Sent: Wednesday, October 6, 2021 10:54 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] #APCC #Mach2 - 3D viewer weird scope position while it is parked (or even while slewing sometimes) #apcc

 

Hi,

 

When I use the 3D viewer in APPC (which is a great feature), it seems to get de-synchronized from the mount position sometimes. Like in the example  below where the mount was parked at park 2 at around 9:30 AM (time of the screenshot is 12:30). 

 

One thing that might explains this is I do not quite fully understand what "correctly calibrated with the night sky" means in the warning window when the 3D viewer is launched. 

 

I would have thought "Find Home" (encoder tab) would be a valid calibration process for encoder mount in this regards. Or maybe the sync at the beginning of an APPM run, or from a third party software, but it doesn't seem to prevent that from happening, so obviously I'm missing something. My prerogative was that since the mount (with encoders) always knows where it is at, the 3D viewer should too, but it seems that at least in my case, it does not. 

 

From the manual, I understand this warning/pre-requisite is probably there for non-encoder mount when clutches are loosen but I couldn't find any information relative to this for encoder mounts or more specifically for the Mach2 (which is one of a kind species in itself, I know). But I might have missed it too. 

 

 

Hitting Sync -> Re-sync 3D view does fix it but it would be nice (and less scary, especially when slewing at 1800X) if it were always showing the correct orientation. 

 

Still, it works 95% of the time. Just trying to understand how I can get the last 5%... I can provide logs if required, but I feel it's just me not doing something I should. Anybody can pinpoint where I need to correctly "calibrate on the night sky", if that is indeed my issue ?

 

Thanks,

 

Sébastien

 

 


RA and DEC stiff after loosing Clutches AP1100

Max Mirot
 

Both my RA and Dec no longer turn freely after loosing the clutches on my AP1100.
Another word it takes a little force or some lbs of misbalance for them to turn

What am I missing ? 

Max


Re: Seeking CP3 Control Box with V2 Chip

Roland Christen
 

The way PEMPro works, you can store the curve on your laptop and load it onto the same CP4 at any time. However, when you change CPs, I would worry that the timing would not be the same. I will have to check with our servo engineer and get back to you.

That said, doing a Pempro run is actually fun, and the more you do it, the easier it becomes.

Roland

-----Original Message-----
From: Christopher Erickson <christopher.k.erickson@...>
To: main@ap-gto.groups.io
Sent: Wed, Oct 6, 2021 5:37 pm
Subject: Re: [ap-gto] Seeking CP3 Control Box with V2 Chip

Every time a new CP3/4 is placed on a mount, a new curve has to be generated and stored in that CP3/4.

"My advice is always free and worth every penny!"

-Christopher Erickson
Observatory Engineer
Summit Kinetics
Waikoloa, Hawaii


On Wed, Oct 6, 2021 at 11:50 AM Chris White <chris.white@...> wrote:
Guess I have one more followup question.  If I make a PEC curve with the loaner CP4 will I ba able to keep that curve when I get mine back from repair, or will it require a new curve be generated at that time?

--
Roland Christen
Astro-Physics


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

Roland Christen
 

I would have to let Ray take a look.

Rolando

-----Original Message-----
From: Seb@stro <sebastiendore1@...>
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Wed, Oct 6, 2021 4:55 pm
Subject: Re: [ap-gto] #APCC #Mach2 - 3D viewer weird scope position while it is parked (or even while slewing sometimes) #apcc #apcc #mach2

Here's what I get. Everything synced to the second (look at the Ottawa time on my cell phone).

When I attempt to check Location on the keypad, I get the following message: "Keypad in EXT mode". I did initialize the mount with APCC and just checked it too has the correct time & date and location as you can see in the screenshot.

So not sure what else I can have wrongly set. If it were a bad sync, it wouldn't get fixed when I click on "Resync 3D viewer", wouldn't it ? 

Just to make sure I'm making myself understood correctly, please notice that the scope position in the 3D viewer has been changing continously during all day, even if the scope is Parked right now and has been parked all day.

Anyway, I would have noticed such a big offset while imaging (successfully) at 2000 mm for the last three nights. I set everything up on monday, and weather has been cooperating since then so I have not touched a thing except perhaps refining PA (for at most +/- 10 arc-sec) from night to night.

Here's a link to my logs anyway:


Sébastien


De : main@ap-gto.groups.io <main@ap-gto.groups.io> de la part de Roland Christen via groups.io <chris1011@...>
Envoyé : 6 octobre 2021 16:43
À : main@ap-gto.groups.io <main@ap-gto.groups.io>
Objet : Re: [ap-gto] #APCC #Mach2 - 3D viewer weird scope position while it is parked (or even while slewing sometimes) #apcc #apcc #mach2
 
Check your keypad time setting. It has to be the same as your computer time if you are going to switch back and forth between the two.

Roland

--
Roland Christen
Astro-Physics


Re: Seeking CP3 Control Box with V2 Chip

Christopher Erickson
 

Every time a new CP3/4 is placed on a mount, a new curve has to be generated and stored in that CP3/4.

"My advice is always free and worth every penny!"

-Christopher Erickson
Observatory Engineer
Summit Kinetics
Waikoloa, Hawaii


On Wed, Oct 6, 2021 at 11:50 AM Chris White <chris.white@...> wrote:
Guess I have one more followup question.  If I make a PEC curve with the loaner CP4 will I ba able to keep that curve when I get mine back from repair, or will it require a new curve be generated at that time?

4901 - 4920 of 86804