User manual
Version: v4.5.2
6
2/10: 1000 received frames among which 1000 have been ignored (size cutoff ),
0 dropped
frames ,
0 processed frames
1 missed frames
7
3/10: 1000 received frames among which 1000 have been ignored (size cutoff ),
0 dropped
frames ,
0 processed frames
1 missed frames
8
4/10: 1000 received frames among which 1000 have been ignored (size cutoff ),
0 dropped
frames ,
0 processed frames
2 missed frames
9
5/10: 1000 received frames among which 1000 have been ignored (size cutoff ),
0 dropped
frames ,
0 processed frames
0 missed frames
10
6/10: 1000 received frames among which 1000 have been ignored (size cutoff ),
0 dropped
frames ,
0 processed frames
0 missed frames
11
7/10: 1000 received frames among which 1000 have been ignored (size cutoff ),
0 dropped
frames ,
0 processed frames
0 missed frames
12
8/10: 1000 received frames among which 1000 have been ignored (size cutoff ),
0 dropped
frames ,
0 processed frames
0 missed frames
13
9/10: 1000 received frames among which 1000 have been ignored (size cutoff ),
0 dropped
frames ,
0 processed frames
0 missed frames
14
10/10: 1000 received frames among which 1000 have been ignored (size cutoff ),
0 dropped
frames ,
0 processed frames
0 missed frames
15
Closing device connection ...
16
Theoretical acquisition period : 2985 us.
17
Device raw acquisition period : mean = 2985.08 us , STD = 0.271293 us ,
min = 2985 us ,
max = 2986 us , median = 2985 us.
18
Device sending period : mean = 2986.27 us , STD = 73.1067 us ,
min = 2985 us ,
max =
8955 us , median = 2985 us.
19
20
UPDATE TIME TEST:
21
Host User PC time between updates : mean = 2986.37 us , STD = 161.047 us ,
min =
11.093 us ,
max = 9297.64 us , median = 2986.1 us.
22
Acceptance criteria : Update time maximum < 30000 us. Test result : PASSED
23
24
MAX downstream latency TEST:
25
Host Latency time added downstream from the device
for
measurement frames : mean =
0.0921108 us ,
max = 2870.29 us , median = 0.816 us.
26
Acceptance criteria : Update time maximum < 20000 us. Test result : PASSED
Listing 8.4: Example of output.
8.5 Compilation of provided samples
The command-line samples discussed in Section 8.3 are shipped with their source code, in order to present
how to use the
SDK
functions. The makefile are built using
. The cmake configuration file to create the
makefile is located in the
fusionTrack SDK/samples
directory, lying in the installation folder. On windows,
creating the makefiles in the default installation directory may require administrator rights.
Compiling the samples requires CMake version 3.11 or newer, and a C++11 compliant compiler (e.g.
gcc 5.4 or newer, clang 3.8 or newer, Microsoft Visual Studio 2015 or newer).
The SDK comes with helper cmake files, which allows to simply use either the C or the C++ sdk with
minimal efforts in a custom-made CMakeListst.txt file, as demonstrated in Listing 8.5.
1
set
(Atracsys_DIR
"path_to_your_install"
)
2
find_package
(Atracsys
REQUIRED COMPONENTS
SDK AdvancedAPI)
3
4
# Using the C API
5
add_executable
(test_sample_c test_sample.cpp)
6
target_link_libraries
(test_sample_c Atracsys::SDK)
7
Atracsys / 2020-06-17 / 16:48:00
63 / 113
