Can also be manually edited outside EKOS with an SQL database editor.

Read More...

I was experimenting with the center telescope feature in the FITS viewer and FITS image in the Align module and noticed an odd behavior.
If the center telescope pointer is used too soon, it will attempt to slew the mount to an area selected around 00°00'00" RA and Dec.
On my Pi4, it took about 15 seconds for the WCS coordinates to load with the solved simulator image and for it to become available to use center telescope.
Currently the center telescope tool is not selectable when there is no WCS information; however it is unlocked while in the process of loading the WCS, thus causing an issue if attempted too soon.
So some kind of indication that WCS is loading would be useful, as well as locking the tool until it is ready.

Read More...

DeepSkyStacker issued a warning in their 4.2.5 release notes regarding recent changes to Libraw. I thought it would be prudent to share this insight to get ahead of any similar issues we might encounter.
They wrote

LibRaw 0.20 has introduced a change that primarily affects users of "older" Canon DSLR cameras and FujiFilm X-Trans series cameras (older includes the EOS 60D and 60Da)!

The change is to increase the size of the frame area of the image that surrounds the "user area" so that top and left margins are an even number of pixels. The resultant image that DSS extracts from the RAW file will be reduced in width, height or both by one pixel. As result the Bayer Pattern (CFA) used for de-Bayering the image also has to change.

Unfortunately the LibRaw developers won't say exactly which cameras this change applies to save to say that it is not a large number. Other have reported that at least the following cameras are definitely impacted by this change:

EOS 1D Mark IV
EOS 5D Mark II
EOS 7D
EOS 60D
EOS 550D
EOS 600D
EOS 1200D

If your camera is one of those affected, you will not be able to use any existing master frames produced with DeepSkyStacker 4.2.4 Beta 4 or earlier releases as they will not be compatible. You will need to delete and re-create your master frames from the original darks, flats etc..



Read More...

Andrew replied to the topic 'Autoguiding with Star Adventurer' in the forum. 2 weeks ago

The auto-guider will only function while the mount is tracking. And since it is not receiving that status from the mount itself, you need to enable tracking on the mount simulator driver to trick it.

Read More...

Andrew replied to the topic 'Zippity.' in the forum. 2 weeks ago

I applied those overclock settings to my Raspberry Pi 4, 4GB running Raspbian Buster 18.04.
over_voltage=6
arm_freq=1750
gpu_mem=256
gpu_freq=600
max_usb_current=1

I thought all was well, but I later found that my Adafruit GPS serial device stopped working. And the culprit was the increase of gpu_freq=600
I don't have a clue how it is at all related. But was fortunate enough to quickly find the issue by undoing the recent change I made.

Read More...

Andrew replied to the topic 'New KStars/Ekos Module: Analyze' in the forum. 3 weeks ago

This looks fantastic. It seems to include some features I've posted for on the Wish List. Great work. Thank you.
Question: The RGB color coding is quite clear. But what about narrowband and calibration frames? I'm thinking you went with something along these lines?
Ha: Dark Red
S: Yellow
O: Cyan
Luminance: White
Dark Frame: Black
Bias Frame: 50% Grey
Flat Frame: 25% Grey
Other: Magenta

Read More...

I believe it is. But can not confirm.
I just use my guidescope for PAA. But a guide-cam with a 50mm CCTV lense will also do the trick of you are inclined to DIY.

Read More...

Andrew replied to the topic 'Autoguiding with Star Adventurer' in the forum. 4 weeks ago

I did not intend to start a debate on internal guider vs PHD2 with or without EKOS. Just giving him the option and how to use it with the Star Adventurer.

Read More...

Andrew replied to the topic 'Autoguiding with Star Adventurer' in the forum. 4 weeks ago

I have been successfully autoguiding my SA with KStars and PHD2.
Strictly speaking you only need PHD2, but it is better to have KStars and EKOS control the camera so it can at least dither in RA. If you are not interested in dithering, you can simplify to just PHD2 and intervalometer.
Aurneth gave excellent instructions, including disabling Dec for EKOS internal guider. But if you use PHD2 there are 2 places you can do that. First, under the guiding graph, on the far right adjacent to Mx DEC, Change Auto to OFF. The other way is in the Brain>Algorithms> Dec guide mode: OFF.

KStars and EKOS can really help with aligning your target with plate solving.
For locating a target I will set the solver to only Sync. Before running the solver manually set a sync point near where you think the camera is pointed. Use manual sync points whenever you make large movements.

The successful result of the solver if you use your main imaging camera will be shown on the skymap. Use that as a guide for RA, Dec and rotation adjustments.
If it has difficulty solving, try increasing exposure time. Or clear the mount alignment to eliminate your manual sync points.

You can also polar align with your guide scope and the EKOS Polar Align Assistant. Choose manual slew at the beginning, and rotate ~30° for each step.

Read More...

I am interested in getting this camera. How has it performed over the last few months? Any issues or workarounds? I would also like to know how big a typical file size is and time to receive it. Anything you can add is most welcome. Thank you.

Read More...