Hopefully, anyone can come up with a solution to this.
Most of what I know just from a couple of cameras is on the device page. A 1 ms sleep appeared to be sufficient while I was able to reproduce the error assuming it even was the same error.
There seem to be about a 100 ms of overhead then snaping an image. The cam appears as working properly in the device manager, but trying to configure MicroManager to use it, I get the same error message as reported above: Hi Mike, On Thu, May 15, 2014 at 02: Hi Mark, Thanks for your reply.
But then I tried to show Chris what was happening, and the error went away: Thanks for the help and the quick fix! The snapImage call will block at least until the exposure is finished, and the getImage will obviously wait for the image to be ready. Carol Norris On May 13, 2014, at 9: I would appreciate the help.
This post was updated on.
Thank you for your reports. Hi Mike, On Tue, May 06, 2014 at 02: Classic List Threaded. As for the error upon rapid snaps, it is possible that dc1394 will not be plagued by these because dc1394 has a capture constantly running and simply pulls out an image when asked for a snap.
When I select the device to be 1394A, the message is that the device does not support 1394B. Free forum by Nabble. Hi Mark, well I played a little and as I noticed before having some pauses in between indeed reduces the chance of an error. Is your 1394 interface either a PICe card or built into the motherboard compatible with 1394B, or is it 1394A-only?