LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Disable identification of network cams

Solved!
Go to solution

Dear all,

 

I'm using LV2010 with 2 USB cameras. The cameras are controlled as NI-IMAQdx devices and everything works fine.

 

However, there is an irritating behaviour:

 

Labview is always scanning the intranet for all connected cameras. In my company are more than 10 cameras identified which are used by other colleagues. Sometimes the ordering of the cams is changing and I have to identify and choose my own USB cam again. Additionally, I think the IP-scan waste some time. The loading procedure takes much longer as soon as I include IMAQdx SubVIs.

 

My question: Is it possible to disable the IP-scan for other cameras? I haven't found any information about how to inentify USB cams, only.

 

Thanks in advance,

 

Mos.

0 Kudos
Message 1 of 10
(3,646 Views)

If the cameras you're using are in a small area, use a home network router to isolate the corporate network from the network on your bench. 

 

Company LAN goes into the "internet" hole, your PC + cameras go into the four downstream ports.  Configure the router to grab an IP from the company's DHCP, then assign its own IPs to the downstream ports.  DAQmx won't go past the router's subnet to look for more devices.

 

Something like this: http://www.dlink.com/products/?pid=478

 

0 Kudos
Message 2 of 10
(3,634 Views)

Thanks SnowMule,

 

I see that it is possible to use a software or hardware firewall to block the intranet cams.

 

However, I would prefer to configure LabView software to confine the "scan range".

 

Any other suggestions?

0 Kudos
Message 3 of 10
(3,620 Views)

Hi MosEisley53,

 

You could try to add the registry key EnabledIPCameras under Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\niimaqdxk\Parameters.

Right click on a part of blank space on the window on the right, and selecting New -> DWORD (32-bit Value). You can then enter EnabledIPCameras as it's name, and leave the value as is.

 

 

Ch



0 Kudos
Message 4 of 10
(3,615 Views)

Christian is right.  See here.

0 Kudos
Message 5 of 10
(3,610 Views)

Hi Christian,

 

this is exactly what I looked for. BUT: It doesn't work. Smiley Frustrated

 

If I disable my network card only my two USB cams are identified and the program immediately starts. But your registry key does not show any effect. Can you check if the key is right, please? I've attached a screenshot from regedit. I've already tried a reboot.

 

Thanks, Mos.

 

 

0 Kudos
Message 6 of 10
(3,591 Views)

Sorry, I forgot to attach the right screenshot:

 

 

0 Kudos
Message 7 of 10
(3,585 Views)

Yes, the key is right.

 

You can also disable the GigE discovery as mentioned by Guenther before. See here.

 

 

Christian

0 Kudos
Message 8 of 10
(3,573 Views)

Disabling the discovery ping works as expected. I have checked this with wireshark several times.

0 Kudos
Message 9 of 10
(3,570 Views)
Solution
Accepted by topic author MosEisley53

Thank you: I found the solution with your help.

 

The suggested reg key EnabledIPCameras has a spelling error. After playing around I found out that EnableIPCameras works. So, the d was wrong. Thank you, Chris!

 

Disabling the discovery ping does not reduce alone the time for IMAQdx Enumerate Cameras VI drastically. And I use this now to check all my USB cams are working well.

 

For your information a comparison of the first time start ups of my program in milliseconds:

 

 

EnableIPCameras=1 DiscoveryTimeout=1000:19082ms

 

EnableIPCameras=1 DiscoveryTimeout=0:18082ms

 

EnableIPCameras=0 DiscoveryTimeout=1000: 1077ms

 

EnableIPCameras=0 and DiscoveryTimeout=0: 79ms

 

 

So, thank you Chris and Günther! With both hints I was able to minimize waiting times!

 

0 Kudos
Message 10 of 10
(3,560 Views)