v0.6.10

• bugfix for selecting the correct camera in Windows when multiple cameras are connected
• Added a parameter to allow disabling per-pixel offsets even if included in conf file
• TintinCDK OPT9221 firmware upgrade: readback and retry if some chunks are not written
• Added a new flying pixels filter (Thanks Larry)
• Minor Bugfix for VCO programming for Tintin
• CameraSystemConfigTest improvements to allow setting (and clearing) a default profile, and to remove parameters from a profile.
• Added a command-line VXL file decoder

v0.6.9

This release mainly contains the following changes from the last v0.6.5 release:

• DML updates for OPT8320 and OPT9221
• A new extra long range example profile for TintinCDKCamera
• Fixes to allow building with VS2015
• Fixes to allow building with Ubuntu 16.04
• A bugfix to allow TintinCDK to work with some slower USB hosts
• A bufgfix to compute the effective illumination frequency correctly for ToFTintinCameras
• Some (work-in-progress) refactoring to separate out UVC PID from the main TintinCDKCamera

The official Linux packages are now for Ubuntu 16.04.2 and this time we also include prebuilt Windows packages built with VS2015.
(Note: The VS2015 packages were built with PCL 1.8.0 and are not be fully tested).

v0.6.5

v0.6.5

v0.6.3

This release mainly contains changes to support the OPT8320 (Calculus) chipset and its reference CalculusCDK EVM board.

v0.6.1-preview

Preview release for OPT8320 - this is just for quick functional checks.
Do not use this release for other devices.

v0.6.0

Major Changes

There are several significant changes/simplifications in the way SDK environment needs to be set by user. These changes will be documented on the Wiki in detail. But, in short, here are the changes:

1. A new environment variable 'VOXEL_SDK_PATH' is understood by the SDK. This can be pointed to the installed SDK path or 'build' directory of source SDK. Using this internally, the library related, configuration related and also firmware related default paths are automatically set.
   The variables VOXEL_LIB_PATH, VOXEL_CONF_PATH, VOXEL_FW_PATH used in prior versions are no longer needed, but will still be honoured as before.
2. The 'VoxelCommon' path is completely removed from the SDK and files will not be installed to "C:\Program Files\VoxelCommon' any more. Instead the necessary default 'relative' paths are defined using 'VOXEL_SDK_PATH'.
3. The locations of built code in 'build' directory are re-organized to resemble install tree. So, you'll find now
   a) bin/ -- for executables
   b) lib/ -- for libraries
   c) lib/voxel -- for Voxel libraries
   d) share/voxel-x.y.z/conf -- for Voxel configurations with SDK version x.y.z
   e) share/voxel-x.y.z/fw -- for Voxel firmwares with SDK version x.y.z
   f) lib/python2.7 -- for Voxel SDK python bindings
   both in the install tree as well as the 'build' directory.
4. Viewer related local configurations are created in "~/.Voxel/viewer-x.y.z/" on Linux and "%HOMEDRIVE%%HOMEPATH%.Voxel\viewer-x.y.z" on Linux in order to prevent any configuration mismatches between viewer versions to cause runtime problems.
5. The full list of environment variables to be set are reduced to the following:

On Linux

export VOXEL_SDK_PATH=/path/to/sdk
export PATH=$VOXEL_SDK_PATH/lib:$VOXEL_SDK_PATH/bin:$PATH
export PYTHONPATH=$VOXEL_SDK_PATH/lib/python2.7:$PYTHONPATH

On Windows

set VOXEL_SDK_PATH=
set PATH=%VOXEL_SDK_PATH%\lib;%VOXEL_SDK_PATH%\bin;%PATH%
set PYTHONPATH=%VOXEL_SDK_PATH%\lib\python2.7;%PYTHONPATH%

NOTE: The above paths are valid for installed SDK as well as 'build' directory of source SDK.

v0.5.7

Minor bug fix in Voxel-D _init() function where illum voltage and mod…

v0.5.6

• pause-resume support for DepthCamera and FrameStreamWriter
• remove stray messages when the depth camera does not support EEPROM read/write for configurations
  • also, add support to know whether the depth camera supports read/write of configurations in the EEPROM
• bugfix: allow calling PointCloudTransform functions directly as an API
• bugfix: allow voxelviewer to correctly identify and select the default configuration, if it is a configuration stored in the EEPROM
• updated firmware for VoxelD

Also included is a lightly-tested win32 build.

v0.5.5

New in this release:

• support for Haddock based boards using the RTS5825 chipset (see TI3DTOF/boards/RTS5825Camera).
• Calibration parameters and defining parameters are now per-chipset and per-board

Main Fixes:

• CameraSystemConfigTest now allows writing parameters with negative values by enclosing them in single or double quotes
• Haddock mod_m lsbit should be zero
• On Windows, DLLs are now versioned and the ABI version can be read without loading them. On Linux too, now ABI version is read without loading the shared libraries (.so). This prevents stray DLLs/SOs from being loaded and possibly corrupting the process using the SDK.

v0.5.4

This is a stable release primarily for the TintinCDK. The other boards may not yet be fully supported. Please see https://github.com/3dtof/voxelsdk/wiki for installation instructions.

Mainly, we now have the ability to store configuration profiles to the TintinCDK EEPROM and retrieve them at startup.

On Windows, please delete the following directory to ensure we start with a clean slate

%HOMEDRIVE%%HOMEPATH%\.Voxel

or

C:\Users\<username>\.Voxel

The above directories will be used for storing local copies of configuration files if read from the EEPROM.