imaqdx Unknown network error (-1074360277) at config

[mathieuchenard]

We are using two Prosilica GigE camera with imaqdx and we are frequently getting error -1074360277 (Unknown network error) at 'IMAQdx Configure Acquisition.vi'.

We also observed that, once the error as happened, we need to close LabView or the compiled app in order to be able to start a live grab again.

I would like to know what could be the cause of that error.

Thanks,

Mathieu

[BlueCheese]

Hi Mathieu,

This generally means that a register that the GenICam XML file is referring to is returning an unexpected GigE Vision error when the register is being read or written. This usually points to an error in the camera's register implementation or mismatch between how the camera's XML file describes how the features interact and how the camera's registers actually behave. Normally the XML file will prevent any register access from occuring that would be invalid.

Prosilica does update their firmware fairly regularly, so you might want to check and see if they have any updates on their website. If you still encounter problems, you could try to take a capture using the Wireshark trace utility (available as open source software online) and provide that to me along with the camera's XML file (usually downloaded to C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data\XML)

Eric

[mathieuchenard]

Good afternoon,

I upgraded to the latest firmware and I still get the error most of the time. I took a trace of two of those events with wireshark and the xml file of the camera.

See the two attached zip files.

Thanks a lot!

[Chris V]

Hi mathieuchenard,

You could also try deleting that xml file in case it got corrupted.  If you delete the file it will be redownloaded from the camera the next time you connect it.

Have a great day,

Chris V

[mathieuchenard]

Thanks for the idea.

I tried deleting the xml files after the error has occurred. The next open operation did redownload the file but the 'unknown network error' occurred again. The only way the restart the grab was to restart the app.

I also also compared the XML file from a successful grab and one when the error occurs and they are the same.

An other interesting fact is that if the 'unknown network error' happen on one camera, the other camera won't start also.

Thanks,

[Chris V]

Hi Mathieu,

It looks like other customers have had a similar problem.  Check out this forum and see if any of these steps help:

http://forums.ni.com/t5/Machine-Vision/Unknown-network-error/td-p/1446698?requireLogin=False

Have a great day,

Chris V

[mathieuchenard]

Thanks Chris for the suggestion,

This thread was started by my colleague so it is the same issue. We have tried those steps but the problem keeps reappearing.

If someone can help, here is the register access log from a good session and one from a bad session (taken with Wireshark).

Thanks,

[BlueCheese]

Your "error" trace does not appear to be from a opening the camera - it appears as though the camera is already open at this point from the driver's perspective. What is the sequence of events that lead up to this? Is the camera being rapidly closed and opened?

Eric

[mathieuchenard]

Good afternoon,

You are right, it does not seem to be starting at the beginning.

Here are some logs I took from this morning.

Thanks,

[Chris V]

Hi mathieuchenard,

What process were you running through when you created each of these logs?

It looks like something is interrupting the communication with your camera towards the end of each log.  Does this correspond with the error you're seeing?

Have a great day,

Chris V