Thanks, great tip.
I had a Samsung T5 (500GB) spare so I decided to give it a try.
I did a few extra steps ensuring I had updated everything including the bootloader before I started.
After I had copied my SD card to the SSD the root partition was the size of the remaining disk. I used "GParted" to shrink the partition to 60GB to make it easier to copy. Then I created a new partition with the rest of the disk space and moved the Pictures folder to that partition.
Last night everything was OK. When I closed down EKOS this morning Kstars did not crash which is a first for me.
Need a few more nights to be sure but maybe using the 64 bit kernel has helped.
Crashed again last night with the fits viewer off. Same as before I find the scope pointing straight up. When I restart Kstars I get the message that a version of Ekos is still running. I am still running 32bit Rasbian so I guess I will try moving to the 64 bit version.
Thanks you so much! I never understood why I couldn't see my image on the Manager Screen. Now it all makes sense and once the session is started I can just display the Manager screen.
I am now switching off the fits viewer when I don't need it. It's is a bit of a pain because I like to be able to see a stretched version of the last sub. Since I have been doing this there have been no more crashes. I do notice that when I stop EKOS in the morning after a session the Kstars always quits (crashes?) too. If I stop EKOS before my session Kstars continues to run. Not really a usability issue but might point to the same problem.
Wolfgang mentioned "The latest captured frame is also visible in the Manager". I don't see the last captured frame anywhere except in the fits viewer. How to I make it visable and what is meant by "the Manager"?
I am running 3.5.3 but just to be sure last night I turned off the fits viewer and the whole session ran flawlessly.
Thanks Bart. I have got into the habit of always restarting the Pi before each session, I think I will also restart the mount each time. Ioptron parking is a little strange. Since I am running the latest firmware it does seem to be behaving much better.
I am running the latest release version of Kstars/EKOS/INDI on a Pi4. If the weather is good I setup my session and let it run to sunrise. This has been working flawlessly for a while but the last 2 nights Kstars seems to crash after one or two hours of imaging. Instead of the mount being parked in the morning (I have autopark set to 5am) the scope is pointing straight up. When I login to the Pi Kstars is no longer running. I re-start Kstars and then re-start EKOS. I get the message that another version of EKOS is running. I have no indication what has gone wrong.
Any suggestions how to debug this? Is the INDI device activity log a good place to start?
I have recently upgraded my setup.
ZWO 174MM Mini guide cam for Celestron OAG
Pegagus Ultimate PowerBox
RPi 4 with Stellarmate
Pegagsus Focus cube.
Dew Strips plus a heated dew shield when imaging.
Apple Airport express
All power from a single power supply providing power to the Ultimate PowerBox.
The RPi has a wired connection to an Airport Express.
I now run Kstars/ EKOS and Indi on the RPi.
I can remove the losmandy plate on top of the scope and put it on my Esprit 100.