Can we restrict the IP address for the NxView object?

Questions & Answers
1

General Information

  • Product: e.g. ENSENSO S10
  • Ensenso SDK Version: 4.1.1033
  • Operating System: Windows

Problem / Question

Hello, I have a problem that on my subnetwork, I have ensenso camera connected, but also RGB camera from another manufacturer. I am using the SDK from the other manufacturer to control these camera, but the Ensenso SDK still detect them and time to time is locking them, producing an error in the other SDK. When we launch the NxView object, is there a way to avoid this conflict ? Or assign a range of IP address the NxView is allowed to look at ?

2

Hello Etienne,

if the cameras are connected to two different network adapters you can disable the RGB camera in the NxLib Tree via the network adapter’s Active flag.

Otherwise, the only possibility right now would be trying to add a firewall exception that blocks NxView from using certain IP addresses.

We are planning to add functionality for a) disabling the listing (and reading) of non-Ensenso cameras and b) filtering the IP ranges.

Kind regards
Benny

3

Thanks for the pointer, I will try them !

4

You could also use multiple, distinct IP ranges on the same adapter, like 10.0.1.0/24 and 10.0.2.0/24. Each IP range will then have a separate flag in the tree to disable camera listing. And then you can separate the Ensenso devices in a separate range and disable listing for the others.

5

I spent some times trying to configure the firewall to filter the IP addresses from the RGB camera to not be used by NxView.exe (as a test), but somehow it’s still discovering the cameras. It’s only when I block ALL IP that finally the discovery doesn’t work, but if I allow only one IP address, all the cameras are still discovered. I will continue to explore. We are using Windows by the way.

@rainer.voigt when you say a separate flag, it will show as a different adapters in the tree ?

Thanks again for your suggestions and help

6

@benthie Correct me if I’m wrong.

Yes, each IP range will show as separate adapter with a separate ‘Active’ flag in the tree, also when multiple ranges are located on the same adapter.

7

Hi @EtienneDavid

I can actually confirm that this doesn’t work as you want it . You can have two IP ranges (let’s say subnet 1 10.0.1.0/24 and subnet 2 10.0.2.0/24) on the same adapter, which will show up as two separate interfaces in NxLib. You can then assign the cameras into the two IP ranges, let’s say Ensenso cameras in 1 and other GigEVision devices in 2, and disable camera listing for 2 via the Active flag.

This has the effect that NxLib will not send discovery packets for the IP range of 2, but it will effectively reach the device via the discovery packets in IP range 1 on this adapter, and list it anyway, but with invalid network configuration…

I admit that this is maybe not optimal, and I don’t see an easy solution/workaround for now, except using separate hardware interfaces. We will try to filter this correctly for this use case in the next release, which is set for end of the year.

best regards, Rainer

8

Thanks for the answer, it’s quite clear and a good enough solution. I hope we can control it better in the future.

Best,

Etienne