toggle quoted messageShow quoted text
You may need to update your Pegasus software to fix this issue.
Older versions of the Pegasus UPBv2 console app and ObservingConditions driver will relay the Fahrenheit temperature to downstream consumers such as NINA or APCC when the console app is set to display units in Fahrenheit.
The ASCOM ObservingConditions interface specification specifies that the values for its various meteorological properties must be in SI units (ie, Celsius when it comes to temperature), so that is what APCC is expecting. Pegasus issued a fix for this last year so you might just need an update unless they’ve reintroduced the bug in a recent version.
This issue was even more obvious to those who have NINA set to convert the SI units too imperial for display. This caused NINA to convert the Fahrenheit temperature to Fahrenheit again, resulting in some outlandish temperature values being reported.
Aside from that, your description is quite an interesting depiction of how much temperature can alter the tracking of the mount under a model, though. Glad you were able to work out the cause. Hope you like the Advanced Sequencer, too. It is of course a work in progress but it’s maturing nicely.
On Apr 20, 2021, at 00:35, W Hilmo <y.groups@...> wrote:
I've been doing some unguided imaging with my AP1600 w/Absolute Encoders and APCC Pro and have seen some interesting behavior with unguided imaging.
The first few nights that I run unguided after building a model of about 180 points, everything was great. I was blown away by how well it worked. The last few nights, not so much. I am seeing elongated stars and some image drift over the course of the night.
I do not believe that this is flexure. I'm imaging with my AP130GTX, and I've double checked all connections. I've double checked to make sure that the pointing model is enabled. I verified that the polar alignment is still spot on. It's a bit difficult to troubleshoot because, without guiding, there aren't any log files to examine. All I have are the subs that I can inspect.
Since we're getting into more moonlight, I've done some software updates (switched to the daily builds for NINA so that I can use the advanced scheduler). I've also set up for doing tonight's run with the guider enabled so that I can get some logs. As I was watching the session get started, I noticed something odd. Specifically, I noticed that APCC reported the temperature at over 40 degrees C, which is very wrong. I am using the Pegasus Astro Ultimate PowerBox v2 as the weather sensor.
It occurred to me that I made a change to the Pegasus software a few days ago to change from reporting the temperature in C, to reporting the temperature in F. It looks like both APCC and NINA are reporting the Fahrenheit value as Celcius. I am wondering if the significantly incorrect temperature interpretation has effected the model such that it's lost accuracy. I have reverted the Pegasus software back to reporting in C, and after tonight's run, I'm going back to unguided operation to see if I get that great result back that I was getting the first couple of nights.