To the OP, A few weeks ago, I upgraded Windows 10 to 19043, and began having problems with a number of applications. This included the same sort of problems you have mentioned. I installed APCC and

The ASCOM MoveAxis method takes two parameters: an axis number and a rate in degrees/second. When initially defined (years ago) the rates were intended to be independent of sidereal rate, for anything

Ray said: So it may be the structure of the command sent from NINA? It's supposed to specify a slew rate? (Where "supposed to" is apparently clouded in lack of a clear standard, but in this case

Hi Linwood and Andy, I took a quick look at this issue, and I don't believe there is a problem with APCC. APCC is properly adding the rate supplied to it whether or not pointing and/or tracking rate

Andrea wrote: Linwood, Can you remind me your mount type? About one year ago I saw something similar in Skyx but I thought was because the mount was new ( Mach 2). After that I learned to use the

Linwood, Can you remind me your mount type? About one year ago I saw something similar in Skyx but I thought was because the mount was new ( Mach 2). After that I learned to use the move commands in

Ray wrote: Ray wrote: Just to circle back around this one, I contacted the INDI developper and that specific issue (leading space character int the FITS header RA/DEC coordinates) has been fixed in

About 3 hours of integration of Ha.

Hi Ray, Last session was the first night of actual data capture. Bin1 scale is 0.47 arcsec/pixel PEM, Dec arc tracking, refraction all ON Model spacing was very small (attached). Tacking was good

Andrea, Did something similar didnt see much in 5 minutes or so. I can refine things more now. Thank, -Rouz

Testing last night and I got the same results...I am not sure where to go next. The plot is nearly identical to the one the night before. This is after I backed off the dec motor to allow

Ray: Yeah, I understand the feeling, I find it hard to believe you can get any actual development done with the volume of email. The mixed blessing of having people actually use the software you

Linwood, Yes, this seems like a bug and is already on my list to investigate. I have just barely caught up with answering online and private offline questions, looking at logs, etc. This hasn't left

-- I run robotic projects on a 900 mount. Higher slew speed would increase system efficiency. Any thoughts on what the downsides might be to selecting the maximum slew speed, or contrarywise, what

Ray said: That's a fair point, but really steps around the core issue. As a simple example, the NINA control panel has simple N/S/E/W controls. These stop working when pointing corrections are

While I do not have an data that would prove the AE/AEL encoders helped my imaging out, I can say that I have lived in Midland,TX for 3 years and prior to owning my AP1600 AE mount. I wouldn’t try

Andy, You should disable tracking/pointing correction during polar alignment routines, or you may get a bad polar alignment result. BTW, changing polar alignment invalidates the model

Hi Rouz, Assuming accurate source plate solves, I think that you have some randomness in your setup. I can tell there is randomness because in each of your pointing models, some of your East/West

0ne thing I can suggest if you didn’t check already: - take a series of short frames, with some delay in between, to cover 30 min or more - do the Sum or create an animation of the series’ and

Here is the Model.