Ken Self replied to the topic 'Client Read EOF error' in the forum. 3 weeks ago

You need to attach the corresponding PHD2 debug log. If it is too large, either use the upload options on the help menu and post a link or you zip it up to attach to this forum.

Read More...

Ken Self replied to the topic 'What camera for a RPI4 ?' in the forum. 1 month ago

Most of the popular astro cameras will work on the RPi with Ekos.So the choice of camera really comes down to what sort of objects you are interested in, the sort of onditions you image under and how you wantto display your images.For example, if you are interested in emission nebulae a cooled mono camera with large field of view and narrow band filters would work best. With planetary you would want a color camera with small pixels and video capable.
 

Read More...

Ken Self replied to the topic 'Exposure calculator' in the forum. 2 months ago

A commonly used technique is to expose the subframe to be shot noise dominant vs read noise dominant. This is done by exposing a frame till the sky background is some factor of read noise squared - usually a factor between 3 to10 or so. To do the calculation you need to know read noise, gain and offset of the camera.
By exposing to be shot noise dominant, the SNR improvement by stacking approaches that of a single long exposure with the same integration time but with reduced saturation issues.
 

Read More...

Ken Self replied to the topic 'INDI/KStars for Windows info' in the forum. 2 months ago

INDI cannot run on a Windows machine. So you need a Linux/Mac running INDI and run KStars on Windows with remote server settings in the profile.
On previous versions of KStars I found the Linux version to be more stable so I run KStars on Windows Subsystem for Linux (WSL.) That requires an Xserver on Windows and a bit of tweaking in WSL.So if you find the Windows version less stable than you like that is an option. I wrote it up at indilib.org/forum/ekos/8596-re-re-re-re-...m-for-linux-wsl.html

Read More...

To control GPIO pins you can also try the indi-asi-power driver.
Latest version uses GPIO 21 for DSLR shutter control but is not yet in the nightly builds. check out indilib.org/forum/ccds-dslrs/8982-issue-....html?start=12#68327
If you want to build from source note that I have moved it to branch asidslr2
it would be fairly simple to convert it to use different pins

Read More...

Ken Self replied to the topic 'Align module - off target' in the forum. 2 months ago

universalmaster wrote:

maxthebuilder wrote:
I'm pretty sure the alignment module still writes that it is centered on the last goto target (e.g. NGC 7023). If it actually wrote "star" or "empty sky" or something when it puts the target off-center it would make sense. I will take a snapshot next time it happens, maybe my memory is wrong....

I think your memory is correct. I've had the align module name the spot where I'm pointing with the nearest known object (e.g. NGC2573 when I'm pointing at the SCP). In other cases I've had it label the coordinates as "star" or "empty sky" when I've moved slighly off target on a nebula or open cluster to get better framing. Or even if I've drifted off target similar to your situation due to a tracking problem. So I guess there is some subtle algorithm that makes a best guess of the target name.



Read More...

I've just pushed through some changes. I've made the DSLR timing a lot better (around 1ms for even long exposures) , fixed some edge conditions, tidied up the messages and set more sensible defaults. They should appear in due course in the nightly builds. Let me know of any improvement requests.
Out of interest, do you use the DSLR standalone and capture the images on its memory card or is it connected to Ekos with USB cable for image transfer?
I'm wondering if it is possible to integrate with the camera driver somehow e.g. by snooping.

Read More...

Ken Self replied to the topic 'Align module - off target' in the forum. 2 months ago

universalmaster wrote: This seems counter intuitive to me. If the last allignment/plate solve was too a certain target, then this should still be the target after some imaging. I don't see a benefit of the target "driftigt" due to guiding and dithering, but maybe I'm missing something?
Is it possible to put allignments into the scheduler to circumvent drifting too far? For example realign every hour or so....

It seems that you and the OP have differential flexure so that the guide scope is driftng away from the imaging scope. Since its the guide scope determing the pointing during guiding it is moving the imaging scope off target - that is, the coordinates of the mount are now different. No different to slewing (slowly) to a target that is close by the one you started on. So the alignment module is going to align you to where the mount coordinates are now since that is what it understands to be the target.
Using the last target coordinates is not a good idea. You could have slewed intentionally to a completely different target.
The real solution is to fix the differential flexure.
A temporary solution is to repoint the mount to the original coordinates before aligning or, better still, load and slew to the first image taken.

Read More...

I've added shutter control in my Fork at github.com/ken-self/indi-3rdparty.git
Checkout branch asidslr
You'll need to build from source as it is not yet ready for pushing to the nightly builds. Some refinement needed but the basic operation looks ok. I can only test by attaching a LED to the relevant GPIO pin.
It needs some work at the shorter exposures and exposures with decimal places.

Read More...

Ken Self replied to the topic 'Headless Ubuntu on Raspberry Pi' in the forum. 2 months ago

You might want to check out my thread on running Ubuntu without a desktop indilib.org/forum/general/8885-running-k...remote-computer.html
On my 1GB RPi3 its not blindlingly fast but it is usable.

Read More...

I will work on that. Just needed to know which port was being used.

Read More...