Which logs would be helpful here?. Leo indicated it was a driver error so would that be an ascom log or am apcc log in this situation?

On Tue, Oct 11, 2022 at 04:45 PM, Clayton Yendrey wrote: My question/concern is that I'm got some history/familiarity with the Software Bisque world and excluding encoders, much the same arguments can

Yeah the 160ED gets very good performance as well on the Mach 2. I am not even sure if the mount knows its there.🙂

For sure, I have found that sometimes my MgBox will stop updating and needs the driver reloaded for it. When this happens, the temp reported by the device can be much higher than the actual values at

Yeah some nights I get over 4" FWHM and when I see that, I usually just call it and pack things in. In the winter, I have to be more tolerant, as the seeing in the PNW is usually horrible all winter

I believe I changed that awhile back based on discussion with John Hayes, oddly I should have had the upper at 0.8 and not 1.0. I did not notice that until you called it out.

I have an m box ascom sensor for temp/humidity but it tends to steal my com ports. May be I should invest one night and debug it. Problem is for me that I have very few nights to imaging and always

Ray - if the Dec-Arc tracking algorithm works fine with points in an All-sky model, then is there any real difference between running the algorithm on either an All Sky model or a smaller Dec-Arc

Ok, thank you. I have a much more forgiving situation, 900mm fl and 5 minutes exposures. I think I don’t need to make things more complicated then 😊

To be sure, the objects that I'm shooting with the 17" are mostly above 40 degrees altitude. If I was shooting low in the East or West, I would probably not get great results. I would also get oval

>>>It is important to collect data on field when we run the model or the weather website data is enough? based on my experience and working with Ray quite a bit, I found both temperature and pressure

Presumably, air temperature, pressure and humidity impact the model by changing the air density and thus the refraction. Altitude also matters – in that it effects barometric pressure, and does so

I'm not sure what you mean by the above. Dual axis tracking is always available in our mounts, encoder and non-encoder both. The keypad has a routine which allows one to measure the actual drift rate

Typo in my prior message - Moffat 4.0 not 5.0. My PI installation defaults to Star detection 0.5 and Moffat 4

That is what PI has used in the past, has that changed? 🙂

Some nights I get no better than 3 to 4 arc sec FWHM resolution and yet the guiding seems perfect. That's when I aim another scope at a star with an eyepiece and I see that the stars are not

Bill I see you changed the defaults in FWHMEccentricity to 0.0 Star Detection sensitivity (from 0.5), and Moffat 2.5 (from 5.0) Could you explain why those settings are more appropriate for your

Amen sister Karen Christen 7:58am #89396 Hey Astro-Nuts, A side note on group etiquette: I’m going to ask that we don’t bash other companies’ products or other astronomers’ choices.

In my case I run a 17 inch F8 astrograph with a model that I made about 6 months ago. I have not changed temperature or pressure in the model. The weather has changed from very hot to freezing in

Brian, On this is 530mm FL and 1.45"/px image scale. Scope is Epsilon e160ED. I've also duplicated Bill's performance with my GTX130 at the same image scale he is using, but that scope is waiting for