Date   

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:
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?

Wes
WA5TKU


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?

Wes
WA5TKU


Re: APPM and ASTAP #APCC

Ray Gralak
 

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?

Ray Gralak
 

Hi Marty,

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?
Unfortunately, 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.

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


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


Re: Mach2 CP5 Orthogonality Model #Mach2GTO #Keypad

 

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.

Peter


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,

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


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 ,
     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:

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


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


Re: Mach2 CP5 Orthogonality Model #Mach2GTO #Keypad

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

5541 - 5560 of 88084