Hi Anders,
I started using an AF3 with my setup (TS 115 f/7 reduced to f/5.6 -> 645mm focal length, ASI1600MM-Pro) a couple of weeks ago only and I've had good results using the polynomial method.

I use the full frame with an annulus between 25% to 70%, exposures are 1 second long, binned 2x2 (I've setup an average of 3 images for exposure, but I'm not sure if this parameter is used in the full-frame mode). Autofocusing takes only 8 exposures and the solution falls consistently within my critical focus zone. The whole process takes approximately 140 seconds.

I'm curious, why does your target move that much during focusing?

I leave auto-guiding on during focusing (I guide a non-moded HEQ5 with a 60mm guidescope at f/11 with an old ASI120MM and my guiding is consistently around 0.5" RMS*), but even if off it will move very little if I've got my PA right. 

* that is, when the ASI120MM is not glitching... :(



Dear Hy,
Here are the images (60 lights taken sequentially, and 16 darks).

File Attachment:

File Name: M5_lights_guider_02.zip
File Size: 4,881 KB

File Attachment:

File Name: M5_lights_guider_03.zip
File Size: 4,874 KB

File Attachment:

File Name: M5_lights_guider_04.zip
File Size: 4,877 KB

File Attachment:

File Name: M5_darks_guider.zip
File Size: 1,759 KB

File Attachment:

File Name: M5_lights_guider_01.zip
File Size: 4,868 KB

These images are not binned but I normally run the guide camera binned 2x2 (less noise helps my guiding more than higher angular resolution). 
Hope they will be of help. 

Best regards,



Of course Hy, I'll take them as soon as I get another clear night (unfortunately, most likely not in the next 7 days according to the local weather forecast).

I should add more specifics: the situation presented itself during guiding calibration. The central area of the globular was in the guide frame and the auto star selection algorithm tended to pick a bright area within it as guide star. This inevitably resulted in a "guide star lost" error during calibration. So, in practice, the guiding could not really start in that scenario.

I guess I could try calibrating a bit off-target and then moving back to it to see how having the globular in the guide frame affects the actual guiding...

I'll post back as soon as I have the frames.



Or avoid mixing SEP Multistar and globular clusters with my current setup ... grin.png



I was trying the SEP multistar guiding algorithm last night -to much delight I should say (thanks for a great tool)- when I stumbled on a small problem potentially affecting any guiding based on automatically selecting stars: 

My setup has a fixed guidescope pointing in the same direction of the main scope and this means the target is partially visible in the guide frame. When pointing at a globular cluster the star selection algorithm just goes crazy....

Is there a way to tell the guide module to avoid certain regions of the guide camera frame?

Or to select stars only from certain areas?

That would be a good option to have also in the case there are areas affected by excessive aberrations or permanent defects...

AWay from the globular, the SEP multistar performed amazingly well, at times achieving RMS below 0.4 arcsec (HEQ5, 60/700mm guidescope, ASI120mm camera, 2 sec exposures, 0.7x guiding rate).

All the best,


Ricardo Serpell replied to the topic 'Post your INDI Setup!' in the forum. 12 months ago

I started trying INDI about a year ago as I was transitioning from unguided to guided exposures. I recently finished putting together the setup shown in these pictures.

I use Astroberry on a Raspberry Pi 4 to control everything remotely. There is a single cable going to the mount from the rest of the world: a 12V power cable, coming from a 12.5A source.

I wanted to have the least number of cables running across moving parts: the raspberry sits on the main telescope and so it moves with it, together with the cameras and electric filter wheel (and I hope an electric focuser in the future) that are connected to it (well, EFW is in fact connected to the ASI1600MM hub, the ASI120MM not, as I felt it worked better plugged in its own port at the raspberry). The raspberry connects to the mount via Bluetooth.

There is a power box (described in a previous post ) attached to the RA arm of the mount. It sources power to the mount and the camera cooler (12V) and to the Raspberry Pi (5V). Power cables to the raspberry and camera cooler run through the declination arm.

It's been a long learning process, but here is the first HaRGB image I have done with this setup: https://www.astrobin.com/thmb4v/

I'm grateful to all the people n this forum. You all have been a source of invaluable help.

Best regards!


porkyhttp wrote: If there is a version of EkosLive that works offline, why do you have to built another system that do the same things??? In Atikbase seems thai it is present and use MongoDB to do some stuff.

I haven't found much information about Ekos live outside the Stellarmate pages (I use Astroberry), neither about it's offline version. Can you point me to instructions on how to implement it ?

I'm looking for a simple, offline, free, solution to interact with Ekos through a smartphone or tablet, that could be customized for mine (or anyone's) requirements. I think web-based is perfect. If Ekos live offline can do that and is available to us all, then no need to look further. I guess customizing it's Interface would be a matter of simple html and css editing.



[quite="rickbassham" post=58200]You've inspired me to create this: github.com/rickbassham/ekos-web

It doesn't control the session, but will let you keep tabs on it from a mobile device.[/quote]

Looks like a great starting point. I'll check it.