I think I need to delete the Optical Train config data. Where is it located on MaxOSX?
(KStars crashes whenever I try and create a new train)

I believe the info is located in userdb.sqlite in the directory
/Users/USERNAME/Library/Application Support/kstars

Thanks!
I deleted that file, and after restarting KStars and rebuilding my profile, all seems to be working now.

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.

I can confirm this issue on some setups. Looking into it.

I'm probably missing something, but is there any way to edit the optical train prior to connecting devices?

Maybe I'm doing this wrong, but on my Celeste 8" I have the optical train set with the native FL and ASI camera. If I add a reducer, is that a new optical train? ... or do I just edit the current Primary?

Ron

If you only ever want that train to have the reducer, then just edit it to include it. If you want 2 separate trains, with/without the reducer, I think 2 separate trains would be the correct approach.

Hello,

AS Ron, I would be able to edit the OT before Ekos connection. In this way you build a library of OT then you call the right one into the modules of Ekos.

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.

Correct, you must connect first before configuring the trains. This isn't going to change.

Do the optical trains store the details like Camera name, Frame size? As the driver maybe common (eg. ZWO Camera).

I may be having a similar problem. With the latest version of kstars-bleeding, I enter my "optical train" data including a 0.7 focal reducer. In the Alignment Module, the telescope focal length and plate solver camera parameters (which is my secondary) are correctly shown for a telescope without a reducer. The reducer value of 0.7 is also shown.

I've attempted some plate solving recently with the FR and I always get the "Not Enough Stars in the Picture" and "check FOV data" even when there are lots of stars in the frame. This function worked fine before I added the FR.