Skip to main content

Configuration & Usage

Configuration Setup​

File Locations​

After installation, the configuration file VxConfig.conf and VxExposure.yaml will be located at:

  • Windows:

    C:\Program Files\vizionsdk\bin\VxConfig.conf
    C:\Program Files\vizionsdk\bin\VxExposure.yaml

  • Linux, NXP-iMX, NVIDIA-Jetpack6.x and later:

    /usr/share/vizionsdk/VxConfig.conf
    /usr/share/vizionsdk/VxExposure.yaml

  • Local library (Tarball Extraction):

    /vizionsdk-{version}-{os}/bin/VxConfig.conf
    /vizionsdk-{version}-{os}/bin/VxExposure.yaml

File Descriptions​

  • VxConfig: A configuration file used by VizionSDK to recognize TechNexion camera series.
  • VxExposure: A YAML file defining the default minimum and maximum exposure time values for each sensor and resolution.
tip

You can also customize the location of VxConfig.conf and VxExposure.yaml by setting the VIZIONSDK_CONFIG_PATH environment variable.

How to use VizionSDK​

You can link the VizionSDK library with CMake. For more details, see the Sample Build Guide.

Prerequisites​

  • CMake (version 3.0 or newer)
  • C++ compiler

Import the library​

Add the VizionSDK header in your code:

#include "VizionSDK.h"

Build the project with CMake​

Using System-Installed SDK (.exe or .deb Installed)​

If you installed VizionSDK using the installer, use the following CMake commands:

# Find VizionSDK package
find_package(vizionsdk REQUIRED)

# Link libraries
target_link_libraries(${PROJECT_NAME}
    PRIVATE
    vizionsdk::VizionSDK
)

Using Extracted SDK Archive​

If you are using the SDK directly from the extracted folder, update the paths manually:

# Set path to the SDK library directory
# NOTE: Update this path to match your SDK location

target_include_directories(${PROJECT_NAME}
  PRIVATE
  <YOUR_SDK_PATH>/include/vizionsdk
)

target_link_directories(${PROJECT_NAME}
  PRIVATE
  <YOUR_SDK_PATH>/lib
)

# Link libraries
target_link_libraries(${PROJECT_NAME}
  PRIVATE
  VizionSDK
)

For more detailed information and advanced usage, please refer to the API documentation or the examples on GitHub.