We are have been having issues with a function of Volocity for a few years and I would like to see if we could find a solution to the problem. The issue pertains to the exposure times while using the acquisition setup.
Our acquisition is only capturing a single frame with multiple channels. The exposure times for the channels are set prior to the acquisition and are saved. The issue occurs when running the acquisition, some exposure settings saved in the channels are not respected during the acquisition setup. For example in a blue fluorescent channel, the exposure time is set to 1s but when acquiring the shutter is only open for 0.001 seconds and does not capture the specific channel. This issue is usually only seen when running 3 channels but decreases in probability of occurring when dropping to less channels. In an attempt to solve this issue I have attempted to measure device latencies but I get an error when trying to do this.
In the ideal situation, I would like to set the exposure times and get the acquisition running smoothly without having to cancel it because the shutters are closing too quickly. When I notice that the acquisition is not good, I usually stop it. I do notice that the channel's disk icon appears unsaved which means I need to go back into the channel and set the correct exposure amount. Some times to take one multichannel picture I need to take at least 5 acquisition before all channels respect their appropriate exposure times. As you might suspect this gets quite annoying.
We have a Mac 5000 controller that controls the shutter speeds and a manual filters cube that is change through manual intervention pop up window that I have set to work.
Any advice on what is wrong with the device latency measurement or else this sporadic exposure time issue. Let me know if you need any additional information.