Indeedy! Bravo friend!! Sent from Smallbiz Yahoo Mail for iPhone

Glad it worked out. 👍 Peter

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

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

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

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

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

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

Michael Kelly wrote: 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

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

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

Hi John, I do not recommend using the ASCOM Device Hub with the AP V2 driver as the ASCOM device hub may not pass through some of the APCC-specific commands from APPM to APCC. -Ray

Ray, Peter, Thanks for the suggestions. I will try increasing the AP-V2 driver timeout first to see if that solves it. I can look into using the ASCOM Device Hub later as a potential fall-back

Hi John, Have you tried increasing the timeout in the AP V2 driver setup window? -Ray

Just a quick follow up. Roland was nice enough to annotate one of my unguided PHD2 graphs to illustrate how he measures Seeing. He explained that he uses this measurement to help determine the initial

Hi John, You shouldn't have to do this but have you tried using ASCOM Device Hub? It's pretty easy. It's already part of ASCOM. When you select ASCOM mount driver, instead of choosing A-P V2 ASCOM

Thanks for the insight. I had verified both and they are OK. What I did find is that the problem is with Stellarium. A photo of where Ceres should be according to Stellarium didn’t show the dwarf

Greg, brilliant proposal!, thank you -- TJF MOBILE

APCC 1.9.0.11 I’m also using an APPM model, although in this case I was using an older all-sky model since I didn’t have time to do a new model prior to the ISS pass. It was for the same setup,

I've been waiting for the upcoming suggestions for enhancements but as it has not yet appeared, I'm going to suggest something now, particularly when I notice some upgrades are being built (between