Applied Concepts Inc ACMI007 Manual De Usuario
Applied Concepts 011-0131-00 rev 2
Page 50
GET_CFG_INTERVAL defines how often (in milliseconds) the application polls the
Speed Sensor to update the status fields in the main window. This parameter applies to
the status fields only (Units, Mode, Zone…) – not the speed windows. The default is
5000 ms (5 seconds). This parameter value can be increased to reduce the message
traffic on the link.
RESPONSE_TIMEOUT is the time in milliseconds that the application will wait for a
response from the Speed Sensor before a retry or failure. The default is 500 ms (½
second).
RETRY defines the number of times the application will resend a configuration setting to
the Speed Sensor if it doesn’t get a response.
EE_FORMAT_INTERVAL defines how often (in milliseconds) the application polls the
Speed Sensor for a speed report in EE Format. Polling begins after selecting “Start EE
Polling” from the Actions pull-down menu, and polling stops after selecting “Stop EE
Polling”. The default value is 100 ms (1/10 second or 10 times per second). The value
can be increased or decreased to speed up or slow down the rate of EE Format polling.
ENABLE_SPEED_LOGGING defines whether a speed log file is generated for the
current session. Logging is enabled when the parameter is set =1 and disabled when
set =0. Logging only takes place if the Speed Sensor’s Serial Port Data Format is set for
EE Format.
LOG_ALL_SPEED_DATA is used to inhibit logging 0 speeds. When set =1 all speeds
are logged including 0 speeds. When set =0 only speeds above 0 are logged, and the
length of the log file is reduced.
DATA_LOG_FILE defines the filename for the speed log. This file will be saved in the
directory where the application file and the Dashboard.ini file reside.
Speed Sensor to update the status fields in the main window. This parameter applies to
the status fields only (Units, Mode, Zone…) – not the speed windows. The default is
5000 ms (5 seconds). This parameter value can be increased to reduce the message
traffic on the link.
RESPONSE_TIMEOUT is the time in milliseconds that the application will wait for a
response from the Speed Sensor before a retry or failure. The default is 500 ms (½
second).
RETRY defines the number of times the application will resend a configuration setting to
the Speed Sensor if it doesn’t get a response.
EE_FORMAT_INTERVAL defines how often (in milliseconds) the application polls the
Speed Sensor for a speed report in EE Format. Polling begins after selecting “Start EE
Polling” from the Actions pull-down menu, and polling stops after selecting “Stop EE
Polling”. The default value is 100 ms (1/10 second or 10 times per second). The value
can be increased or decreased to speed up or slow down the rate of EE Format polling.
ENABLE_SPEED_LOGGING defines whether a speed log file is generated for the
current session. Logging is enabled when the parameter is set =1 and disabled when
set =0. Logging only takes place if the Speed Sensor’s Serial Port Data Format is set for
EE Format.
LOG_ALL_SPEED_DATA is used to inhibit logging 0 speeds. When set =1 all speeds
are logged including 0 speeds. When set =0 only speeds above 0 are logged, and the
length of the log file is reduced.
DATA_LOG_FILE defines the filename for the speed log. This file will be saved in the
directory where the application file and the Dashboard.ini file reside.
8.1 Speed Sensor Configuration File
The Speed Sensor configuration files are also ASCII files which can be edited with a text
editor. Stalker Radar provides a different file for each different model of Speed Sensor
and for each different software version for each model. These standard configuration
files define the settings from Appendix D that the application can control in a unit. A
short portion of a configuration file is shown below. Note that the file is organized in a
series of text blocks: three blocks in the example below.
editor. Stalker Radar provides a different file for each different model of Speed Sensor
and for each different software version for each model. These standard configuration
files define the settings from Appendix D that the application can control in a unit. A
short portion of a configuration file is shown below. Note that the file is organized in a
series of text blocks: three blocks in the example below.