Date
1 - 11 of 11
Mach 1 connection
|
Michael Kelly
Reaching out here….
In an effort to not freeze my you-know-what off this winter, I added a Pegasus USB hub so I can attach everything and run one cable into my downstairs. While I love being outside with the gear, being warm wouldn’t really suck…… I’m using a CP3 and when hooked thru the new powered usb hub, SGP can’t connect to the mount but managed to find my main camera, guide camera and Planewave focuser just fine. I’m using the serial to USB adapter by Tripp Lite from the mount to the hub. This configuration seems to work fine when hooked directly to my laptop….I’m probably making some goofy rookie mistake here and would gladly laugh at myself for some excellent guidance! Best and Clear Skies! |
|
|
|
Peter Nagy
Michael,
You need to find out which COM port number your computer assigned to your USB-to-Serial adapter by going to your computer's Device Manager under "COM & LPT". Once you get that, then fill in the COM port number in A-P V2 ASCOM mount driver. Peter |
|
|
|
ap@CaptivePhotons.com
Michael Kelly wrote:
Besides the com port mentioned, the Pegasus Pocket Powerbox Advanced (is that the one?), in the first generation, has an oddball port 1, it is USB3 only, and even many USB3 devices will not work due to how they negotiate. If you have the original of this, make sure you avoid port 1 until you test and make sure things work. I just have mine covered up.
They changed this in the second generation recently released.
Linwood
|
|
|
|
Michael Kelly
I have the Pocket Powerbox Advance on the telescope with main camera, guide camera, focuser and Heater controller attached. I then HAD one cable from that and the mount attached to my computer. No problems! I have added the USB hub and now have the PPB and the mount plugged into the USB hub and everything from the scope manages to pass thru just fine but the mount ‘can’t be found’ whole unplugging and plugging I get a the requisite windows ‘ga-dunk, ga-dunk’ when plugging/unplugging.
toggle quoted message
Show quoted text
Sent from Smallbiz Yahoo Mail for iPhone On Saturday, November 20, 2021, 10:05 PM, ap@... <ap@...> wrote:
|
|
|
|
Patrick Spencer
Hi Michael,
The configuration that worked for me was a 2-cable setup. I plugged the USB-to-Serial adapter into a USB port on my imaging PC and connected a serial cable from the adapter directly to the CP3. Then I ran a separate USB cable from the PC to the Pegasus, to which I connected everything else. You could try the FTDI USB-to-Serial adapter that AP sells. It's more expensive than the Tripp-Lite, but it always worked flawlessly for me. However, I never tried to connect it through a hub, so can't vouch for whether it will work any better than the Tripp-Lite in that regard. How long is the cable run from your house to the location where the mount is set up, and what type of cable(s) are you using for that connection? Is your imaging PC outside near the mount? Patrick Spencer |
|
|
|
Michael Kelly
Patrick,
toggle quoted message
Show quoted text
Thanks, I’ve been using the two-cable set up. My Dell XPS only has usb-c inputs so I have been using a usb c to 3-3.0 usb a adapter. The serial to USB adapter and the usb cable from the Powerbox advance go into the adapter. The computer instantly found everything on ‘CommPort 5’ the first time without having to change anything. I was psyched it was soo painless. I did get the FTDI adapter under George’s advice but haven’t used it since the one-maneuver-adapting cable worked out of the gate. My set up is about 30’ from my back door so I was hoping to just add a powered hub to connect the mount and the output of the scope hub and one long usb cable into the house. I find it strange the mount can go into a cheesy usb-c to usb a adapter and be found, but not thru the hub. Perhaps there is some configuration in the usb hub to identify the port that the mount is plugged in so it can be found….. Sent from Smallbiz Yahoo Mail for iPhone On Sunday, November 21, 2021, 8:14 AM, Patrick Spencer <patrickspencer2@...> wrote:
|
|
|
|
Patrick Spencer
Yeah, USB can be flaky for sure.
You mentioned you hear the "ga-dunk, ga-dunk" sound when you connect the mount to the Pegasus, so is it possible the COM port is being created but you're just not able to determine which port it is? I don't want to waste your time with suggestions you've already tried, but you might try this: Open the Device Manger with the Pegasus connected to the PC but the mount NOT plugged into the Pegasus, and expand the "Ports (COM & LPT)" entry to see which COM ports are listed. Then leave Device Manager open and connect the mount to the Pegasus to see if another COM port appears in the list. If so, you can open the AP V2 ASCOM driver and select that port in the COM Port dropdown list (this is what Peter was referring to in his post earlier). Patrick |
|
|
|
Peter Nagy
The advantage of using FTDI USB-to-Serial adapter is it retains COM port retention so if you plug into different USB port, your COM port should retain same port number and you don't have to look up in Device Manager anymore. If you're not using FTDI chipset, then adding USB hub will likely change COM port number.
Peter |
|
|
|
Michael Kelly
Peter,
toggle quoted message
Show quoted text
You’re a genius! The FTDI adapter did the trick. Showed right up and easy to ID by unplugging. Officially down to one cable connecting all the gear to my laptop! Thanks all for the help! Now for the clouds….. Best, On Saturday, November 20, 2021, 10:03 PM, Peter Nagy <topboxman@...> wrote:
|
|
|
|
Peter Nagy
Glad it worked out. 👍
Peter |
|
|
|
Michael Kelly
toggle quoted message
Show quoted text
On Sunday, November 21, 2021, 5:53 PM, Peter Nagy <topboxman@...> wrote:
|
|
|