|
Re: Keypad 4.19.5 unsuccessful upload
I will try to reproduce your issue, but I have 2 keypads that have been loaded with the Java loader several times during recent testing.
You can stay with 4.19.3 if you don’t mind the following:
I will let you know when I know more about your loader issue.
The Java loader produces a log file that may provide me with some information. It will be in the same folder as the program.
Mag. 7 or Better Skies!
Howard Hedlund Astro-Physics, Inc. AP Phone: 815-282-1513 Direct Phone: 815-315-7015 Please include this e-mail with your response.
P Consider the environment before printing this e-mail.
From: main@ap-gto.groups.io <main@ap-gto.groups.io>
On Behalf Of Peter Nagy
I was able to successfully install Keypad version 4.19.3. Whew!!!!
|
|
|
|
Re: Keypad 4.19.5 unsuccessful upload
Peter Nagy
Howard,
I went ahead and re-installed Keypad version 4.19.5 and it was not successful. I successfully reverted back to Keypad version 4.19.3. It could be the following reasons: 1) I didn't follow your installation procedure correctly. 2) The installation documentation procedure may be incorrect. 3) The Keypad version 4.19.5 firmware at your web site may be corrupted. 4) There may be issues with Keypad version 4.19.5 firmware. I am going to hold off installing Keypad version 4.19.5 until others say don't have issues installing. Anyone else successfully installed Keypad version 4.19.5? I suggest you to download Keypad version 4.19.5 from your web site to make sure the files are not corrupted and re-flash your Keypad. Peter
|
|
|
|
Re: #WiFi SkySafari Pro won't connect to GTOCP4
#WiFi
Sébastien Doré
Not 100% sure about this but IIRC, the last byte (digit) of the mount's IP address when using the access-point mode should correspond to your CP's serial number, (if you have not changed the default value).
So the IP you should type in skysafari is 172.31.0.serial_number_of_the_CP
The 172.31.0.1 address is the access-point itself (not the mount). It is the network gateway you connect through to communicate with the mount (even if it resides inside the CP too, hardwarely-speaking).
Sébastien
De : main@ap-gto.groups.io <main@ap-gto.groups.io> de la part de Thomas Giannaccini <tgiann3@...>
Envoyé : 2 novembre 2021 15:46 À : main@ap-gto.groups.io <main@ap-gto.groups.io> Objet : Re: [ap-gto] #WiFi SkySafari Pro won't connect to GTOCP4 I like using the IP address with my ethernet and yours do not seem to match. I'm not sure if this works the same way as with ethernet but I would try that first
Best,
Tom
On Tue, Nov 2, 2021 at 3:29 PM Brian Valente <bvalente@...> wrote:
-- CN: HasAnyoneSeenMyNeblua
|
|
|
|
Re: APPM and ASTAP
#APCC
Sébastien Doré
Hi Bryan,
You have already figured the following out but for the sake of other people who wouldn't have yet the FOV for ASTAP is the field height (in degrees) of the image you're trying to solve. So it is related to your "vertical" sensor size (in pixels) and your image scale (arc-sec per pixel), through the following formula:
FOV_height = vertical_height * image_scale / 3600
and can be set directly in ASTAP in the Stack Menu -> Alignment Tab. (That answers in part your above question)
For example, my ASI183MC Pro sensor which has a 5496 x 3672 pixels and used with a 70mm refractor at 338 mm FL. Image scale for this setup is 1.4646 arc-sec/pixel so FOV height to set in ASTAP will be :
3672 px x 1.4646 arc-sec/px / 3600 arc-sec/deg = about 1.49 degree.
That's the value ASTAP needs to work the most efficiently, all others being equal.
With the new Beta version of APCC (1.9.1.3), this FOV is automatically calculated from the FITS header information, as you said. And it is used by APPM when launching the ASTAP platesolving process if you have checked the new "Use FITS header for RA, Dec and Image scale" checkbox. So the need for you to provide the FOV manually to ASTAP is now gone as APPM correctly does the work for you. That assumes your imaging program includes all the required information in the FITS header in the first place (which NINA 1.11 does), of course.
Prior to APCC v1.9.1.1, APPM forced the FOV setting to be determined by ASTAP through trial and error (i.e. not using the manually user-supplied value as seen above) which added some unnecessary time to solving each point of a mapping run. So it is a great bug-fix in the latest version in this regard, especially for those using somewhat old/slow imaging PC by today's standard.
Hope that helps understand it a bit further.
Sébastien
|
|
|
|
Re: #WiFi SkySafari Pro won't connect to GTOCP4
#WiFi
Thomas Giannaccini
I like using the IP address with my ethernet and yours do not seem to match. I'm not sure if this works the same way as with ethernet but I would try that first Best, Tom
On Tue, Nov 2, 2021 at 3:29 PM Brian Valente <bvalente@...> wrote:
--
CN: HasAnyoneSeenMyNeblua
|
|
|
|
Re: #WiFi SkySafari Pro won't connect to GTOCP4
#WiFi
is that the correct port number? mine is set to 4030 but that is for a different mount.
On Tue, Nov 2, 2021 at 12:21 PM Tom Zepf <tjzcos@...> wrote: I'm trying to get SkySafari on iOS (and MacOS) to work with the builtin wifi on a AP1100GTO. I've got the network configured to connect to the GTOCP4 wifi, and verified the connection by visiting http://172.31.0.1 and seeing the configuration pages. Network setting look like: --
|
|
|
|
#WiFi SkySafari Pro won't connect to GTOCP4
#WiFi
I'm trying to get SkySafari on iOS (and MacOS) to work with the builtin wifi on a AP1100GTO. I've got the network configured to connect to the GTOCP4 wifi, and verified the connection by visiting http://172.31.0.1 and seeing the configuration pages. Network setting look like:
 SkySafari settings look like:  But I get an error:  Is there something wrong with this configuration? Thanks, Tom
|
|
|
|
Re: Keypad 4.19.5 unsuccessful upload
Peter Nagy
I was able to successfully install Keypad version 4.19.3. Whew!!!!
Shall I try installing Keypad version 4.19.5 again or should I wait? Are you in the process of investigating that there may be an issue with installing Keypad version 4.19.5? Thanks, Peter
|
|
|
|
Re: Keypad 4.19.5 unsuccessful upload
Peter Nagy
OK. I'll re-install 4.9.13.
Peter
|
|
|
|
Re: Keypad 4.19.5 unsuccessful upload
AP GTO Keypad firmware v.4.19.3 is loaded using a Windows program that you install. It shouldn’t care whether the GTOCP4’s firmware is VCP4-P01-xx or VCP4-P02-xx. The Java loader used with v.4.19.5 is for CP4s with P02-xx and later.
Mag. 7 or Better Skies!
Howard Hedlund Astro-Physics, Inc. AP Phone: 815-282-1513 Direct Phone: 815-315-7015 Please include this e-mail with your response.
P Consider the environment before printing this e-mail.
From: main@ap-gto.groups.io <main@ap-gto.groups.io>
On Behalf Of Peter Nagy
Should I install CP4-P01-14 in CP4 so I can re-install keypad 4.19.3? If successful, I then can re-install VCPx-P02-08 in CP4?
|
|
|
|
Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"
Erkaslan Aygen
Hi Ray and AP community,
As promised, I had the chance to test the new version. It seems to work like a charm ! I did only a couple of slew / center / syncs and I haven't received a sigle warning / error messages. In case something goes wrong, I will let you know anyway. In the meantime, thanks again for your 5 stars support ! Best regards, Aygen
|
|
|
|
Re: Electro-Static Discharge Protection for Older Mounts
Jeff B
Perhaps Wes but I would not recommend it. But I DO recommend the boards be installed by AP if your mount can take them. My Parallax 250 Observatory mount uses the AP servo system. It's a good 12 to 15 years old, did not have the boards at the time of make and both RA and DEC motor/encoders eventually went belly up from static (with the last one about 6 months ago and they are heavy duty servos too). When the first one went out a few years ago, I got two replacement assemblies from Maxim, sent them to AP and they installed the boards for, at the time, around $200 each. It's' interesting to me that with the new motor/encoder/anti-static/surge boards, the mount seems slightly more accurate in slewing and tracking....go figure. I also have a freshly overhauled Mathis MI-500 (the BEAST) and it too has the AP servo system but without the static/surge boards as well as two AP1200s, and an AP900. The APs so far have been rather bulletproof and the Mathis has fresh motors/encoders (new old stock from Mathis), but my experiences with the Parallax 250 and its uncommanded slewing when the motors/encoders failed, gives me a bit of pause for my other mounts. Jeff
On Tue, Nov 2, 2021 at 11:26 AM Scott Cooke <TSCOOKE64@...> wrote:
|
|
|
|
Re: Electro-Static Discharge Protection for Older Mounts
Scott Cooke
Wes, I don't know. I asked that question because I wanted to do it myself for my 400 mount. Unfortunately, they don't have an ESD board for this mount so I never found out. Thanks, Scott
On Tue, Nov 2, 2021 at 8:05 AM Wes Atchison via groups.io <wa5tku=atchisonlocal.com@groups.io> wrote: Is it possible for the board to be installed without sending the motor assemblies back to AP? How much does this addition cost?
|
|
|
|
Re: APPM and ASTAP
#APCC
Bryan,
Regarding ASTAP plate solves, you can look at the APPM logs to see the command line arguments passed to APPM. If you set all of ASTAP values to zero in APPM’s plate solve tab and check the box to use the FITS header, then APPM will pass just the filename to APPM. If an image is not solving it’s likely a setting in ASTAP needs to be tweaked. APPM cannot predetermine which settings will best work with ASTAP, which is why it exposes controls to tweak command line parameters.
Regarding the 70 Mpix image not loading, I assume you are using the camera’s ASCOM Camera driver? There are some VERY inefficient ASCOM drivers that require over 1 GB of ram for a 40 mpixel image. The maximum memory for APPM is 1GB so the image fails to load. If the manufacturers would create efficient ASCOM camera drivers then APPM would not have a problem. Binning or using a subframe will reduce memory size below 1GB and thus APPM can use the image.
Lastly, FOV is something ASTAP needs to reduce plate solve time. With the default values ASTAP will use the FITS header to calculate FOV.
-Ray
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Worsel via groups.io
Sent: Tuesday, November 2, 2021 7:41 AM To: main@ap-gto.groups.io Subject: Re: [ap-gto] APPM and ASTAP #APCC
Ray
Thanks for the new BETA 1.9.1.3. A few comments follow. Your insight IS appreciated. I hope these are helpful to others. · Program installed without issue. (1100 GT non-AE) · Following using o FOV = 135’ x 90’ o Image scale = 1.1”/pxl o 70 MP fits file. No need to bin. APPM would not read the original file. Cropped to 1/4x1/4. Cropped image also downloads faster and solves fast. No brainer there. · Initially, astrometry.net (local install) would solve, but ASTAP and, hence, APPM would not. · Took significant fiddling with gain, exposure, etc to come up with images that will solve. Some images that would solve in ASTAP directly would not solve in APPM. · Finally got everything lined out sufficiently to build a 227 pt model (Large Map default) with only 3 Solve Fails and those point were on the horizon. Using this model, I was able to capture up to 15 minute subs un-guided. I did not test beyond 15 minutes. · I also solved images from following train o FOV = 27 x 18’ o Image scale = 0.4’/pxl o 22 MP fits. Uncropped, no need to bin. · Tips (at least these helped me) o Getting the image close is key (Ray says this in the documentation as well.) o However, setting Image scale tolerance to 50% gave me more latitude. May increase solve time, but only by small amounts. o Solve button will work when Blind Solve does not on the same image. o The initial RA and Dec only needs to be accurate to 1 hour and 1 degree, e.g. 3 50 will solve an image with center at § 3h 23m 15s § 49d 43m 36s One comment. People mention ‘setting’ the FOV. As near as I can determine, there is no place to set the FOV directly. APPM can calculate FOV from the sensor parameters, which is supplied from FITS header, and image scale, which is set in APPM and sent to FITS header. Is this correct?
Bryan
|
|
|
|
Re: APPM and ASTAP
#APCC
Worsel
Ray
Thanks for the new BETA 1.9.1.3. A few comments follow. Your insight IS appreciated. I hope these are helpful to others. · Program installed without issue. (1100 GT non-AE) · Following using o FOV = 135’ x 90’ o Image scale = 1.1”/pxl o 70 MP fits file. No need to bin. APPM would not read the original file. Cropped to 1/4x1/4. Cropped image also downloads faster and solves fast. No brainer there. · Initially, astrometry.net (local install) would solve, but ASTAP and, hence, APPM would not. · Took significant fiddling with gain, exposure, etc to come up with images that will solve. Some images that would solve in ASTAP directly would not solve in APPM. · Finally got everything lined out sufficiently to build a 227 pt model (Large Map default) with only 3 Solve Fails and those point were on the horizon. Using this model, I was able to capture up to 15 minute subs un-guided. I did not test beyond 15 minutes. · I also solved images from following train o FOV = 27 x 18’ o Image scale = 0.4’/pxl o 22 MP fits. Uncropped, no need to bin. · Tips (at least these helped me) o Getting the image close is key (Ray says this in the documentation as well.) o However, setting Image scale tolerance to 50% gave me more latitude. May increase solve time, but only by small amounts. o Solve button will work when Blind Solve does not on the same image. o The initial RA and Dec only needs to be accurate to 1 hour and 1 degree, e.g. 3 50 will solve an image with center at § 3h 23m 15s § 49d 43m 36s One comment. People mention ‘setting’ the FOV. As near as I can determine, there is no place to set the FOV directly. APPM can calculate FOV from the sensor parameters, which is supplied from FITS header, and image scale, which is set in APPM and sent to FITS header. Is this correct?
Bryan
|
|
|
|
Re: Keypad 4.19.5 unsuccessful upload
Peter Nagy
Should I install CP4-P01-14 in CP4 so I can re-install keypad 4.19.3? If successful, I then can re-install VCPx-P02-08 in CP4?
Peter
|
|
|
|
Re: Keypad 4.19.5 unsuccessful upload
Peter Nagy
|
|
|
|
Re: TPoint vs. APPM -- Translation Possible?
Hi Marty,
So the question: is there any way to translate the TPoint results into an APPM model? I suspect not, but hadUnfortunately, there is not a TPoint translator nor a way to manually select stars at this time. What is the field of view of your setup and pixel dimensions of the sensor? -Ray
|
|
|
|
Re: Keypad 4.19.5 unsuccessful upload
fernandorivera3
Version 4.19.5 keypad firmware is available for download? Is this a recent development or did this happen many moons ago? I thought 4.19.3 was the current version- guess I'm wrong about this.
Fernando
|
|
|
|
Re: TPoint vs. APPM -- Translation Possible?
George
T-point cannot provide dual-axis tracking with AP mounts…only APCC can do that.
Regards,
George
George Whitney Astro-Physics, Inc. Phone: 815-222-6538 (direct line) Phone: 815-282-1513 (office) Email: george@...
From: main@ap-gto.groups.io <main@ap-gto.groups.io>
On Behalf Of mjb87 via groups.io
I use APPM with great results on my Mach2 with the 130mm refractor. I have been unable, after a year of effort, to build a APPM model on my 1100 with the 300mm f/15 Cassegrain. The FOV and the pixel size is just too small to get plate-solving
to work reliably. Yes, I've tried focal reducers, different databases, different cameras, etc., etc. When I do get solutions they don't make sense,e.g., 7 degree orthogonality difference whereas ConeSharp says it is about 10 arc-minutes.
|
|
|
