Troubleshooting

Error codes

Error codes

Error Code

Value

Description

VmbErrorSuccess

0

No error

VmbErrorInternalFault

-1

Unexpected fault in Vmb or driver

VmbErrorApiNotStarted

-2

VmbStartup was not called before the current command

VmbErrorNotFound

-3

The designated instance (camera, feature, etc.) cannot be found

VmbErrorBadHandle

-4

The given handle is not valid

VmbErrorDeviceNotOpen

-5

Device was not opened for usage

VmbErrorInvalidAccess

-6

Operation is invalid with the current access mode

VmbErrorBadParameter

-7

One of the parameters is invalid (usually an illegal pointer)

VmbErrorStructSize

-8

The given struct size is not valid for this version of the API

VmbErrorMoreData

-9

More data available in a string/list than space is provided

VmbErrorWrongType

-10

Wrong feature type for this access function

VmbErrorInvalidValue

-11

The value is not valid; either out of bounds or not an
increment of the minimum

VmbErrorTimeout

-12

Timeout during wait

VmbErrorOther

-13

Other error

VmbErrorResources

-14

Resources not available (e.g., memory)

VmbErrorInvalidCall

-15

Call is invalid in the current context (e.g. callback)

VmbErrorNoTL

-16

No transport layers are found

VmbErrorNotImplemented

-17

API feature is not implemented

VmbErrorNotSupported

-18

API feature is not supported

VmbErrorIncomplete

-19

The current operation was not completed (e.g. a multiple
registers read or write)

VmbErrorIO

-20

There was an error during read or write with devices
(camera or disk)

General issues

Transport layer not found

See Typical Linux issues

Feature not usable

If a feature is not usable, use the latest camera firmware.

Issues by camera interface

GigE cameras

To use your GigE camera with best possible performance, follow the instructions in the User Guide of your camera.

5 GigE Vision cameras

To get your 5 GigE Vision camera up and running, see the user guide for your camera.

PacketSize

Make sure to set the PacketSize feature of GigE cameras to a value supported by your network card. If you use more than one camera on one interface, the available bandwidth has to be shared between the cameras.

  • GVSPAdjustPacketSize configures GigE cameras to use the largest possible packets.

  • DeviceThroughputLimit enables to configure the individual bandwidth if multiple cameras are used.

  • The maximum packet size might not be available on all connected cameras. Try to reduce the packet size.

Other issues

  • Access Mode “Config” is not available in this SDK. Please use IP Config instead.

  • By default, the Allied Vision GigE TL is set to Broadcast (instead of Discovery Once), which constantly consumes bandwidth. For a higher bandwidth, use Discovery Once every time you connect a GigE camera.

USB cameras

Windows only: Make sure the correct driver is applied.

CSI-2 cameras

  • Install the CSI-2 driver before installing the SDK.

See also

For compatible ARM boards, installation instructions, and additional information, see github.com/alliedvision.

Typical Linux issues

Installation instructions:
Vimba Installation under Linux

Transport layers not found

In most cases, Install.sh automatically registers the GENICAM_GENTL64_PATH environment variables in /etc/profile.d, so that every GenICam GenTL consumer can access the Vimba transport layers. If the transport layers are not found:

  • If multiple users work with the system, make sure all users can access /etc/profile.d.

  • If your display manager doesn’t support the install script (for example, lightdm and wdm): Please add the required environment variables to the /etc/environment file.

  • If login shell support is not supported, Install.sh in /etc/profile.d will not be loaded for X-Session. In this case, please copy the following line into the ~/.bashrc file and reboot. export GENICAM_GENTL64_PATH=$GENICAM_GENTL64_PATH: "/PATH_TO_VIMBAFOLDER/VimbaGigETL/CTI/x86_64bit/"