Come and join our community. Expand your network and get to know new people!
It was started from the command line. I have renamed the driver configs and now it connects correctly.
I run a scheduled session starting after twilight to maintain the ASAP and the Twilight schedule. It was completed within the job constraint time minus 1 hour.
As it didn't complete the session it rescheduled it 2 days later. This confirms Pauls findings.
Settings usually sits in the ".indi" folder, in your "home".
But you mostly get this kind of error when your "indi_sv3055_ccd" binary doesn't match the loaded library (ie the SDK version).
Did you start the driver from "command line", or from the Ekos GUI ?
Hi Collin, i have tried now to connect the camera once again but this is an error I am getting:
2021-10-26T08:11:40: Driver ./indi_sv305_ccd: Camera(s) found
2021-10-26T08:13:06: Driver ./indi_sv305_ccd: stderr EOF
<delProperty device="SVBONY SV305M PRO 0"/>
Child process 2479 died
2021-10-26T08:13:06: Driver ./indi_sv305_ccd: restart #2
2021-10-26T08:13:06: Driver ./indi_sv305_ccd: Camera(s) found
And now the camera could not connect anymore. It seems that something in the setting is broken. But without camera connected in Ekos I don't know how to purge the configuration again.
Could you please post me a new capture of the "main control" panel like this one :
Sorry! I personally used this possibility for SX-Wheels (not MDPD) successfully, and was not aware of the restrictions with MDPD-drivers. I remember however that it is/was? possible to tweak such drivers with custom XML-files (/usr/share/indi). Perhaps somebody has done it this way and can help?
I found the same issue with the GPS dongle not getting a fix due to local electrical noise from the Pi or Beelink PC.
To solve it I just added a 5m USB extension and at 5m away the GPS fix is near instant.
They're used for capture flat frames at the same focus position.
Hi Collin, I haven't found any setting like that so I have purged the configuration, reconnected the camera and now it works!
What about using the mount directional keys? Does this move the scope in the mount control panel?
I see that there is a Talon 6 INDI driver available for controlling a roll-off-roof observatory. Is this being used in the wild to automate observatories via KStars/Ekos? I see it hasn't been modified since 2019 so I'm wondering how full-featured it is compared to the ASCOM version. Any real-world experience to share out there?
My observatory roof will indeed strike my large OTA, so I'm trying to find a solution that will suspend a sequence, park the mount, confirm parking with a sensor, and close the roof if dangerous conditions are detected. And if it can resume everything automatically and safely when conditions improve, fantastic!
BTW, I know I should lower my mount so there's no possibility of a roof strike -- no amount of automation is worth that cost and heartache. It's more easier said than done, though -- I'm having a hard time finding a fabricator who can make a new custom pier.
That's correct. Unlike many other mount brands, iOptron PEC handling fiercely fights with mount guide inputs. I've tried it a dozen times on three different mounts with the internal guider and PHD2 and the result was clear each time: if you're guiding an iOptron mount, do not use mount-based PEC. My results were always noticeably worse, and often were disastrous.
The thing is, none of my iOptron mounts have anything but smooth PE... and smooth PE is easy to guide out.
Predictive PEC in PHD2 or GPG RA Guiding in KStars work great, though. Just find the worm period of your mount and specify it in the software vs letting the software "guess" at your worm period.
MDPD = Multiple Devices Per Driver. With such drivers, aliasing would not work. When you start this driver with two ASI EFWs plugged it, what are they exactly named in INDI control panel?
Here are some, hopefully I give you what you want, otherwise, please give me specific parameters for which you want defaults: