Date   

Re: Ethernet connection to V2 Driver

Ray Gralak
 

Did you edit that screenshot? There are a couple of checkboxes missing ("APCC Virtual Port" and "Use ASCOM Serial Object"). If you didn't, then you might want to try downloading and re-installing the AP V2 ASCOM driver again. Also, reboot your computer.

Also, make sure you have the latest ASCOM platform 6.1 SP1 installed and have enabled .Net 3.5 on your computer, and have the.NET Framework 4.8 installed. These steps are mentioned on the ASCOM website.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Michael Freeberg
Sent: Saturday, October 2, 2021 7:37 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] Ethernet connection to V2 Driver

I am just starting to setup my Mach 2 and I tried to connect to ethernet. I have a ethernet ip address in the
driver but it will not let me go back to the serial mode of connection. I have re-installed driver and it keeps
showing this ip address. it will not let me clear it out to go back and use a com port and this ip address does
not work either. I tried to reset driver to default parameters and keeps coming back to the ip address. How
can I reset the driver to use with a com port.

Thanks,

Mike


RA Mesh adjustment for 2104 model Mach 1 GTO

nicholas
 

I would like to know from other owners of AP mounts if you are fully loaded and you grip the counter shaft and use a small amount though distinctive force through the DEC axis will you  notice any discernable movement of the RA structure? I do, when it is fully loaded. It is a small a amount, maybe 1/8 MM or less. but that movement is discernable. 

 

Thank you!


Re: Ethernet connection to V2 Driver

Michael Freeberg
 

I can switch it in the window that you have above to a come port, and then I hit ok.  but when I open it up again it has the ip address in the window.  It will not let me clear the ip address.  I have uninstalled the driver and reinstalled the driver and it automatically comes up with the ip address.  I had everything working until I decided to try the ethernet connection and now it is all messed up where I cannot connect to driver.  

Mike


Re: Ethernet connection to V2 Driver

Mike Dodd
 

On 10/2/2021 10:37 PM, Michael Freeberg wrote:
I am just starting to setup my Mach 2 and I tried to connect to
ethernet. I have a ethernet ip address in the driver but it will not
let me go back to the serial mode of connection.
Have you tried the Setup Telescope utility? That's a stand-alone program that searches for the mount, and tells you what it finds. I've attached a screen shot of mine, and it has fields to set the COM port. My 1200 has no Ethernet port, so I don't know what provisions this has to choose between that and a serial port.

--- Mike


Ethernet connection to V2 Driver

Michael Freeberg
 

I am just  starting to setup my Mach 2 and I tried to connect to ethernet.  I have a ethernet ip address in the driver but it will not let me go back to the serial mode of connection.  I have re-installed driver and it keeps showing this ip address.  it will not let me clear it out to go back and use a com port and this ip address does not work either.  I tried to reset driver to default parameters and keeps coming back to the ip address.  How can I reset the driver to use with a com port.  

Thanks,  

Mike


Mach 2 Meshing

Bill Long
 

I am curious, how does the Mach 2 maintain its gear meshing on its own?


Re: WR 134

Steven Panish
 

Hi Carl,
Here is my image:

We had a (rare) clear night here (NH) so I was able to image for about 4 hours.  The moon was almost full and came up partway through the S2, and was there for all the R,G, B.  Oh well.  Not exactly like your marathon, but this is a widefield view with my FSQ106, which at f5 is pretty fast.  Definitely could use more time on O3 and S2, there isn't the detail in that gas cloud that you have by a long shot.   The captures were:
20 x 3min H2
30 x 3 min O3
30 x 3 min S2
30 x 1 min each R, G, B

Camera: ASI 294MM Pro, ZWO filters, ZWO OAG w/ ASI290 mini guider, PHD2
Mount: AP1200
Processing was entirely AstroPixelProcesser.  I've been using it for about 6 months and am no expert.  (My intent was to try that and then try PI, but I haven't made it to PI yet.)
The image data were combined as RGBHSO to keep somewhat natural  star colors.  

I'd like to see your latest version!

Steve

On Sun, Sep 26, 2021 at 10:45 PM carlburton2001 <cburton52@...> wrote:
Thanks Steven
I originally posted version A.  I'm now up to version K and learning more & more about Pixinsight.  This is a good one to practice with.

Good luck, looking forward to seeing your results. 

Carl


Re: Smart Meridian Flip with NINA #APCC

Joseph Beyer
 

Yes, it was NINA.  I'll dig deeper into the settings and see if there's anything that reverses the direction of movement after flip.  The good news is the standard flip worked as designed a couple nights ago and I didn't need to touch the rig all night.  The standard meridian flip doesn't take into consideration the APCC user defined custom meridian limits at each declination but if the flip is being handled accurately and automatically by the program it doesn't matter if the flip occurs at the meridian or slightly after.  I guess if it's not broken don't fix it...


Re: Smart Meridian Flip with NINA #APCC

Roland Christen
 


after the mount flipped it ended up pointing somewhere north of the target - plate solved - then slewed further away from the target.  
This is an indication that the reversing of the Dec direction was not set correctly in your plate solve program (NINA?). When you change sides in any German equatorial mount the Dec directions reverse and must be accounted for in automation software. The mount was never lost, it went to the place where it was sent. Your plate solve program was lost.

The same exact ting happens when you are guiding and flip sides. The guider program must reverse the guide corrections on the other side, otherwise the guide star will be lost after a few guide exposures.

Roland

-----Original Message-----
From: Joseph Beyer <jcbeyer2001@...>
To: main@ap-gto.groups.io
Sent: Sat, Oct 2, 2021 5:21 pm
Subject: Re: [ap-gto] Smart Meridian Flip with NINA #APCC

The smart meridian flip didn't work well for me last night.  I ran a 28 point APPM arc before imaging.  When I started the sequencer the telescope slewed directly to the target, centered (no movement was required as it was centered already) and focused.  Before NINA started imaging the meridian flip flow alert popped up indicating a meridian flip was scheduled in 35 minutes - which was wrong based on my position.  The program didn't start imaging but just seemed to be waiting for the flip.  I canceled the alert and NINA started imaging and the interval east of the meridian was uneventful.  The flip came at the correct time indicated by the sequencer, not the 35 minutes initially indicated, but after the mount flipped it ended up pointing somewhere north of the target - plate solved - then slewed further away from the target.  I attempted to repoint the mount using CdC and it also went the wrong direction.  Shortly after APCC crashed and after restarting the virtual ports I use 20 and 21 had been replaced by 8 and 9.  Tried reslewing to the target and it was clear the mount was lost.  Manually moved it to PARK 3 and closed it up for the night.

The standard meridian flip worked great several days earlier.  The smart meridian flip not so much.

I can provide logs if anyone is interested.  I'll check in with the NINA forum as well.

Joe

--
Roland Christen
Astro-Physics


Re: Smart Meridian Flip with NINA #APCC

Joseph Beyer
 

The smart meridian flip didn't work well for me last night.  I ran a 28 point APPM arc before imaging.  When I started the sequencer the telescope slewed directly to the target, centered (no movement was required as it was centered already) and focused.  Before NINA started imaging the meridian flip flow alert popped up indicating a meridian flip was scheduled in 35 minutes - which was wrong based on my position.  The program didn't start imaging but just seemed to be waiting for the flip.  I canceled the alert and NINA started imaging and the interval east of the meridian was uneventful.  The flip came at the correct time indicated by the sequencer, not the 35 minutes initially indicated, but after the mount flipped it ended up pointing somewhere north of the target - plate solved - then slewed further away from the target.  I attempted to repoint the mount using CdC and it also went the wrong direction.  Shortly after APCC crashed and after restarting the virtual ports I use 20 and 21 had been replaced by 8 and 9.  Tried reslewing to the target and it was clear the mount was lost.  Manually moved it to PARK 3 and closed it up for the night.

The standard meridian flip worked great several days earlier.  The smart meridian flip not so much.

I can provide logs if anyone is interested.  I'll check in with the NINA forum as well.

Joe


Re: Off Topic-NUC Computer

Sébastien Doré
 

Derek,

From what I see on PassMark, that CPU would be about 26% slower, which doesn't tell the hole story of course but I wouldn't worry about that that much. It is still a quad-core which in my opinion will result in very reasonable performance with the upgraded 8Gb RAM. I use RDP with no problem with mine, I suppose VNC would be similar...

Sébastien


Re: Off Topic-NUC Computer

Derek S
 

Sebastien,

I have this one:

https://www.amazon.com/gp/product/B0788DJQR9/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

I added 4 GB ram.  I think the N4200 is 30-40% slower than the newer processor.  I used vnc to control the computer.

Derek


Re: IP Address of mount

Thomas Giannaccini
 

This is very helpful. Thank you

Tom

On Sat, Oct 2, 2021 at 12:09 PM W Hilmo <y.groups@...> wrote:
For what it's worth, I have two AP mounts, but only one imaging computer.  I also have two different wireless networks, depending on whether I am running at home or in the field (different routers, with different properties).  I connect via Ethernet.

My original plan was to use a static IP address for each mount, but that got to be a hassle, since I could end up with one of 4 different addresses, depending on which mount and router I am using.

So I configured both mounts to be DHCP clients.  I have APCC set up to not connect automatically.  When I start APCC, I use the button that finds the mount, and then connect using IP address (which is a checkbox on the "find mount" screen).

This has been 100% reliable.

If you have a simpler setup than I do, then I would still recommend using DHCP.  I would also configure my router so that the mount gets a permanently reserved lease.  This will cause the mount to get the same IP address each time, so it's as convenient as a static IP address.  If you do that, then you can skip the "find mount" step after the first connection.  If it ever fails to find the mount, you can always try the "find mount" feature again.

I also connect to the mount from my phone via WiFi periodically.  In that case, I have the WiFi on each mount configured to be a hotspot.  I connect directly to the mount's WiFi.  In that case, the IP address of the mount for a wireless connection is the same as the default gateway on the wireless network.

I have never joined the mount directly to any of my wireless networks, and I have never connected via serial or USB, so I can't offer any suggestions on a reliable workflow.  I do assume that the "find mount" steps would work fine if the mount were joined to my main WiFi, and I expect that both serial and USB connections would be pretty seamless (except that you may need to verify the COM port that Windows assigns).

On 10/2/21 9:10 AM, Thomas Giannaccini wrote:
Thank you Christopher; I appreciate the help.

Tom

On Sat, Oct 2, 2021 at 10:00 AM Christopher Erickson <christopher.k.erickson@...> wrote:
Also, the WiFi port and Ethernet port are different networks with different IP addresses. And the CP4 does not route IP traffic between the ports. So if you are connected via Ethernet, for example, the WiFi IP address will be unreachable via the Ethernet network, unless your WiFi and Ethernet networks are bridged at some other point in your network(s).


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

On Sat, Oct 2, 2021, 5:49 PM ap@... <ap@...> wrote:

Thomas Giannaccini wrote:

 

  • I was under the impression that the IP address of the mount is static. Several weeks ago I was on the phone with AP and as part of that call my IP address for the mount was determined. I took a picture of it after I typed it in so that I would have it. Now I am trying to access the mount via ASCOM and ASCOM cannot find the mount. I inquired on Cloudy Nights as to what the issue could be (at the time I was using RDP to a headless PC at the mount) and thought that RDP might be the issue. But When I try to ping the mount's IP address from the command prompt it times out (on 2 different computers going pier to pier via ethernet cable directly to the mount.) This is odd because ASCOM worked before when connected pier to pier. So I'm starting to wonder if I have the wrong IP address? I'm typing it with the picture right in front of me.

 

The controller follows networking standards, which means the address can be assigned either via a static address (human set), a DHCP (IP address) server (home routers sometime do that), or via Windows stupid idiotic inane random address generator.  It all depends on details of your setup, and what you did the first time you used it.

 

So yes, it can change.

 

There’s a rather lengthy discussion on the subject in the “Astro-Physics GTO Servo Drive System Model GTOCP4 Operating Instructions” manual starting on page 12 and page 56 (at least in my version).  My recommendation is use ethernet (not wifi) and the first time you use it enter a static IP address and it will stop changing.

 

 


--
CN: HasAnyoneSeenMyNeblua


--
CN: HasAnyoneSeenMyNeblua


Re: Off Topic-NUC Computer

Sébastien Doré
 

Hi Derek,

I don't know what you have under the hood of your minix, but with mine (J50C-4 Max: 8Gb DDR4 RAM, Intel Pentium Silver J5005) I have absolutely no problem runnning APPM with NINA/ASTAP with a bunch of other DSO imaging softwares simultaneously. For comparison, I've benchmarked it side-by-side with my trusty old HP Probook 450 G3 (12GB DDR3 Ram, Intel i5-6200U dual-core clocked at 2.4GHz) which was my main imaging PC before the J50C and it is literally on par performance-wise (except for the GPU part as stated in my previous message).

Sébastien


Re: PEMPro connection

legendtrail@...
 

Thanks Ray, I can wait a couple days no problem.

Roland, I wanted to try using the polar alignment routine.


Re: PEMPro connection

Ray Gralak
 

Ray - I can try next session - may be a few days to a week away.
I was able to reproduce the issue, and there is a workaround. If you would like to try the workaround, let me know. Otherwise, I'll publish a new build of PEMPro within the next couple of days to fix this issue.

-Ray


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of legendtrail via groups.io
Sent: Saturday, October 2, 2021 10:22 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] PEMPro connection

Ray - I can try next session - may be a few days to a week away.

Marj - Yes, received mount in August.


Re: IP Address of mount

W Hilmo
 

For what it's worth, I have two AP mounts, but only one imaging computer.  I also have two different wireless networks, depending on whether I am running at home or in the field (different routers, with different properties).  I connect via Ethernet.

My original plan was to use a static IP address for each mount, but that got to be a hassle, since I could end up with one of 4 different addresses, depending on which mount and router I am using.

So I configured both mounts to be DHCP clients.  I have APCC set up to not connect automatically.  When I start APCC, I use the button that finds the mount, and then connect using IP address (which is a checkbox on the "find mount" screen).

This has been 100% reliable.

If you have a simpler setup than I do, then I would still recommend using DHCP.  I would also configure my router so that the mount gets a permanently reserved lease.  This will cause the mount to get the same IP address each time, so it's as convenient as a static IP address.  If you do that, then you can skip the "find mount" step after the first connection.  If it ever fails to find the mount, you can always try the "find mount" feature again.

I also connect to the mount from my phone via WiFi periodically.  In that case, I have the WiFi on each mount configured to be a hotspot.  I connect directly to the mount's WiFi.  In that case, the IP address of the mount for a wireless connection is the same as the default gateway on the wireless network.

I have never joined the mount directly to any of my wireless networks, and I have never connected via serial or USB, so I can't offer any suggestions on a reliable workflow.  I do assume that the "find mount" steps would work fine if the mount were joined to my main WiFi, and I expect that both serial and USB connections would be pretty seamless (except that you may need to verify the COM port that Windows assigns).

On 10/2/21 9:10 AM, Thomas Giannaccini wrote:
Thank you Christopher; I appreciate the help.

Tom

On Sat, Oct 2, 2021 at 10:00 AM Christopher Erickson <christopher.k.erickson@...> wrote:
Also, the WiFi port and Ethernet port are different networks with different IP addresses. And the CP4 does not route IP traffic between the ports. So if you are connected via Ethernet, for example, the WiFi IP address will be unreachable via the Ethernet network, unless your WiFi and Ethernet networks are bridged at some other point in your network(s).


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

On Sat, Oct 2, 2021, 5:49 PM ap@... <ap@...> wrote:

Thomas Giannaccini wrote:

 

  • I was under the impression that the IP address of the mount is static. Several weeks ago I was on the phone with AP and as part of that call my IP address for the mount was determined. I took a picture of it after I typed it in so that I would have it. Now I am trying to access the mount via ASCOM and ASCOM cannot find the mount. I inquired on Cloudy Nights as to what the issue could be (at the time I was using RDP to a headless PC at the mount) and thought that RDP might be the issue. But When I try to ping the mount's IP address from the command prompt it times out (on 2 different computers going pier to pier via ethernet cable directly to the mount.) This is odd because ASCOM worked before when connected pier to pier. So I'm starting to wonder if I have the wrong IP address? I'm typing it with the picture right in front of me.

 

The controller follows networking standards, which means the address can be assigned either via a static address (human set), a DHCP (IP address) server (home routers sometime do that), or via Windows stupid idiotic inane random address generator.  It all depends on details of your setup, and what you did the first time you used it.

 

So yes, it can change.

 

There’s a rather lengthy discussion on the subject in the “Astro-Physics GTO Servo Drive System Model GTOCP4 Operating Instructions” manual starting on page 12 and page 56 (at least in my version).  My recommendation is use ethernet (not wifi) and the first time you use it enter a static IP address and it will stop changing.

 

 


--
CN: HasAnyoneSeenMyNeblua


Re: PEMPro connection

Roland Christen
 

An AE mount doesn't use or need a PE curve.

Roland

-----Original Message-----
From: legendtrail via groups.io <legendtrail@...>
To: main@ap-gto.groups.io
Sent: Sat, Oct 2, 2021 11:55 am
Subject: Re: [ap-gto] PEMPro connection

I'm sorry, apparently I'm not making myself understood. This is appearing after clicking connect in PEMPro v3. The mount is an 1100GTOAE with a GTOCP4 controller. I had already read through the checklist you reference, and had done all of those things. I start the mount, start APCC and connect, then click on PEMPro from the setup screen. PEMPro starts. I click on connect scope, then get the "Unable to verify mount" message under the PEMPro v3 banner. I'm asking what set of conditions cause this message to appear. Is there some other connection I need to make? Is there another install step I've missed? Is there a security rule in Windows 10 causing a problem?  ????

--
Roland Christen
Astro-Physics


Re: PEMPro connection

legendtrail@...
 

Ray - I can try next session - may be a few days to a week away.

Marj - Yes, received mount in August.


Re: Rookie Question

Tom Zepf
 
Edited

I went with an approach similar to what's been posted here, but put the Pegasus Powerbox Advance forward on the saddle as all my scopes are back heavy and I have to move have the dovetail to the forward-most position. 3 foot cables just reach comfortably to the camera at the back. This works well on my DOVEDV10 as well for my smaller telescopes. I used the Pegasus Astro bracket PEG-BRACK-PPBA.

Clear skies,

     Tom

5081 - 5100 of 86806