User manual
Version: v4.5.2
9
}
10
]
11
}
12
}
Listing 15.1:
JSON
file setting the IP to 172.16.2.4
Please note the UDP port used by the fusionTrack (the 3509 value) cannot currently be changed.
15.2
Changing the local UDP port
The local UDP port (i.e. the random port on the machine used to communicate with the UDP server on
the fusionTrack device) can be forced to a value. To be valid, the value should neither be currently in use
nor reserved by the operating system. The configuration
JSON
file must be changed, and a new attribute
"localPort": port_number
added to the interface to be modified (see example on Listing 15.2). If the
port cannot be used for any reason, the device will not be detected, resulting in a ‘No device detected’
error.
1
{
2
" network ":
3
{
4
" version ": 1,
5
" interfaces ": [
6
{
7
" address ": "172.17.1.7" ,
8
"port ": 3509 ,
9
" localPort ": 13485
10
}
11
]
12
}
13
}
Listing 15.2:
JSON
file trying to force the local UDP port.
15.3
Connection to multiple fusionTrack devices
The new
ftkInitExt
function also allows to use the same library handle to connect to more than one
fusionTrack device. The recommended way to do it is to use one dedicated Ethernet adapter per fusionTrack
device, in which case, all devices must have a different IP address, if possible each on a different subnet.
Then the host PC must have one direct connection of each fusionTrack. The configuration file to set one
device with IP
172.17.1.7
and another one with IP
172.17.10.7
is presented on Listing 15.3. It is also
possible to use a GigaBit switch, implying all fusionTrack device having a
different
IP address in the
same
subnet.
1
{
2
" network ":
3
{
4
" version ": 1,
5
" interfaces ": [
6
{
7
" address ": "172.17.1.7" ,
8
"port ": 3509
9
},
10
{
11
" address ": "172.17.10.7" ,
Atracsys / 2020-06-17 / 16:48:00
85 / 113
