HYDROCAL 1005 Manual for Installation and Operation
Page 106/111
7.2.3.1
Command Line Options for Windows Task Scheduler
HydroSoft comes with two new command line options for use in conjunction with the scheduled his-
tory data update.
Example:
<path>\Hydrosoft
-IdleClose 0:15:00 -Minimized
7.2.3.2
IdleClose
The
IdleClose
command line option can be given to let the application terminate after all history data
updates have be carried out. Following the command line option, a time span argument must be
supplied, that defines the idle close time. The syntax for the close time is [hh:[mm:]]ss.
When the HydroSoft scheduler scans the transformers for pending history data updates, it deter-
mines the shortest time span, when the next communication has to be started. If this time span is
greater than the idle close time, the application exits. When a daily update is configured a reason-
able default for the idle close time is 15 minutes. This would allow for repeated communication tries
(in case of failure), but exit, when the communication fails too often.
7.2.3.3
Minimized
The
Minimized
command line option can be given to let the application start minimized.
Remark: This option will also suppress the warning message, if the HydroSoft data directory is in use
by a manually started HydroSoft application. A Windows task scheduler started instance of Hydro-
Soft can immediately exit, if a manually started HydroSoft application is already running.
7.2.4
Internal Operation
This is a more detailed description of the internal operation of the scheduler (the terms in
italics
are
related to the data configured in the connection scheduler dialog).
The scheduler runs as a separate thread in the background of HydroSoft. Approximately every 15
seconds all transformers are checked if
scheduled data read-out
is active. Once a transformer is ac-
tive, a further check is made, whether the current time is greater than the
next connect at
time. This
way a list of pending connections is generated.
If the list of pending connections is non empty, it is processed step by step, i.e. the list is traversed
and all pending connection requests are executed before a new list is build.
For each transformer a try to update the data is done. On success the
connect fail count
is set to
zero and the
next connect at
time is updated (current time plus
connect interval
- optionally aligned
to the
connect time
).
In case of an error the
connect fail count
is incremented and the
next connect at
time is set based on
the current
connect fail count
. If the count is less than 3, a connection retry with 5 minutes delay is
set, for a count less than 5 the retry is scheduled in 10 minutes. If the count exceeds 5, the next retry
is scheduled to the current time plus the
connect interval
(- optionally aligned to the
connect time
, i.e.
the same time as if the connection had succeeded).
When the scheduler detects, that a time span of 3 times the
connect interval
has expired since the
last start of the application, the
connect fail count
is reset to 4. This will lead to a double communica-
tion try for a transformer with a bad status when the application has not been used for a longer time
period.
Because of the internal operation the following notes apply:
Changes applied through the connection scheduler dialog take some time until they are reflected
in the tree view.
Even if the read-out status of a transformer is bad, there will always be a try to update the data
with the configured
connect interval
.
A manual update of the history data does not update the
next connect at
time of the scheduler.
Even if an update occurs immediately before the
next connect at
time, the scheduled data read-
out will still be executed.
A log file 'Scheduler.log' is created in the root if the HydroSoft data directory. If a problem arises with
the scheduler a look into this file may help finding the cause. The log file entries are always written in
English.
