IFM device discovery and change of the IP

[matijazigic]

Hello everyone,

I've been trying for quite some time to find a way to connect to the VPU and cameras programmatically or from the command line, but without success. For my company, it is important to have this functionality because we are running three cameras on a vehicle, and a fast configuration and calibration procedure is essential for our end-of-line process.

As mentioned in other topics and here, there is an auto-discovery option and the ability to change the IP address when the VPU device is found. This would be extremely useful for us to integrate into our workflow. I am able to do this with the ifmVisionAssistant, but we prefer not to use two separate software solutions. We want the process to be as fast as possible, and some of our colleagues do not have access to ifmVisionAssistant.

Below are screenshots showing what I get with the ifm3d discover option and with the VisionAssistant:

Additionally, here is what I get when running the Python script for ifm discovery mentioned earlier in the discussions. I encounter the same error on both Windows and Ubuntu. Am I doing something wrong?

Do you have any other options for identifying the IP and changing it? The user will not be on the same subnet, so we need to replicate what is done in the ifmVisionAssistant (image 2) — specifically, retrieving the device and programmatically changing its IP address.

Perhaps @graugans or @lola-masson could help?

[lola-masson]

Hi @matijazigic,

Looking at your first screenshot, it looks like the device is actually found, only the device type cannot be identified:

Regarding setting a temporary IP address using the CLI, this is a feature we are currently implementing, so it should be available shortly. Until then, you would need to set your computer in the same subnet.

[matijazigic]

Hello @lola-masson, is official update going to be out soon?

[graugans]

Maybe a bit late in the game, there is this archived version of the Python script I wrote ages ago: https://github.com/ifm/python-ipv4-discovery/blob/master/discovery.py as far as I do remember there was an issue with sending request on a distinct interface without root access on Linux.

[matijazigic]

Hello @graugans yes, I tried that one over a year ago. We had problems while using that script with the detection of the devices, and also there is no possibility to change the IP once the device is discovered.

[lola-masson]

Hi @matijazigic, we are planning on doing a pre-release at the end of the week, followed by our tests, which means we should have an official release within the next few weeks.

[graugans]

Hello @graugans yes, I tried that one over a year ago. We had problems while using that script with the detection of the devices, and also there is no possibility to change the IP once the device is discovered.

I am not sure if I fully understand your sentence there is no possibility to change the IP once the device is discovered Within the script the ip can be changed: https://github.com/ifm/python-ipv4-discovery/blob/master/discovery.py#L114

[matijazigic]

I fixed some problems with the print statements inside the script but still there is an error:

[sudo] password for hrjhmz00: IP: 192.168.0.69 interface: eth0 Traceback (most recent call last): File "/home/code_sandbox/3D/o3r_framework/discovery.py", line 75, in <module> s.setsockopt(socket.SOL_SOCKET, 25, args.interface) # 25 is the magic number to use a specific interface 'SO_BINDTODEVICE' TypeError: a bytes-like object is required, not 'str'

I can try to fix it, but exact same errors I got before. Where can I find updated script? Thanks for your help.

[matijazigic]

I fixed some problems with the print statements inside the script but still there is an error:

[sudo] password for hrjhmz00: IP: 192.168.0.69 interface: eth0 Traceback (most recent call last): File "/home/code_sandbox/3D/o3r_framework/discovery.py", line 75, in <module> s.setsockopt(socket.SOL_SOCKET, 25, args.interface) # 25 is the magic number to use a specific interface 'SO_BINDTODEVICE' TypeError: a bytes-like object is required, not 'str'

I can try to fix it, but it is same errors I got before. Where can I find updated script?

[matijazigic]

I tried with all changes you introduced, problem still exists.

[graugans]

Okay, the script does execute without a Python Error but still you are not able to change the IP right?

[graugans]

VPU: M04239 Firmware version:

I'm running script in the WSL2 environment.

I am not sure if the broadcast will work in an WSL2 Environment. Do you have an RaspBerry PI running Linux or maybe a second VPU available to test this?

[matijazigic]

Is it possible to run script from windows machine?

[matijazigic]

I got response via Windows; I made couple changes on the script.

PS D:\SW\AGVEP-o3r_tools> python discover2.py -i 192.168.0.143
No IP address specified. Just reading responses.
Trying to find server...
Magic matched, sender: ('0.0.0.0', 3321)
Device IPv4 addr:   192.168.0.69
Gateway IPv4 addr:  192.168.0.201
IPv4 subnetmask:    255.255.255.0
XML-RPC port:       8080
Vendor-ID:          0x0001
Device-ID:          0x0302
Device-MAC:         48:b0:2d:54:d7:fd
Device-Flags:       0x0000
Device-Hostname:    ovp80x-54-d7-fd
Device-Name: