There are two installation
kits for manual logger.
One for PCs and one for mobile
devices. What this video covers is the
PI manual logger installation kit for
PCs. As with all software
the manual should be consulted
to make sure that pre-requisites, install steps and
post install steps are understood clearly.
Two of the pre-requisites for
PI manual logger are first
installation of the OSI pre-requisites
kit and also the presence of SQL
server. Most versions of SQL server are
supported, including SQL server express and that's what I'll be using
here today. Also SQL server
does not have to reside on the same machine as manual
logger, but in this case I'll do that to show a simple case.
There are actually two install
paths for manual logger. One is installing
logger to get the database which
resides in SQL server setup. The
second case is just install manual logger on any
PC that will be used for the manual logger data
entry. We are really showing both of these cases here today.
Also if you are planning
to use PI ML web
services. What PI ML web services does is it enables
mobile devices to communicate wirelessly back to manual
logger. If that's the case, then ISS must already be
properly installed and running on this computer.
With SQL server
that has been previously installed, it's important to note that
the user that you are running the
installation under should have the rights to create
databases in SQL server. Also SQL server
should have windows authentication
turned on. The installation
kit that I'll be using is PI manual logger 2012.
Here are the components that will be installed.
It is verified that my pre-requisites
are available.
Here are some notes that include instructions if you are
upgrading manual logger, also if you are planning to
use PI ML web services.
The path for PI ML windows is the
manual logger installation path. This normally
would go under the PI PC folder. If you already
have a PI installation on this box, then this is already defaulted for me.
Here is my install feature selection
list. First, database
file. If I'm going
to be using SQL server on this
box, I want this enabled.
Next, plant application. Again this is actually
putting the manual logger application on this box.
So if this is going to be station then operator.. or
[inaudible] I want to include
this auto sync utility.
This is noted here, it let's me automatically
sync the data between a [inaudible] device and host server.
So again, if I'm using this as a work station to have
someone enter manual logger data, I probably want
auto sync. Windows
services -- as is noted here, this is a
Windows service that runs in the background
and it enables the PI ML database to stay in sync with
PI. It also allows caching and sending out
future data. Also as is
noted here, this only needs to be installed in one place.
Presumably where the SQL server database resides.
Finally, there is the
web services. This is what was mentioned earlier, this
allows wireless data to transfer to and fro PI
ML mobile devices.
I'm going to select all the options for now.
Since I have the web services option
selected, I'll have to choose my IIS website.
I'll choose the default
website.
After this, the
install of manual logger proceeds.
Here is an additional note to
please refer to the post installation procedures in the guide.
Now the installation
is complete.
Now for my post install
steps. The first thing I must do is
attach the manual logger database to SQL
Server.
For this, I'm going to go into the directory where manual
logger was installed and find the different SQL server
version templates.
Then I'm going to my PI PC
directory.
Then into PI
ML Windows.
If I look
there is a folder here entitled
data.
And then I see PI
ML Windows, MDF Files. There are my
database files for different versions of
SQL server. I'm using 2008. So what I want to do
first is copy these to a secure
location.
I'm going to create a new
folder for this.
I'll paste these into
this folder and also I'm going to change
the properties so that they are no longer read only.
The templates come shipped as read only.
OK, now I'm ready to go into SQL
server and attach these to a SQL server.
So I'll use SQL server management
studio for this.
I'll login using my
Windows user.
Now I need to do an attach.
I go and browse
to the location that I just added the files
too.
And I'll choose my
SQL server specific manual logger database.
Here I will say OK
and I'll notice there is a new database listed
called PI ML Windows.
This is all I need to do in SQL
server. My next step
is simply to get into manual logger and test that
I've successfully created the database, attached
to it, and I'm able to login.
So I'm going to my PI system
menu, going into the manual
logger group and open manual logger. I can also go to
configuration tools and test as well. These are the
tools that I would use if I needed to change databases
at some point.
It is attached to the SQL server and
now I need to login. By default manual logger
ships with one user, PI ML,
with the password of PI ML.
So I say OK, manual logger is initiated.
This shows me that I have a
successful installation. And as I see on the status bar across
the bottom, my SQL Express instance is
being used by PI ML Windows. This also shows me the
PI server that I've defaulted into which is my default PI
server. From here I can go on and
start to create tours or collect
data. A second check that I
might do is see if my PI ML Windows service is
actually installed. So I can look at the
services control
panel.
And I'll scroll down to
PI ML Windows.
And I'll see that he
in fact is here and started.
Again, this is the service that provides future
and cached data as well as syncing
to PI. Finally
as I mentioned earlier, one of the other tests that
I could've done was bring up the configuration tool. So
again I'll go into the PI manual logger group just to show this.
In configuration tools,
here I see my database. I can sub the connection,
sync data and also see my services.
If I setup
the connection, I see that it
default in what I've already used and I can do a test here.
This shows me I successfully connected to my PI ML
database in my local SQL server which is SQL Express.
And with that we've shown that we have a successful PI ML
2012
installation.