Win32 CVB V14.01.007 IP Assignment Issues

The Newest Version of Win32 CVB (14.01.007) does not allow me to assign an IP to my Device. However the previous version (14.01.006) will, even though I am following the same process. See Below:

14.01.007:

Used the Common Vision Blox forum to download and install the:
CommonVisionBlox Runtime 14.01.007 (x64)
Then installed the full package.

Opened the 4.12.6 version of GenICam Browser and scanned for devices (The Device already has a previously set IP and the Network Settings of the PC are already set to match)

Right Clicked on the GO-5000C-PGE device and “assign IP” selected

chose to Auto select the IP port. This showed my desired IP of 172.16.200.1.

Then pressed Set and it comes up with an error

Error string

14.01.006:

Used the Common Vision Blox forum to download and install the:
CommonVisionBlox Runtime 14.01.006 (x64)
Then installed the full package.

Opened the 4.12.2 version of GenICam Browser and scanned for devices (The Device already has a previously set IP and the Network Settings of the PC are already set to match)

Right Clicked on the GO-5000C-PGE device and “assign IP” selected

chose to Auto select the IP port. This showed my desired IP of 172.16.200.1.

Then pressed Set. The pop up now appears to set the IP to persistent.

Once i choose yes to this Option it displays and saves as expected.

Has something been changed regarding the assignment of IP addresses in the recent release?

Hi @Oliver,
thank you, we already have a look at this.
Will come back, as soon as fixed.
Best

1 Like

The same error occurs in the new 14.01.008 release.

Could you please verify, whether you correctly uninstalled 14.01.006 before and installed 14.01.008.

Hello,
I have uninstalled all CVB software from my PC.
Using the CVB forums to download:

Common Vision Blox for Windows - Downloads - Common Vision Blox User Forum

image

I then installed the newest version.
Allowed it to preform a complete installation into the file path the installer chose.
Opened the GenICam Browser application.

Set my PC’s port “Internet Protocol Version 4 (TCP/IPv4) Properties” to “use the following…”


(with the driver active and the IPv4 only)

then inside of the GenICam Browser I clicked on the “Ignore Subnet discover” to search for my device.
The device in this instance is a GO-5000C-PGE camera
GenICam found the device under the “Socket driver”

image

I right-clicked on the result and then clicked “assign IP” from the dropdown list.
I changed the IP and Subnet to the below and then clicked “set”

This is where the error shows up.

image

Following the same method in 2 versions Prior this exact method brings up no errors and will allow me to proceed

I installed the software as per the installer. Is there anything you can suggest to ensure that the previous version is properly removed before installing the newer software in case there are any remnants of the older version left over.

Thank you in advance

Hi @Oliver,
that seems correct. We countercheck the issue on win32 here. Because that bug was fixed with 14.01.008 and verified on 64bit Windows.

Could you tell us the version within the properties of GevTL.cti within %CVB%\GenICam\bin\win10_i86\TLIs .

Here is a screenshot of the properties window for each of the items within my:
C:\Program Files (x86)\STEMMER IMAGING\Common Vision Blox\GenICam\bin\win32_i86\TLIs
Folder

Hi @Oliver,

We have investigated this issue internally on CVB 14.01.008 Win32 and can reproduce the issue only if we do the following:

  1. Open GenICam Browser
  2. Whilst the GenICam Browser is open, change the network address of the interface that the camera is attached to.
  3. Change IP of a camera connected to previously modified interface

At this point, the warning “Please check if the device with IP … is in the correct subnet” will be shown.

The reason for this issue is that the GenICam Browser caches the network interface IP addresses on startup and does not expect these to change whilst it is running. When they are changed, the mismatch that you experience occurs.

You can check this by right-clicking on the driver → Info and looking what the subnet IPv4 address is set to. See below (network interface is cached as 172.16.200.10 but was changed to 172.16.100.10 whilst the camera is using the new address of 172.16.100.2):

I have created an internal ticket to improve this behaviour.

Restarting the GenICam Browser refreshes the network interface cache and fixes this issue.

Please let me know if restarting the GenICam Browser after changing the network interface fixes the issue.

1 Like