Anthony Hinsinger replied to the topic 'Ekos Optical Trains' in the forum. 3 months ago

In the profile, you only specifiy drivers, not devices, this is a big difference : as I said before, if you setup your profile with the indi_asi_ccd driver, it cannot know it will detect an asi2600mm and an asi120mm before you really start the profile.

Anthony

Read More...

Anthony Hinsinger replied to the topic 'Ekos Optical Trains' in the forum. 3 months ago

Not sure it's really possible to set the trains before connecting to indi, because it's not possible to know the real devices behind an indi driver, and that's the case with multiple device drivers. For example the ZWO drivers can detects multiple zwo cameras, but it's impossible to know before starting/connecting the driver.

Anthony.

Read More...

Anthony Hinsinger replied to the topic 'Ekos Optical Trains' in the forum. 3 months ago

Hello,
I'm playing with optical train (kstars 3.6.1 on a Raspberry pi with ubuntu 22.04 arm64) and I've a problem.
I've two train, one is my main "imager" train with the filter wheel, focuser and main camera, the other is my "guide" train with just the guide cam and scope to guide.
When I first connect ekos, all the ekos modules where the imager train is selected have the select filter box empties. To populate it, I need te set my guide train active, and then come back to the imager train. I've to do it separatly for each modules (capture, focus, align)

Anthony.

Read More...

Hello,

I'm using a eqmod mount (eq6r) and I'd like to understand how the encoder values stored in the ParkData.xml file are "converted" to celestial coordinates.
Especially, when you powerup the mount, how does it assumes (or compute) "thoses" values are pointing to ECP, (or any other park direction if you've changed it)
It is a state saved into the mount ? not clear to me ... :S

thanks to help my curiosity :)
Anthony.

Read More...

the crash of kstars was due to a default gcc option when building 21.04 packages and has been fixed now.

Read More...

Hello,

I've reported a bug on the KDE bugtracker with kstars-bleeding (from the unstable PPA) on ubuntu 21.04, which happen as soon as you start the application.
I've provided a backtrace, but is the KDE bugtracker the prefered way to submit a Kstars bugs ?

Thanks
Anthony.

Read More...

So ... you can now [SOLVE] this one :P

Anthony.

Read More...

Hello,

same problem as explain in this topic indilib.org/forum/mounts/9705-problem-to...mod-with-ubuntu.html (where I attached a log file)
An EQ6-R (with pegasus  eqdir cable) on an Ubuntu 20.10 with ekos/indi 5.3.5/1.9.0 from the stable ppa.
Crash one or two seconds after the connection.

Anthony.

Read More...

sure:

[2021-05-24T00:38:01.588 CEST DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[DEBUG] Connecting to /dev/serial/by-id/usb-Pegasus_Astro_EQDIR_Stick_PA40UU16-if00-port0 @ 9600 "


Read More...

Hello,

I've the exact same problem on an Ubuntu 20.10, with the last kstars/indi from the stable repo. (3.5.3 / 1.9.0)
When I connect the eqmod driver, I seems to connect (all the tabs appears, and looks good) then one or two seconds later, it crashs.

I've attached a logfile. It seems to have a connection issue at line 523. It also complains the port is already used sometime, but it's not the case

I tested the same mount/cable on a Macos with the last kstars (3.5.3 with indi 1.9.0 embedded) ... it works perfectly well.
I tested the indinighly PPA ... (indi 1.9.1) and have the same problem.
I've to admit I had some issue on linux with all my "serial" device since upgrading to 1.9.0 (for example my PPBA powerbox is hard to connect sometimes...)

I never had any issue with the same ubuntu with indi 1.8.x.

Don't hesitate to ask me anything needed to find the problem.

Anthony.

Read More...

Anthony Hinsinger created a new topic ' Ubuntu PPA and gsc' in the forum. 2 years ago

Hello,

The Ubuntu stable PPA doesn't contain GSC packages for Groovy (20.10).
Any problem with this ubuntu release ? or just not done yet ?

Thanks
Anthony

Read More...

Hello,

I just had my first 100% automated night using the Ekos scheduler. It was near perfect !!! but I had some small issues coming from misunderstood concept, so I have now some questions :) I scheduled two targets, one was high in the sky early, the other after 2am, so I use an object altitude constraint (>65°).

My first questions are :

- The first target drop below the 65% constraint at ~90% of job done, but the scheduler pauses until the next day, pausing also the second job, so I had to delete the first target to start the 2nd one (may be a "live" reorder has been enough ??)
- Is the scheduler able to start a job "in the middle" of another job with less priority - as soon as the highest priority constraint is reached - and then resume lowest priority job when it's finish (assuming the low prio job doesn't have any constraint so it can start before the highest one)
- what is the mount behavior between two targets when there is some time to wait between both ? does it park ( even with preemptive shutdown uncheck)
- Is there any examples of startup/shutdown scripts more complex that the one in the documentation ? (using indi to talk to devices for examples...)

I also had a display bug in the job list : the end time of the running job decreases each time a frame was done :) (it seems its calculated this way : start time + job remaining time instead of current time + job remaining time)
I'm using kstars 3.5.0 nightly build

Thks for support and for this amazing tool !

Anthony.

Read More...

What an explaination :)
So yes, I was always starting my DSLR (and then ekos) in Bulb mode... so it explain why it was working w/o bulb force

Anthony.

Read More...

@Herrhausen, Are you sure Force Bulb to ON has any effect when camera is in bulb mode ? i've not seen any difference in my tests.

Anthony.

Read More...