Activity
From 01/05/2012 to 02/03/2012
02/03/2012
- GS 04:40 PM Support: RE: Application does not receive callback from hardware trigger input
- Following up with some code that may be useful to others. The image callback works with this code using GPIO line 1. The change from the above code was to make sure the BINCODE_SEND flag was set appropriately.
Note that this code will c... - GS 10:30 AM Support: RE: Application does not receive callback from hardware trigger input
- The following line: r = CLReadCCDArea(c, NULL, 0, 0); // results in many callbacks
causes many callback with image data but they aren't tied to the hardware trigger. It looks like using a 0 for the number of images causes it to free-run...
02/02/2012
- MW 03:52 PM Support: RE: Application does not receive callback from hardware trigger input
- Why is the CLReadCCDArea() call commented out? You need to leave that call in place to get an image.
Do you see the printf show the GPIO pin in question change?
Do you get heartbeat callbacks?
Try removing the CLClearCCD() comm... - Customer reports that their application does not receive a callback from the camera hardware trigger.
"It's not clear from the documentation if we need to call CLSetGPIO() before CLSetTrigger(). But either way, the application does no... - OR 01:03 PM Support: RE: MityCCD Camera reports "Missed my noops, aborting"
- Could you describe the acquisition cycle (i.e. time line and data captured) and sent over USB? Also, are there any other devices on the USB bus?
- Customer reports seeing the message "missed my noops, aborting" occasionally when using a Mity CCD-H70310906-BS camera. What is the underlying cause and possible remedy.