Solar Scintillation Monitor SSM3
Forum rules
'+1' posts are welcome in this area of the forums to indicate your support for a particular feature suggestion. Suggestions that get the most +1's will be seriously considered for inclusion in future versions of SharpCap.
'+1' posts are welcome in this area of the forums to indicate your support for a particular feature suggestion. Suggestions that get the most +1's will be seriously considered for inclusion in future versions of SharpCap.
Solar Scintillation Monitor SSM3
Dear Sharp Cap Team
I build and sell self-made solar scintillation monitors. I have also had software written to visualise the seeing data. Now I have been asked by several customers if it would be possible to trigger the recording in Sharp Cap with the measured values of the Seeing Monitor. Could you imagine something like this?
I build and sell self-made solar scintillation monitors. I have also had software written to visualise the seeing data. Now I have been asked by several customers if it would be possible to trigger the recording in Sharp Cap with the measured values of the Seeing Monitor. Could you imagine something like this?
- Attachments
-
- thumbnail_IMG_7868.jpg (690.96 KiB) Viewed 3091 times
-
- SSM3 Software 2025 02.jpg (125.07 KiB) Viewed 3091 times
- admin
- Site Admin
- Posts: 17584
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Solar Scintillation Monitor SSM3
Hi Marc,
that sounds like a great feature to add - the question is how to do it...
Option A - SharpCap defines some way that another application (like your monitor application) can send commands to start/stop capture - your application has control over what the threshold should be for good seeing and of when the captures happen.
Option B - Your application makes data available to SharpCap on the seeing conditions - SharpCap then controls the threshold of when to start capturing. You could possibly use an ASCOM 'ObservingConditions' driver for this and (slightly) misuse the StarFWHM property to report the seeing conditions.
I have to admit that my preference right now would be option A, as it would probably be a relatively simple thing to add to SharpCap, which would let me get it done relatively quickly (I don't think I have any time in my development schedule for something on the scale of option B at the moment).
cheers,
Robin
that sounds like a great feature to add - the question is how to do it...
Option A - SharpCap defines some way that another application (like your monitor application) can send commands to start/stop capture - your application has control over what the threshold should be for good seeing and of when the captures happen.
Option B - Your application makes data available to SharpCap on the seeing conditions - SharpCap then controls the threshold of when to start capturing. You could possibly use an ASCOM 'ObservingConditions' driver for this and (slightly) misuse the StarFWHM property to report the seeing conditions.
I have to admit that my preference right now would be option A, as it would probably be a relatively simple thing to add to SharpCap, which would let me get it done relatively quickly (I don't think I have any time in my development schedule for something on the scale of option B at the moment).
cheers,
Robin
Re: Solar Scintillation Monitor SSM3
Hello Robin
Sorry for my late reply. To be honest, I would definitely prefer option B. My device provides three things via the serial port
1. the strength of the sensor signal in volts
2. the seeing value in Arc Sec
3. the temperature in °C
In Sharp Cap you would only have to display these three things and have the option of defining the value for the seeing. As soon as the sensor delivers seeing values below the defined value, the recording starts or stops if the value is exceeded.
I did not write the analysis software I use myself. I don't know enough about it.
Of course it would be great if we could realise this. As already mentioned, many people who use my devices ask me whether it is possible to trigger Sharp Cap.
I could also provide you with a device so that you can test it. The device runs via USB.
Marc
Sorry for my late reply. To be honest, I would definitely prefer option B. My device provides three things via the serial port
1. the strength of the sensor signal in volts
2. the seeing value in Arc Sec
3. the temperature in °C
In Sharp Cap you would only have to display these three things and have the option of defining the value for the seeing. As soon as the sensor delivers seeing values below the defined value, the recording starts or stops if the value is exceeded.
I did not write the analysis software I use myself. I don't know enough about it.
Of course it would be great if we could realise this. As already mentioned, many people who use my devices ask me whether it is possible to trigger Sharp Cap.
I could also provide you with a device so that you can test it. The device runs via USB.
Marc
- admin
- Site Admin
- Posts: 17584
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Solar Scintillation Monitor SSM3
Hi Marc,
no problem, let's try it that way, although it will take a bit longer on my side. Can you drop me an email using the 'contact us' button at the bottom of the page please so we can talk further.
cheers,
Robin
no problem, let's try it that way, although it will take a bit longer on my side. Can you drop me an email using the 'contact us' button at the bottom of the page please so we can talk further.
cheers,
Robin
Re: Solar Scintillation Monitor SSM3
Hi Robin
its done.... i was sending you a E-Mail....
Marc
its done.... i was sending you a E-Mail....
Marc
-
RossHampton
- Posts: 1
- Joined: Sun Jul 05, 2026 11:52 pm
Re: Solar Scintillation Monitor SSM3
Good day and thank you for all of your work on an outstanding product.
Only because it has happened to me 3 times this week ... if would be nice that if SharpCap 1) sees a solar scintillation monitor attached and 2) is capturing files that the data from the solar scintillation monitor is automatic saved with the SharpCap settings data. I don't think it needs to be a separate csv file but that would be fine with me - for some reason I just cannot remember to save the data after a session or series of sessions.
Thank you again - stay well
Only because it has happened to me 3 times this week ... if would be nice that if SharpCap 1) sees a solar scintillation monitor attached and 2) is capturing files that the data from the solar scintillation monitor is automatic saved with the SharpCap settings data. I don't think it needs to be a separate csv file but that would be fine with me - for some reason I just cannot remember to save the data after a session or series of sessions.
Thank you again - stay well
- admin
- Site Admin
- Posts: 17584
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Solar Scintillation Monitor SSM3
Hi,
so you could have something like...
Save the appropriate part of the scintillation history automatically when
* A capture finishes
* and the scintillation UI is active
* and the scintillation monitor is connected at that point in time
That would be quite nice as it would record the data from the capture period that you could then analyse alongside the capture quality variations...
Overall, I think a separate file would be best - that would let you (for example) load the scintillation data straight into excel or process it without having to worry about other data (the normal capture settings) not having the same format.
I will put this one on the to-do list.
cheers,
Robin
so you could have something like...
Save the appropriate part of the scintillation history automatically when
* A capture finishes
* and the scintillation UI is active
* and the scintillation monitor is connected at that point in time
That would be quite nice as it would record the data from the capture period that you could then analyse alongside the capture quality variations...
Overall, I think a separate file would be best - that would let you (for example) load the scintillation data straight into excel or process it without having to worry about other data (the normal capture settings) not having the same format.
I will put this one on the to-do list.
cheers,
Robin
-
paulhummerman
- Posts: 3
- Joined: Thu Aug 28, 2025 10:31 pm
Re: Solar Scintillation Monitor SSM3
Although my SSM3 works quite well with Sharpcap, it sometimes freezes Sharpcap, to the point that I cannot even close Sharpcap and have to shut down my computer. It seems to have to do with switching between the histogram display and the SSM3 display: I cannot display both at once, and when I switch from one to the other Sharpcap sometimes freezes.
- admin
- Site Admin
- Posts: 17584
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Solar Scintillation Monitor SSM3
Hi,
if SharpCap's display freezes up then you should get a pop up about 30s later offering you the opportunity to submit a report about the freeze (there is a separate watchdog check that runs in the background to try to detect this sort of thing). Have you seen that prompt pop up? If you do, submit the report and then let me know so that I can go and find it and check out what is happening.
If you are not seeing anything like that, the information needed has still probably been recorded in SharpCap's log file - let SharpCap sit frozen for at least a minute or two, then close it using task manager, then go to the SharpCap logs directory (see https://docs.sharpcap.co.uk/4.1/#The%20SharpCap%20Log) and find the newest log file - that should be the one from the frozen copy of SharpCap and hopefully near the end it will have recorded what was going on when it froze. The best thing to do is to send the whole log to me (zip it up if necessary) and I will see what I can work out.
cheers,
Robin
if SharpCap's display freezes up then you should get a pop up about 30s later offering you the opportunity to submit a report about the freeze (there is a separate watchdog check that runs in the background to try to detect this sort of thing). Have you seen that prompt pop up? If you do, submit the report and then let me know so that I can go and find it and check out what is happening.
If you are not seeing anything like that, the information needed has still probably been recorded in SharpCap's log file - let SharpCap sit frozen for at least a minute or two, then close it using task manager, then go to the SharpCap logs directory (see https://docs.sharpcap.co.uk/4.1/#The%20SharpCap%20Log) and find the newest log file - that should be the one from the frozen copy of SharpCap and hopefully near the end it will have recorded what was going on when it froze. The best thing to do is to send the whole log to me (zip it up if necessary) and I will see what I can work out.
cheers,
Robin
-
paulhummerman
- Posts: 3
- Joined: Thu Aug 28, 2025 10:31 pm
Re: Solar Scintillation Monitor SSM3
Robin - thanks. What happens is that when I launch SSM via Tools not only does Sharpcap freeze, but the whole computer (Beelink ser5) partly freezes, though I can still shut it down. When I reboot the Beelink then relaunch Sharpcap, it restarts the Log anew - the log up to the point where Sharpcap froze is not available.
This doesn't always happen. Typically, I can launch the SSM3 and it will record the seeing for quite prolonged periods, eg 1/2 hour. But if I leave unattended for a while when I return to the session I see SSM3 has frozen, and also Sharpcap. I usuually start the session by recording the seeing for 5 minutes, then I close SSM3 to avoid future crashes. Then later in the session, I sometimes reatart SSM to check seeing - at this point SC and the Beelink usually freeze, and I lose several minutes of data while I relaunch. Because Sharpcap and the Beelink freeze, I do not get a notification about the crash from SC.
A couple of notes about my setup. Solar capture is being done with SC running on a remote Beelink Ser 5 miniPC at the rig itself, with data being saved to an externel SSD. The Beelink is controlled from inside the house with Rustdesk running on my Mac laptop.
I suspect that SC is being worked very hard (1TB of data every hour) and the extra load of running SSM3 puts it over the edge. - Paul
PS I read your instructions re logs more carefully and was able to retrieve the portion of the log just at the crash point:
Thread #33 ('Capture Write Thread'):
at System.Threading.WaitHandle.WaitOneCore(IntPtr, Int32)
at System.Threading.WaitHandle.WaitOneNoCheck(Int32)
at SharpCap.Base.Utilities.ConcurrentQueue`1[[System.__Canon, System.Private.CoreLib]].WaitFor(Int32)(C:\Documents\Source Code\SharpCap4.1\src\SharpCap.Base\Utilities\ConcurrentQueue.cs:49)
at SharpCap.Base.BaseImageProvider.RunWriteThread()(C:\Documents\Source Code\SharpCap4.1\src\SharpCap.Base\BaseImageProvider.cs:325)
at SharpCap.Base.BaseImageProvider.CaptureWriteThreadProc()(C:\Documents\Source Code\SharpCap4.1\src\SharpCap.Base\BaseImageProvider.cs:312)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at DebuggerU2MCatchHandlerFrame
Thread #18 (''):
at DebuggerU2MCatchHandlerFrame
in void SharpCap.Watchdog.DumpThreadStacks(string source)
Debug 09:24:14.238153 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)
Debug 09:24:19.776117 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)
Warning 09:24:23.096675 #19 Possible dispatcher overload/UI Freeze. Background priority not run for 20.5s since 1:24:02 PM. Dispatcher queue length is 24, currently 0 in progress. Dispatcher disable count : 0 in async Task SharpCap.UISwitcher+DispatcherWatchDog.MonitorDispatcher()
Debug 09:24:25.324230 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)
Debug 09:24:30.873255 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)
Debug 09:24:36.420936 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)
This doesn't always happen. Typically, I can launch the SSM3 and it will record the seeing for quite prolonged periods, eg 1/2 hour. But if I leave unattended for a while when I return to the session I see SSM3 has frozen, and also Sharpcap. I usuually start the session by recording the seeing for 5 minutes, then I close SSM3 to avoid future crashes. Then later in the session, I sometimes reatart SSM to check seeing - at this point SC and the Beelink usually freeze, and I lose several minutes of data while I relaunch. Because Sharpcap and the Beelink freeze, I do not get a notification about the crash from SC.
A couple of notes about my setup. Solar capture is being done with SC running on a remote Beelink Ser 5 miniPC at the rig itself, with data being saved to an externel SSD. The Beelink is controlled from inside the house with Rustdesk running on my Mac laptop.
I suspect that SC is being worked very hard (1TB of data every hour) and the extra load of running SSM3 puts it over the edge. - Paul
PS I read your instructions re logs more carefully and was able to retrieve the portion of the log just at the crash point:
Thread #33 ('Capture Write Thread'):
at System.Threading.WaitHandle.WaitOneCore(IntPtr, Int32)
at System.Threading.WaitHandle.WaitOneNoCheck(Int32)
at SharpCap.Base.Utilities.ConcurrentQueue`1[[System.__Canon, System.Private.CoreLib]].WaitFor(Int32)(C:\Documents\Source Code\SharpCap4.1\src\SharpCap.Base\Utilities\ConcurrentQueue.cs:49)
at SharpCap.Base.BaseImageProvider.RunWriteThread()(C:\Documents\Source Code\SharpCap4.1\src\SharpCap.Base\BaseImageProvider.cs:325)
at SharpCap.Base.BaseImageProvider.CaptureWriteThreadProc()(C:\Documents\Source Code\SharpCap4.1\src\SharpCap.Base\BaseImageProvider.cs:312)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at DebuggerU2MCatchHandlerFrame
Thread #18 (''):
at DebuggerU2MCatchHandlerFrame
in void SharpCap.Watchdog.DumpThreadStacks(string source)
Debug 09:24:14.238153 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)
Debug 09:24:19.776117 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)
Warning 09:24:23.096675 #19 Possible dispatcher overload/UI Freeze. Background priority not run for 20.5s since 1:24:02 PM. Dispatcher queue length is 24, currently 0 in progress. Dispatcher disable count : 0 in async Task SharpCap.UISwitcher+DispatcherWatchDog.MonitorDispatcher()
Debug 09:24:25.324230 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)
Debug 09:24:30.873255 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)
Debug 09:24:36.420936 #30 SharpCap.FrameTransforms.ScintillationMonitor.ScintillationMonitorTransform processed frame in 0ms in void SharpCap.Base.CaptureProviderBase<T>.ActuallyProcessTransform(IFrameTransform frameTransform, ICapturedFrame frame, ICapturedFrame sourceFrame)