Hello all,
SX-100, PeakSight 4.0, modern beefy computer that's 99% too powerful for the software.
As usual I've got something unusual - I was having to take a bunch of photos, and I already have hotkeys programmed in to set the screen to our "standard" imaging modes (2500fov, 600, 300, 150, a few others). I have them programed to un-freeze ("acq fixe off 1" in the interpretor) set the resolution to 1024x786 and scan time to 12.8.
Today I got lazy, and decided to figure out if I could automate the wait/freeze so all I or users would have to do is press button, press save, name file. It works! I can post my command.keys if anyone would like my special sauce.
However, I noticed that despite having the wait command set to 12 seconds, it takes 20 for the "acq fixe on 1" command to trigger.
I've also noticed that while performing video scan maps, the program waits an incorrect amount of time to freeze, grab and move on - way worse on fast scans than slow scans, e.g. 256x192 video scan maps *always* take 6 seconds per frame, no matter what time interval I specify, but other modes are closer (i think 1024 and 12s takes about 20 but I haven't timed it recently). I just shrug this off and don't try to do quicker maps.
I am now wondering if the video map wait issue is related to the issue with the SPF WAIT command while also being a bug in the acquisitions set-up.
Does anyone know? Is there a better way to test the wait timer? It's entirely possible that there's some communications lag between the computer and the SX100 that causes this. Is my timer chip bad?
Is the timer for SPF WAIT also used for timing quantitative acquisitions?
In the mean time I'm just going to test different wait values until I empirically determine the quickest way for lazy imaging!
Cheers!
Neko