Hi Robin,
My sequence was supposed to stop at 7h30 but it was still running 20 minutes after that time See log attached.
Can you please investigate?
Many thanks.
Eric.
Sequence not stopping on time
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
Sequence not stopping on time
- Attachments
-
- Log_2024-04-16T21_04_51-24886-Extract.log
- (906.26 KiB) Downloaded 8 times
-
admin
- Site Admin
- Posts: 13370
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Sequence not stopping on time
Hi,
I'm not sure about the expected behaviour of two stop at steps one inside the other with the same stop time - that may be part of the issue.
I can also see that after the main part of the cancellation was complete, an auto-refocus kicked off at 07:30:01 with the detection of a large temperature change. That has a 'repeat 20 times' in it, and I think that is what kept things stuck - once the autofocus subroutine had kicked in outside the scope of the 'stop at', it kept going.
I would suggest extending the outer 'stop at localtime 07:30' to 07:35 or similar so that the two times are not the same. Also, at the end of the outer 'stop at', add a 'Stop running a periodic named Refocus'. There is still an issue though that the inner periodic can still finish at 07:30:00 and then there is a chance that refocus will trigger before starting the step that stops the periodic. That refocus should then get cancelled by the outer stop at, but it will still try to run again. Yuck... I don't think there is a robust way to stop the refocus periodic
As a hack, you could put a 'stop at 07:40' or something in the autofocus subroutine, but even that is not bombproof.
I will have to think about how best to deal with this!
cheers,
Robin
I'm not sure about the expected behaviour of two stop at steps one inside the other with the same stop time - that may be part of the issue.
I can also see that after the main part of the cancellation was complete, an auto-refocus kicked off at 07:30:01 with the detection of a large temperature change. That has a 'repeat 20 times' in it, and I think that is what kept things stuck - once the autofocus subroutine had kicked in outside the scope of the 'stop at', it kept going.
I would suggest extending the outer 'stop at localtime 07:30' to 07:35 or similar so that the two times are not the same. Also, at the end of the outer 'stop at', add a 'Stop running a periodic named Refocus'. There is still an issue though that the inner periodic can still finish at 07:30:00 and then there is a chance that refocus will trigger before starting the step that stops the periodic. That refocus should then get cancelled by the outer stop at, but it will still try to run again. Yuck... I don't think there is a robust way to stop the refocus periodic
As a hack, you could put a 'stop at 07:40' or something in the autofocus subroutine, but even that is not bombproof.
I will have to think about how best to deal with this!
cheers,
Robin