开云体育

Much better tonight and so many thanks for the help! Attaching the baseline PHD log. Calibration, 20 or so mins of guiding and 20 or so mins of Guide Assistant Much more stable I'm now taking some

OFF.? But I will try ON as soon as its clear and get back to you ASAP. ------------------------ Jim W Phoenix, AZ. USA Losmandy GM811G, NINA 1.11, ASI2600MC Pro, Sky-Watcher Scopes

Just making sure: did you get the successful runs with Gemini expects J2000 setting turned on or off? If off, that's not really using the changes I made to the driver to let it work with J2000 client

I did manage to get two successful runs using the 1.0.82.0 driver but would like to do additional testing.? For the past 3 to 4 weeks the conditions have been poor at best.? Heat, not getting below

Guilherme, With this checked, every time you sync you are adding another point to the model. Over time you will have a complicated multi-point model which may not be correct. I used to click Add'ln

Hi Jim, Did you ever test the updated ASCOM driver with J2000 setting and NINA? I'd like to know if that fixed the problem, and to see the logs if it didn't improve things. This change was based on

Not sure about " keep everything on JNow "...? Its my understanding that most / all planetarium uses J2000. ------------------------ Jim W Phoenix, AZ. USA Losmandy GM811G, NINA 1.11, ASI2600MC Pro,

Thanks Jim, I have found other recommendations to keep everything on JNow but mostly to make sure Planetarium, mount, and imaging tool are all on the same page. Had not read about this sending the

Jumping back in...? I found that if "Gemini Expects J2000 Coordinates"?is *ON* everything goes to hell.? If you tell NINA to plate-solve / center your mount will move away from the target the

OK so that may have been my problem last night. I had this option set for some reason and that's when the mount went crazy. I'll keep that off thanks! Guilherme

yes that setting can create problems. i'd recommend turning it off unless you have a specific reason to enable it as mentioned before, the vast majority (i'd guess 99% ) do plate solving with no

Possibly, especially if the plate solve found the wrong location and now added a bogus alignment point into the model. I am not sure what the best practice is for that setting but I leave it off

Also, go ahead a do a COLD start at CWD to clear out any of the bogus model parameters. It was likely, not that you needed the 3-star modelling, but that in doing so you made a clean start on the

Make sure "Gemini Expects J2000 Coordinates" is *OFF*.? I use ASTAP with NINA and Gemini ASCOM driver 1.0.82.0. -- ------------------------ Jim W Phoenix, AZ. USA Losmandy GM811G, NINA 1.11,

I suspected it could be the modeling because after trying plate solve on the Crescent nebula for some time, I used the hand controller to park the mount at CWD, and it stopped at a completely wrong

It also should be clear tonight and a lot less worse than last night - it was insufferably hot and the seeing looked terrible. I think what I can do tonight, is - Reset PHD to all defaults -

star modeling, and the plate solve worked like a charm after that. ? well most Losmandy imagers who are doing plate solving don't use any gemini modeling (myself included). so I'm wondering if it's

On Tue, Jun 29, 2021 at 08:21 AM, Brian Valente wrote: This log is as close as I could get to the baseline. I could not get 30 mins and you can see toward the end, I touched the mount to tape off the

Hello all I tested yesterday with parameters set according to the XLS shared by Edward, and (almost) everything worked fine. The flip happened at expected time and the image after flip was just fine.

only in one direction the GA analysis of a spring-loaded worm is often not accurate. I would focus on your guiding results. I'm guessing your DEC is not the constraining factor right now my guide cam