07-02-2013 08:22 AM
Hello together,
I trying to set the AOI and the Binning.
Please see the attached VIs. If I choose Binning 2x or 4x, the following error occured:
Error -1074397150 occurred at IMAQ Snap.vi
Possible reason(s):
NI-IMAQ: A timeout error occurred while waiting for the specified event. If waiting for an image, verify that all video data is acquired within the timeout period. If waiting for a signal, verify that the signal assertion occurs within the timeout period.
Does anybody has a idea, how I can set the AOI and the Binning?
Thank you very much in advance.
greetings zaepfle
LV2012
07-03-2013 06:12 AM
Hi,
could you please give some more information about your environment,
What Brand is the Camera?
What is your framegrabber?
What Kind of Software are You using (OS, Drivers, Versions) ?
07-03-2013 08:36 AM
Hi,
sorry that the informations are incomplete.
- VieWorks camera VA-29MC-M5
- PCIe 1433
- WIN7
- the current NI Software and Drivers (e.g. LV2012, NI-IMAQ 4.7.2)
greetings zaepfle
07-04-2013 12:29 AM - edited 07-04-2013 12:43 AM
Hello,
I believe I'm a step forward to the goal (see attached vi).
But any questions are unanswered.
Is the while loop faster then the case structure would not every while loop run. But only if I change the Ring value? If yes, do you have a easy programmatically solution?
If I set the ring value from 0 to 1 and back from 1 to 0, unfortunately the resolution doesn't go back. Why?
How can I display the frames per second in the front panel?
Many thanks in advance.
greetings zaepfle
07-04-2013 03:26 AM - edited 07-04-2013 03:27 AM
Hi,
The while loop is very fast if you dont use timing. So you should implement a timing vi to reduce the speed and the cpu load.
I added a timing VI set to 1000ms so the While loop will iterate 1x per Second. Then I added a property node with the frame count. I hope this helps.
07-04-2013 03:57 AM
Hi,
thanks for your VI.
Unfortunately the problem is the same:
"If I set the ring value from 0 to 1 and back from 1 to 0, unfortunately the resolution doesn't go back."
The property node with the frame count causes the following error:
Error 304609024 occurred at Property Node (arg 2) in VieWorks_SetCameraAttribute_ROI_inside.vi
This error code is undefined. Undefined errors might occur for a number of reasons. For example, no one has provided a description for the code, or you might have wired a number that is not an error code to the error code input.
Additionally, undefined error codes might occur because the error relates to a third-party object, such as the operating system or ActiveX. For these third-party errors, you might be able to obtain a description of the error by searching the Web for the error code (304609024) or for its hexadecimal representation (0x1227F700).
Hmm, Why the resolution won't go back and How can I get the frames per second?
greetings zaepfle
07-05-2013 04:53 AM
Hi!
"Binning" is not an attribute mentioned in the Camera File available from the NI Camera File repository:
ftp://ftp.ni.com/support/imaq/camera_support/camera_files/digital/Vieworks/Vieworks%20VA-29MC-5M.icd
Are you using a different camera file? Does the option "Binning" show up in MAX?
I noticed that you wire the error cluster in your VI, but there is no error handling implemented. I added basic
error handling in the VI. Please run the VI and see if an error occur when you try to set Binning in your camera.
Regards,
Georg
07-08-2013 03:34 AM
Hi,
thanks for your answer.
The attribute Binning is in the MAX, because I edited the camera file (*.icd] with the NI Camera File generator (see MAX_Binning.png). If I chosse the correct imagesize (MAX - tab Acquisition Parameters) and set the Binning (MAX - Camera Attributes), it works. I can switch between 0x, 2x, 4x Binning without an error message. But unfortunately I can do it with the LabVIEW VI (see attached VI). I will try to describe the process with the attached LV program:
- run program
- default resolution 6576x4384, 0xBinning: all OK
- set resolution 3288x2192, 2xbinning: all OK
- set resolution 1644x1096, 4xbinning: all OK
- set resolution 3288x2192, 2xbinning: the resolution (1644x1096) remains
or
- set resolution 6576x4384, 0xbinning: the resolution (1644x1096) remains
Why the resolution doesn't go back?
How can I get the frames per second?
" Please run the VI and see if an error occur when you try to set Binning in your camera."
It doesn't appear a error message.
I hope we can find a solution.
greetings zaepfle
07-17-2013 02:25 PM
Hi,
I am having the same 1074397150 error at IMAQ snap.vi
Can you please tell me how you resolved this. I already tried the suggestion given in common error codes to set boolean input to false for the async? control on imageSessionAcquire.vi
I still get the same error in Measurment & Automation explorer and also in IMAQ vision builder 6 s/w
PS: I am using IMAQ PCI-1409 frame grabber and Sony-xc-55 cameras.
N
07-22-2013 08:15 AM
Hi,
unfortunately I don't know the solution regarding error 1074397150. This error apears, if I change the binning from 2x to 0x or 4x to 2x or 4x to 0x.
regards Zaepfle