Try putting a one-second delay in the "Delay" field. What I discovered some time ago is that a big sensor camera (with large file sizes) doesn't have enough time to finish writing the file to drive before the next image is ready - because the exposure time for bias frames is so short. I add a one or two second delay always, for all types of frames for that reason.

Read More...

From this post: indilib.org/forum/ekos/10678-fov-feature-request.html

"KStars has a good FOV system where I can specify my imaging specs, including FOV position angle, but it's a bit clumsy to drill down to the dialog to edit the FOV rotation. My request is twofold: First, some simple keyboard shortcuts to quickly change the displayed FOV rotation angle. From there, once I'm happy with the FOV framing, I'd like a menu command or something to send that FOV framing (including the rotation of course) to the alignment module to slew to the FOV, using the solver to precisely match the target - just like the Load & Slew functionality. This would be a huge timesaver! (and really cool!)"

Read More...

I have a ZWO EAF with the temp sensor connected to KStars/Ekos 3.5.8 Stable running on Ubuntu 20.04 and it indeed does work. Takes some treaking of the parameters (like everything else) to optimize the focus process for your rig. There's a spot on the Focus Module to select the source of the temperature used for re-focus on delta-temp and the current & delta reading just below the pull-down menu (see picture)

ASI EAF.CONNECTION.CONNECT=On
ASI EAF.CONNECTION.DISCONNECT=Off
ASI EAF.DRIVER_INFO.DRIVER_NAME=ASI EAF
ASI EAF.DRIVER_INFO.DRIVER_EXEC=indi_asi_focuser
ASI EAF.DRIVER_INFO.DRIVER_VERSION=1.0
ASI EAF.DRIVER_INFO.DRIVER_INTERFACE=8
ASI EAF.DEBUG.ENABLE=Off
ASI EAF.DEBUG.DISABLE=On
ASI EAF.POLLING_PERIOD.PERIOD_MS=500
ASI EAF.CONFIG_PROCESS.CONFIG_LOAD=Off
ASI EAF.CONFIG_PROCESS.CONFIG_SAVE=Off
ASI EAF.CONFIG_PROCESS.CONFIG_DEFAULT=Off
ASI EAF.CONFIG_PROCESS.CONFIG_PURGE=Off
ASI EAF.FOCUS_MOTION.FOCUS_INWARD=On
ASI EAF.FOCUS_MOTION.FOCUS_OUTWARD=Off
ASI EAF.REL_FOCUS_POSITION.FOCUS_RELATIVE_POSITION=0
ASI EAF.ABS_FOCUS_POSITION.FOCUS_ABSOLUTE_POSITION=30098
ASI EAF.FOCUS_MAX.FOCUS_MAX_VALUE=100000
ASI EAF.FOCUS_ABORT_MOTION.ABORT=Off
ASI EAF.FOCUS_SYNC.FOCUS_SYNC_VALUE=0
ASI EAF.FOCUS_REVERSE_MOTION.INDI_ENABLED=On
ASI EAF.FOCUS_REVERSE_MOTION.INDI_DISABLED=Off
ASI EAF.FOCUS_BACKLASH_TOGGLE.INDI_ENABLED=On
ASI EAF.FOCUS_BACKLASH_TOGGLE.INDI_DISABLED=Off
ASI EAF.FOCUS_BACKLASH_STEPS.FOCUS_BACKLASH_VALUE=30
ASI EAF.Presets.PRESET_1=0
ASI EAF.Presets.PRESET_2=0
ASI EAF.Presets.PRESET_3=0
ASI EAF.Goto.Preset 1=Off
ASI EAF.Goto.Preset 2=Off
ASI EAF.Goto.Preset 3=Off
ASI EAF.USEJOYSTICK.ENABLE=Off
ASI EAF.USEJOYSTICK.DISABLE=On
ASI EAF.SNOOP_JOYSTICK.SNOOP_JOYSTICK_DEVICE=Joystick
ASI EAF.FOCUS_TEMPERATURE.TEMPERATURE=21.629999160766601562
ASI EAF.FOCUS_BEEP.ON=On
ASI EAF.FOCUS_BEEP.OFF=Off
ASI EAF.VERSION.VERSION_FIRMWARE=3.1.9
ASI EAF.USEJOYSTICK.ENABLE=Off
ASI EAF.USEJOYSTICK.DISABLE=On
ASI EAF.SNOOP_JOYSTICK.SNOOP_JOYSTICK_DEVICE=Joystick

Interesting - OK thanks. Maybe I'll poke around in the module and look into it.

Read More...

+1 for me too - I made this request five months ago! Would be super handy!
indilib.org/forum/ekos/10678-fov-feature-request.html

Read More...

Scripting question: Is the Directory listed under the File Settings in the Camera & Filter Wheel Module available from indi_getprop? I would assume it's in the RECORD_FILE.RECORD_FILE_DIR property, but I get 'indi__D_' in the path rather than the directory name.

ZWO ASI1600MM Pro.RECORD_FILE.RECORD_FILE_DIR=/home/airbourn/indi__D_
ZWO ASI1600MM Pro.RECORD_FILE.RECORD_FILE_NAME=indi_record__T_

Here's the script I put together to check if the Flip Flap is open, close it if it is, and wait for it to report closed. I also have the companion to open it if it's closed.

BTW, a side note about the Flip Flat: Don't use it to generate flats immediately after a set of lights during a job if you have an OAG. Don't ask why I know this...

#!/bin/bash

#Shell script to close/park the Flip Flat if the cap is open
#AirBourn 2022

debug=false

coverProp="Flip Flat.Status.Cover"
motorProp="Flip Flat.Status.Motor"

#Delineator
IFS='='

coverStatus=$(indi_getprop "$coverProp")
read -ra cArr <<< "$coverStatus"
coverString=${cArr[1]}
if $debug; then echo "  cStatus: ${coverStatus}"; fi
if $debug; then echo "  cString: ${coverString}"; fi

motorStatus=$(indi_getprop "$motorProp")
read -ra mArr <<< "$motorStatus"
motorString=${mArr[1]}
if $debug; then echo "  mStatus: ${motorStatus}"; fi
if $debug; then echo "  mString: ${motorString}"; fi

if [[ "$coverString" == "Open" ]]
then
	if $debug; then echo "  Sending Close Command"; fi
	indi_setprop "Flip Flat.CAP_PARK.PARK=On"
	indi_setprop "Flip Flat.CAP_PARK.UNPARK=Off"
	
	while [ $coverString != "Closed" ]
	do
		coverStatus=$(/usr/bin/indi_getprop "$coverProp")
		#echo "Cover: ${coverStatus}"
		read -ra cArr <<< "$coverStatus"
		coverString=${cArr[1]}
		if $debug; then echo "  Cover: ${coverString}"; fi
		
		motorStatus=$(/usr/bin/indi_getprop "$motorProp")
		#echo "Motor: ${motorStatus}"
		read -ra mArr <<< "$motorStatus"
		motorString=${mArr[1]}
		if $debug; then echo "  Motor: ${motorString}"; fi
	done
fi

if $debug; then echo "  Cover is ${coverString}"; fi

exit 0

It's working now. I ran a couple of jobs overnight (first clear night in a long time!), and in the morning while I was transferring images, I started experimenting with the indi_getprop and indi_setprop on the command line. I don't know if that cleared out some buffer or initialized something, but it's working now. The script execution is reported in the status and the path stays in the Scripts Manager. The Pre-Capture script works for Previews, too. (In the case below, the script actually fails because I wasn't running the Simulators, but you can see the error in the status) Thanks for your help, Jasem!

Yes - just did that. Updated to 3.5.8 Stable Build 2022-03-24T22:52:45Z and it acts exactly the same.

Read More...

Bizarre. Tried your test. I get the exact same non-working behavior as mine. No indication anywhere that it ran, no change to the gain in the module UI, and the script path disappears from the Scripts Manager. Yes the script file is executable (+x). I'm using 3.5.7 Stable on Ubuntu 20.04.

Before I run the job:

[2022-04-08T12:42:02.546 CDT INFO ][   org.kde.kstars.ekos.capture] - "Warning: temperature delta check is selected but autofocus process was not started."
[2022-04-08T12:42:02.556 CDT INFO ][   org.kde.kstars.ekos.capture] - "Job requires 1.000-second  images, has 0/1 frames captured and will be processed."
[2022-04-08T12:42:02.594 CDT WARN ][   org.kde.kstars.ekos.capture] - Skipping flat/dark cap since it is not connected.
[2022-04-08T12:42:02.594 CDT INFO ][   org.kde.kstars.ekos.capture] - "Capturing 1.000-second  image..."
[2022-04-08T12:42:03.636 CDT INFO ][           org.kde.kstars.indi] - "FITS" file saved to "/home/airbourn/Pictures/Test/Light/Red/Light_Red_1_secs_003.fits"
[2022-04-08T12:42:03.678 CDT INFO ][   org.kde.kstars.ekos.capture] - "Received image 1 out of 1."
[2022-04-08T12:42:03.679 CDT INFO ][   org.kde.kstars.ekos.capture] - "Captured /home/airbourn/Pictures/Test/Light/Red/Light_Red_1_secs_003.fits"

I've tried a number of things. I wrote a python script that uses the indiclient (PyIndi) to connect to the server, watch my FlipFlat device, check the CAP_PARK property, and if it's UNPARK, then set the property to PARK and send the new switch to close the cap. It works perfectly from the command line. I set up just a one capture sequence job in Ekos (capture three short light frames) and setting that .py file as the Post-Job script. When I run the job, I get zero indication that Ekos did anything with the script and the file path disappears in the Scripts Manager dialog. I don't see anything in the status area or the logs or anything.

I tried a .sh shell script to call "python script.sh" with full pathnames, tried all four of the script boxes in the Scripts Manager, anything I could think of. I just get zero indication anywhere and the script path disappears.

I'd like to see just the simplest of examples of a script that works in the Scripts Manager. There's got to be something simple I'm missing - specific path or file suffix or ?

Read More...