Activity
From 01/10/2012 to 02/08/2012
02/08/2012
- 10:57 PM Support: RE: USB driver not responsive after camera is disconnected during acqusition
- By disconnecting, I mean it is physically disconnected from the computer. The solution thus far has been to go into d...
- Customer reports the following issue: If the MityCCD_I51100F is connected to the MityCCD Viewer and then it's discon...
- 09:58 PM Support: RE: Application does not receive callback from hardware trigger input
- It's best to avoid making calls to camera DLL functions from within the callback routine. The best approach is to se...
02/03/2012
- 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. ...
- 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 d...
02/02/2012
- 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 t... - Customer reports that their application does not receive a callback from the camera hardware trigger.
"It's not cl... - 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 o...
- Customer reports seeing the message "missed my noops, aborting" occasionally when using a Mity CCD-H70310906-BS camer...
Also available in: Atom
Go to top