开云体育

Since deploying this new (used) QSI 632camera a problem has emerged with the connection upon startup.? It is a real puzzle that will require someone who understands this camera better than I to figure out.?

?

My system uses ACP and Scheduler.? Scheduler manages ACP and ACP controls the camera via Maxim.? I am using the QSI Universal driver.? After Scheduler initiates system start-up everything looks nominal with the camera.? See the first screenshot below.? However, the first image attempt will fail and Maxim will throw an error message, see second screenshot. ?If you close the error message maxim changes to show “no camera”, and the cooler is said to be off as shown in the third screenshot. ?All subsequent image attempts will fail the whole night.?

?

Typically, if I intervene by disengaging Scheduler to release the camera, I can disconnect and reconnect the camera and it will work without a problem for the rest of the night.? By the way, the cooler also remains in operation even when Maxim shows "no camera".? When you disconnect and reconnect the cooler is shown to have been on the whole time.?

?

Today, I decided to try and dig into this and perhaps I have gained some useful insight.? I used “test startup” in Scheduler then tried using Maxim to order an image.? It failed and I got the same error message I have gotten before when doing this.?But, this afternoon, disconnecting and reconnecting did not solve the problem.? I tried it multiple times.? Then in the evening, Scheduler booted everything up as usual, and as usual the first image failed and as usual, disconnect reconnect worked.

?

The only difference I can think of between the afternoon experiment and the routine startup in the evening is the temperature of the camera had dropped to the setpoint in the latter case, while in the earlier case, the camera was warm (40+ C).?

?

Is there some reason, whether firmware, software, or hardware that would cause a connection failure when attempted before the camera has cooled to the setpoint?

?

?