Clear skies tonight having spent the last few days re-configuring usb connections and hubs.  Unfortunately no better, Kstars crashed on taking the second image!  I had logging to file on as requested in verbose and attached is the kstars log file and the sys log  

File Attachment:

File Name: kstars_crash.zip
File Size: 378 KB

The kstars log file last entries has warnings regarding threads and timers.
The syslog has many entries like 'reset  high-speed USB' which is for the ASI120mm mini (USB2) and 'reset SuperSpeed Gen 1 USB' for the ASI 2600MM Pro' (USB3).  Is this expected?

Some other less important issues to report:
  1. Raspberry Pi 4 not powering up. This is due to the powered usb hub connected to the Pi 4.  Chaining an un-powered hub between the pi and the powered hub solves this issue (USB power feed design fault in Pi 4) This only happens if hub is powered on before the Pi.
  2. Kstars permits running an image sequence when the dome is still moving to syncronise with the mount direction.  User should be warned and sequence not started until dome has reached position.
  3. With telescope in home position pointing at the celestial pole and mount not tracking dome gets continuous command 'Dome is moving to position' then 'Dome reached requested position.  The position is not changing when mount is not tracking! 
  4. When aligning using slew to target there is no mention of what the target actually is in the align TAB. Could this be added please.


Read More...