Configure session error # BFFF800B

[stevegraff]

I have a Dalsa camera model CR-GM00-H6400.  It is a GigE camera.  I have configured and used other Dalsa cameras on this system, but this camera gives me a session configuration error as soon as I click on it.  The Dalsa viewer works fine.  The camera is hooked up and talking.  I can ping it.  Why will NI-IMAQDx not start a session?.  I am using the labview drivers supplied with my 2011 release and I also have the latest vision development module.

Also I have a Balser Scout camera model SCA640-120gm which the image comes up as a 641X494 pixels giving a skew to the final display.  Is there any way to change this in NI-IMAQDx viewer in MAX.  I have not tried this in the vision module yet because of the poor results in MAX caused me to switch cameras and then I found the problem described above.

[MHoffmann]

Hi,

do you use the latest firmware of your camera? There was a similar topic where upgrading the cameras firmware fixed the problem. Additional i found this to your problem code:

"This may be caused by the user that is currently logged into the computer not having sufficient access rights. Software should always be installed from an administrator account. If this is not the case, uninstall your software and reinstall from an administrator account. If you are sure the software is installed correctly and you are still getting the same error from a user account only (not the administrator account), try giving your user account "Power User" rights."

[stevegraff]

I have admin privileges and can see a dalsa camera C1400 no problem.  I can also contact and talk to a basler camera.   I have up to date firmware according to dalsa although I will keep in contact with them on this issue.

NI-IMAQDx is now the only GigE driver installed on the system.

[Matt_McLaughlin]

Hi,

Just to clarify, the error is thrown as soon as you select the camera in MAX, not when you attempt to perform a grab or snap? If the error is ocurring when image acquisition is attempted, it may be possible that the packet size needs to be reduced. What is the current setting for packet size in Acquisition Attributes? What operating system are you using?

[stevegraff]

First the easy question.  The error occurs on clicking on the camera and not on the grab.  The screen shot of the error is below.  Also a screen capture of my MAX is below.

I am running XP SP2.

Since I cannot even get the session started I cannot check on the packet size.  No grab is in progress.  The camera however indicates that it is connected to the application through a green LED.  This goes out when I select away from the camera.  There seems to be a problem bringing up the session screen with this camera.  It works for the Genie C1400 which I also can connect and grab images with.

[Matt_McLaughlin]

Hi Steve,

The error comes when the Dalsa Genie HM6400 is selected, not the Unidentified PXI System, correct? If this erroneous behavior is limited to this specific camera, there may be a problem with the cameras XML file. Every GigE camera will have an XML camera file identifying how commands are sent and received and there may be a problem with how the HM6400's specific files were imported. Try disconnecting the camera from the system, deleting these files, and reconnecting the camera. This should reinstall these files. These files will be intuitively named and will located at a location very similar to that described in the Where Do I Place My Camera File Once I Download It? knowledge base article. The only change in file location will be that the folder is called NI-IMAQdx not NI-IMAQ. In side the Data folder, we will want to delete three files: a .xml, a .icd and a .iid file.

Let us know how it goes.

[stevegraff · Accepted solution]

Okay,

          Telling me where the files are stored was the winner.  I found there were only 2 files for the HM640 the .iid and the .xml  the .iid had no camera file.  This is because the XML file had a bad line in it.  When I deleed the camera I found that the file reappeared with the asme bad lines. I assume that this is downloaded from the camera.  I went to the dalsa site and downloaded another version of the XML file and replaced the downloaded one.  Bingo.  Then there was also an .icd file everythingworked.  thanks for the hints.  apparently that BFFF800B error was because of the bad line in the .xml file.  I'll go to Dalsa with this problem and see if they still have a firmware bug.  Thanks for the help!