I really appreciate the Analyse module developed by Hy Murveit . Simply beautiful .
I'm lucky to have my set-up installed in a dome.
Would it not be possible to add a Dome line to the panel ?
Thanks.

Jean-Claude,

I envy your dome! I have no experience with a dome, but it seems to me that dome and mount could probably share a line, since you probably aren't slewing etc while the mount is closed--that is, their timelines most likely don't overlap. Would you agree? What signals would you like to see on a dome timeline?

If you could, share with me a log that has debug logging with mount and dome, that represents a typical dome-based session you'd like to see. It would be fine (even better than fine) to make it artificially short. E.g. startup, open dome, do whatever to slew somewhere and take a few shots, then do whatever that winds up parking and closing the dome. If you do this, please send me a side note with approximately what happened (e.g. opened the dome at 21:00, started up the mount at 21:03, ....).

Hy

Hy,My 2.3 meter Sirius dome has a 0.6 m aperture which - of course - must be synchronized with the scope. KStars slaves the dome to the scope.But if for some reason this is no more the case, recording photos might be difficult !As many of us, I am facing device connection problems and from time to time a device might disconnect during a session.This is where the Analyze Module helps .I attach a .analyze file where my mount (named Reducer) disconnected at 22:42:42This disconnection has also been reported in the log at 22:42:42 :[2021-04-07T22:42:42.789 CEST DEBG ][           org.kde.kstars.indi] - Reducer : "[DEBUG] CMD <e> "[2021-04-07T22:42:42.911 CEST INFO ][           org.kde.kstars.indi] - Reducer :  "[ERROR] Serial read error: Read Error: Device not configured "[2021-04-07T22:42:42.913 CEST INFO ][           org.kde.kstars.indi] - Reducer :  "[ERROR] Failed to read RA/DEC values. "[2021-04-07T22:42:43.560 CEST DEBG ][     org.kde.kstars.ekos.mount] - Mount status changed from  "Tracking"  to  "Error"[2021-04-07T22:42:43.587 CEST DEBG ][           org.kde.kstars.indi] - MaxDome II : "Shutter error "[2021-04-07T22:42:43.914 CEST DEBG ][           org.kde.kstars.indi] - Reducer : "[DEBUG] CMD <e> "[2021-04-07T22:42:43.915 CEST INFO ][           org.kde.kstars.indi] - Reducer :  "[ERROR] Serial write error: Write Error: Device not configured "[2021-04-07T22:42:43.917 CEST INFO ][           org.kde.kstars.indi] - Reducer :  "[ERROR] Failed to read RA/DEC values. "If a disconnection of the dome occurs, it is also reported in the log :[2021-04-15T00:43:26.198 CEST DEBG ][           org.kde.kstars.indi] - Reducer : "[DEBUG] CMD <e> "[2021-04-15T00:43:26.270 CEST DEBG ][           org.kde.kstars.indi] - Reducer : "[DEBUG] RES <6A372F00,31147A00

Oh I just made a mess.
I'll try to send a clearer message again

My 2.3 meter Sirius dome has a 0.6 m aperture which - of course - must be synchronized with the scope. KStars slaves the dome to the scope.But if for some reason this is no more the case, recording photos might be difficult !As many of us, I am facing connection problems and a device might disconnect.This is where the Analyze Module helps .I attach a .analyze file where my mount (named Reducer) disconnected at 22:42:42This mount disconnection has been reported in the log at 22:42:42 :
[2021-04-07T22:42:42.789 CEST DEBG ][org.kde.kstars.indi] - Reducer : "[DEBUG] CMD <e> "
[2021-04-07T22:42:42.911 CEST INFO ][org.kde.kstars.indi] - Reducer :  "[ERROR] Serial read error: Read Error: Device not configured "
[2021-04-07T22:42:42.913 CEST INFO ][org.kde.kstars.indi] - Reducer :  "[ERROR] Failed to read RA/DEC values. "
[2021-04-07T22:42:43.560 CEST DEBG ][org.kde.kstars.ekos.mount] - Mount status changed from  "Tracking"  to  "Error"
[2021-04-07T22:42:43.587 CEST DEBG ][org.kde.kstars.indi] - MaxDome II : "Shutter error "
[2021-04-07T22:42:43.914 CEST DEBG ][org.kde.kstars.indi] - Reducer : "[DEBUG] CMD <e> "
[2021-04-07T22:42:43.915 CEST INFO ][org.kde.kstars.indi] - Reducer :  "[ERROR] Serial write error: Write Error: Device not configured "
[2021-04-07T22:42:43.917 CEST INFO ][org.kde.kstars.indi] - Reducer :  "[ERROR] Failed to read RA/DEC values. "If a disconnection of the dome occurs, it is also reported in the log :
[2021-04-15T00:43:26.511 CEST INFO ][org.kde.kstars.indi] - MaxDome II :  "[ERROR] No response from MAX DOME "
[2021-04-15T00:43:26.512 CEST INFO ][org.kde.kstars.indi] - MaxDome II :  "[ERROR] Error on command: (No response from MAX DOME). "
[2021-04-15T00:43:26.514 CEST INFO ][org.kde.kstars.indi] - MaxDome II :  "[ERROR] Write Error: Device not configured "
[2021-04-15T00:43:26.515 CEST INFO ][org.kde.kstars.indi] - MaxDome II :  "[ERROR] MAX DOME II: Reconnecting ... "
[2021-04-15T00:43:26.516 CEST INFO ][org.kde.kstars.indi] - MaxDome II :  "[ERROR] Write Error: Device not configured "
[2021-04-15T00:43:26.517 CEST INFO ][org.kde.kstars.indi] - MaxDome II :  "[ERROR] MAX DOME II: Reconnecting ... "
[2021-04-15T00:43:26.517 CEST DEBG ][org.kde.kstars.indi] - MaxDome II : "Dome failed to move to new requested position. "
[2021-04-15T00:43:26.518 CEST INFO ][org.kde.kstars.indi] - MaxDome II :  "[ERROR] Dome failed to sync to new requested position. "
[2021-04-15T00:43:26.798 CEST INFO ][org.kde.kstars.indi] - MaxDome II :  "[ERROR] Write Error: Device not configured "
[2021-04-15T00:43:26.799 CEST INFO ][org.kde.kstars.indi] - MaxDome II :  "[ERROR] MAX DOME II: Reconnecting ... "But a dome disconnection is not displayed in the Analyze Module although it would be useful.Generally speaking, the alert system of KStars could be improved.KStars should alert VERY CLEARLY the user that one of
- mount
- dome
- imager
- guiderhas got a problem.This CLEAR alert should pop up as a front alert that the user could confirm or dismiss.I suggest also to add 4 buttons on the top of the KStars Setup Module for : Mount, Dome, Imager, GuiderThese 4 buttons would have a color green, red, or transparent :
- green : the device works OK
- red : the device has a problem
- transparent : no deviceThese 4 buttons would complete the Setup Module and give a general view of the process.They would be a complement to the detailed info contained in the Analyze Module.Thanks Hy for your interest.Attached : ekos-2021-04-07T15-35-35.analyze(BTW it would be nice if KStars could open directly a .analyze file located on the Finder by a double-click)

Hy,
I finally manage a simple session involving only the mount and the slaved dome.
I’m sending a compress folder containing the log and the analyze files :
- ekos-2021-04-18T09-02-18.analyze
- log_09-02-07.txt
It just happened that during that short session the mount connection failed at 08:32.277.
This is reported in the log file :Reducer :  "[ERROR] Failed to read RA/DEC values. "
and nicely shown in the .analyze file by a red segment.
I disconnected-reconnected the mount (called “Reducer”) to solve this problem and continue the session.
What I think would be useful is a .analyze graphic for the dome similar to the graphic for the mount.
In the log file, the lines referring to the dome contain [org.kde.kstars.ekos.observatory]
Do not pay attention to the MaxDome II : "Shutter error " lines.
They are due to the fact that my shutter opening is manual and not automatic.
Please ask me for further testing.