Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Impossible to get image from Imaqdx camera , error 1074360306

Hello ,
WHo know about this error 1074360306 , it is impossible to get image from camera with Vbai 3.0.1
With Max 4.2 it is all ok , with vbai it is all ok in edit step mode  , in run mode it not work .
Vision Acquisition 8.2.2
 
Log of vbai:
 
0 12/04/2007 15.38.02,750 Pass
Inspect Acquire Image (IEEE 1394 or GigE) 1 Step Status Fail  
Inspect Acquire Image (IEEE 1394 or GigE) 1 Frame Index -2,00000  
Inspect Acquire Image (IEEE 1394 or GigE) 1 Timeout False  
Inspect Acquire Image (IEEE 1394 or GigE) 1 Trigger Overrun False  
Inspect Acquire Image (IEEE 1394 or GigE) 1 Warning Message WARNING! Image Acquisition Error: -1074360306 -   
Inspect Acquire Image (IEEE 1394 or GigE) 1 Number of Images Missed 0,00000  
Thank you for help .
Maury
 
0 Kudos
Message 1 of 5
(7,831 Views)

Hello Maury,

 

which camera does uses you ??

0 Kudos
Message 2 of 5
(7,721 Views)
Hello ,
I'm Using Pixelink PL-A 782 colour 6.6 mop camera .
Bye
 
0 Kudos
Message 3 of 5
(7,680 Views)
Talked to our VBAI expert and this was his reply:

"We saw this same problem with a PixeLink camera.  The default value for one of the attributes was invalid and since we don't write all the values in edit mode, only when you try and acquire in run mode the first time, it wasn't a problem until they tried running the inspection after editing.  They should look closely at all the attributes in the tree and see if any of them are empty for the value and make sure to change those to valid values.  I'm not sure why the camera is initialized that way, but I don't think MAX has a problem with it because it works in a similar way that VBAI does in edit mode where it only updates attributes that have changed and doesn't try writing all attribute values.  You should see in MAX that the camera has the invalid value for the messed up attribute as well though."

The summary:
1) Go into MAX and set all attributes
2) Save attributes
3) Go back to VBAI

Hope this helps,

JohannS
0 Kudos
Message 4 of 5
(7,667 Views)
Hi,

I seem to have a simila problem with my camera. The difficulty I meet is that I cant change it like you propose, since MAX checks the validity of every attribute everytime I change one. Here are the details :
I have two attributes for my camera, KneeX1 and KneeX2. Default values for both is 255. Max fr both is 255. Min for KneeX1 is 0, and Min for KneeX2 is KneeX1+1. Thus, since KneeX1 default value is 255,  there is no valid KneeX2 possible, and I keep stuck, unable to change anything since, whatever I do, it is illegal.

I am now wondering if someone could explain how default value is defined, when MAX does send its parameter to the camera to be set, and if anyone can think of a workaround for my problem...


0 Kudos
Message 5 of 5
(7,499 Views)