Re: Keypad 4.19.5 unsuccessful upload
Peter Nagy
|
|
Re: TPoint vs. APPM -- Translation Possible?
Ray Gralak
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
Sent: Tuesday, November 2, 2021 8:28 AM To: main@ap-gto.groups.io Subject: [ap-gto] TPoint vs. APPM -- Translation Possible?
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.
|
|
TPoint vs. APPM -- Translation Possible?
mjb87@...
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.
I can easily build a TPoint model using TSX for that setup by visually aligning the stars selected. Took me 40 minutes last night to build a 24-point model. However, that locks me into using TSX, with the tracking/pointing in APCC turned off. There are time I may want to taker TSX out of the loop. Note: I am looking primarily for pointing accuracy as opposed to tracking accuracy with this setup since I do not do long-duration unguided imaging. It is mainly planetary and visual work. So the question: is there any way to translate the TPoint results into an APPM model? I suspect not, but had to ask. Alternatively, is there any way to to manual star alignments in APPM instead of using plate-solving? Thanks, Marty
|
|
Re: Electro-Static Discharge Protection for Older Mounts
Wes Atchison
Is it possible for the board to be installed without sending the motor assemblies back to AP? How much does this addition cost?
Wes WA5TKU
|
|
Re: Keypad 4.19.5 unsuccessful upload
Peter Nagy
It's not possible for me to call with a telephone because I am deaf. I cannot use TTY because I don't have landline. TTY is not possible with cell phone.
It appears that the Keypad Loader is working up to a point and hangs at 20% completion. Is it possible my Keypad does not have enough memory space? Like I said earlier, the serial number is 3771GTO. Would it be possible to communicate with me using e-mail? Can you send me further instructions on how to get my Keypad working again? Or would it be better if I ship the Keypad to you? The Keypad is 8 years old and it's probably due for a battery replacement. My e-mail address is: pnagy at sbcglobal dot net Peter
|
|
Peter,
I agree and made a note to do so.
Clear Skies, Marj Christen Astro-Physics 11250 Forest Hills Road Machesney Park, IL 61115 Phone: 815-282-1513 www.astro-physics.com
From: main@ap-gto.groups.io <main@ap-gto.groups.io>
On Behalf Of Peter Nagy
Sent: Monday, November 1, 2021 5:12 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] Mach2 CP5 Orthogonality Model #Mach2GTO #Keypad
This should be mentioned in A-P manuals either in Mach2 or Keypad documentations. This is useful information.
|
|
Re: Keypad 4.19.5 unsuccessful upload
Peter,
Give Howard a call on Tuesday for assistance.
Clear Skies, Marj Christen Astro-Physics 11250 Forest Hills Road Machesney Park, IL 61115 Phone: 815-282-1513 www.astro-physics.com
From: main@ap-gto.groups.io <main@ap-gto.groups.io>
On Behalf Of Peter Nagy
Sent: Monday, November 1, 2021 10:00 PM To: main@ap-gto.groups.io Subject: [ap-gto] Keypad 4.19.5 unsuccessful upload
Hello,
|
|
Re: Keypad 4.19.5 unsuccessful upload
Peter Nagy
Yes, my CP4 firmware version is P02-08.
Peter
|
|
Re: Keypad 4.19.5 unsuccessful upload
Peter Nagy
Hi Suresh,
I am using USB cable from USB port of CP4 to PC's USB port via powered USB hub . Device Manager says this port was assigned to COM 3 port. Peter
|
|
Re: Keypad 4.19.5 unsuccessful upload
Suresh Mohan
Peter ,
toggle quoted messageShow quoted text
I did that two years ago had hell , I’m trying to recall how I finally did it. If im not mistaken it was a cable issue . How do u connect to the pc ? Suresh
On Nov 2, 2021, at 8:29 AM, Peter Nagy <topboxman@...> wrote:
|
|
Keypad 4.19.5 unsuccessful upload
Peter Nagy
Hello,
I've been trying to upload Keypad version 4.19.5 firmware to my Keypad that was previously version 4.19.3 but no success yet. The first two times I tried to upload Keypad version 4.19.5 to my Keypad was unsuccessful and I allowed two hours each time for uploading when it should have taken about 20 minutes according to A-P instructions. I followed A-P "Upgrading Your Keypad to 4.19.5 - Code Only Java Keypad Loader" documentation as close as possible. I got as far as to Step #7 under "Keypad Code Load" and it stayed stuck at "Completed 20% of Code Load" as shown in first screenshot. Here are the two screenshots of trying to upload to Keypad version 4.19.5 to my keypad. The first screenshot showed only 20% completion of upload after two hours of trying. The second screenshot shows status of Keypad after two hours of uploading without success. Please advise me what I could do for successful uploading of Keypad version 4.19.5. Now my Keypad is totally useless because it does not any longer boot to previous 4.19.3 version. My Keypad serial number is 3771GTO which is well above the minimum Keypad serial number of 1565GTO. I have been successful uploading three previous versions Keypad in the past without issues since owning first run A-P1100GTO mount (October 2013). This is my first time using Java Keypad Loader and it was not successful. Thank you, Peter
|
|
John Upton
Mike,
Thanks again. The method worked perfectly. I have been using this feature of the V5 Keypad since I set up anew each night for the most part and found that my cone error changed slightly night to night. (In addition to any dovetail induced cone error, I am also using an 11" SCT with mirror flop until I tighten the mirror clutches/clamps.) This feature has been helping with pointing until I get a model built. That is ... until I messed it up the other night. It is great to be able to recover so easily. It took very little time. John
|
|
Re: APPM and NINA Plate Solving -- Possible to use PlateSolve2?
David
John, I used to use Platesolve 2 all the time as well, but switched to ASTAP. It’s free, is WAY faster at solving, and just seems to work better. You should give it a look and try it. Plus, I didnt think Platesolve 2 was being supported anymore, but I may be wrong. David
On Nov 1, 2021, at 1:45 PM, John Upton <upton@...> wrote:
|
|
Peter Nagy
This should be mentioned in A-P manuals either in Mach2 or Keypad documentations. This is useful information.
Peter
|
|
Electro-Static Discharge Protection for Older Mounts
Scott Cooke
All,
If anyone has a 900 or 1200 mount and perhaps other older GTO mounts, AP is offering an Electro-Static Discharge board to be installed in the motor-gearbox assemblies. The Dec motor on my 900 decided to stop working so after a conversation with Howard in tech support, I sent both my RA and Dec assemblies. It turns out that the motor encoder on the Dec had gone bad. They had to replace the motor and encoder so they moved the old motor to the Dec and installed the new motor in the RA and installed new protection boards in both to help prevent this from happening again. I would recommend this board change to avoid paying for new motors and encoders. I know it is available for the 900, 1200, and I believe they said the 3600, but it is not available for the 400. Scott
|
|
New AP1100 Guiding Great on Very Windy Night
Mark Lamb
Last night, my new AP1100 (base) peformed great on very windy night. I got the AP1100 a couple of weeks ago, and I am very early on the learning curve. Per George's recommendation, I have yet to try any of APCC modeling, and using it just as I would my G11. I was imaging with a tiny scope, Vixen FL55ss at 237mm, f/4.3, and using my QHY268M capturing the Question Mark nebula in narrowband, using 8 min subs.
A couple nights earlier, I tried using an old ST80 (just purchased) as a guidescope, but the results were not that good, even though PHD2's total RMS was in the 0.4-0.5" range. I had to throw out ~40% of the subs for eccentricity. I did not know if the issue was the night's bad seeing (~2.9" according to MeteoBlue; the worst I had encountered in 3 years) or the long focuser cantilever on the ST80; I had to add ~100mm of M42 extensions and rack the focuser fairly far out to focus. Previous attempts with a generic 60mm/240mm guidescope did not have eccentricity issues, though sky conditions were much more typical at ~1.5" seeing. My 1st attempts using the AP1100 with a generic 60mm/240mm guidescope was similar to my G11 guiding with OAG, but more consistent. It is nice to have practically zero backlash compared to my G11's ~800ms typical (400-1200ms range). My only disappointment so far is the single bad night using the ST80 as guidescope, but I do not think the AP1100 had anything to do with the bad results. With the single night's bad experiment with ST80 guiding, I decided to use a QHY OAG instead of guidescope. Even with the bad wind conditions, PHD2's total RMS was in the 0.2" range, and I only threw out 1 of 60, 8 min subs, and the sub that I deleted was not that bad. Even though it was very windy, the online seeing estimates were in my typical range at ~1.4". So here on, I will be using an OAG even on my very short FL scopes. I know I benefited from the very tiny FL55ss lack of much wind surface, but I had to add much to get it balance in DEC, as well as balance in RA. I am glad I got the 10" combo saddle instead of the larger saddle, as this tiny scope train gets very back heavy with OAG/CFW/QHY268. I end up mounting the FL55ss on back end of a 14" DUP using a camera mount clamp, with additional pair of ~140mm CNC rings with 8" Vixen bar on top (very forward on DUP) with heavy Vixen clamp on the Vixen bar and Losmandy D clamp attached to the underside of the DUP. For AP, I guess one can never have enough additional clamps, bars, tubes, etc.... I am very please at how the AP1100 without encoders handled last night's windy conditions!
|
|
Re: APCC Meridian Tracking Limits and Sequence Generator Pro
Ray Gralak
Hi Steve,
In the current implementation of APCC it appears that APCC is basically intercepting the slew command whenIt doesn't work that way. The mount's flip point is controlled by the meridian delay set in the mount. The cause of the flip failure is probably a time discrepancy between the mount's meridian delay value and when SGPro thinks it is okay to flip. If there is even a split-second difference between the two times, that could prevent the pier flip from occurring if SGPro sends the slew command at the exact moment a flip should work. If SGPro delayed a few seconds, it might solve the problem. The new flip padding control in the 1.9.1.3 beta tries to address this timing issue. -Ray -----Original Message-----
|
|
Re: AP1100 / APCC Wired Ethernet Connection to Laptop Turning Off WiFi
Mark Lamb
Disabling the LAN-WLAN switching setting in BIOS did not fix the issue. Since this is a convenience issue only, I do not babysit outside in the cold, and having other things to do, I will leave this for now.
|
|