Re: New Astro-Folks
Roger Laureys
Warm welcome to the newcomers !!! Good to see AP is looking forward to the future
Roger
From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Karen Christen <karen@...>
Sent: Thursday, September 23, 2021 11:33 PM To: ap-gto@groups.io <ap-gto@groups.io>; ap-ug@groups.io <ap-ug@groups.io> Subject: [ap-gto] New Astro-Folks Hello Astro-Nuts,
As many of you know, we’ve been gradually growing our team to meet the high demand for our products. We’d like to introduce you to our two newest Astro-Folks, as of this week:
Eric is part of our production team. He’s working closely with Don and Vic in Finishing, and with Dave, our mount assembly master. Eric has been AP-adjacent for many years – he’s George’s son – and is already jumping in with both feet.
Amber has joined our office team. She’s quickly learning the myriad duties Daleen and Paige juggle every day and coordinating with our Shipping/Receiving guru, Amanda. Many of you will speak with or hear from Amber when calling or emailing the office.
Please join us in welcoming Amber and Eric to the Astro-Folks! Karen AP -- Karen Christen Astro-Physics
|
|
Re: APPM different with V1.9.0.9?
Ok I just noticed it only appears with " Require high accuracy slews".
It takes 15 sec per point. This is with V1.9.0.11. Some points work fine and its only some point that have the warning.
|
|
Re: APPM different with V1.9.0.9?
Rouz
I'll be testing it tonight.
Does anyone know where these slew warnings come from: 0392354 2021-09-23 00:06:10.941: Info, ProcessVPortCommand, RX from VPort 1: :APCC,45352,GZ#
0392355 2021-09-23 00:06:10.941: Info, ProcessVPortCommand, APCC Seq= 45352, CMD=GZ#
0392356 2021-09-23 00:06:10.941: Info, VPortCheckVPort1(COM3), (RX: GZ#), TX: APCC,13,45352,+343*30:59.7#
0392357 2021-09-23 00:06:10.942: Info, VPort1(COM3), RX: :APCC,45353,*SLEWUNSAFE,15.5769238888889,78#
0392358 2021-09-23 00:06:10.957: Info, ProcessVPortCommand, RX from VPort 1: :APCC,45353,*SLEWUNSAFE,15.5769238888889,78#
0392359 2021-09-23 00:06:10.957: Info, ProcessVPortCommand, APCC Seq= 45353, CMD=*SLEWUNSAFE,15.5769238888889,78#
0392360 2021-09-23 00:06:10.965: Debug, Command Thread, TX=':GH#'|RX='07:00:25.79#'
0392361 2021-09-23 00:06:10.965: Debug, Command Thread, TX (High Priority) = ':RT3#'
0392362 2021-09-23 00:06:10.965: Debug, Command Thread, TX (High Priority) = ':RT2#'
0392363 2021-09-23 00:06:10.966: Debug, Command Thread, TX = ':pS#'
0392364 2021-09-23 00:06:10.973: Info, VPortCheckVPort1(COM3), (RX: *SLEWUNSAFE,15.5769238888889,78#), TX:
|
|
Re: Computer not recognizing CP5 control box
#APCC
AaronW
Great tip, Luca. Thanks! I will take any tips I can get. I am going to need them :)
On Thu, Sep 23, 2021 at 5:38 PM Luca Marinelli <photo@...> wrote:
|
|
Re: New Astro-Folks
Jim Roberts
Warm greetings Amber and Eric!
------ Original Message ------
From: "Karen Christen" <karen@...>
Sent: 9/23/2021 3:33:34 PM
Subject: [ap-gto] New Astro-Folks
-- Karen Christen Astro-Physics
|
|
Re: Computer not recognizing CP5 control box
#APCC
Luca Marinelli
Hi Aaron,
I just connect to the mount via USB so I cannot help you with the WiFi problem. However, you do not want to connect power to the CP5 through the powerpole ports on the mount. Connect the AC adapter to the CP5 power cable and directly into the
CP5. The powerpole connectors on the mount are to bring 12V from a separate power supply to the telescope.
This will not solve your Wi-Fi problem but prevent snagging that power cable on the first slew.
—Luca
On Sep 23, 2021, at 7:28 PM, AaronW via groups.io <aaron.wilhelm@...> wrote:
|
|
Computer not recognizing CP5 control box
#APCC
AaronW
Brand new A-P customer here. I'm sure I'm doing something stupid. Any help is much appreciated.
Am installing / setting up the AP V2 driver / APCC Pro for the first time. Also plugging in my Mach2 and CP5 for the first time. Goal was to set CP5 to station mode and use it via my home's WiFi network. The manual gives clear instructions for how to do this, which are basically: 1) Go to CP5's homepage by first configuring for "Access Point Configuration" 2) Change the setting to use Station Mode in the advanced wireless settings there. So I did this. I turned on the mount/CP5. CP5's network appeared in my wireless networks after a few seconds. I connected my computer to this network using the default password provided by A-P. It worked. I then navigated to CP5's homepage and attempted to change the setting to use the CP5 in station mode. I selected my home network and entered the password. I then clicked CONNECT. It then said CONNECTING... All seemed well, but five minutes later it was still CONNECTING... So I closed the window, unplugged the mount/CP5, rebooted, and tried again. But now my computer does not find the CP5's network, and as a result, I am not able to navigate to CP5's homepage or proceed further in setting up APCC Pro. Instead, the computer recognizes a "hidden network" among my wireless networks. I attempted to connect to this network and it asked me for the network's name (SSID) and password. I provided the name of GTOCP5_Net_X, where X represents the numeric portion of my CP5's serial number without the leading zeros. I entered the password as well. I got a message saying "Cannot connect to this network." I've tried rebooting everything and doing it again. Same problem. I have A-P's AC adapter and anderson powerpoles going from my wall outlet into the mount anderson powerpoles on the RA rear plate, the CP5's power cable going from the CP5 to the mount anderson powerpoles in the DEC top plate, the RA/DEC cables going from the CP5 to the Mach2, and a USB cord going from the CP5 to my computer. The CP5's power indicator light is red, indicating proper power functioning. Any ideas? Best, Aaron
|
|
Re: [ap-ug] New Astro-Folks
Pete Lardizabal
Welcome to the Team!!! 😎 Pete
On Sep 23, 2021, at 5:33 PM, Karen Christen <karen@...> wrote:
|
|
Re: Trouble with MaxDome II slaving to APPM
Shane Ramotowski
No problem, Alan. Glad to have been some help!
toggle quoted messageShow quoted text
- Shane
On 9/23/2021 11:49 AM, Alan Erickson wrote:
Hi Shane,
|
|
Re: New Astro-Folks
Welcome aboard, One thing about this forum and this company is it we are all in a constant state of learning. Welcome from INdy
toggle quoted messageShow quoted text
TJF Mobile
On Sep 23, 2021, at 17:33, Karen Christen <karen@...> wrote:
|
|
Re: New Astro-Folks
Jeff B
Welcome and warmest regards! Jeff
On Thu, Sep 23, 2021 at 5:46 PM Eric Weiner <weinere@...> wrote: Welcome to an amazing team, but you already knew that!
|
|
Re: New Astro-Folks
Welcome to an amazing team, but you already knew that!
Regards, Eric & Amber -yes, that’s really our names too 🤪
|
|
New Astro-Folks
Hello Astro-Nuts,
As many of you know, we’ve been gradually growing our team to meet the high demand for our products. We’d like to introduce you to our two newest Astro-Folks, as of this week:
Eric is part of our production team. He’s working closely with Don and Vic in Finishing, and with Dave, our mount assembly master. Eric has been AP-adjacent for many years – he’s George’s son – and is already jumping in with both feet.
Amber has joined our office team. She’s quickly learning the myriad duties Daleen and Paige juggle every day and coordinating with our Shipping/Receiving guru, Amanda. Many of you will speak with or hear from Amber when calling or emailing the office.
Please join us in welcoming Amber and Eric to the Astro-Folks! Karen AP -- Karen Christen Astro-Physics
|
|
AP Version 2 error: Run-time error 91
Tom Blahovici
Hi
I have run into this three times lately. The AP driver is set to connect automatically as is the mount in APCC. However, the mount has not yet initialized. Seems to maybe stop if I automatically set the mount to initialize but I am not sure. The error is Run-time error 91. Object variable or With block variable not set. And then about 20 seconds later, APCC cannot create active-x object. Is this due to the mount not automatically initializing? All the latest software including APPM. Thanks, Tom
|
|
Re: #Keypad Park Positions: AP 1100 GTO with encoders
#Keypad
Thomas Giannaccini
Thank you Tom
--
CN: HasAnyoneSeenMyNeblua
|
|
Re: APCC Pro 1.9.0.11
R Botero
v1.9.0.11 working just fine with my 1600GTO. Solving happily under the full Moon.
Thank you Ray! Roberto
|
|
Re: APPM different with V1.9.0.9?
R Botero
New version working just fine!
Thank you Ray. Roberto
|
|
Re: APCC with SGP Pier Flip Failure
#APCC
Luca Marinelli
Hi Marcelo,
Be careful not to confuse the crossing of the Meridian line with Meridian limits set in APCC. Flip Offset is relative to the Meridian limit, which could be minutes or hours after the crossing the Meridian line. It's simply the RA position of the mount when the camera may get close to colliding with the pier at that declination. A positive Flip Offset is the time before reaching the Meridian limit when APCC will accept a command to flip the mount. When you check the West Limits checkbox and Send Limit with Offset to SGPro, the time that appears on the SGPro console when the flip will be initiated is the time displayed in the Time before limit reached box in APCC minus the Flip Offset. Again, depending on your setup, OTA, and target, this time could be hours after the Meridian crossing. A negative Flip Offset would put the mount in the danger zone of a pier crash. If you use SGP to take care of pier flip, you can still use the Meridian limit tab in APCC to ensure that in case of software malfunction your OTA will stop tracking before a pier collision. Again, if you map out your meridian limit, this can be a fail safe if the pier flip does not happen. In that case, simply do not check the Send Limit with Offset to SGPro and you SGP will continue managing the flip as you have done before. --Luca
|
|
Re: #Keypad Park Positions: AP 1100 GTO with encoders
#Keypad
Roland Christen
Hello Thomas,
I sent you an e-mail with instructions that should solve the limit issue for Park4.
Rolando
-----Original Message-----
From: Roland Christen via groups.io <chris1011@...> To: main@ap-gto.groups.io <main@ap-gto.groups.io> Cc: tgiann3@... <tgiann3@...>; howard@... <howard@...>; mikeh@... <mikeh@...> Sent: Thu, Sep 23, 2021 2:12 pm Subject: Re: [ap-gto] #Keypad Park Positions: AP 1100 GTO with encoders Hello Thomas,
It appears that you are reaching a Dec limit when trying to slew to Park4. So do not use that park position until we can clear that up. I will consult with our tech guys and get back to you.
Roland
-----Original Message-----
From: Thomas Giannaccini <tgiann3@...> To: main@ap-gto.groups.io Sent: Thu, Sep 23, 2021 2:00 pm Subject: Re: [ap-gto] #Keypad Park Positions: AP 1100 GTO with encoders Roland,
Thank you for the time you took to write that email. Yesterday, I was able to follow your instructions with some success but an issue still remains. I will outline my actions below.
I rough polar aligned the mount using RAPAs.
I updated the keypad firmware. I still do not have Park 5 in my list. Therefore, I used Park 4 instead, as will be described.
I double checked my time and location data. Please note I am currently in the mountain time zone. The time was precisely synched at the correct moment although the screen shot of the official time was taken a few seconds after the time synch was completed.
I began this process with Auto Connect "No" to see how the process would go and to allow for a comparison.
I started in Park 3 (a rough, eyeball approximation)
I slewed to Park 2; It was spot on. Level was verified with a carpenter's level,
I slewed to Park 4. It was off as shown below. The RA moved correctly The CW shaft was level and pointing West. When the Dec axis rotated it stopped at approximately the 10:30 position (just past 10 O'clock) and retreated to about 10 O'clock. This makes me think some sort of limit was hit?
I then adjusted the OTA position so that it was correctly in Park 4. this change in Dec axis rotation was made my loosening clutches and moving the OTA by hand. Level was verified with a carpenter's level.
I then slewed the mount back to Park 3. It was also not correct. It appeared to be off by the same amount that Park 4 was off. This is what Park 3 looked like:
Again I loosened the clutches, corrected the OTA position to Park 3. Then I slewed to Park 2. It was, again, spot on. Park 4 was again off by the same amount as before. So the issue here is that I can attain either Park 3 or Park 4 but not both. This was all with AutoConnect "No".
I then selected Auto Connect "Yes"
I powered down the mount. I plut the OTA in Park 3 by loosening the clutches. I powered up the mount and repeated the above process Going from Park 3 to Park 2 to Park 4. The behavior of the mount was identical to when AutoConnect was set to "No"
I then went to the polar alignment menu. Used 3 star alignment with a Reticle eyepiece in the main OTA. I slewed to 3 target stars. Polaris, Vega, and I can't remember the third. Each time any necessary adjustments were made only using keypad direction keys. I synched each star. No re-cal was performed. Just synch to each of those 3 stars.
Then I slewed to targets. I would describe the mount performance as nearly flawless at this point; certainly good enough for where I am in my learning curve.
If starting in Park 3, verifying Park 2 and then polar aligning via 3 stars will yield accurate results, this is easily within my grasp. I will continue to leave Auto Connect On and just restart from where I left off. I agree that this will be much easier. Thank you for the suggestion. I did not understand the details as you described them regarding a permanent mount.
Lastly, I placed a volt meter in line from the battery as you suggested. It is now semi-permanent. I did notice that the voltage dropped pretty quickly from over 13 volts to somewhere between 12.5 to 12.85 volts but was always above 12 volts.
Thank you for your help,
Tom
-- CN: HasAnyoneSeenMyNeblua -- Roland Christen Astro-Physics -- Roland Christen Astro-Physics
|
|
Re: #Keypad Park Positions: AP 1100 GTO with encoders
#Keypad
Roland Christen
Hello Thomas,
It appears that you are reaching a Dec limit when trying to slew to Park4. So do not use that park position until we can clear that up. I will consult with our tech guys and get back to you.
Roland
-----Original Message-----
From: Thomas Giannaccini <tgiann3@...> To: main@ap-gto.groups.io Sent: Thu, Sep 23, 2021 2:00 pm Subject: Re: [ap-gto] #Keypad Park Positions: AP 1100 GTO with encoders Roland,
Thank you for the time you took to write that email. Yesterday, I was able to follow your instructions with some success but an issue still remains. I will outline my actions below.
I rough polar aligned the mount using RAPAs.
I updated the keypad firmware. I still do not have Park 5 in my list. Therefore, I used Park 4 instead, as will be described.
I double checked my time and location data. Please note I am currently in the mountain time zone. The time was precisely synched at the correct moment although the screen shot of the official time was taken a few seconds after the time synch was completed.
I began this process with Auto Connect "No" to see how the process would go and to allow for a comparison.
I started in Park 3 (a rough, eyeball approximation)
I slewed to Park 2; It was spot on. Level was verified with a carpenter's level,
I slewed to Park 4. It was off as shown below. The RA moved correctly The CW shaft was level and pointing West. When the Dec axis rotated it stopped at approximately the 10:30 position (just past 10 O'clock) and retreated to about 10 O'clock. This makes me think some sort of limit was hit?
I then adjusted the OTA position so that it was correctly in Park 4. this change in Dec axis rotation was made my loosening clutches and moving the OTA by hand. Level was verified with a carpenter's level.
I then slewed the mount back to Park 3. It was also not correct. It appeared to be off by the same amount that Park 4 was off. This is what Park 3 looked like:
Again I loosened the clutches, corrected the OTA position to Park 3. Then I slewed to Park 2. It was, again, spot on. Park 4 was again off by the same amount as before. So the issue here is that I can attain either Park 3 or Park 4 but not both. This was all with AutoConnect "No".
I then selected Auto Connect "Yes"
I powered down the mount. I plut the OTA in Park 3 by loosening the clutches. I powered up the mount and repeated the above process Going from Park 3 to Park 2 to Park 4. The behavior of the mount was identical to when AutoConnect was set to "No"
I then went to the polar alignment menu. Used 3 star alignment with a Reticle eyepiece in the main OTA. I slewed to 3 target stars. Polaris, Vega, and I can't remember the third. Each time any necessary adjustments were made only using keypad direction keys. I synched each star. No re-cal was performed. Just synch to each of those 3 stars.
Then I slewed to targets. I would describe the mount performance as nearly flawless at this point; certainly good enough for where I am in my learning curve.
If starting in Park 3, verifying Park 2 and then polar aligning via 3 stars will yield accurate results, this is easily within my grasp. I will continue to leave Auto Connect On and just restart from where I left off. I agree that this will be much easier. Thank you for the suggestion. I did not understand the details as you described them regarding a permanent mount.
Lastly, I placed a volt meter in line from the battery as you suggested. It is now semi-permanent. I did notice that the voltage dropped pretty quickly from over 13 volts to somewhere between 12.5 to 12.85 volts but was always above 12 volts.
Thank you for your help,
Tom
-- CN: HasAnyoneSeenMyNeblua -- Roland Christen Astro-Physics
|
|