81
For example, a one-hour session will result in a one-hour raw
data file.
NOTE: Data recording can also take place out of any sessions
through the Web Server’s Data Recording function.
In each session batch, sessions can be created either
automatically (in this case they are all of the same duration),
or created individually through a manual procedure.
The two methods can be combined. For example, sessions
can first be created automatically and then adjusted
manually and individually, if necessary. The following
parameters can be edited for each session individually:
session start and end times, recording interval and data
recording control. No session overlapping is allowed. Doing so
would result in an error message.
Sleep mode: The receiver can be configured to be powered
down automatically at the end of each session, provided
these sessions are part of Session Batch #1 and there is
enough idle time between an ending session and the next
one. The receiver will wake up automatically just before the
next session (from session batch #1) is due to start.
Two additional options exist that may affect the way the
programmed sessions are executed:
• Reference Day (1-366): This is the day when the execution
of the programmed sessions should start. This option
should be used when you want the receiver to start
executing sessions only several days after having
configured the receiver.
The principle is the following: If the current day is prior to
the Reference Day, the receiver will wait until that day
before starting running the sessions. If it is after, the
Session A
Session Batch #1
Session B Session C
Raw data files (G-files) covering one hour each
Session D
8:00 9:00 10:00 11:00 12:00
Raw data files (G-files) covering one hour each
Session A
Session Batch #2
Session B Session C Session D
8:00 9:00 10:00 11:00 12:00
To Next Page
Loading...
