Not waiting for cool down on Sequence start

Sequence Generator SGPro Support
1

Note: I still cannot use “Report a Problem” function, even after reboot/SGP restart). Waiting for ver 455 with additional logging …]

I have checked “Cool down on Sequence Start” but not “Cool down on camera connect”. When I start a sequence, the camera starts the cooling process but begins capturing images right away (ie. before the camera has reached set temperature). Is this expected behaviour? Could have sworn it used to wait in the past. Or perhaps there is another setting I’ve missed somewhere?

DaveNL

2

Possibly. Depends what temperature your TEC starts at and how close it is to the specified temp. It could also be a bug since most folks don’t use it. Logs would tell us here…

3

OK - just sent you a log to your support email.

Dave

4

Well, fwiw, the logs show that you were able to successfully upload logs from report-a-problem. The UI still showed that it failed?

As for the TEC, SGPro will start the sequence within 3 degrees of target and your camera reported that it was so SGPro did not wait:

[03/09/20 00:31:47.694][DEBUG][TEC Thread][SQ;AF;] TEC Change: Changing temp from -12.90 to -15.00 in 300 seconds...

In terms of what “most people” use… they cool the camera on connect as opposed to sequence start. Some folks have a reason to not want this, but it is preferable in terms of starting the sequence as soon as possible.

5

Here is what the logs say for the report-a-problem:

[03/09/20 11:17:08.577][DEBUG][Unknown][SQ;CC;] Packaged log archive to C:\Users\admin\AppData\Local\SequenceGenerator\Temp\sgpro_log_archive_be524a5f-6063-4a07-bfcd-c3c2c4aee292.zip [03/09/20 11:17:10.685][DEBUG][Unknown][SQ;CC;] File uploaded to DropBox: /03-09-2020/sgpro_log_archive_be524a5f-6063-4a07-bfcd-c3c2c4aee292.zip [03/09/20 11:17:11.984][DEBUG][Unknown][SQ;CC;] File successfully shared at -> : https://www.dropbox.com/s/h1tdo3tu83bpppd/sgpro_log_archive_be524a5f-6063-4a07-bfcd-c3c2c4aee292.zip?dl=0

6

Hi Ken,
Hmmm, interesting. The log is indeed at that local drive location
when I browse manually. Does it actually show up in Dropbox on your
end?

Unfortunately, after I select the checkbox for the log (any log) and

then OK, I get this error (and can’t continue with the error
submission process):

![eodddigkpdbhicdp.png|446x137](upload://mB5lh2KhnWMqbIRhv0jCGlOAMvZ.png)

Cheers,
Dave
7

Capture_Report_a_Problem_error