Now that we have finished
configuring our Tour, let's collect some data
by doing a Tour Run. This is the
Welcome Window in Manual Logger. If
I click on Manage Tour Runs, that will
take me to the window where I
can select the Tour for
which I want to collect some data. Here,
on the bottom pane, I can see
that several Tour Runs have already been performed.
This Tour was configured for Hourly Runs
or Hourly Collection of Data.
The last one was performed at 6:53.
By selecting the Tour
and clicking on New Tour Run, I can
select the next Collection
Time which, in this case, I am going to set
to 7:53.
I click OK, and I am immediately
taken to the
Data Entry Form. In here
there are a couple of different ways in which I can
enter data. I can enter data
using this center pane
and the Data Entry Form, or
I can also go to the Data Entry
Sheet that will allow me to enter data
for all of the tags at the same time.
There are several
items that are being
displayed in this Data Sheet.
I like the Data Entry Form, so I am going enter data
here, one tag at a time.
I am going to enter the value
of 45
for the first tag, and a comment saying
that this is my
first value. Now,
there a couple of things that we can observe
as a consequence of entering the value 45.
The first one is that
the next tag was checked
here as not being due now.
If you remember,
we had configured this tag for Data
Collection only when the first
tag, PIML-Float10, was
above 50. In this case,
because it's 45, we can see that
the next tag now is not due, and
if we navigate now by using the
Navigation Toolbar at the bottom of the Data
Entry Form, moving onto the next tag,
we will see here an X mark
showing that this tag is not
due for Data Collection. This is not going
to stop me from entering data
if I so desire.
I will go ahead and leave this tag empty
and move on to the next one.
For the value of this tag, I am going to enter two,
and I am going to move on to the next one.
Now I see the windows
that show me that a limit was
violated due to the limits that I
entered under the Data Validation Option
for this tag. In this case, I entered
a limit of LoLo, which was five, and
Low, which was ten. If I acknowledge
the Window, then I am
reminded that I need to call the control room
for this value because I have
exceeded the limit of five.
After I acknowledge the Window and the Message,
I am now prompted to enter a
comment which is required for this tag
when limits are violated.
So I am going to enter my
comment
and I can see here the Message
that the limits were violated.
I will now go to the next tag.
For this tag, I am going
to enter the value of 45
also. Move on to the next one.
And, if you remember, for Unit
#2, we had
configured a
Conditional Data Entry that the first
tag, PIML-Float10,
had to be greater than 90 before
we could enter data in Unit2.
As a consequence of that, and because we entered
45 for PIML-Float10,
now Unit #2
and its entire Group is showing there is
not due for data collection, and this is
a consequence of the
Conditional Data Entry Requirement which
we said. If we would have entered
90, or 95
rather, as a value for the first tag,
then Unit #2 and all of its tags
would have been available for data collection.
Now the fact that they are checked and that they
show that they are not due for data collection,
is not going to stop me from entering data
if I so desire. This is a
reminder that they -- data is
not required. So
I can now Save my data collection
and Exit.