05-21-2014 05:38 PM
Hi Buttersworth,
One step that works sometimes is to go into your windows firewall in Control Panel and then go to advanced settings. I would create a new inbound rule, by right-clicking inbound rules and selecting New Rule. In the following menu I would choose Port and then hit next. Then I would choose UDP and All llocal ports and then hit next. Then I would choose Allow the Connection and Next.In the next menu leave it all selected and hit next. Then name it as you want and hit finish. I would do this for outbound rules as well. This makes sure that we are allowed access through the windows firewall. Even if it is off, there may be some interference by windows firewall.
05-22-2014 10:44 AM - edited 05-22-2014 10:56 AM
@FuManWho wrote:
Hi Buttersworth,
One step that works sometimes is to go into your windows firewall in Control Panel and then go to advanced settings. I would create a new inbound rule, by right-clicking inbound rules and selecting New Rule. In the following menu I would choose Port and then hit next. Then I would choose UDP and All llocal ports and then hit next. Then I would choose Allow the Connection and Next.In the next menu leave it all selected and hit next. Then name it as you want and hit finish. I would do this for outbound rules as well. This makes sure that we are allowed access through the windows firewall. Even if it is off, there may be some interference by windows firewall.
Hello Fu.
I think I am the 1st person who did not find an appropriate solution for this GigE problem. I exactly did you what you said about adding Inbound/Outbound Ports. But nothing has changed. Still "Time Out Error". But this time when I activate Firewall, I don't get "Packet Size Error". I only get "Time Out Error" independent of Firewall's activity. I think we've made some progress (:
Do I need to make some adjustments at those options?(max.jpg)
05-23-2014 06:00 PM
Hi Butterworth,
First I would try to increase the timeout. It seems you have already done this, but this is a good step to try. Another thing we can try to do is to reset your camera file. To do this you will need to unplug your camera and then create copies of your camera files (.icd). After that move the copies to a different folder and delet the ones in the current folder. Afterwards plug your camera back and check the folder to see if a new camera file populates. Once it has try to select the camera file in NI MAX and try to acquire. The location of your camera can be found in a folder similar to:
C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data
06-06-2014 02:45 AM
@FuManWho wrote:
Hi Butterworth,
First I would try to increase the timeout. It seems you have already done this, but this is a good step to try. Another thing we can try to do is to reset your camera file. To do this you will need to unplug your camera and then create copies of your camera files (.icd). After that move the copies to a different folder and delet the ones in the current folder. Afterwards plug your camera back and check the folder to see if a new camera file populates. Once it has try to select the camera file in NI MAX and try to acquire. The location of your camera can be found in a folder similar to:
C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data
I've already done this but It could not help.
06-09-2014 10:07 AM
Do you have it configured for an external trigger? That would cause a timeout. Have you tried to lower the packet size to something much smaller? Have you tried enabling resends?
Jeremy P.