Found one correction I could make. Setting the telescope aperture and focal length using the indi driver, rather than the mount tab, updated the solver.

Found one correction I could make. Setting the telescope aperture and focal length using the indi driver, rather than the mount tab, updated the solver. The FOV is now correct.

I noticed this as well. Even though you can update it in Ekos and it has a pretty save button, it does not seem to do anything. I have to change it in INDI and then it shows up correct in the solver tab. @knro is the Ekos telescope info and Save button used for something else?

Sorry for the double posts - traveling and slow connection. However, I am connecting to my gear, minus mount as no observatory, that is 5 time zones away though Attempting to prepare a session using the Telescope Simulator for a session when I return.

Anyhoooo... I also tired the --no-verify on and off. Still times out.

If anyone thinks of anything please let me know.

Set your simulators to have the same focal length as the real one, then set the sim camera to have the same number and size of pixels as your real one, then save that configuration so when you load your simulator profile, it emulates your real hardware.

Thank you. I should have been more specific. The cameras, EFW, and focuser are real and it is only the telescope that is simulated. The profile use all real drivers and equipment save the Telescope Simulator.

Aside, the CCD Simulator will not accommodate the sensor size needed to simulate the ASI1600.

The "save" button in Ekos mount was indeed not working due to a simple mistake that was fixed here . Hopefully I can make another release soon.

Thank you. Setting in INDI for now does correct the FOV for load and slew. The image still will not solve by loading the fits file...

1. Does the Load & Slew try to load RA/Dec from the fits file? If so how to I tell Ekos to put them there so they are there next time?

2. The time out was changed to 480s and it stopped at 180s. This was done to see if the fits file would solve since it is doing it blindly

3. How to get the Load & Slew to Use (or not Use) the mount coordinates as a guess on where it is?

4. the load and slew will crash if there is more than one option set. Capture and Solve the following works: -d 11-20 -d 21-30. Only -d 11-20 can work. Adding any additional options and it fails.

Is there anything I can change to get the load and slew to work. I added the solve log above.

Good questions.

1. Load & Slew tries to load RA/DE/FocalLength from file, if not found it falls back to current values or blind solve.
2. Will check it out.
3. It falls back to mount coords when reading fails. or suppose to at least.

I'll check the logs and get back to you.

If there are specific logs needed I can capture tonight. I am wondering if it is Kstars or mount. The above log is the astrometry verbose.

Thank you.

I found some issues... working on it now and will get back to you soon.