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.

But when you create à profile, you can do without starting Ekos. So what is the difference ?

@Robert: It could be the following bug I found while trying to work with "optical trains"!?
Seems like the calculations of the focal length are done the wrong way around, resulting in a excessive magnification, which the solver cannot handle:


FL = 2839mm/0.7 = 4050mm (wrong!) instead of FL = 2839mm*0.7= 1988mm (correct!)

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, so the opticaltrain UI cannot have it in its comboboxes.

Anthony

Optical Trains work OK for me.
But I did have a problem trying to set up a DSLR Lens - it didn't worked right for me so I ended up setting it as refractor (which worked fine).

I found one issue where it saves the effective field of view in the database and it wasn't considering focal reducer. This could lead to some issues. It is now fixed in KStars 3.6.2

Bingo.

Last night I put the scope on a well populated star area to do a plate solve. The parameters in the "Plate Solving" tab (FL, FOV of guide camera, etc) were as one would expect without a focal reducer. The value of the focal reducer (0.7) was also displayed.

Attempted a plate solve and it failed. Got the usual error message.

I tried to change the aperture and FL parameters, but they were locked. The software would allow me to change the guide camera FOV to reflect the FR. Attempted another plate solve: success. I went to another tab and when I came back to the plate solve there were parameters just like yours where it looked as if the software applied the FR in the wrong direction. However, the guide camera FOV was now correct. I did another plate solve just for verification.

I see Jasem says he has it fixed in the latest build so we can try it out.

Bob

Is it possible to implement considering the focal reducer factor in 3.6.1 stable as well?

Thx, Bernd