I have solved this problem by the following content from link:
http://dev.theeyetribe.com/dev/#advancedAdvanced
This section describes the advanced features of the EyeTribe Server, e.g. how to change the TCP socket port, how to utilize more than one tracker on the same system, etc.
Configuring the EyeTribe Server
The EyeTribe Server can be configured manually to some degree by modifying the EyeTribe.cfg configuration file. By default this config file is placed in
C:\Users\<current_user>\AppData\Local\EyeTribe\EyeTribe.cfg
If the supported operating system does not support the local app data path the tracker falls back to placing the config file in
C:\EyeTribe\EyeTribe.cfg
The very first time the tracker is launched the config file is saved with default, usable values. If the file is deleted or relocated it will simply be recreated.
The EyeTribe Server reads the config file when it starts up. It will never write to the file once it exists. If the content of the config file is changed the EyeTribe Server must be restarted for the changes to take effect.
Loading a specific config file
The EyeTribe Server can also be launched and instructed to load any supported configuration file. In general the server takes the following argument
EyeTribe.exe
where is optional, and if no config file argument has been provided the server will load the default config file. The config.cfg argument indicates a valid configuration file. It can be provided using either a relative or an absolute path.
The EyeTribe.cfg file
The configuration file contains a JSON formatted structure. The config section describes the parameters that can be modified by the user;
"config" : {
"device" : 0,
"framerate" : 30,
"port" : 6555
}
Configuring socket port
The default TCP socket port that the EyeTribe Server listens to for incoming client requests is 6555. The default port can be modified to cater for special user-defined behavior and environment, for instance when port 6555 is already utilized for another service. Setting the socket port manually is constrained to
1024 < port < 65535
where it is assumed that the port number is not already in use and not reserved by the system or conflicting with other services. If the port is already in use or the EyeTribe Server is unable to bind it, an error will be reported during initialization of the tracker.
Configuring device numbert
The EyeTribe Server only supports operating one tracking device at a time. Up to 8 supported devices can be present in the system, and any one of these can be utilized by the tracker. The device parameter can be used to instruct the EyeTribe Server to utilize a different device than the first, default, device. Setting the device manually is constrained to
0 ≤ device ≤ 7
The EyeTribe Server will report an error upon initialization if the device is either not supported or not present.
Changing frame rate
The EyeTribe Server supports two frame rate modes: 30 and 60 frames per second (fps). The default frame rate is 30 fps. Running in 30 fps will allow for a larger tracking box, whereas the 60 fps mode in nature will be faster but allow for smaller head movements. Setting the framerate manually is constrained to two options 30 and 60 frames per sercond
Only 30 and 60 are valid values. If other values are specified an error will be reported upon initialization of the EyeTribe Server.
Multiple trackers and monitors
It is possible to have a system with multiple concurrent EyeTribe Servers, each operating on a dedicated Tracker and on a dedicated monitor. An instance of the EyeTribe Server must be spawned per Tracker device. Utilizing individual config files per server instance will be a practicable way of setting up such a system.
The client must be able to communicate with each EyeTribe Server on different TCP socket ports. The client must also remember to specify the active monitor screen to each EyeTribe Server instance, if different monitors are to be distributed between the different trackers. The user must avoid having several trackers active simultaneously due to interfering infrared illumination. A way to control this is to disconnect the client from the EyeTribe Server (e.g., by stopping sending heartbeats) when the eyes are no longer looking at the screen.
by mingxinbit » 28 May 2014, 00:41 