Thank you guys, very helpful!
I was not aware of adjustable astrometry settings. Now I am. Will give this a try.

BTW, on my installation of Windows KStars the off-line solver is not available - only online (astrometry.net) and remote (RPI).
Thanks!
Max

I have a 32Gb card on my RPI. Installed ALL index files.

Hi Stash,
Where exactly these options are? Can't find...
Thanks!

see attachments

Funny.. I was looking for "sampling" option and could't find it. "Downsample" was of course there : )

OK...The verbose logging is really helpful. Downsample (8 ) reduced the solve time significantly. My time-limiting factors now are the image capture/upload (about 40 sec - I shoot RAW and the files are about 20Mb) and downsampling takes another 90 sec or so. Solving itself is pretty quick - 10-15 sec. So total is about 3 min on RPI. If I use Windows client (with either ansvr or astrometry.net) the whole align process takes about 90 sec.
I guess, I am OK for now.
Thank you all!
Max

Still not right :-

1). I use a RPI3 Raw files take 5-6 secs to download a 25mb RAW Canon file,Fits are about 35mb so take longer - so check your Sd card - use best quality and non fake - e.g. I use Sandisk Ulta A1 32gb.
Even using Indiserver on the RPI and Kstars on my PC it takes about the same to transfer (5-6secs) so check your WiFi coverage/speed or use wired ethernet.

2. I think I am right in saying Align module always uses FITS except when uploading to the net when it converts to JPG - check options there is a tick box for JPG upload.

3. Check you haven't too many index's loaded on the RPI or PC - i.e. ones you will never use as this also slows plate solving down

Hi stash and thanks!
As I mentioned - everything is quite reasonable on Windows client connected to RPI running INDI server.
The bottle neck is picture capture/download. Still reasonable. The whole align capture/solve process takes around 90 sec. Plate solving is 10-15 sec only.
I do use a wired connection when using Windows client.

When everything is run on RPI then it's much slower. This is to be expected, I guess, RPI is not a supercomputer.
The longest step there is actually downsampling (takes around 90 sec). Capture/download - 40-60 sec. Plate solving is quick.

I'll play some more and maybe will make things faster.

(yesterday/today encountered another problem - will start a new topic on that).
Thanks!
Max

Tonight was a bit of a disaster...
Last Thursday the skies were relatively clear so attempted to shoot the Wirtanen Comet. Didn't have any big problems and got the comet in the end.
Tonight the sky was clear again and I decided to give the comet another try.
Polar alignment was good. Capture/solve/slew to Navi, Betelgeuse, Alcyone. All went well, though slow (my goto's are not very accurate - takes a few iterations to center). Then I pointed/slew the mount to the comet (which was close to Alcyone) and the mount started to move (I think clockwise) constantly, making a couple of full circles and going below horizon before I noticed and stopped it. Cables were messed up and the mount was crooked. Strange...
I didn't install any updates since last successful session, didn't change the setup. Frustrated a bit.
max

All Ekos/INDI does is send the target RA/DE to the mount. The rest is up to the mount. Were you using Synscan driver or EQMod?

EQMod from nightlies (three weeks old or so). I am using SW AZ-GTi in EQ mode.
Thanks!

Post the EQMod log if you have one. You can also do this:
1. Remove ~/.indi/ParkData.xml
2. Make sure your mount is in its Home parking position.
3. Start EQMod driver.
4. Park Mount (it should stay as is)
5. Unpark and slew to any object to test.