Gemini 2 strange behavior.

[MilwaukeeLion]

Did a quick start to change daylight savings time, used align assist and found align stars no problem, made minor adjustments.  Went on to modeling and it couldn't find barn door in front of it, plus modeling error page that pops up after you align each star in West or East models showed zero information after aligning each star so something is definitely wrong.  Was only using hand controller, not connected to Gemini.net, web interface, phd or stellarium scope, nothing.  Checked coordinates, no issue there, updated software couple weeks ago but everything worked fine last weekend mount hasn't moved since.  Anyone run into this before?  Moving ahead an hour cause meltdown?

[Demonperformer]

sily response - didn't check subject line

[coatesg]

Obvious things here are checking the location and time are correct, and that the RA/DEC cables are not reversed. Can you set the G2 unit up to use NTP via ethernet at all? This is by far the easiest route IMHO. Alternative to avoid this change every 6 months is to use 0 for timezone and enter UT - Gemini uses UT for all internal calculations, the timezone thing is only really useful for displaying/entering local time, you don't need it to run the mount (UT+Lat+Long is enough). 

Here, I'd do a cold start, check all the lat/long/UT times are correct. Do a single goto bright star, centre it up with HC, choose to synchronise and then check the model parameters via the handset. Assuming this is OK, you should be able to do the modelling run/manual model building/building via platesolves (whichever your method is).  

[MilwaukeeLion]

15 hours ago, coatesg said:

Obvious things here are checking the location and time are correct, and that the RA/DEC cables are not reversed. Can you set the G2 unit up to use NTP via ethernet at all? This is by far the easiest route IMHO. Alternative to avoid this change every 6 months is to use 0 for timezone and enter UT - Gemini uses UT for all internal calculations, the timezone thing is only really useful for displaying/entering local time, you don't need it to run the mount (UT+Lat+Long is enough). 

Here, I'd do a cold start, check all the lat/long/UT times are correct. Do a single goto bright star, centre it up with HC, choose to synchronise and then check the model parameters via the handset. Assuming this is OK, you should be able to do the modelling run/manual model building/building via platesolves (whichever your method is).  

Its possible thanks, I have all the connections and they work but the fastest for me to start imaging is polar align, quick model with HC, slew to target, start guiding.  No issues 4 days earlier which is what's puzzling along with no modeling errors shown.  There should be error data shown regardless of time.  Maybe a restart of the HC is in order.

[coatesg]

Any modelling issues, go for a cold start definitely. Check lat long and use UT!