Date   

Re: Lost in space

Lee Dodge
 

OK, a variation on the same theme for my AP1100 with absolute encoders.  I was happily imaging on Arp273, even using the pointing and tracking model that I  had made just for that declination (I used +35 and +40 degrees declination).  I was ready to climb out of the dome and take over with my other computer located in a warm building.  I bumped the scope enough to throw it off by a degree or so.  I asked APPM to plate solve and recal.  It tried and failed, even using AllSky.  I remembered that with absolute encoders you could ask the mount to Go Home, which I did.  However, I could not remember what to do after it got to Home.  Then I tried going to Polaris, and doing a recal there (a bad idea). 

What was I supposed to do with the Go Home command?

Lee 


Re: Mount Status Not Updating in MaxIm DL Observatory Control Window

Roland Christen
 


Did I understand your previous post correctly that this configuration (MaxIm connected directly to mount via AP-V2 Driver and NOT through APCC) is what you have been using when you experienced the same issue ?
Yes, that is what I have been using. Maxim won't update after a slew. The only difference is that i always have a camera and guider connected. So, maybe I will try using Maxim as you did, without anything else connected. I ran both camera and mount connections thru a powered hub, so maybe that's another variable.

Roland

-----Original Message-----
From: M Hambrick <mhambrick563@...>
To: main@ap-gto.groups.io
Sent: Thu, Nov 11, 2021 4:51 pm
Subject: Re: [ap-gto] Mount Status Not Updating in MaxIm DL Observatory Control Window

Hi Roland

Yes I did. I did two separate slews to objects that I selected from the Catalog tab in the MaxIm DL Observatory Control window. I also parked and then un-parked the mount from MaxIm and in each case the mount status was being correctly picked up in MaxIm.

Did I understand your previous post correctly that this configuration (MaxIm connected directly to mount via AP-V2 Driver and NOT through APCC) is what you have been using when you experienced the same issue ? If so, then the only difference with what I have done is that I am using an ethernet cable, and I believe that you are using USB.

I am not sure that it will make any difference, but until now, I have been running these experiments without my cameras connected. Normally I will have two cameras connected to MaxIm as well as the mount. I plan to check this out as well, but for now, my next experiments will be to try a different ethernet (Cat 6a) cable with the current scenario, then to go back to using APCC.

Mike

--
Roland Christen
Astro-Physics


Re: Mount Status Not Updating in MaxIm DL Observatory Control Window

M Hambrick
 

Hi Roland

Yes I did. I did two separate slews to objects that I selected from the Catalog tab in the MaxIm DL Observatory Control window. I also parked and then un-parked the mount from MaxIm and in each case the mount status was being correctly picked up in MaxIm.

Did I understand your previous post correctly that this configuration (MaxIm connected directly to mount via AP-V2 Driver and NOT through APCC) is what you have been using when you experienced the same issue ? If so, then the only difference with what I have done is that I am using an ethernet cable, and I believe that you are using USB.

I am not sure that it will make any difference, but until now, I have been running these experiments without my cameras connected. Normally I will have two cameras connected to MaxIm as well as the mount. I plan to check this out as well, but for now, my next experiments will be to try a different ethernet (Cat 6a) cable with the current scenario, then to go back to using APCC.

Mike


Re: Sudden run-away during imaging run #APCC #Guiding

Roland Christen
 

If the mount stopped tracking the stars will run across your chip at 15 arc sec per second. Maybe the mount didn't run away, just stopped tracking due to any number of external commands.

Roland

-----Original Message-----
From: Endymion <john.creigh@...>
To: main@ap-gto.groups.io
Sent: Thu, Nov 11, 2021 3:49 pm
Subject: Re: [ap-gto] Sudden run-away during imaging run #APCC #Guiding

No model being used.  Encoders on.

--
Roland Christen
Astro-Physics


Re: Error in APCC pro reading RA encoder on Mach2 #appc #Mach2GTO

Endymion
 

Thanks Ray.  Will give it a try tonight.  


Re: Sudden run-away during imaging run #APCC #Guiding

Endymion
 

No model being used.  Encoders on.


Re: Mount Status Not Updating in MaxIm DL Observatory Control Window

Roland Christen
 

Did you slew with Maxim after doing part2?

Roland

-----Original Message-----
From: M Hambrick <mhambrick563@...>
To: main@ap-gto.groups.io
Sent: Thu, Nov 11, 2021 2:21 pm
Subject: Re: [ap-gto] Mount Status Not Updating in MaxIm DL Observatory Control Window

Part 2 of this experiment was actually to connect from MaxIm directly to the mount via the AP-V2 Driver. I got the same results as above - all were normal, and the mount status was the same in both MaxIm and in the AP-V2 Driver.

Part 3 will be to go back to my original setup with APCC


--
Roland Christen
Astro-Physics


Re: Mount Status Not Updating in MaxIm DL Observatory Control Window

M Hambrick
 

Part 2 of this experiment was actually to connect from MaxIm directly to the mount via the AP-V2 Driver. I got the same results as above - all were normal, and the mount status was the same in both MaxIm and in the AP-V2 Driver.

Part 3 will be to go back to my original setup with APCC


Re: Ethernet Connection to Mount in APCC

Peter Nagy
 

Mine works with direct connection to computer Ethernet port or through Ethernet switch. It shouldn't matter. I don't use APCC, just A-P V2 ASCOM mount driver. 

Peter


Re: Ethernet Connection to Mount in APCC

ap@CaptivePhotons.com
 

M Hambrick wrote:

 

  • In the troubleshooting discussions of why my mount status is not being updated in MaxIm DL after slew commands it was suggested that when connecting to the mount with an ethernet cable that it should be done through an ethernet hub (e.g. Netgear). 

Short answer: if it's working at all, you do not need a hub (switch).

 

Longer answer: A switch (so far as I know you can't buy a real hub any more) generally provides: (1) ability to have more than 2 devices share the same ethernet, (2) allow devices with different speeds, that cannot adjust, to communicate, (3) allow devices with different duplex that cannot adjust to communicate, (4) allow devices that cannot auto-sense transmit/receive to communicate, and (5) to provide power if a device requires Power over Ethernet.

 

Anything made in the last decade or so already handles (2) thru (4), mostly (5) is just for things like security cameras and very rarely anything you will run into with telescopes, so the only real need for a hub/switch is to allow more than 2 devices to talk to each other jointly.  And you would know if you had more than 2.

 

It's not like a powered USB hub where you might get a more solid connection, longer cable use, etc.  For the most part, for this sort of thing, ethernet either works, or doesn't, and when it does not it is almost always bad configuration.   

 

[Network engineers here can tell hours of stories of flakey wiring and incompatible standards that give lie to the above, but … this is about a simple computer to mount connection, but in those weird cases a switch didn't fix it anyway I bet!]


Re: #APCC and The SkyX #APCC

Thomas Giannaccini
 

Thank you everyone. This fixed the issue. I has selected Astro-Physics mount rather than ASCOM mount.

Best,

Tom

On Wed, Nov 10, 2021 at 11:49 AM Roland Christen via groups.io <chris1011=aol.com@groups.io> wrote:

It seems like The Sky X is that platform but I cannot get it to connect to the mount. 
SkyX connects to the mount via the ASCOM driver. You need to set SkyX up to connect to ASCOM mount. Make sure that the ASCOM driver is connected to an appropriate COM port. Use the computer's Device Manager to find the available com port and set up the ASCOM driver to connect to that com port.

Rolando

-----Original Message-----
From: Thomas Giannaccini <tgiann3@...>
To: main@ap-gto.groups.io
Sent: Wed, Nov 10, 2021 10:36 am
Subject: [ap-gto] #APCC and The SkyX

I’m new to APCC and have been working my way around the program. I did browse the manual. I see the section where I can enter coordinates to slew to a target in APCC and I am able to grossly find targets this way  but I would like a point and click solution with a high degree of refinement in target selection. My end goal is astrophotography so having integrated functionality is key. 

I tether my mount via Ethernet. I use a DSLR which connects to Backyard Nikon via usb. As soon as I get this sorted I’ll be adding a Lodestar Pro guide camera, QHY 163M camera, Starlight Xpress filter wheel, and eventually a  Nitecrawler focuser; all incrementally.

I have both The Sky X and Starry Night. I’m looking for the easiest way to get point an click slewing functionality in a platform which easily lends itself to AstroPhotography. It seems like The Sky X is that platform but I cannot get it to connect to the mount. 

Is there any type of workflow or tutorial which walks someone through this process? I thought I would ask here before calling in.

Thank you in advance,

Tom
--
CN: HasAnyoneSeenMyNeblua

--
Roland Christen
Astro-Physics


--
CN: HasAnyoneSeenMyNeblua


Ethernet Connection to Mount in APCC

M Hambrick
 

In the troubleshooting discussions of why my mount status is not being updated in MaxIm DL after slew commands it was suggested that when connecting to the mount with an ethernet cable that it should be done through an ethernet hub (e.g. Netgear). 

Is this necessary ?

Mike


Re: Oops! Powered-off mount while still connected

Mike Dodd
 

On 11/11/2021 11:47 AM, Roland Christen via groups.io wrote:

In your special case we don't know what was sent to the mount when you powered it back on. One would have to dig thru your ASCOM log file to figure out why the alt-az was off.
So the best way to recover is:
1. Loosen the clutches
2. Move the mount to Park5 and level it
3. Tighten the clutches
4. In the ASCOM driver, command the mount to unpark from Park5
5. In the ASCOM driver, command the mount to park to my normal Alt/Az 0/90 coordinates
6. At night, recal in SkyX

Thanks, Roland.

--- Mike


Re: Mount Status Not Updating in MaxIm DL Observatory Control Window

M Hambrick
 

Doug George at Diffraction Ltd had me run an experiment to connect to the mount through the ASCOM Device Hub (by way of the AP-V2 ASCOM Driver) instead of APCC, and then connecting MaxIm DL to the mount through the Device Hub. When this was all done I had three different screens showing the status of the mount; the ASCOM Device Hub, MaxIm DL, and the AP-V2 Driver.

I am not sure if I set everything up as Doug was asking me to do. It seems to me that whether I am using APCC or the ASCOM Device Hub, the communication from MaxIm to the mount is still by way of the AP-V2 Driver. The only difference is that the connection to the mount from the AP-V2 Driver was done using the IP address of the mount instead of using the APCC virtual port.

The object of this experiment was to make slewing commands to the mount and compare the mount status in all three after the command was executed. I did this and gave several GoTo commands as well as a park command to the mount from MaxIm. In each case, all three screens were in agreement as to the mount status after the slew was complete (see example below).

I think the next experiment is to go back to my original setup through APCC


Re: Oops! Powered-ff mount while still connected

Roland Christen
 


is the "park anywhere" feature valid only with the
hand box connected?
No, the park anywhere feature is correct regardless of what is used for initialization.
In your special case we don't know what was sent to the mount when you powered it back on. One would have to dig thru your ASCOM log file to figure out why the alt-az was off.

Rolando


-----Original Message-----
From: Mike Dodd <mike@...>
To: main@ap-gto.groups.io
Sent: Thu, Nov 11, 2021 9:32 am
Subject: Re: [ap-gto] Oops! Powered-ff mount while still connected

On 11/11/2021 10:04 AM, Dale Ghent wrote:
>
> Seems like quite an involved procedure you have there.

As I wrote, "I had occasion to check" the pointing accuracy. This is not
my normal startup procedure. I normally power-up everything, unpark, and
start an ACP imaging run. No sweat. But last night was special: I needed
to do the Park5 level, then a recal.

> As for your power-off issue, the mount's CP would come back up in an uninitialized state after being powered on.

Why? I thought AP mounts have a "park anywhere" feature where
powering-off the mount means it's parked, and it remembers where it was
when powered-on again. Did the fact that it was connected via ASCOM mess
up this feature? IOW, is the "park anywhere" feature valid only with the
hand box connected?

  Are you using the AP ASCOM driver in TSX, or are you using TXS'
bult-in AP mount driver?

I'm using the AP ASCOM driver Ray wrote. My first connection was with
the APJog utility. SkyX was the second connection.

> If you're using the AP ASCOM driver:
[...]
> For step 3, you can manually go out and loosen the clutches and rearrange the axes so that they're in a park 5 position, then do the park to current, followed by the unpark from 5... but any plate solver should do just fine if you've instead nudged things close enough to park 5, and the correction via the plate solve+sync operation will be exact.

Yep, that's what I did yesterday, Except (since I knew the mount was
pretty close to being correct), I Parked to Park5, loosened the clutches
to level the mount there, tightened the clutches, then did Unpark From
Last Parked. Everything was fine, and my initial slew to a star put it
only 8-10 arcmin from the center of the camera sensor. I tweaked to
exact center, then did a recal in SkyX. All other slews resulted in the
star being within 2-3 arcmin of center.

Per your procedure, I will again use a level to get the Park5 position
exactly right, instead of nudging close enough. :-)

What I don't understand is why/how the mount got so confused about its
position. Its site coordinates, clock, LST, and time zone are still
correct. But the RA/Dec and Alt/Az are way off.

If the Park5 procedure is the only way to recover, I can easily do that
tomorrow (rain later today).

--- Mike






--
Roland Christen
Astro-Physics


Re: Mach2 with CP five jiggling while tracking

Roland Christen
 

Yes, we are working on something like that for all our encoder mounts, including the 1100 and 1600 mounts.

Rolando

-----Original Message-----
From: Brent Boshart <bboshart@...>
To: main@ap-gto.groups.io
Sent: Thu, Nov 11, 2021 9:19 am
Subject: Re: [ap-gto] Mach2 with CP five jiggling while tracking

It might be nice if a future version of APCC had a slider control for encoder dampening (for each axis) as I frequently switch back and forth with a lighter and a heavier scope. 

--
Roland Christen
Astro-Physics


Re: Mach2 with CP five jiggling while tracking

Roland Christen
 

I sent you instructions in a separate e-mail that will fix this.

Rolando

-----Original Message-----
From: Allen Ruckle <aruckle@...>
To: main@ap-gto.groups.io
Sent: Thu, Nov 11, 2021 9:16 am
Subject: Re: [ap-gto] Mach2 with CP five jiggling while tracking

Roland,
Here is a bit of information, from just before I had the issue with the oscillation of the mount tracking, I rebalanced the mount to eliminate all imbalance.  However the oscillation did not start immediately, but about an hour and a half later.

aruckle 

--
Roland Christen
Astro-Physics


Re: Mach2 with CP five jiggling while tracking

Roland Christen
 

?



-----Original Message-----
From: Allen Ruckle <aruckle@...>
To: main@ap-gto.groups.io
Sent: Thu, Nov 11, 2021 12:07 am
Subject: Re: [ap-gto] Mach2 with CP five jiggling while tracking

Roland,  
      Here is an image with the results from accessing the mount with APCC to get the list of values requested,
hopefully you have previously solved the issue.

I have a C14 with HyperStar and Mirror less Canon RP. 
Thank you for your help.

PS  I used the mount and telescope tonight controlling everything with my ASIair Pro.

aruckle

--
Roland Christen
Astro-Physics


Re: Oops! Powered-ff mount while still connected

Mike Dodd
 

On 11/11/2021 10:04 AM, Dale Ghent wrote:
Seems like quite an involved procedure you have there.
As I wrote, "I had occasion to check" the pointing accuracy. This is not my normal startup procedure. I normally power-up everything, unpark, and start an ACP imaging run. No sweat. But last night was special: I needed to do the Park5 level, then a recal.

As for your power-off issue, the mount's CP would come back up in an uninitialized state after being powered on.
Why? I thought AP mounts have a "park anywhere" feature where powering-off the mount means it's parked, and it remembers where it was when powered-on again. Did the fact that it was connected via ASCOM mess up this feature? IOW, is the "park anywhere" feature valid only with the hand box connected?

Are you using the AP ASCOM driver in TSX, or are you using TXS' bult-in AP mount driver?

I'm using the AP ASCOM driver Ray wrote. My first connection was with the APJog utility. SkyX was the second connection.

If you're using the AP ASCOM driver:
[...]
For step 3, you can manually go out and loosen the clutches and rearrange the axes so that they're in a park 5 position, then do the park to current, followed by the unpark from 5... but any plate solver should do just fine if you've instead nudged things close enough to park 5, and the correction via the plate solve+sync operation will be exact.
Yep, that's what I did yesterday, Except (since I knew the mount was pretty close to being correct), I Parked to Park5, loosened the clutches to level the mount there, tightened the clutches, then did Unpark From Last Parked. Everything was fine, and my initial slew to a star put it only 8-10 arcmin from the center of the camera sensor. I tweaked to exact center, then did a recal in SkyX. All other slews resulted in the star being within 2-3 arcmin of center.

Per your procedure, I will again use a level to get the Park5 position exactly right, instead of nudging close enough. :-)

What I don't understand is why/how the mount got so confused about its position. Its site coordinates, clock, LST, and time zone are still correct. But the RA/Dec and Alt/Az are way off.

If the Park5 procedure is the only way to recover, I can easily do that tomorrow (rain later today).

--- Mike


Re: Mach2 with CP five jiggling while tracking

Brent Boshart
 

It might be nice if a future version of APCC had a slider control for encoder dampening (for each axis) as I frequently switch back and forth with a lighter and a heavier scope. 

4101 - 4120 of 86907