Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

GigE camera

Just for clarification:  the error message above is from MAX.  I get no message from cameravalidator - it just disappears.
 
Gretchen
0 Kudos
Message 11 of 25
(2,637 Views)
Gretchen, it sounds like it is possible that something went wrong with the firmware update. Are you still able to communicate with and receive an image using Dalsa's configuration utilitiles, like QuickCam?
0 Kudos
Message 12 of 25
(2,621 Views)

Hi Gretchen,

The camera validator utility window is vanishing because it is a command-line utility. If you just click on it when it exits with an error the window will just close. It is meant to be accessed from the command line so that you can pass arguments to it regarding which camera to test and which tests to run. Without any arguments it will run on the first camera found.

Since MAX is giving an Unable to Load XML error, it is not suprising that the utility would give the same error. Both applications need to open the camera and that is when the file is loaded. Assuming you have cleared the XML file directory to remove any corrupted files, I am suspecting that your camera does have an invalid XML file in its firmware. Do you see an XML file downloaded to the XML directory after trying to open the camera? If you click on it does it open in internet explorer without any parsing errors? Can you possibly attach it to a post?

-Eric

0 Kudos
Message 13 of 25
(2,617 Views)
"Are you still able to communicate with and receive an image using Dalsa's configuration utilitiles, like QuickCam?"
 
The Dalsa program called "Coyote" works with the Spyder camera after the firmware upgrade.  I get images of my office window just fine!  (streaky, since it is a line scan camera, but I can tell it's the blinds in my office).
 
Thanks for your coments, Michael.  any other help would be greatly appreciated.
 
Gretchen Zimmer
0 Kudos
Message 14 of 25
(2,609 Views)
Hi Eric,
I admit, when I first found the cv tool in the correct folder, I just double-clicked on it - so tempting!.  But then, when it just vanished, I re-read the NI website, and followed the directions - go to Start -> Run and enter the path & name along with the /ATTRIBUTE argument.  It still just vanishes.
 
Before running cv, I removed all files from the Data/XML folder.  When I run either MAX or the cv tool, an XML file is created in that folder.
 
So, I suspect that you are both right - the camera has an invalid XML file.
 
I can open the XML file in IE, and there are no errors.  I will attach it to a separate post.
 
gretchen
0 Kudos
Message 15 of 25
(2,609 Views)
Hi Gretchen,
 
I'm not sure where those directions are that you are referring to. Executing the application from Start->Run may allow you to now pass arguments, but it doesn't change the fact that as a console application when it exits, the window will close on its own. When I said to run from the command line I meant that you would open a shell first (one way is to run "cmd.exe" from start->run) and then run the utility from there.
 
-Eric
0 Kudos
Message 16 of 25
(2,604 Views)
"Can you possibly attach it to a post?"
See attached.  I had to change the extension to .txt
0 Kudos
Message 17 of 25
(2,603 Views)
What-dya know!  Works better that way!
 
However - same result: 
        Opening 'cam0'...
        FAIL: Error Code = 0xBFF6901D: unable to load camera's XML file
 
Gretchen
0 Kudos
Message 18 of 25
(2,596 Views)
Hi Gretchen,
 
I was able to load that file fine, but I am using a slightly newer version of the software that parses the XML file (this is a standard component shared by all companies supporting GigE Vision). I'll try it with an older copy to see if that is actually affecting it, but in the meantime I might suggest downloading the following patch available here:
 
 
If you follow those directions it will update this specific component to the same version that I was able to successfully load the XML file with. While I'm still unsure if not having this update could cause the specific error you are seeing (as opposed to a different error), it is worth a try at this point.  Unfortunately we don't have this exact camera in-house to try, although I can tell you we have used others in the same series without this problem. However, the XML file and probably the rest of the firmware was a different revision than yours.
 
Let me know if this helps,
Eric
0 Kudos
Message 19 of 25
(2,594 Views)
Once again, thanks for the help.  I updated NI-IMAQdx to 3.0.2 according to the instructions,
removed all xml files from the Data/XML folder, and ran MAX and .......
 
got the same error ........
 
Gretchen
0 Kudos
Message 20 of 25
(2,586 Views)