No part of this technical manual may be reproduced, transmitted, transcribed, stored in a retrieval
system, or translated into any language or computer language, in any form or by any means, without
prior written permission of Mass Electronics Pty Ltd.
Trademark
The term ‘Innotech’ used in this manual is a trademark of Mass Electronics Pty Ltd trading as
Innotech Control Systems Australia.
'Microso', 'Windows' and 'Internet Explorer' are registered trademarks of Microso Corporation in
the United States and other countries.
Disclaimer
While great eorts have been made to assure the accuracy and clarity of this document, Mass
Electronics Pty Ltd assumes no liability resulting from any omissions in this document, or from
misuse of the information obtained herein. The information in this document has been carefully
checked and is believed to be entirely reliable with all of the necessary information included. Mass
Electronics Pty Ltd reserves the right to make changes to any products described herein to improve
reliability, function, or design, and reserves the right to revise this document and make changes
from time to time in content hereof with no obligation to notify any persons of revisions or changes.
Mass Electronics Pty Ltd does not assume any liability arising out of the application or any use of any
product or circuit described herein; neither does it convey licence under its patent rights or the rights
of others.
This document explains the procedure to implement trending within a Magellan project.
This guide should be used in conjunction with the ATOM Installation Instructions which is available on
the Innotech website.
Chronicle Implementation
The following document has been developed to assist in the configuration of Trending
implementation in Chronicle Manager/Server.
For Release Versions:
Chronicle v1.9 or later
Requirements:
• Appropriate Hardware (Innotech or 3rd party).
• Soware as shown in Table 1 below.
Supported Operating Systems
• Windows® Server 2008 R2 with Service Pack 1
• Windows 7 Professional (32-bit / 64-bit) with Service Pack 1
• Windows XP Professional 32-bit with Service Pack 3
Table 1: Software Table
LogoSowareDescription
c
Chronicle supports SQLServer Express 2008 R2 with a maximum of 4 GB of data (10GB with optional dongle).
iCommConnects the Hardware to the soware.
Chronicle Server
Chronicle Manager
SQL Server 2008 R2/ SQL
Server Express 2008 R2
SQL Server Database
Magellan / eServerEither of these are used to run the ATOM project.
Reads values from iComm and sends them to the SQL
Server.
This is used to program the Chronicle Server and also
contains a monitoring tool.
Handles SQL traic and stores the values from Chronicle
Server into the SQL Database. The SQL Server also allows
calculations and querying of the database.
This is the actual SQL Database. The SQL Server handles
all traic.
• The information on this page is relevant only if you are upgrading from iSEA v1.1 or earlier.
• iSEA v2.1 is installed during the installation of Chronicle Manager. Aer the installation has completed, the iSEA
Virtual Points window needs to be opened and the existing Virtual Points configuration saved by clicking OK.
Database Schema Upgrade
During installation you will be prompted to update the database schema (if a database exists).
Updating the schema could take some time (20 minutes or more) depending on the speed of your
computer, available RAM and the size of your database.
If you receive any error messages similar to the images shown below, you should restart the Chronicle
Server in the Windows Services screen. If your computer appears to not be responding, do not restart your computer. If you restart your computer, the upgrading process will need to start over.
Figure 1: Database Restore Errors
Aer the Schema upgrade, SQL Server may still be working in the background. In the Chronicle
Manager Communication Menu, select "Transfer from Chronicle Server". If the database upgrade
operation is still in progress, you will see the error on the right. Click OK and wait for the process to
complete. If the error does not show aer subsequent transfer attempts, the process is complete.
Figure 2: Communication Menu -
Figure 3: Server Busy Error
Transfer from Chronicle Server
It is considered good practice that post-installation all the site settings are checked.
Figure 4 below shows a pictorial representation of how Chronicle interacts with other Innotech
Soware. All soware and hardware communicates through iComm.
To ensure that Chronicle Trending Setup is completed correctly, follow the procedures in this
document.
1. Setup the Networks. Use the network design document so you know all I/O Server
connections, Devices and Addresses. (Ensure all hardware is powered and communicating
with iComm prior to proceeding)
2. Install the soware:
a. Chronicle Server (This installer will install iSEA and SQL Server if required)
b. Chronicle Manager
c. Magellan Builder/Bundle (Only Required for initial Setup, then remove the dongle)
d. Magellan Explorer or eServer (using the customer supplied dongle)
The Chronicle Server installation file contains all the soware for the installation of Chronicle Server and its
pre-requisites. The user must have Administrator rights to install the soware.
Aer Chronicle Server has been installed, you can check the Windows Services to see if the Chronicle
Server and SQL Server (SQLExpress) services are running. See Table 2 below for instructions on
viewing the services. You can also view if the services are running in iSEA's status window. Refer to
the iSEA Installation Instructions.
Table 2: Windows Services
Operating SystemProcedure
1. Right click "My Computer" in the start menu or the icon on the desktop.
Windows XP
2. Select Manage from the Context Menu.
3. Click the plus (+) to the le of Services and Applications in the le pane.
4. Click Services. The running services will appear in the right pane.
1. Right click "Computer" in the start menu or the icon on the desktop.
Windows 7
2. Select Manage from the Context Menu.
3. Click the arrow to the le of Services and Applications in the le pane.
4. Click Services. The running services will appear in the middle pane.
Open the iComm window to view the connections. Ensure all devices are ALIVE.
If the iComm window is minimised, double click the iComm icon (shown at right) in the system tray.
If the device is Dead, right click the device and select "Rebuild Information for selected devices". If aer rebuilding it
is still dead, check the connections and settings of the device to determine the problem.
c
The iComm window below, shows connections already setup and alive.
Figure 7: iComm Screen
Connections that are not required should be removed from iComm. Right click the connection and select "Remove
Connection" from the context menu to delete.
The Communications Settings sets the location of the computer running Chronicle Server. This can
be a remote computer on the LAN or the same computer running Chronicle Manager. Edit the Comms
Settings by selecting Comms Settings from the Communication menu within Chronicle Manager.
Figure 9: Communication Menu - Select "Comms Settings"
When you click on Comms Settings, the window in Figure 10 appears.
This field needs to be set to the computer
DNSname, or Static IP address that
Chronicle server is installed on.
If it is the local computer, then it will
be the computer name or IP of that
computer.
If Chronicle server is running on another
computer on the LAN, then type in the
name or IP of that computer.
Click here to test the connection. If you
see an error, check the server name
& authentication details are correct
and Chronicle server is running in the
services list of the relevant computer.
Upon a successful connection the Success dialogue is displayed, as shown in Figure 11.
Figure 11: Connection Test Success Window
If an error message is shown, ensure that the name of the Chronicle Server computer is correct and
use iSEA or the Windows Services screen to confirm that the service is running.
This option sets the location of the computer running SQL Server. This can be the local computer or a
remote computer on the LAN.
Select Change Chronicle Server Settings from the Communication menu to edit the SQL Server
settings.
Figure 13: Communication Menu - Select "Change Chronicle Server Settings"
Figure 14: Change Chronicle Server Settings Window
• SQL Server Location. This could be
on the same computer, or located
elsewhere on the LAN. (Ensure you
use DNSname, or IP Address)
• Database. This is always called
Greenstarlogging and cannot be
altered.
• SQLServer Security Settings. The
Greenstarlogging Database always
uses:
Username = Innotech
Password = 1nn0t3ch
(One, n, n Zero, t, three, c, h)
Click here to test the connection.
If you see an error, check that the
name and authentication details are
correct.
IM PO R TAN T
• Ensure that you have Administrator rights for your User logon account in Windows. Without administrator rights,
access to the required folders may be restricted.
• The SQL Database should never be renamed. Problems will occur if the database is renamed.
• The SQL Server Location address must also be used in the ATOM or Magellan trending project. For example, if the
DNS Name ATOM is used, then this must also be used in the database settings in the Magellan / ATOM project.
Click on the Test Connection Button in the Server Settings window. If the settings are correct you
should see the success popup as shown in Figure 15.
If the settings are not correct, the error popup appears as shown in Figure 16. Check all parameters in
the settings screens and retest the connection. If the database connection still fails, contact Innotech
for assistance (See the last page of this document for contact details).
Figure 15: Database Connection Success Window
Figure 16: Database Connection Failure Window
If you have selected SQL Express 10GB as the Database Server Type and have NOT plugged the USB
dongle into the PC you will see the following error message aer testing the connection as shown
below.
With the above steps completed, we can now begin to build the project.
1. Right click in the blank portion of the Server & Device window and select Create iComm
server. You can also select Create an iComm Server, from the Project menu item in Manager.
NOTE
Refer to the Chronicle Manager section to identify the individual Chronicle Manager windows .
Right Click a
blank area.
Le click
Create iComm
Server.
Figure 18: Click "Create iComm Server" in the context menu
The Server Address will be
the DNS name, or the Static IP
of the computer that iComm
is running on.
Make the Server Name
meaningful. This name
is used for reference and
cannot be blank. It is
recommended that the
default name 'Local Host' is
NOT used.
Figure 19: iComm Server Window
IM PO R TAN T
The Server Address must also be used in the ATOM or Magellan trending project. For example, if the DNS Name
ATOM is used, then this must also be used in the database settings in the Magellan / ATOM project.
2. Right click on the iComm Server and select Import Items from the menu.
Right click on the
iComm server
Le Click Import
Items
Figure 20: iComm Server Context Menu
3. In the Import Items window, Select Import items from network.
Figure 21: Import Items Window
Click Import items
from network.
During the Import process, all iComm connections will be added to the Item panel. This includes
Facility Manager, Simulators, BACnet and serial/USB. It is important to ensure that iComm only
contains any required connections. Any unused imported connections can be easily removed prior to
project transfer to Chronicle Server.
Note that you have the option of importing items from a file (Config), or from an existing iComm database.
4. Aer a successful import, a Tree view of your network will be displayed underneath your
iComm server. If you highlight a device, it will then list all available points to the right, ready
to filter and select for logging.
Figure 23: Chronicle Manager Window with Points
Once the Import process has completed, the Chronicle Manager window updates with the imported
devices and points.
Trending and Reporting Panels
• Trending points are used in the Magellan Trend Frames and purge over time.
• Reporting points are used in the ATOM project. These points are also purged, however you can
determine if there is suicient space available to ensure there is no loss of data.
You have the ability to use the filters to locate or isolate any points in the list. This can speed up the
selection process and help ensure you select all the required points.
Data storage works on a “first in, first out” scenario, and once the designated space is used, the
oldest data will be replaced with the newest to give a “sliding window” eect.
Select the Trending Points Tab, select and drag the points to the Trending pane. Typically, these are
items such as temperatures, volts, current. This is non-critical information used in the Trend Frame
in Magellan (No longer using the Access Database in iComm). Note that the Trending points also have
various properties that can be edited.
Take into account when setting up your Point logs, that rate and tolerance are factors which may save
database usage over time; for example: Digital points may be set using a Tolerance instead of a Rate.
This will only log when the point changes state which may be far less frequent than any rate set, it will
also be more accurate.
Figure 24: Trend Point Context Menu
In the Trending and Reporting Window, select one
or more Trend Points. Right Click a selected Trend
Point and select Edit from the context menu.
Figure 25: Edit Trend Point Window
IM PO R TAN T
Hours Run Meters: Please note, an Hours Run point that is designed using an ON/OFF scenario (e.g. a wall mounted
push button), requires special consideration when added as a Reporting Point. These types of meters must use
a tolerance of 0.5 which will log values outside this tolerance upon activation (values returned from the point
generally read 1 - ON or a 0 – OFF).
The tolerance field is ignored when set to zero (default setting), in this case the Reporting Point will be logged at the
interval specified in the Rate field, regardless of if it has changed in value or not. Trending Points will continue to
use tolerance as per before, that is, they will not log if they haven’t changed by a value greater than the tolerance.
Aer successfully transferring the project to Chronicle Server, you have the option to monitor the
project using Chronicle Manager’s Monitor Mode function.
Monitor mode allows you to monitor live data values of the points added to the Trending or Reporting
tabs. This is a useful commissioning tool to ensure that data values are correct and reading from
iComm.
Figure 26: Go to Monitor Button
Aer clicking the Go to Monitor button, it will change to Go to Config as shown below in Figure 27.
Figure 27: Chronicle Manager Window
While in Monitor mode, no project modifications are possible, you must “Go to Config” before you can make further
alterations. When monitoring in either Tab, you will notice the Orange Circle on the Tab and orange headings to
indicate you are in Monitor mode.
To utilise the SQL database trending points in Magellan, a few items require setting. Once the points
have been added to the Trending Tab in Chronicle Manager and transferred to Chronicle Server, we
need to advise Magellan to use the SQL database points.
1. Once the Magellan project is open in Magellan Builder, the database settings need to be
configured as shown in Figure 28.
Figure 28: SQL Connection Settings
IM PO R TAN T
The Database server settings must match in Magellan and Chronicle. The DNS name or IP address must be
identical, mixing DNS and IP address will cause project issues.
2. In Magellan Point manager, double click on the iComm Server connection and enter the
Host Computer Name.
IM PO R TAN T
The Host Computer name will be the same as the Server Address name in Chronicle. The DNS name or IP address
must be identical, mixing DNS and IP address will cause project issues.
Double Click the iComm Server Connection to
show the Properties Window
Figure 29: IO Server Properties Window
Figure 30: iComm Server Properties Window in Chronicle Manager
In Magellan Frame manager, open the Trend Frame. Select the Trend Object and open the properties
dialogue.
Figure 31: Example Trend Object Properties - Magellan
In the properties window, make sure that the “Load data from SQL” radio button is checked. This
loads the point log data from the SQL database via Chronicle Server.
Click OK to save the changes.
All "actual points" must also be added in the Trend Items tab.
Chronicle Manager provides the ability to print a report for the Reporting and Trending points. From
the File menu, select Print. If a points filter is used, only the filtered points will be printed.
Figure 32: File Menu
In the print report window shown below, select the Print all Trending or Print all Reporting radio
button. Click the Print Preview button to view the report or click Print to print the report to your
selected printer. Figure 34 shows a sample report print preview.
Several advanced settings are available in Chronicle. In the Communication Menu, select Change
Chronicle Server Settings. In the Server Settings window (Figure 36), select the Advanced tab.
Figure 35: Communication Menu
The Advanced tab in Figure 36 presents you with 3 dierent configurable options. Locking the
Chronicle Server with a password, adjusting the amount of the allotted Database size to either
Reporting or Trending and setting up the automatic backup time and location for the SQL Database.
Figure 36: Change Chronicle Server Settings Window
Click Modify Password in the Advanced tab to edit the password.
First time users will be able to enter a new password straight away. A “greyed out” old password also
indicates that there is currently no password set.
Set a password and then add it to a Master file for safe record keeping. Once the password is set,
it will need to be re-entered each time you wish to make ANY changes to the Chronicle Server
configuration.
Click Modify Password to open
the Modify Password window.
Figure 37: Modify Server Password Window
IM PO R TAN T
It is imperative that you DO NOT lose this Chronicle Server password.
If you lose your password, you will need to contact Innotech in order to unlock the server.
Modifying the Database Reporting/Trending space allocation
Click Edit in the Usage section of the Server settings Advanced tab to edit the Server Database usage.
You may adjust the amount of storage dedicated to Trending and Reporting. (Reporting is the
Priority) Adjust as required and press OK to save the settings. Keep in mind that Trend data should
only really be kept for as long as a Service contractor/Building Manager may need to view any historic
data to perform any troubleshooting.
Trend Data then works on a “first in, first out” scenario, and once the designated space for Trending
is used, the oldest data will be replaced with the newest to give a “sliding window” eect. With clever
management, this will reserve the majority of the database for Reporting which will then allow the
maximum amount of Historic Data to be saved.
Click Edit to open the
Chronicle Server Database
Usage Window.
Storage Remaining based
on the settings below.
Modify the details as required.
Figure 38: Chronicle Server Database Usage Window
The amount of storage allocated to logged data is limited to 4gb if you do not use a Chronicle dongle. The allocated
storage increases to 10GB if a Chronicle dongle is used. The 10GB option is limited to a maximum allocation of 4GB
for reporting. If the database is downgraded, Chronicle will retain Reporting point data up to a maximum of 3.96GB.
IM PO R TAN T
When allocating the database usage, you should note that large Trending allocations will drastically reduce the
performance of applications which use the database (Trends, ATOM etc). In most cases, 90 days (3 months) Trending
allocation should be adequate without degrading performance.
Click Edit in the Backup section of the Server settings Advanced tab to edit the Database Backup
Schedule.
As the options show, you are able to set the interval, the date of next backup, the time of backup (in
24 hour time) and also the backup location.
Once you are happy with all backup settings, click “backup now” and make sure that the database is
saved without error.
To avoid data loss, ensure that a copy of the backup is copied to another computer at regular
intervals, as only the latest backup will be retained by Chronicle Server..
Click Edit to open the Edit
Database Backup Schedule
window.
Figure 39: Database Backup Schedule Window
The backup location can only be a local drive. For example, on any Hard drive on the local computer or an External
USB Plugged directly into the computer. This location CANNOT be a network drive.
IM PO R TAN T
To avoid backup restoration problems, DO NOT rename the backup files located in the Backup Location. If
necessary, copy the backup files to another location before renaming.
During installation you will be prompted to update the database schema (if a database exists).
Updating the schema could take some time (20 minutes or more) depending on the speed of your
computer, available RAM and the size of your database.
If your computer appears to not be responding, do not restart your computer. If you restart your
computer, the upgrading process will need to start over.
Aer the Schema upgrade, SQL Server may still be working in the background. In the Chronicle
Manager Communication Menu, select "Transfer from Chronicle Server". If the database upgrade
operation is still in progress, you will see the error on the right. Click OK and wait for the process to
complete. If the error does not show aer subsequent transfer attempts, the process is complete.
iSEA v2.1 is installed during the installation of Chronicle Manager. Aer the installation has completed, the iSEA
Virtual Points window needs to be opened and the existing Virtual Points configuration saved by clicking OK.
Figure 43: iSEA Virtual Points Window
It is considered good practice that post-installation all the site settings are checked.
Innotech provides technical information on the Web to assist you with using its products.
At www.innotech.com.au, you can find technical manuals, user instructions, and data sheets for all
our products.
For direct product support or product information, contact your local distributor, or an Innotech
representative.
You can contact us via email, fax, or postal mail:
Website: www.innotech.com.au
Email: sales@innotech.com.au
Fax: +61 7 3421 9101
Mail: Innotech Control Systems