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.
|
|
|
|
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. |
|
|
|
Similar mount and connection.
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:
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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. |
|
|
|
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. |
|
|
|
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.
|
|
|
|
Woody Schlom
Strange. I’ve never had my computer just randomly change a COM port assignment unless I plugged into a different USB port. In fact, I’ve labeled my main astronomy equipment USB port (that goes with the same USB hub) so I don’t accidentally forget which one goes with which adapter. And in 6 years now with this particular laptop, the COM port associated with that USB port and my #1 FTDI serial to USB adapter has never changed. And that’s through all the Win-7 updates and Win-10 updates. My laptop recognizes my #2 FTDI adapter as a different one – and so it has a different COM port assignment.
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:22 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] Can't connect to mount
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----- 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
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. |
|
|
|
CurtisC <calypte@...>
> Why not plug it directly into the USB connection on the controller?
What USB connection? |
|
|
|
This has been resolved. The FTDI adapter is toast. I bought it as recently as Jan 5, 2020. I dug out my old Keyspan adapter, and I can connect to the mount. Thank you to everyone for your replies. I'm mystified by Rolando's suggestion.
|
|
|
|
Was it the adapter with the flashing blue lights? Mine croaked too
about a week ago.
On 7/20/2020 9:40 PM, CurtisC via
groups.io wrote:
This has been resolved. The FTDI adapter is toast. I dug out my old Keyspan adapter, and I can connect to the mount. Thank you to everyone for your replies. I'm mystified by Rolando's suggestion. |
|
|
|
CurtisC <calypte@...>
Yes. Today it would flash very briefly when the system was booting up, but it never responded again. Glad I saved the old Keyspan.
|
|
|
|
Woody Schlom
Curtis,
That’s amazing. My Keyspan hasn’t worked since Win-98 2nd Edition. Of course, I gave up on it then too and haven’t tried it since.
I think Roland got confused and didn’t realize you have an old CP3. He’s been living in CP4 and now CP5 land now for too long.
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 9:41 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] Can't connect to mount
This has been resolved. The FTDI adapter is toast. I dug out my old Keyspan adapter, and I can connect to the mount. Thank you to everyone for your replies. I'm mystified by Rolando's suggestion. |
|
|
|
Well, Woody, this issue would be a motivation to spring for CP4. Funny thing, my Keyspan appeared to crash back in January, and I bought the FTDI in desperation to replace it. So now the FTDI doesn't work, and the Keyspan has saved me.
|
|
|
|
Woody Schlom
Spares are a good thing. I highly recommend them.
I’m holding off on the CP4. So far, I’m more than fine with the CP3 on my Mach1. And I sure can’t afford a Mach2 at the moment.
Woody
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of CurtisC via groups.io
Sent: Tuesday, July 21, 2020 2:19 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] Can't connect to mount
Well, Woody, this issue would be a motivation to spring for CP4. Funny thing, my Keyspan appeared to crash back in January, and I bought the FTDI in desparation to replace it. So now the FTDI doesn't work, and the Keyspan has saved me. |
|
|