Differences between genicamBrowser and CVB management console

gigevision
genicam
acquisition
#1

Hi all,

I have the strange situation where on one device running windows 10, the genicam browser cannot find any cameras at all, but the CVB management console can. This sparks an interesting question; what exactly is the difference between the two “under the hood”.

Also, there are some curious errors being thrown in the management console;
1 : ReadMem returned error: Timeout: -1011, ReadReg failed : RuntimeException thrown (file ‘Port.cpp’, line 132) (CVC_E_ERROR)
2 : ReadMem returned error: Timeout: -1011, ReadReg failed : RuntimeException thrown (file ‘Port.cpp’, line 132) (CVC_E_ERROR)

#2

Regarding what cameras and interfaces are shown, one difference is that in the Device Configurator portion of the Management Console you see what the VIN driver provides while the GC Browser goes directly through the transport layer. So, what you see in the GC Browser is similar to what you see in the Advanced Config of the Management Console/Device Configurator.

#3

That is what I thought as well, but alas, genicam browser does not show any cameras. With advanced config in the management console, they show up as expected.

Also of interest, I can grab images from the camera, although with a -lot- of dropped packages. Maybe that is the cause?

#4

Do you see the transport layers in GenICamBrowser? As there are more possibilities to configure the view, it might be the case, that Transport Layers are disabled?

Screenshot_GCBrowserTLs

Did you check the cameras with the multiple magnifying glasses? This one is for device discovery ignoring the subnet.

#5

image

#6

Did you check the cameras with the multiple magnifying glasses? This one is for device discovery ignoring the subnet:
Screenshot_GCBrowser_Discovery

#7

Yes, although the camera is in the same subnet. At first, I suspected some firewall to be the culprit, but that would not explain why it does work in the management console. A .vin driver configured by the management console can also be loaded in the viewer.

The configured device cannot be found via the genicam browser.

#8

The devices, defined in the INI file, should show up in “Configured Devices” of the GenICam Browser. Those are the ones, you see in management console. The cameras you see in advanced config should be the same as in Available Devices. So there are 2 cases:

  • Management Console (.vin) -> GenICam Browser Configured Devices
  • Advanced Config (Transport Layer) -> GenICam Browser Available Devices

Maybe I see more if you send me a log output (with --debug) by starting the GenICam Browser in Command Shell. Nevertheless this behaviour is strange and has not happened before.

#9

Another point: Please check if the INI file is located in %cvbdata%Drivers.

#10

It is, everything seems normal in that regards (mind you, using the CB viewer with the geniCam.vin works just fine)

#11

Also one key difference is that the Management Console is run with administrator rights. Do the cameras appear if you start the GenICam Browser with elevated rights?

#12

No, that was one of the first things I tried. Still no luck! There is something horribly wrong on that system though; I can grab about 180 images before the stream freezes, and there is a horrible package resend. I’m suspecting this might be a bit more complicated than just the difference between the management console and the genicam browser… Although, it still is very odd that these two behave differently.

#13

@Diverl I sent you a set of logs via email :slight_smile:

update:
SO, a weird exception is being thrown;
2018-03-28 12:23:57.645 FATAL Module::getNodeMapFromHandle(): Failed to get NodeMap due to cvbBase::exception: “Unable to load Interface-XML: No matching file found.” for FD::MAC->D8-9E-F3-2E-01-A8 (Nodemap: Interface )

Seems to be the culprit. Is that a local file that is missing?

#14

Update;
After a complete clean instal of the system, and installing camerasuite 13.000.00 the problem was gone. It came right back after installing the full CVB package v 13.000.05

Uninstalled, and installed full CVB 13.000.00, and it now runs without the aforementioned issues.