|
Re: Mach2 Keypad
Hello Michael,
So nice to hear from you.
The keypad from 2011 will work with the Mach2, however it will have to be updated to the upcoming v5 software and you will probably want to replace the keypad buttons with a new version.
The Mach2 base is the same as the 400, 600E or Mach1 base. It is smaller than the 900. However, there may be a way to use the same tripod.
The Notify Me button only shows up when click the button on the bottom of the screen on our website to accept cookies from our website. You can click into the banner on the bottom to specify your preferences, but the cookies must be allowed. The reason is that you will be entering your email as part of the Notify Me process. So, we must have your permission to do this. I know it sounds silly, but that’s the way it works.
Clear Skies,
Marj Christen Astro-Physics, Inc 11250 Forest Hills Rd Machesney Park, IL 61115 Phone: 815-282-1513 Fax: 815-282-9847 www.astro-physics.com
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io]
On Behalf Of Michael Dolenga via groups.io
Sent: Monday, July 20, 2020 7:25 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] Mach2 Keypad
Opposite question, will a 2011 keypad sold with a new 900GTO work with the Mach2?
Another question, is the Mach 2 base the same as a 2011 series 900GTO base? Basically, can I use the same tripod?
Last question, how exactly do you get on the waiting list for a Mach 2? I don't see a "notify me" button anywhere on the page for the mount.
Michael
On Wednesday, June 24, 2020, 10:32:45 AM PDT, uncarollo2 <chris1011@...> via groups.io <chris1011@...> wrote:
The newest keypad version will work with CP4/CP5 controllers.
Rolando
-----Original Message----- Will the new update be backward compatible with the older mounts as well? For instance, if I update my existing keypad to work with the CP5, then can it also be
used with my CP3 equipped 900GTO?
|
|
|
|
Re: Mach1 and GTOCP4 Yellow Light
OK so my happiness lasted for a week and now the issue is back. Or at least I assume (hope?) that this is related to the problem.
|
|
|
|
Re: Can't connect to mount
Roland Christen
My Windows laptop constantly changes the com port that is available for the mount. Time and again I get Mount Not Found when trying to open a planetarium app. It's easy to fix. I simply open Device Manager, check to see what Com port is available. Then I open the ASCOM Telescope setup window, set it for the available com port and check to see if it connects. That's it, and it works every time.
Rolando
-----Original Message-----
From: Woody Schlom <woody_is@...> To: main@ap-gto.groups.io Sent: Mon, Jul 20, 2020 8:11 pm Subject: Re: [ap-gto] Can't connect to mount No, I doubt that the FTDI adapter is bad. I’ve had one now for 9 years I think. I started with Win-98 second edition and now I’m on Win-10 Pro. And that old FTDI adapter still works great.
And if the USB connector is making a bad connection, you can bite it to slightly bend the two parallel flat sides in a little so it makes a tighter fit. Or use pliers to very slightly tighten the USB connector.
Have you checked to see that the COM port assigned to the FTDI adapter matches the COM port the software is set to? They must match. And if you moved the FTDI serial adapter to a different USB port, then the COM port DID change. That’s what happens when you move it to a different USB port. You can still use the FTDI adapter in that “new” USB port, but you have to change the mount software’s COM port to match it. No big deal. Takes a second.
Woody
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of CurtisC via groups.io
Sent: Monday, July 20, 2020 5:57 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] Can't connect to mount Thank you for your reply. The only USB cable in the mix is the cable from the FTDI adapter to the computer. The cable is permanently attached to the adapter. So; the implication is that the adapter has gone south. I bought it in Feb to replace the previous Keyspan adapter.
|
|
|
|
Re: Can't connect to mount
Woody Schlom
Rolando,
Huh? CP3 doesn’t have USB. Unless I completely misread the original post and he’s got a CP4.
Woody
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of uncarollo2 <chris1011@...> via groups.io
Sent: Monday, July 20, 2020 6:08 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] Can't connect to mount
Why not plug it directly into the USB connection on the controller?
Rolando
-----Original Message----- Thank you for your reply. The only USB cable in the mix is the cable from the FTDI adapter to the computer. The cable is permanently attached to the adapter. So; the implication is that the adapter has gone south. I bought it in Feb to replace the previous Keyspan adapter.
|
|
|
|
Re: Can't connect to mount
Woody Schlom
No, I doubt that the FTDI adapter is bad. I’ve had one now for 9 years I think. I started with Win-98 second edition and now I’m on Win-10 Pro. And that old FTDI adapter still works great.
And if the USB connector is making a bad connection, you can bite it to slightly bend the two parallel flat sides in a little so it makes a tighter fit. Or use pliers to very slightly tighten the USB connector.
Have you checked to see that the COM port assigned to the FTDI adapter matches the COM port the software is set to? They must match. And if you moved the FTDI serial adapter to a different USB port, then the COM port DID change. That’s what happens when you move it to a different USB port. You can still use the FTDI adapter in that “new” USB port, but you have to change the mount software’s COM port to match it. No big deal. Takes a second.
Woody
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of CurtisC via groups.io
Sent: Monday, July 20, 2020 5:57 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] Can't connect to mount
Thank you for your reply. The only USB cable in the mix is the cable from the FTDI adapter to the computer. The cable is permanently attached to the adapter. So; the implication is that the adapter has gone south. I bought it in Feb to replace the previous Keyspan adapter.
|
|
|
|
Re: Can't connect to mount
Roland Christen
Why not plug it directly into the USB connection on the controller?
Rolando
-----Original Message-----
From: CurtisC via groups.io <calypte@...> To: main@ap-gto.groups.io Sent: Mon, Jul 20, 2020 7:57 pm Subject: Re: [ap-gto] Can't connect to mount Thank you for your reply. The only USB cable in the mix is the cable from the FTDI adapter to the computer. The cable is permanently attached to the adapter. So; the implication is that the adapter has gone south. I bought it in Feb to replace the previous Keyspan adapter.
|
|
|
|
Re: Can't connect to mount
CurtisC <calypte@...>
Thank you for your reply. The only USB cable in the mix is the cable from the FTDI adapter to the computer. The cable is permanently attached to the adapter. So; the implication is that the adapter has gone south. I bought it in Feb to replace the previous Keyspan adapter.
|
|
|
|
Re: Can't connect to mount
Similar mount and connection.
toggle quoted messageShow quoted text
For me the most unreliable part has been the USB serial driver (FTDI) and USB to RS-232 device. I used a 2-port USB-to-serial device for years (Exatron? something like that), then bought a new USB-to-serial (one port) cable last year. That one failed fairly quickly, and I went back to my tried-and-true device which I never should have replaced. Some troubleshooting techniques that have been useful: On Windows, open "Device Manager" and look at the USB connections. You might try uninstalling the serial port driver, and let it reinstall when you plug in the adapter to the USB port. You might also try unplugging the serial converter and plugging it into a different USB port. I've had trouble where it would only work if you plugged it into the same port you used last time. Someone else might have more precise instructions. I will say I'm really enjoying the reliable wired ethernet connection to the CP4 on my 1100, but the Mach1/CP3 still gets most of my observing time. Mojo
On 7/20/20 5:13 PM, CurtisC via
groups.io wrote:
|
|
|
|
Re: Can't connect to mount
Woody Schlom
1) Are you sure the COM port the FTDI serial adapter is assigned to NOW, is the same one you’ve selected in the mount control software? I ask because you said you switched the USB port the FTDI serial adapter was plugged into. And whenever you do that, the computer assigns a new COM port to it. So you need to make sure the COM port selected in the software matches the COM port the FTDI serial adapter is currently plugged into. And if you move the FTDI serial adapter around to different USB ports, the computer keeps assigning new COM ports – and eventually you run out. Then you have to delete all the bogus COM ports and start over. 2) Just for grins, I’d replace each cable – one-at-a-time to see if that makes a difference. Serial cables are usually pretty solid and dependable. But USB cables (usually the connectors) are notorious for failing.
Woody
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of CurtisC via groups.io
Sent: Monday, July 20, 2020 5:14 PM To: main@ap-gto.groups.io Subject: [ap-gto] Can't connect to mount
Mach1GTO, CP3 controller. I cannot connect to my mount. I've uninstalled-reinstalled the latest V2 driver and FTDI driver. I installed the latest version of APCC. I've unplugged-replugged all cables, several times. This gear has always been picky about turning on the mount power before turning on the computer, so I've been diligent about shutting everything down, letting it sit a bit, then restarting.the mount first, then the computer. I went through something like this during the winter, but plugging the FTDI driver into a different USB port got it working that time. No joy this time. Device Manager says the FTDI driver is working correctly. Should I just assume that any or all pieces, from the FTDI controller to the CP3 driver, are defective and need to be replaced? I'm at a loss to explain this or to come up with a solution. I'm looking for suggestions about something I've overlooked.
|
|
|
|
Re: Mach2 Keypad
Michael Dolenga
Opposite question, will a 2011 keypad sold with a new 900GTO work with the Mach2? Another question, is the Mach 2 base the same as a 2011 series 900GTO base? Basically, can I use the same tripod? Last question, how exactly do you get on the waiting list for a Mach 2? I don't see a "notify me" button anywhere on the page for the mount. Michael
On Wednesday, June 24, 2020, 10:32:45 AM PDT, uncarollo2 <chris1011@...> via groups.io <chris1011@...> wrote:
The newest keypad version will work with CP4/CP5 controllers.
Rolando
-----Original Message-----
From: Dean Jacobsen <deanjacobsen@...> To: main@ap-gto.groups.io Sent: Wed, Jun 24, 2020 11:53 am Subject: Re: [ap-gto] Mach2 Keypad Will the new update be backward compatible with the older mounts as well? For instance, if I update my existing keypad to work with the CP5, then can it also be used with my CP3 equipped 900GTO?
-- Dean Jacobsen http://astrophoto.net/wp/ Image Gallery - http://astrophoto.net/wp/image-gallery/ Astrobin - https://www.astrobin.com/users/deanjacobsen/
|
|
|
|
Re: FITS Image Header Issues Using APPM-Help!
lmbrabec@...
Great information Michael! Looks like I updated to Windows 10, Version 1909 on April 15th. So do I try to go back to the previous version of Windows 10(I'm not sure how to do this)? Thanks for the clue! What do you think Ray or any other suggestions? Scott
|
|
|
|
Can't connect to mount
Mach1GTO, CP3 controller. I cannot connect to my mount. I've uninstalled-reinstalled the latest V2 driver and FTDI driver. I installed the latest version of APCC. I've unplugged-replugged all cables, several times. This gear has always been picky about turning on the mount power before turning on the computer, so I've been diligent about shutting everything down, letting it sit a bit, then restarting.the mount first, then the computer. I went through something like this during the winter, but plugging the FTDI adapter into a different USB port got it working that time. No joy this time. Device Manager says the FTDI driver is working correctly. Should I just assume that any or all pieces, from the FTDI controller to the CP3 driver, are defective and need to be replaced? I'm at a loss to explain this or to come up with a solution. I'm looking for suggestions about something I've overlooked.
|
|
|
|
Re: FITS Image Header Issues Using APPM-Help!
Michael Hambrick <mike.hambrick@...>
I am running Windows 10, Version 1909 since
February 5, 2020. The latest update was 2020-07 and I installed it last
Friday (July 18). The infamous 2020-04 (also flagged as a bad actor by
the folks at Diffraction Ltd) was installed on April 14, 2020.
Best Regards Michael Hambrick ARLANXEO TSR Global Manufacturing Support PO Box 2000 Orange, TX 77631-2000 Phone: +1 (409) 882-2799 email: mike.hambrick@...
|
|
|
|
Re: FITS Image Header Issues Using APPM-Help!
lmbrabec@...
Ray: I should have added that it says 2019 Microsoft for the version. Sorry about that! Scott
|
|
|
|
Re: FITS Image Header Issues Using APPM-Help!
lmbrabec@...
It says version 1909 (OS build 18363.959) so its not version 2004. I agree with you as I had success this morning trying the NASA internet option in APPM. It ran great, but the FITS Image Header is full of information and has the proper format for the image start time that I'm not seeing when I run the ASCOM camera driver with the ZWO camera. Scott
|
|
|
|
Re: FITS Image Header Issues Using APPM-Help!
Ray Gralak
BTW, what version of Windows are you running?
toggle quoted messageShow quoted text
Type "WinVer" from a command prompt to get the exact version and post the information. If it's version 2004 that could be the problem. -Ray Gralak Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro Author of PEMPro V3: https://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
-----Original Message-----
|
|
|
|
Re: FITS Image Header Issues Using APPM-Help!
Ray Gralak
Scott,
As I said APPM sets the DateTime via ExposureStartTime in PinPoint before doing the plate solve.
Sorry, I don't have any other suggestions and I don't see that behavior. Here's a screen shot just done using Nasa SkyView and PinPoint just a moment ago:
-Ray Gralak Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro Author of PEMPro V3: https://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of lmbrabec@... > Sent: Monday, July 20, 2020 3:06 PM > To: main@ap-gto.groups.io > Subject: Re: [ap-gto] FITS Image Header Issues Using APPM-Help! > > Thanks so much Ray and Michael for the help! The first time I tried APPM was on 7/15 and then again today to > see if the FITS Image Headers still caused issues and on both dates it was the same issue. I also tried using the > NASA option this morning and ran a small model (38 or so points) and everything ran fine so it seems like it is > maybe ASCOM/camera driver maybe? As far as version of PinPoint It is the most recent as I just purchased and > downloaded it on 6/24/2020 and for PinPoint Astrometric Engine version is 6.1.5. I'm also attaching some of the > feedback I got from the PinPoint forum (I hope that's o.k.). I figured it would be better that way for you to see > what the PinPoint experts had to say. The last Windows 10 x64 update I got was on July 14th. > > Thanks in advance! Scott
|
|
|
|
Re: FITS Image Header Issues Using APPM-Help!
lmbrabec@...
Thanks so much Ray and Michael for the help! The first time I tried APPM was on 7/15 and then again today to see if the FITS Image Headers still caused issues and on both dates it was the same issue. I also tried using the NASA option this morning and ran a small model (38 or so points) and everything ran fine so it seems like it is maybe ASCOM/camera driver maybe? As far as version of PinPoint It is the most recent as I just purchased and downloaded it on 6/24/2020 and for PinPoint Astrometric Engine version is 6.1.5. I'm also attaching some of the feedback I got from the PinPoint forum (I hope that's o.k.). I figured it would be better that way for you to see what the PinPoint experts had to say. The last Windows 10 x64 update I got was on July 14th.
Thanks in advance! Scott
|
|
|
|
Re: Ser No 900349
Michael Dolenga
I think it would be hilarious if someone named Karen posted a video of herself complaining to the manager of the internet about the memes.
On Monday, July 20, 2020, 12:58:47 PM PDT, Karen Christen <karen@...> wrote:
To be frank, I think Karen memes are funny as heck. :-D No offense taken, ever. Karen
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io]
On Behalf Of khursh via groups.io
To you and all the Karens out there, I am truly sorry this was done to you. I'm sure Kevins are next. -- Karen Christen Astro-Physics
|
|
|
|
Re: FITS Image Header Issues Using APPM-Help!
Michael Hambrick <mike.hambrick@...>
Hi Scott
Did you happen to do a Windows update just prior to all of this ? I downloaded the latest Windows update (2020-07) on Friday night, and the next time I started up my laptop was Saturday night getting ready for a night of imaging. MaxIm DL went absolutely crazy on me. I shut everything down a rebooted my laptop and then everything worked fine after that. I think I had a similar issue once several months trying to run PinPoint Astrometry on an image. Best Regards Michael Hambrick ARLANXEO TSR Global Manufacturing Support PO Box 2000 Orange, TX 77631-2000 Phone: +1 (409) 882-2799 email: mike.hambrick@... From: lmbrabec@... To: main@ap-gto.groups.io Date: 2020-07-20 12:54 PM Subject: [ap-gto] FITS Image Header Issues Using APPM-Help! Sent by: main@ap-gto.groups.io Hello all: I'm new to the forum and just got my Mach2 up and running and learning the ropes with APPM. I've been working on an issue where plate solving is failing. My camera set-up in APPM is: ASCOM Camera, ASI Camera (1), ZWO ASI294MC Pro. Current versions I'm using is: ASCOM 6.4.1.2695, and the ZWO camera ASCOM driver is the most current 1.0.4.3. I'm also using APCC-Pro version 1.8.2.1, and APCC V2 driver 5.3.10. I'm also using the PinPoint (Full Version) for the plate solver. The error message during plate solving that I get is "plate solve failed! The plate's exposure start time is required for catalog proper motion calculation". I also got same message when trying the "plate solve" under the Run tab in APPM. I pulled in an older FITS image that had been imaged with SharpCap software and using the "image link test" in the Plate Solve Settings tab and everything looked good (plate solved). I've attached a PDF of the failed image FITS Image Header captured through APPM and the FITS Image Header captured with SharpCap. Looking at the "Date-Obs." row in the FITS image header for the image that failed to plate solve and said that exposure start time is needed the format used was: "7/20/2020 10:53:41 AM'. I am also noticing that there is no RA and DEC information in the FITS file. The FITS Image Header from the SharpCap acquired image showed for "Date-Obs." row: "2019-10-25T02:02:11.2774146'. I'm also attaching a PDF of camera settings used in APPM and the plate solve results along with the FITS Image Headers of the successful plate solve (SharpCap acquired), and failed through APPM. I ran this by the PinPoint forum and they mentioned that the Date-Obs. format is incorrect for the failed plate solve and that the FITS image information does not come from Pin Point but the acquisition software? Thanks in advance for your help! I'm loving the Mach2 so far and looking forward to learning the modeling capabilities. Scott
|
|
|
