Christopher,
Everything seems to be working now when slewing to different targets.
Seems to get some clear skies tomorrow and can get it tested with guiding as well.

Read More...

Bug filed - and solved within minutes.
I've rebuilt indi from git and confirmed that slewing now works on GEM45 with the iOptronV3 driver.

Read More...

Running ASI1600mm, ASI120mm mini, EFW, EAF, building from git on RPI4. No issues (anymore).

I did have an issue with the ASI1600mm where it would fail to capture, and the image from the ASI120mm would occationally pop up in the preview instead.
Deleted xml-files from .indi, and set everything up from scratch again. After deleting the xml-files, I saw that the ekos driver setting for both ASI120mm and ASI1600mm were both set to main scope. I set ASI120mm to guide scope, and everything were working again. Not in front of kstars at the moment, so tick boxes could have different names.

Read More...

Still have this problem.
Indi built from git on RPI4. Running kstars either on the RPI or on windows. GEM45 runnin the iOptron v3 driver.
When the GEM45 slews, it will slew to the correct location and stop, but indi/ekos does not detect that the scope has stopped. Status in ekos is that the scope is still slewing even if has stopped. The scope will automatically start tracking if I press the red stop button in ekso scope controls.
I have tried to delete the .indi folder and set up everything from scratch, but no solution.
Same behaviour with handset attached and without.

Ideas anyone?

Read More...

I have an Ioptron GEM45 updated to latest firmware, no hand controller attached.
Raspberry PI is running indi from git sources.Windows laptop is running kstars/ekos from nightly builds.

Tracking does not automatically start after a slew.
I can manually push tracking under scope controls in ekos to start tracking after a slew, and everything will work fine
Tracking is not automatically enabled after an automatic meridian flip.
Log attached.

Read More...

I have the same failure with my as1600mm with indi and asi driver compiled from the latest git.
Capture fails.

$ cat /sys/module/usbcore/parameters/usbfs_memory_mb
16

$ echo 1024 /sys/module/usbcore/parameters/usbfs_memory_mb
solves the problem

Read More...

GEM45 running latest firmware (V20210105), raspberry pi running indi from git sources, laptop running kstars nightly dev snapshot for windows.
Ekos profile using telescope driver for GEM45.

When issuing Search for home position for the mount, ekos responds: "Home search is not supported in this model".
Search for home position is supported in this model (Command: MSH#): www.ioptron.com/v/ASCOM/RS-232_Command_Language2014V310.pdf

Read More...

I'm running EKOS 3.5.0 compiled from source on a raspberry pi 4 8 GB (64-bit ubuntu mate) and experienced the same.
I was about to take flats, and all tickboxes for focus was unchecked in the capture menu. The first thing Ekos did was to call focus upon filter change.
Changing focus when taking flats is probably not what we want.

Else, I must say that stellarsolver and multistar guiding is working really great. Great work!

ASI1600mm Pro, Zwo EFW, Zwo EAF, GEM45.

Read More...

Eivind replied to the topic 'ASTAP Issue' in the forum. 10 months ago

I never got astap to blind solve. So before polar alignment, I'll double click Polaris in the kstars star map, then do an ASTAP solve with "do nothing" checked to set the camera wcs. Then run polar alignment.

Never works unless I track Polaris in kstars first.

Read More...

Eivind replied to the topic 'Quick Controls Widget?' in the forum. 1 year ago

El Corazon wrote:

astromyr wrote: Great! I’ve been wanting capture controls in the fits viewer. l.e. exposure time, gain, start, stop. And perhaps focus. Integrated in the viewer (the same way as the histogram split view) is better for my usage pattern than a floating widget that can hide other stuff or become hidden.


I am not sure how that would work. Once the FITS file is acquired, it is too late to change the .esq Sequence file that controls the raw data acquisition in the scheduler.

Can you explain how you see that integration in the FITS viewer to feed back on the saved .esq file?


It's only for live view during framing and focusing. Once the sequence is running, you go to bed :-)
Not everyone is running sequences. I think a manual work flow is common for beginners and quick OSC imaging sessions.

We already have the mount control widget for slewing and gotos, and a similar panel for capture, focusing and solver would be nice - especially if they were integrated in a tabbed manner in the FITS viewer. With smaller screens, it is easier to have everything available in a maximized viewer window, than having to rescale and move multiple windows to get everything into place .

Read More...

Eivind replied to the topic 'Quick Controls Widget?' in the forum. 1 year ago

Great! I’ve been wanting capture controls in the fits viewer. l.e. exposure time, gain, start, stop. And perhaps focus. Integrated in the viewer (the same way as the histogram split view) is better for my usage pattern than a floating widget that can hide other stuff or become hidden.

Read More...