Configuration & Usage
Configuration Setup
File Locations
After installation, the configuration file VxConfig.conf and VxExposure.yaml will be located at:
/vizionsdk_c-{version}-{os}/bin/VxConfig.conf
/vizionsdk_c-{version}-{os}/bin/VxExposure.yaml
File Descriptions
- VxConfig: A configuration file used by vizionsdk_c to recognize TechNexion camera series.
- VxExposure: A YAML file defining the default minimum and maximum exposure time values for each sensor and resolution.
Setting the Config Path
If you haven’t installed the native VizionSDK library, please set the VIZIONSDK_CONFIG_PATH environment variable as shown below:
- Windows
- PowerShell:
$env:VIZIONSDK_CONFIG_PATH = "path\to\vizionsdk_c-{version}-{os}\bin" - Command Prompt (CMD):
set VIZIONSDK_CONFIG_PATH=path\to\vizionsdk_c-{version}-{os}\bin
- PowerShell:
- Linux
export VIZIONSDK_CONFIG_PATH=/path/to/vizionsdk_c-{version}-{os}/bin
Alternatively, you can place the VxConfig.conf and VxExposure.yaml files in the same directory as your executable.
How to use vizionsdk_c
You can link the vizionsdk_c 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_c header in your code:
#include "vizionsdk.h"
Build the project with CMake
Link vizionsdk_c library from the extracted folder, update the paths manually:
# Set path to the vizionsdk_c library directory
# NOTE: Update this path to match your vizionsdk_c location
set(VIZIONSDK_C_PREFIX <your_vizionsdk_c_path>)
list(APPEND CMAKE_PREFIX_PATH ${VIZIONSDK_C_PREFIX})
find_package(vizionsdk_c REQUIRED)
target_include_directories(${PROJECT_NAME}
PRIVATE
${VIZIONSDK_C_INCLUDE_DIR}
)
# Link libraries
target_link_libraries(${PROJECT_NAME}
PRIVATE
vizionsdk_c::vizionsdk_c
)
vizionsdk_c automatically links to VizionSDK if it is available in the system PATH.
If not found, it will link to the native library located in the same directory as vizionsdk_c.
For more detailed information and advanced usage, please refer to the API documentation or the examples on GitHub.