Carry-on weight limits vary by carrier, from no limit to 15kg. I find that US carriers tend to have no or high limits, and euro and asian carriers tend to be a little more restrictive on both size and

I'd say this is a bit too optimistic for airline travel. Airline overhead bin capacities vary by plane type, interior age, and even which side of the plane has a space available (looking at you, E175

If you're using Advanced Sequencer in NINA, you can use the Smart Meridian Flip plugin. You can point it at the .mlm file that APCC recorded your meridian limits to. It will turn off tracking before r

NINA won't park the mount in response to reaching the meridian or being unable to flip, though. From NINA's point of view, parking the mount is an explicit, not implicit, instruction - NINA will do it

I just tested a fix from Ray that seems to solve the issue, so expect an update in due course. /dale

I also use the M54 spacer variety pack from Agena, and they have similar packs for other diameters.

I think this situation boils down to the impressions one gets when programming against a model, and you believe that model to be correct and it turns out it is not! George has a non-AP mount and, natu

I'm not the author of the Orbitals plugin, but George Hilios is availble on the NINA Discord chat as are many users of it. Plugin authors also post notices of updates there, well. The intention of the

First, create a custom horizon file for APCC and APPM to use. With this, you can have APPM not plot points that are below the horizon. Second, you can create a dec-arc model of sufficient width for ju

The photo with the actual error in it unfortunately has the full text of the error cut off, but it seems like you ran into a dither settle time exceeded warning? This indicates that PHD2 was not able

The ASTAP plate solve is then failing because the RA and Dec that it is being hinted with, which is taken from what the ASCOM driver reports, is outside the search radius of ASTAP when it compares sta

I suggested plate solving in the eastern or western sky with the intent to imply that plate solving at zenith, on or near the meridian, is not necessary. Because I can't see how you've actually go abo

It's likely you're running one of your imaging apps as Administrator, and the other as your regular Windows user. This will cause 2 instances of the A-P ASCOM driver to be opened. Whichever app you're

Yeah. I run a single TOA-150 on a 1200GTO for my club and I personally have an 1100GTO. The single TOA-150 is at home on the 1200. The 1200 could do two of them but that would put it at the upper boun

You seem to have APPM configured to use the QHY ASCOM driver instead of NINA as the camera. Please review the configuration guide for my plugin here: https://daleghent.com/astro-physics-tools#appm-con

I think your hands-on approach, pardon the pun, might be getting in the way of things. NINA (or any app) has no advanced knowledge of what the park position of any given mount is. When the app tells t

Is your mount even slewing to the correct position in the sky at the start of your sequence in NINA?

Hi Philippe, It might be that you are running a firewall that is blocking port 59590, which is the TCP port in question here. As far as the Windows firewall goes, this is usually taken care of effortl

#APCC

And, just to be clear, the message is just a warning, which will self-resolve after 30 seconds of hanging out on your screen unlike an error that will stick around until interactively dismissed. The i

Man, I step away to get the kid in bed and you've got it sorted. Thanks, Brian. Philippe, a tip that might save you some time: If you are using the same profile in NINA for your QHY camera, make sure

#APCC