Storage of Settings

The different software components of the Ensenso SDK store their settings and cached data in a settings directory inside of the directory indicated by the ENSENSO_INSTALL environment variable.

When running the SDK from an archive file without an installation the settings directory is stored where you extracted the archive unless the ENSENSO_INSTALL environment variable is set (either manually or from installing another version of the SDK).

Subfolder

Purpose

NxLib

camera_cache.json: A local cache of the EEPROM content for cameras that have been discovered in the past. Depending on the camera model, the EEPROM can contain additional information, such as the camera’s model name and calibration status. Reading the EEPROM requires to open the camera and can take a long time. The cache can therefore speed up listing of cameras. The file can be removed without losing any data.

file_cameras.json: A list of file cameras registered on the current system.

virtual_cameras.json: A list of virtual cameras registered on the current system.

NxView

settings.json: Global (camera independent) settings saved when last closing NxView. The same file also contains general NxView settings.

camera_settings_<serial>.json: The last parameters used for a camera in NxView. Opening the camera in NxView will apply these parameters by default.

NxTreeEdit

settings.json: General settings for NxTreeEdit.

cameras

eeprom_<serial>.json: Files for storing the EEPROM content for file cameras, virtual cameras, and GigE Vision-based cameras that do not support EEPROM or flash storage.

genicam

genicam_cache_<serial>_<model>_<firmwareVersion>.xml/zip: Compressed or uncompressed GenICam XML specification of a specific camera and firmware. This is used to speed up the process of opening GigE Vision-based cameras

presets

*.json: Parameter preset files. See the GetPresets command for a detailed description of the preset schema.

schema

*.json: Our provided JSON schema files. You can reference e.g. our preset schema in your own presets and let your IDE auto-complete and validate the preset while editing it. The schema files also provide documentation for each of the data fields they validate.