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

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.

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. teatv.ltd/teatv download
hellodear.in

Apparently there is a bug in the system. If you set your telescope FL correctly in telescope definition area, then in the optical train add the focal reducer, it dose not "do the math" and give the correct focal length. You have to set the focal length WITH the reducer factored in the telescope definition field. In my case, instead of setting 710mm and a reducer of 0.8 and getting around 586mm, I have to set the telescope at 568mm. Jasem is aware of the issue and there should be a fix pushed out in a few weeks to the new version.

Apparently DATE-OBS field is not being populated in fits files. I've heard this from another spectroscopist.

I have been using indi/kstars/ekos for several years for astro spectroscopy, where the platesolving camera via flip mirror is separate to the spectro camera which is never platesolving as it only sees the slit spectroscopy images through the spectrograph.

Not including DATE-OBS is a total deal breaker as the isis spectroscopic reduction software commonly used by amateur spectroscopist needs it.

Is there a particular reason why the new optical trains system does not populate this field of the fits header? When using indi for actual science not just pretty pictures, the actual observation date and time are essential information.

I'm seeing DATE-OBS in a regular capture. How to reproduce your issue?

Hi!

I'm also doing spectroscopy. My main camera does not do any plate solving. And I do not get DATE-OBS in the fits headers. At least I did not last night. Below is a header.

Magnus

SIMPLE = T / file does conform to FITS standard
BITPIX = 16 / number of bits per data pixel
NAXIS = 2 / number of data axes
NAXIS1 = 1391 / length of data axis 1
NAXIS2 = 1039 / length of data axis 2
EXTEND = T / FITS dataset may contain extensions
COMMENT FITS (Flexible Image Transport System) format is defined in 'Astronomy
COMMENT and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H
BZERO = 32768 / offset data range to that of unsigned short
BSCALE = 1 / default scaling factor
ROWORDER= 'TOP-DOWN' / Row Order
INSTRUME= 'Atik 314L' / CCD Name
TELESCOP= 'Celestron NexStar' / Telescope name
OBSERVER= 'Unknown ' / Observer name
OBJECT = 'HD208501' / Object name
EXPTIME = 4.500000E+01 / Total Exposure Time (s)
CCD-TEMP= -1.502E+01 / CCD Temperature (Celsius)
PIXSIZE1= 6.450000E+00 / Pixel Size 1 (microns)
PIXSIZE2= 6.450000E+00 / Pixel Size 2 (microns)
XBINNING= 1 / Binning factor in width
YBINNING= 1 / Binning factor in height
XPIXSZ = 6.450000E+00 / X binned pixel size in microns
YPIXSZ = 6.450000E+00 / Y binned pixel size in microns
FRAME = 'Light ' / Frame Type
IMAGETYP= 'Light Frame' / Frame Type
FOCALLEN= 0.000E+00 / Focal Length (mm)
APTDIA = 0.000E+00 / Telescope diameter (mm)
FOCUSPOS= 735 / Focus position in steps
FOCUSTEM= 2.000E+01 / Focuser temperature in degrees C
END

Hamish and Magnus: Could you please post your optical trains? Jasem will likely have a better take on the data than I.
I have some spectroscopy files from my latest observing sessions in November and the DATE-OBS field is present. I don't understand the connection between plate solving and the appearance of the observation date, or how a spectrometer affects whether the field is present. INDI/Ekos isn't aware of a spectrometer.

Something I did notice: in my FITS header there is always a "Comment Generated by INDI"
FWIW, i did not see a similar line in the header from Magnus.

Bob

Hi!

I've been talking to Jasem and it seems he has fixed the issue - though I'm still not clear what it is all about.

The point about plate solving was/is my hypothesis that since optical trains are separate, maybe the main camera train is not "aware" of the plate solving data. Which again is odd since that is related to mount, not camera. So just an attempt to make sense of it all.

I'll post my optical trains later.

Magnus