10-12-2009 06:02 PM
Zen,
Have you checked all the triggering settings and ensured you didn't enable some sort of triggering? IMAQdx will save the camera's settings and so if you turned on a frame trigger in the past it might still be set. You could also try switching the camera into a test image mode which would eliminate all triggering as a source of a timeout. You can find these attributes in the camera attribute tree. If you get a test image this indicates it is not a network-related issue you are running into.
Eric
10-13-2009 11:55 AM
10-13-2009 12:16 PM
Hi Zach,
Yes, I have read this note and performed all the relevant steps outlined there. I have come accross it before I posted my question on this forum.
Hi Eric,
I did check the triggering setup and the camera is set up NOT to use external trigger. In fact, Pylon Viewer has no problem grabbing images from the camera, which makes me suspect that either there is something missing in my LabVIEW (8.6) installation or there is some confusing messup with the NI device drivers, or something... To add to the confusion, I tried using identical camera on a different computer where LabVIEW 7.1 is installed with vision, etc. and get the same results. This installation of LabVIEW (7.1) has been used successfully with a different camera, not GigE.
I have placed an order for the Intel PRO 1000 network card and am hoping that using that card will make the problem go away.
Thank you both.
Zen
02-09-2010 10:31 AM
Hi Zam...
Actually I have exactly the same problem. Do you found some solution to this yet??
I'll really appreciate this information.
Thank you in advance.
Nft
02-09-2010 12:02 PM
Hello everyone.
We already fix this issue; the solution was reduce the packet size for the camera and no timeout error occurs again.
I hope this will be helpfull for someone else.
Best Regards,
Nft
03-19-2010 04:54 AM
i have the same problem how did you reduce the packet sizes.
thanks for advance
03-19-2010 07:45 AM