Thermoguard System Manual System Manual-en.pdf · Thermoguard System Manual * September 22, 2017 Page 5 of 92 Security Notes on installing the Temperature Sensors Changes to the electric

Thermoguard

System Manual

Version 2.94

Thermoguard System Manual * February 3, 2018 Page 2 of 94

Contents Page

- Copyright ............................................................................................................ 4 - Security Notes on installing the Temperature Sensors .................................. 5 - WEEE and RoHS Information ............................................................................ 6 - References to further supporting documentation ........................................... 7

Part 1: Introduction

- Overview: Steps to perform .............................................................................. 8 - ! Data Backup ! ................................................................................................... 8 - Functional Principle ........................................................................................... 9 - Operational and Cost Benefits ........................................................................ 10

Part 2: Installing and Running the Software

- Installation Requirements ............................................................................... 12 - Installation of the Thermoguard Windows Software ..................................... 14 - Update Installation ........................................................................................... 17 - Uninstalling Thermoguard .............................................................................. 18 - Starting and Stopping Thermoguard .............................................................. 19 - Licensing Thermoguard .................................................................................. 21 - Configuring the Software ................................................................................ 22 - Running the Software ...................................................................................... 39 - Thermoguard as a Service .............................................................................. 41

Part 3: Installing the Hardware

- Sensorcontroller Model Overview ................................................................... 45 - Sensorcontroller Connections: Network and Power .................................... 48 - Sensorcontroller Connections: Sensors ....................................................... 49 - Sensor Model Overview .................................................................................... 51 - Connecting the Indoor and Cold Storage Sensor .......................................... 53 - Assigning IP Addresses to Sensorcontrollers .............................................. 54 - Assigning the IP Address using the "Assign IP Address" Function ............ 55 - Assigning the IP Address using the ARP Command ..................................... 56 - Changing the IP Address of SCn/AC2 using a Browser ............................... 57 - Configuring AC2nP .......................................................................................... 59 - Installing the Temperature Sensors ................................................................ 63 - Mounting Cases ............................................................................................... 66


Part 4: Advanced Information

- Alarm Options .................................................................................................. 67 - Alarm On Fail .................................................................................................... 71 - Forwarding E-Mail as SMS to Cell Phones .................................................... 74 - Supporting "Passport Images" for each Sensor ........................................... 77 - Simulation Mode .............................................................................................. 78 - The Source "Text file" ....................................................................................... 80 - Tips and Tricks ................................................................................................. 81 - The Sensor Port Switch Function ................................................................... 82 - Export and Import of sensors as *.scxtpl ...................................................... 85 - The Sensor List Search Function ................................................................... 86

Part 5: Appendices

- The TG Decrypt Utility ..................................................................................... 87 - Ports used / Firewall ........................................................................................ 88 - Data Format of the TGuard.scx File ................................................................ 89 - Files installed by Setup ................................................................................... 91 - Information on GMP, cGMP, CFR 21 Part 11, FDA ........................................ 93


Copyright © Thermoguard 2001 - 2018 All rights reserved. Trademarks "Thermoguard" is a registered and protected trademark in Switzerland. Naming the trademarks of other providers only serves describing their products, which can be used in combination with Thermoguard products. Trademark IDs of other providers have only been omitted for better legibility; this does not mean these trademarks or names can be used freely and without permission. Deployment Thermoguard products are expressly not meant, nor verified, for use in medicine, aerospace and any other indus-tries where human life depends directly on the deployment of our products. Deploying our products in the above industries is expressly contrary to the intention of Thermoguard, and completely at the user's risk. Disclaimer of Liability Thermoguard expressly disclaims all liability for any damage that may arise from faulty functions, including soft-ware alarm failure. This also applies to damage arising from profit loss, lost or damaged data or any other com-mercial or business loss. The software and all its documents have been designed and developed to the best of our knowledge and belief. Thermoguard does not guarantee, however, that this software is suitable for all functions of use under any condi-tions or that it will work trouble-free. The user is obligated to validate the software and its functions in their envi-ronment when using them, specifically within a legal environment. Thermoguard will, however, try to correct any recognized errors, and continue customizing the software.


Security Notes on installing the Temperature Sensors Changes to the electric installation of your devices are not required for the use of Thermo-guard. You should still take security measures when working with electricity. Unplug the de-vices from the socket prior to carrying out your work!

Never open or damage the Thermoguard sensorcontroller's power supply or any of the switches of your freezers. Working with open electrified wires may cause severe or fatal dam-age. Leave all work to be done with electricity wires or open cables to your expert electrician.

Please make sure that while installing the temperature or humidity sensors you do not damage any electrical wires.

Also, do not damage the wires for the cooling agent or for the freezing sensor in device interiors!

Thermoguard disclaims any liability for damage done to humans or institutions due to improper installation!


WEEE and RoHS Information According to the "Waste Electrical and Electronic Equipment" Direc-tive 2002/96/EG of the European Community electronic products will be labeled with the mark of the crossed out trashcan. After their end of working life, these product should not be disposed with other household or commercial wastes. This Directive is more commonly known under the English abbreviation WEEE: "Waste Electrical and Electronic Equipment".

WEEE-Reg.-Nr. DE 68960573 This directive was converted into individual national law. For return and disposal of commercial waste special legal regulations apply. In Germany registration at "Stiftung EAR" documents the fulfillment of this regulations. Thermoguard Germany is registered under number WEEE-Reg.-Nr. DE 68960573. In Switzerland the "Verordnung über die Entsorgung elektronischer Geräte (VREG)" is a com-parable directive.

Thermoguard products are sold solely to industrial or commercial consumers. Manufacturer and customer may be state by contract which site must take care of the legal requirements. According to Thermoguard's Conditions of Business the industrial or commercial consumer bears this responsibility.

Further on all Thermoguard products are compliant to directive 2002/95/EG, the Restriction of Certain Hazardous Substance in Electrical and Electronic Equipment (RoHS). From July 1st, 2006, only products without exceeding a certain level of Lead, Mercury, Cadmium and some other compounds may be sold. In Switzerland the Chemikalien-Risikoreduktions-Verordnung is a comparable directive. You may download our RoHS-Declaration from our homepage: http://www.thermoguard.com/download/RoHS-001.pdf.

http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2003:037:0024:0038:EN:PDF

http://www.stiftung-ear.de/

http://www.admin.ch/ch/d/sr/c814_620.html

http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2003:037:0019:0023:EN:PDF

http://www.admin.ch/ch/d/sr/c814_81.html

http://www.thermoguard.com/download/RoHS-001.pdf


References to further supporting documentation The following documents are no longer part of this System Manual, but located in the root directory of your Thermoguard Installation CD:

TG Quickstart-en.pdf Quickstart checklist

TG Silent Installation-en.pdf Notes on automatic ("silent") installation

TG CIM-de.pdf (available in German only) Interface "Custom Integration Module"

TG GSM Modem-en.pdf Operation with optional GSM Modem

TG Relay Interface-en.pdf Operation with optional Relay Interface

TG Alarm Relay Channel-en.pdf Documentation of the Alarm Relay Channel feature

The two latter files are copied to subdirectory \doc of the installation target path; by default this

is %ProgramFiles[(x86)]%\Thermoguard\doc.

The separate manual for Thermoguard Report/Thermoguard Live! TG Report-en.pdf is copied

by default to %ProgramFiles[(x86)]%\Thermoguard\TGReport\doc

and can be accessed via the start menu:

Numerous other documents as well as additional software are located on the CD in the subfolders \Documents-001 and \Weitere Software

Thermoguard Report is a standalone program for displaying data recorder by the Thermoguard main program and comes withi its own manual:


Part 1: Introduction

Overview: Steps to perform The following steps need to be performed to install the Thermoguard system

Install the Thermoguard software on a computer

Configure the software for the sensorcontrollers

Configure the software for the desired alarm modes

Configure the sensorcontrollers: specifying the IP numbers

Integrate and connect the sensorcontrollers and temperature sensors on-site GMP compliant installation and operation usually require the following additional measures:

Installation Qualification, IQ

Install Alarm Action Sheet for measures carried out on alarm at device on-site or keep ready in device folder

Create and enact SOP

Name and train person who is responsible for the devices

Perform recordings on alarm and other events

Perform regular function checks (Operational and Performance Qualification, OQ and PQ)

Templates for SOP, including calibration SOP for temperature sensors, SOP for Installation Qualification (IQ), and an Alarm Action Sheet are available on the CD in both English and German. After System has gone live:

! Data Backup ! As for all areas of IT the "first law" applies to a Thermoguard-Installation as well:

Backup all user data on a regular basis. This applies to ... 1) ... configuration files TGuard.ini, TGuard.scx and (if applicable) *.scxtpl

2) ... Log files *.log

3) ... Sensor data files *.tg

Please keep in mind: A Backup is sensible only if the success of the associated data Restore is checked periodically!


Functional Principle Genuine online temperature and humidity monitoring using sensorcontrollers on the computer network, direct e-mail and cell phone SMS alarm messages - that's Thermoguard! The Thermoguard system consists of smart network thermometers, and network humidity sen-sors called "sensorcontrollers" with connected temperature and humidity sensors as well as a central monitoring software running on a computer. Thermoguard monitors on-site tempera-tures using the sensorcontrollers and their temperature and humidity sensors regardless of other installations. Thermoguard uses an existing computer network and a central and protected computer that runs the Thermoguard software which polls the on-site sensorcontrollers at configurable inter-vals. The polled values can be saved continually in serial data files. Falling below or exceeding default limits and alarm conditions will trigger the alarm. On-site electricity blackout as well as mechanic or electric failure of a temperature sensor or sensor-controller can also trigger the alarm. Alarm can be forwarded in audio form, visually or via e-mail. Alarm can additionally be sent as an SMS message to cell phones. Using back-end programs and switches allow triggering other processes. Thermoguard not only monitors temperature and humidity but - via its AC2nP range of Sensor-controllers - supports any analog sensor providing a 0..10V or 4...20mA output signal. For example, barometric pressure, gas pressure, room light etc. can be controlled.


Operational and Cost Benefits Due to the functional principle, Thermoguard provides multiple advantages on installation and when running. Low installation costs

No new cables need be laid for Thermoguard for all new measuring units in the building. In-stead, Thermoguard uses the existing computer network. Other systems, e.g. building mo-nitoring systems, require their own bus system such as House Bus, I2S or RS-485, for which separate, new cables must be laid. These additional installation costs are eliminated for Thermoguard.

Alarm without delay in the event of damage

Thermoguard directly sounds the alarm. Unlike other systems, e.g. traditional data loggers with measured value caches, the responsible persons are sent audio, e-mail or alarm SMS without any further delay. With local minimum/maximum thermometers or saving data log-gers, this information is sent only after the responsible person has made a check. The in-formation delay about a limit violation or crucial state can be as much as a month with clas-sical data loggers. Thermoguard, unlike other systems, alarms even when electricity fails or when there is on-site mechanical or electric damage. The central computer detects the sensor failure, and triggers the appropriate alarm. Comment: It is for this reason that, for instance, the Food and Drug Administration (FDA) in the U.S. requires at least daily manual on-site checks and recordings carried out by the responsible employee for stability studies of pharmaceutics in addition to data loggers with measuring caches and retrospective analysis (Source: Information by Dr. Weyers of Confarma AG, President of the Gesellschaft der schweizerischen Dienstleistungslaboratorien GSDL [Association of Swiss Private Laboratories], May 2003).

User independent operation

A central computer performs the recurring task of regular queries and comparison to the limits. Unlike local thermometers or data loggers, no monitoring user is required to leverage the system. Human errors such as gaps in recordings, particularly over a string of holidays such as Christmas, or no available delegates during absence due to vacation or sickness, irregulari-ties due to lack of discipline among employees or missing measures despite obvious devia-tions from the target values will not occur on principle.


Self-financing operation

Data loggers need to be monitored and read by qualified personnel on a regular basis. In addition, data loggers require fresh special batteries at regular intervals to ensure secure operation. Thermoguard sensorcontrollers require no batteries; they work without any addi-tional follow-up costs for material or human resources.

Overview: Thermoguard's main assets

Automatic, continuous and centralized monitoring with no dependency on humans

Supported temperature range -200 .. +650 °C

Alarm is signaled directly "online" and not if it's already too late

Simple and flexible installation within the standard computer network ("Ethernet") - no

special cabling needed

No need to change any leaking or empty batteries, unlike data loggers

Alarms are signaled acoustically, via e-mail or via SMS using cell phones

"Multilevel" alarm per sensor configurable. For example if the first limit has been violated,

an e-mail alarm is triggered, if the second limit has been exceeded, an additional

acoustic alarm will be fired.

Optionally SMS dispatch directly throug a GSM Modem

Triggering external alarm devices via optional relay interface

An alarm is signaled in case of an electrical or mechanical sensor failure

Compliant with GMP; with sample SOPs and xQ qualifications

Software, Sensorcontroller and sensors "Made in Germany"

Sensors use proven PT100 four-wire technology; up to 100m connection cable

Thermoguard Report included: a free reporting tool for graphical data views

Thermoguard main program and Thermoguard Report bilingual (German/English)

Flexible expandability: Just add new sensorcontrollers to the network

Simple licensing policy: No further software license fees if "professional" license is pur-

chased once


Part 2: Installing and Running the Software

Installation Requirements To ensure permanent and secure operation of Thermoguard, the following requirements are recommended or must be met: Operational computer network

An operational computer network with TCP/IP protocol is required. The sensorcontrollers require regular IP addresses. The network load that is generated is minimal and limited to transferring a few bytes per poll interval and sensorcontroller. Thus unrestricted use of the Thermoguard system in older 10 MBit networks or via the Internet is possible.

Hardware requirements

The Thermoguard program does not include any particular requirements for the PC hard-ware. Any PC that fits the selected operating system can be used. A network card sup-ported by the operating system is required. Sound cards and active loudspeakers are recommended. The processor load caused by Thermoguard is minimal; there are no special memory re-quirements. Thermoguard uses about 18 MB memory when running.

Supported operating systems

Thermoguard supports the following operating systems:

- Microsoft® Windows XP™ 1), includes Windows XP Embedded

- Microsoft® Vista™, Windows 7 1)

- Microsoft® Server 2003 1)

- Microsoft® Server 2008 1)

1) Please note that the 64 bit versions of these operating systems had not specifically tested with Thermoguard. However, at the time being no incompatibilities are known regarding 64 bit versions.

Network rights Installation and uninstall require local administrator privileges.

The Thermoguard main program TGuard.exe can be run without administrator privileges.

To install Thermoguard as a service and to control this service (start, stop) administrative rights are required. This it is recommended to set up an exclusive domain account (e.g. "Operator-Thermoguard") for the service. This account requires complete read and write permissions for the Thermoguard program and data directories (data and log files).


Firewall

An exception must be defined for the Thermoguard program (TGuard.exe) with the Win-

dows XP SP2 or later. See Ports used / Firewall for details.

File storage, access protection, and data backup The Thermoguard data and log files can be stored locally or on any network drive. Access protection, routine data backup, and uninterruptible power supply for your computer are ex-pressly recommended.

Archiving and Signature according to cGMP In an environment with cGMP requirements compliant with the American Federal law CFR 21 Part 11, additional software such as Agilent Cerity ECM (Enterprise Content Mana-

ger) or Nugenesis SDMS (Scientific Data Management System) provide a network-wide op-

tion for archiving and digitally signing data and log files.


Installation of the Thermoguard Windows Software Installing the Thermoguard software requires local administrator privileges.

The setup program TGuard_294.exe is located in the CD's root directory.

You can execute the file directly with a double-click. Alternatively you can use the corresponding link in the CD's Splash Screen. The Splash Screen pops up automatically after

inserting the CD (with active Windows autostart, if not, execute TgStart.exe):

Initially a dialog appears that lets you select the desired setup language.:

The selected language determines if english documentation *-en.pdf or German *-de.pdf will be installed. The language will also be used for the language of all dialog windows of a possible later uninstall of the software.


After confirming the license terms and selecting the destination location folder you can pick the desired components:

If you want to perform an installation for the Thermoguard-Server standard selection (all components checked) should be kept. In case you want to install just Thermoguard Report on a workstation, only check the last component listed.

Notes on an automatic silent installation are provided in the TG Silent Setup-en.pdf file

(in the root directory of the CD or via the Splash Screen's menu entry Notes on silent Instal-lation). After passing the dialogs for changing the default name of the start menu folder, "Additional Tasks" (Creation of desktop icons and firewall rule, if Main program selected) the installation can be started by clicking on the "Install" button in the final "Ready to Install" dialog.

After the software has been installed setup shows the program's version history. It documents all changes for the Thermoguard main program as well as for Thermo-guard Report since their very first versions. The associa-

ted file TG Version History.pdf is located in the

root directory of your Thermoguard-CD as well.


(here on Windows XP)

The data directories are created independently of the destination folder in %ALLUSERSPROFILE%\Thermoguard Data

and

%ALLUSERSPROFILE%\TGReport Data respectively.

%ALLUSERSPROFILE% is an environment variable poin-

ting by default to: On Windows XP/Server 2003: C:\Documents and Settings\All Users

On Windows Vista/Server 2008: C:\ProgramData

(here on Windows XP)

When initially launching the Thermoguard main program

the \log and \tg subdirectories will be created.

By default, the *.log files are saved in \log, and the

*.tg sensor data files are saved in \tg. These local directories can also be modified later via configuration; e.g. to a protected network data server. Note: Since Setup is not yet aware of these two directories during installation, these directories and the data files they contain will not be deleted when uninstalling the software.


Update Installation An update installation requires local administrator privileges. Thermoguard Setup supports automatic updates of existing installations in the same target di-rectory. This makes it unnecessary to uninstall an existing version prior to install the update.

Nor is a special backup of configuration files or of the \log and \tg data directories required.

On updating setup requires a confirmation "Do you want to keep your configuration files ..." for

the detected files in directory %ALLUSERSPRO-

FILE%\ Thermoguard Data.

Usually you want to keep your previous configu-ration so be sure to click on Yes here!

If the service did run before setup has been launched, it will be stopped and restarted at the end of the installation process. This message confirms the successful restart.

Setup will create a backup directory in which the configuration files are saved each time it is exe-cuting an update. That directory will have the current date/time stamp, so it will not be over-written by other update processes.


Uninstalling Thermoguard Uninstalling the Thermoguard software requires local administrator privileges.

Two options for executing uninstall are available:

Via the corresponding menu entry in the start menu

or:

via Windows Control Panel

As with an update installation access to open Thermoguard files must be released so that they can be deleted by setup If an existing file lock is detected a warning dialog appears listing the files involved. If the Thermoguard service should be installed and/or be running it will be stopped automa-tically and be removed. After uninstall, the following message appears: Thermoguard was successfully removed from your computer. As with update installation, the three configuration files were copied to a

backup directory named \CfgBak*....The %ProgramData%\Thermoguard Data and

%ProgramData%\TGReport Data subdirectories are not deleted on uninstall.

Therefore: If you really want to remove the installation completely from your computer, please 1) backup both of the subdirectories including all subfolders and 2) delete them manually


Starting and Stopping Thermoguard Start

Depending on the options selected in Setup, the main Thermoguard program can be launched using one of the following methods:

Via the desktop icon

Via the "Thermoguard" start menu entry

Or directly by running TGuard.exe.

Note: There are no command line parameters for TGuard.exe.

The program's two windows, the monitor and the configuration window ("Thermoguard Mo-nitor" and "Thermoguard Configuration") appear at initial startup. Closing these windows will not end the running program!

The size of the configuration and monitor window can be modified at any level through dragging with the mouse!

The respective status, "visible or not", of all windows as well as window sizes and positions are saved when ending the program, and restored at re-starting it.

The "Open configuration/Close Configuration" and "Show/Hide Monitor" buttons enable opening or closing ei-ther window.

If the program is already running the left-hand message pops up when trying to start the program a second time. If you want to establish different instances each of it using its own Ther-moguard main program with different polling intervals, you must install them on separate PC systems. Unless you alternatively use virtual machines with appropriate software as VMware® or Microsoft® Virtual PC/Server on the same host system.


The "Program language" selection field of the configura-tion window allows you to set the desired language. The program's supported languages are English and Ger-man. The program must be restarted after you select the required language.

Termination The running program is displayed via the Thermoguard icon in the operating system's status line ("Taskbar"). Right-click the icon to display the context menu that, among others, includes entries for opening/closing the main windows and for ending the program:

Note: As described above, the program saves the last window position. When closing the configuration or monitor window during a program run and closing the program completely, these windows will not be displayed when restarting the Thermoguard program. The menu described above lets you reopen the windows (Open configu-ration or Show monitor).

If Thermoguard runs as a service the service will not be stopped when the

"interactive instance" is terminated. In this case an appropriate note is shown in the

context menu and the configuration dialog (as shown above).

When shutting down Thermoguard the confirmation dialog shown left-hand shows up. You can switch off this dialog under "Thermoguard Con-figuration" => "Miscellaneous":


Licensing Thermoguard A valid license file comes with each sensorcontroller. Please import this from the "Licensing" tab of the CD's "Thermoguard Configuration" window, using the "Reload *.lic file" function. The

license file resides in the \_License subdirectory.

Select the file with the extension *.lic, not *.licsrc. The file *.licsrc only serves veri-

fication purposes for the contents of the *.lic-file.

Without a valid license file, the program will only run in simulation mode. An entry in the "Licensed MAC addresses" window must be present for each purchased sen-sorcontroller (not for each individual sensor).


Configuring the Software After successful installation and licensing, the program can be configured to your require-ments. All settings are carried out via the corresponding tab in the "Thermoguard Configura-tion" window. Thermoguard Configuration: General settings, Data file settings, Mail settings, Sensor configuration, Logging Licensing, Scan local network, Global settings, Miscellaneous, Service

Poll interval: For laboratory refrigerators 15 or 30

minute intervals have proved themselves. Use shorter intervals of 10 or 15 minutes for incubators

and 1 to 5 minutes for climate chambers.

General settings

- Poll Interval: Settings for polling interval and start time for first poll of the sensorcontrollers

- Alarm hours: Specify the hours at which alarm can be triggered Example shown in image: Mondays to Fridays from 08:00 AM to 07:00 PM no alarm will be triggered Non alarm hours which are configured here override non alarm hours which can be configured for any sen-sor individually.

- Holidays: Opens the calendar pane ("Set Holidays") to specify the days at which alarm is triggered in any event, regardless of "alarm hours".

- Program language: The selection field lets you set the required language. "Use regional settings" automati-cally selects English or German. In order for the conversion to take effect, the program must be restarted after you select the required langu-age.

Set Public Holidays

- Allows specifying days at which the alarm is triggered in any event, regardless of the "non alarm hours" (ge-neral as well as sensor specific). In the left-hand example Whit Monday 2014 has been set.

- If neither general non alarm hours nor individual non alarm hours are set, settings in the "Set Public Holi-days" dialog are ignored since alarm will be triggered any time anyway.


Note on encryption The encryption will not protect from unauthorized access to the file but against content manipulation. Access must be restricted to authorized users in a legal environment by the responsible administrator. The TG Decrypt utility enables decrypting the encrypted data. The log file can also be encrypted, see below under "Logging".

*.tg Branch Support checkbox: See separate Documentation TG Mandantenfähigkeit-de.pdf (German only, located in the root directory of your Thermoguard Installation CD)

- Simulation file (*.sim) and Text file (*.txt) settings: Path to *.sim and *.txt files: In this path the program expects the files for sensor source settings "Simulation file Temperature", "Simulation file Humidity " and "Text file".

Data file settings - Measured value data file settings (*.tg):

Path to *.tg files: Here, data files containing the re-corded data values are stored. Interval for file separation: Settings for beginning a new data file: Daily, weekly, monthly, quarterly or annually *.tg filename format information: Providing a readonly preview of the filename scheme which will be used depending on the above interval setting (e.g. "TGw.." for weekly, "TGq.." for quarterly interval selection for file separation) Encrypt *.tg files checkbox: The plain text data re-cording in the *.tg files can be encrypted to protect against content manipulation.

- Target Path for automatic TG system files backup on configuration changes: Here, you may enter a path to a network share. On every global configuration change, the TGuard.ini file is copied into this directory automatically as well as the TGuard.scx file on a single sensor configuration change. A simple Backup of these two important files is one purpose of this feature, however it additionally provides the possibility to avoid a share on the standard %ProgramData%\Thermoguard Data" path on the "Thermoguard Server " which is needed by Thermoguard Report. Thermoguard Report can be configured to use this backup path instead.

- Alarm e-mail on *.tg write failures checkbox: If the pro-gram is not able to write the measured value to the *.tg file of any sensor after 3 retries (i.e. 4 attempts in to-tal), an alarm e-mail can be sent optionally. For the Name: and E-mail: input fields the same possibilities (several rescipients, "GSM addresses" etc.) can be used as explained in chapter Mail settings (see be-low). IMPORTANT NOTE: If a general problem occurs writing to *.tg files (e.g. a mapping is lost), one e-mail will be sent for every single sensor poll. This may re-sult in a huge volume of e-mails. Be aware of this danger especially if you send SMS e-mails (liable to charges). These same E-mail settings are also used for notifica-tion if the automatic system files backup (described above) failed.


Example of entering two e-mail recipients

Here the e-mail message is sent to two main recipients, and a copy to two other employees.

Mail settings - Commands for dial-up connection: Settings for

sending e-mail on standalone systems through mo-dem via RAS or data com

- Authentication required: Select authentication (POP, ESMTP or TLS), mail user specifications.

- SMTP/POP3 server: Mailserver: IP address or DNS name of the server Port: You may change standard SMTP Port 25. Retry: Number of retry attempts for sending mail in case the first attempt should fail. A maximum of 5 retry attempts can be set. From e-mail: Sender address. Please change the de-fault to a valid mail address of your choice, because this address is used for deferring mail items in case mail dispatch should fail through an unknown recipi-ent!

- E-mail recipient(s) ...: E-mail names and addresses of recipients. Multiple e-mail recipients can be entered under "Name/E-mail" or "CcName/CcE-mail"; the names/mail addresses are then simply separated by a semicolon. In this case, the number of specified names (e.g. in "Name") should match the number of the corresponding mail addresses (e.g. in "E-Mail"); see bottom figure on left.

- Send test mail(s): Test button for sending a test mail message to check mail settings. Up to 500 mail items can be sent one after the other in a test ("Number" in-put field).

- SMS via GSM Modem: See separate documentation TG GSM Modem-en.pdf


The sensor list

Maximum capacity is 999 entries.

Sensor configuration Using the sensor list:

- Adding a new sensor / copying a sensor: Add a new sensor by clicking the "Insert" button. If a sensor has been copied by clicking "Copy" before, a copy of this sensor will be created after the marked line. If not, a sensor with default settings (name= Name, IP address = 192.168.0.5 etc.) will be created. You may also use the following keyboard shortcuts: Copy the selected sensor:

+ or +

Insert sensor: or +

Only one single sensor can be copied/inserted at the same time. If more than one entry is selected, buttons "Edit", "Copy", "Insert" and "Delete" are disabled.

If you move the mouse over the "Insert" button, name and location of the copied sensor is displayed.

- Changing the sensor order in the list: The sequence in the list determines the sequence in which the sensors are polled one after the other. The position of the sensors within the list can be shifted upwards or downwards to a new one using the two blue arrow buttons. Even several sensors (must not be adjacent) can be selected and shifted together. After the desired position has been reached, the new order can be applied or discarded clicking the appro-priate buttons. Tip for a "continuous shift": Just click on one of the

buttons once shortly, then click and hold Enter

. The selected lines will be moved smoothly (i.e. without the need to click on an arrow key repeatedly).

Deleting one or more sensors: All selected sensors will be deleted by clicking on the "Delete" button. This process is irreversible. Thus a confirmation dialog shows up. Alternative keyboard shortcut: Press the key


The sensor list's context menu

TGuard.txt imported into Excel

- Sorting the list: Click on a column header (e.g. "Location") to sort the list alphabetically respectively numerically ascending or descending according to the column's content. The new sort order will be saved on program exit and re-stored on restart. If such a user defined sort order is active, it is not possible to edit a sensor. First the de-fault order (sort by "#", ascending). Appropriate dia-logs notify about this restriction.

- (De)activating (multiple) sensor(s) (together) / Exporting selected sensors: Right-clicking the sensor list allows common enabling, disabling or inverting status for the previously selected sensors on the "Please Confirm" context menu. This function also allows en/disabling an individual sensor in a simple manner without requiring you to open the "Sensor configuration" window of a sensor first. The "Export as *.txt (TAB separated)" menu item exports the settings of the previously selected sensors to a simple text file containing tab stops as separators; the first line contains the column names. This file can be further processed using Microsoft Excel, for example.

- Editing a sensor:

One of the following actions opens the window for configuring a sensor (only one single row must be se-lected):

Double-click a row of the list Click the "Edit" button Press the enter key

Configuration of a single sensor will be described be-low.

- Export and Import one or more sensors as *.scxtpl and

- The Sensor list Search function see => Part 4: Advanced Information


In GMP compliant environments do not change the default setting "Keep old log file" to prevent over-

writing of recorded data.

You should backup all log files on a regular basis (see Data Backup)!

Logging

- Log file: Path and settings of the log files Write log file: The checkbox should only be unchecked in rare cases (e.g. running out of hard disk space). Log file prefix: The format of the log file(s) filename is [Prefix]_JJJJ_MM_TT_HH_MM_SS.log

Example: TG_2008-05-04_15-26-32.log.

The Date/Timestamp in the filename is equivalent to the date of the first entry in the file. Max. size / KB: Minimum=64KB, Maximum=1.048.576KB (=1GB) Erase/Keep old log file: Only in rare cases (e.g. low hard disk space) the Erase options should be selected. Encrypt log file: The plain text recording in the log file can be en-crypted to protect against manipulating the contents.

1)

- Log file output: Selection options for the log file contents: Error (ERR), warnings (WARN), single sensor (SNG=single), infor-mation (INF), change (CHG=Change), failures (FAIL), computer name and user name (the logged in Win-dows user)

- Monitor's activity log: Options as above (Log file output), additionally: Max. lines: If the maximum number of output log lines that is set here is exceeded in the monitor window, that window will be cleared.

- Advanced logging: Writes additional debug information in the log file for possible support in case of an error.

- Show last log file (no decryption): Opens the last log file using the application which is associated with the

*.log extension.

1) The encryption will not protect from unauthorized access to the file but against content manipulation. Access must be restricted to authorized users in a legal environment by the responsible administrator. The TG Decrypt utility en-ables decrypting the encrypted file. The *.tg data files can also be encrypted, see "Thermoguard Configuration: Data Files"


Licensing

- Lic. file version: "Date issued:" and "Expiration date:" provide informa-tion about the license type: SIM: Program runs in simulation mode BAS: License of a Thermoguard Basic package PRO: Thermoguard Professional license

- Reload *.lic file: Button for reading the license file that comes with the product

- Licensed MAC addresses: Lists the MAC addresses of the licensed sensorcon-trollers which are encrypted in the license file

- Company/Name: Name of company and licensee (user)

For inventory purposes, right-click the list of the

controllers to exported it.

Scan local network

- "Scan local network:" The button starts search

for Thermoguard sensorcontrollers on the local net-work. Sensorcontrollers which are linked remotely (e.g. via VPN) can not be reached. All recognized, licensed and non-licensed sensorcontrollers are listed.

Note: When enabling the Windows firewall for the Thermoguard (TGuard.exe) program, an exception must be defined with the

Windows XP SP2 or later operating systems. The scan process uses UDP Port 8513 which must be possibly opened in a firewall.

Assign IP address

A new, fixed address can be entered in the "IP address" field. After the IP address is entered correctly, clicking "Assign IP address" assigns the address to the controller (after a security prompt). This IP address may not already exist on the local network. A sensorcontroller is recognized on the network for its unique MAC address worldwide. The MAC address can be found on the outside of each sensorcontroller for identifying the device.

- Include details: If this checkbox is checked (default), an internal second scan process gathers additional information for some (older) sensorcontroller types. If the local network scan is too slow you may uncheck this option.

- Note that you can sort the list by clicking on a column header.


Open a sensorcontroller's built-in internal website (respectively telnet for HC1P) directly from "Scan local network"

- If keyboard shortcut

+ (Shift + F1) is pressed the following action

will be executed for the selected sensorcontroller:

If sensorcontroller is SC1eP, SC2e, SC8eP, AC2nP or HM1P/HF1P: Opens internal website using default internet browser

If sensorcontroller is HC1P (obsolete model): Issues command <telnet IP address:1111> Note: On Windows Vista and Server 2008 the telnet program must be installed explicitly.

Warning: Use the internal website of a sensorcontroller only to modify the basic network settings. These are the IP address and if necessary (e.g. for a remote access scenario) the subnet mask and the gateway address. All other settings will not be used by the software and should not be changed in any way to avoid possible malfunctions. An exception is the Configuration of an AC2nP which requires performing some additional settings.

Global settings The "main switch" Enable global settings is used to enable or disable the defaults for all sensors. The individual de-faults must then be activated by clicking "Activate" (when activated, a red button can be seen). These will then have priority over the settings that are carried out separately for a single sensor.

For option "Use E-mail recipient(s)..." you may check option "for all sensors *additionally*...". Then, all e-mails are sent to the global as well as the individual recipients. If this option is not checked, e-mails are sent to the global recipients exclusively and the recipients configured for each sensor will be ignored (standard behavior before Version 2.94).

The example on the left shows two activated settings: 1. In any event, the data of all sensors is written in a *.tg file (if checkbox "Write *.tg files" were not checked, not a single sensor would write any data!), and 2. the e-mail recipients set on the mail tab apply to all sensors ignoring individually configured addresses.

The descriptions of the Alarm options correspond to those in the following chapter on Sensor Configuration/Alarm.


Program- and Path Information show the exact program

build, the path to the executables, i.e. TGuard.exe, and

the path to the configuration files, i.e. TGuard.ini

- Reset Retry counter ...: If this option is set, the alarm behavior changes. The (German) PDF Alarmverhalten Beispiel.pdf provided on your installation CD illustrates different alarm states and actions depending on the various alarm settings.

Technical information:

The option "Thermoguard classic" sets for the applica-

tion TGuard.exe the appropriate (userspecific!) registry

entry for the file property Compatibility/Settings/ "Disable visual themes".

Miscellaneous

- Unit: Temperature settings in Celsius or Fahrenheit (U.S.)

- Skip dialog when shutting down: Turns off the security query "Do you really want to shut down Thermo-guard?" when closing Thermoguard

- Monitor: Clear activity log before poll: The Thermo-guard monitor's log pane is cleared prior to automatic or manual polling of sensors.

- Maximum number of popup windows: Maximum num-ber of alarm windows that may appear on the screen at the same time

- Relay Interface: Setting for the serial interface for the eight-fold Relay Interface from AK-Modul-Bus Corpo-ration. Values in the range 1 - 16 are allowed. For details see Separate documentation.

- Play test tune: For testing the acoustic alarm via the sound card. You must stop the test by clicking on the

"Stop" button (square symbol). File violhi49.wav is

used for the test. - Use Proxy: Sensorcontrollers can also be polled be-

hind a proxy server; e.g. sensorcontrollers outside of the local network protected by a Microsoft ISA Server.

- AOF - Special settings: Fire AOF repeatedly: By default (option not checked) a one-time AOF will only be triggered the first time an AOF occurs. This avoids "spam" of huge quantity of AOF alarm e-mails being sent, e.g. during network dis-ruption or power blackout which affects many sensor-controllers. If this option is checked, an AOF alarm will be triggered for each poll when an AOF occurs. Fire AOF during "non alarm hours": If this option is checked, AOFs will also be fired during "non alarm hours".

- Design (requires restart): To use "Windows XP Style":

Windows XP/Vista/7: the service "Designs" must run (default)

Windows 2003/Server 2008: the service "Themes" must run (deactivated by default!)

Windows Server 2008: The "Desktop Experience" feature must be installed

If these requirements are met, you may select the ap-propriate design under "Display Properties" => "Ap-pearance"; select "Windows Vista"under "Designs" with Vista/Server 2008.


- HC1/HR1 "Sensor Missing" sensitivity (0..20) (not applicable for models HM1P/HF1P):

Thermoguard immediately recognizes missing sensors (ES/EP) on sensorcontrollers HC1P or HR1, if the controller is set for the first time or reset through power blackout, because 0.0°C or %RH will then be measured for both the temperature and the humidity values. Whereas if an HC1P/HR1 sensor is removed while the system is running, then (unlike SCn devices) the same last temperature value will be "supplied" for each poll. If the value set for "HC1/HR1 "Sensor mis-sing" sensitivity" >0, the software will perform a check on how often exactly the same value (temperature and humidity) was read in succession. If, for instance, the same value is read four times, it is extremely likely that no sensor is connected, and an AOF "Sensor missing" will be triggered. This is an extremely secure procedure, since Thermoguard does not use the "normal" values (with one decimal point) here, but the internal value with two decimal points (respectively for temperature and humidity). It is compara-tively unlikely that exactly the same value is measured several times in succession for a connected ES/EP sensor. But we cannot give a total guarantee that false alarm may be triggered for this procedure anyway, of course. The value that is set here should be customized depending on the duration of the poll interval. When selecting "0" as a value, the recognition procedure will be turned off completely

NetIO

- "NetIO" Configuration (Internet Power Controller, optional accessory): Thermoguard directly supports 1 to 16 "NetIO" Internet Power Controllers available from company Koukaam. Each controller can switch one to four 230V~ devices, e.g. for example a rotating flashing beacon or a siren. Compared to the relay interface using the NetIO for switching 230V~ devices is far less complicated, be-cause it comes in a protected housing and can be attached anywhere to the network. If you intend to switch an alarm device far away from the Thermo-guard server there is no need for an additional COM server as with the relay interface. Please see your NetIO manual regarding the setup of your NetIO. On the NetIO tab in Thermoguard confi-guration shown left you then enter the IP address, username and password for your device(s). Afterwards, use the "Test" button to perform a short test afterwards. Every single sensor can be configured to switch any combination of the 1 to 4 OUTlets of one NetIO. This sensor specific configuration is described here: CAM settings / Trigger "NetIO" Internet Power Controller NetIO

Remote alarm made easy using a NetIO Controller


Service and information e-mail

- Configure Thermoguard as an NT Service: The buttons with the blue pictograms enable configu-ring Thermoguard as Windows NT service. Read the separate chapter on Thermoguard as a Service.

Thermoguard must be started with local administrator privileges in order to be able to configure the service. If not, the shield symbol will be displayed together with a related message:

- Send Heartbeat e-mail: Daily information e-mail ensures that the employee in charge of the device is regularly informed about the proper state of the Thermoguard program. This is es-pecially useful when Thermoguard runs as a service, because otherwise the service does not have an infor-mation interface (except for the log file) to the user. The info mail is also sent, though, when running Ther-moguard as an application (even if the configuration of the info mail resides on the "Service" tab). The info mail provides information about the computer name of the PCs where Thermoguard is running; it outputs some statistical data in the mail text.

- The functioning of the Heartbeat e-mail requires

configuration and trouble-free functioning of the e-mail server on the "Mail" tab.

- Multiple e-mail addresses can be specified in the e-mail address bar. The addresses must be separated by a semicolon (see also E-mail recipient(s)).

- An information mail is sent to the specified e-mail ad-

dress(es) once every day.

Sample of a Thermoguard Infomail, which has been received using Microsoft

Outlook; the body length is small so the text can be sent as SMS completely too.

"APP" means "Application", "SVC" "Service", "Polls" (here = 8480) informs about number of total polls since start of

the current session, "Run" is the runtime of the current session and "Tot" the total

runtime (here = 11days, 18 hours and 19 minutes)


Sensor configuration: Sensor #nnn Basic settings, Alarm settings, E-mail settings, AOF settings, CAM settings, Calibration

Double-click a sensorcontroller or temperature sensor in the list, or the "Edit" button on the "Sensor Configuration" tab, to open the dialog for detailed configuration of each sensorcon-troller or temperature sensor.

Note: While the "Sensor configuration" window is open, the two windows, "Thermoguard Monitor" and "Thermo-guard Configuration", are locked against input - the window titles are then supplemented by the additional word "-LOCKED". Only after closing the "Sensor Configuration" window will these windows allow new input.

All sensor specific settings are saved to the file

TGuard.scx

Example for the correlation between "Source" and the physical connection-port of an SC8e

Basic settings

- Basic sensor settings: Label: Maximum length is 30 characters, invalid characters are: \ / : * ? < > | " and a period. Location: Max. length and invalid characters: ditto Use IP Address/Use hostname: The selection buttons allow optionally entering the sensorcontroller's IP ad-dress or host name (not relevant for Sources "Simula-tion file ..." and "Text file").

Note: Using a host name and setting the port allows a port deviat-ing from Port 80 in the 81-89 range for polling sensorcontrollers of the SCn type. For sensorcontrollers of the HC1P type, this is a fixed polling port at 8000. Specifying a port deviating from the default of 80 can, for example, be used to run polling for multiple sensorcontrollers over the Inter-net and a router with a fixed and dynamic IP. The router must then convert the different IP addresses of the sensorcontrollers to the specified ports in the 81-89 range.

Source: Selection of the data source for this sensor: Sensorcontroller with associated port (SC2e=Port 1,2; SC8e=Port1..8), HC1P/HR1 (each with Temperature and Humidity), Simulation file Temperature/Humidity, analog sensorcontroller AC2 (Port 1,2, /Single 3) or Text file

Simulation file: When selecting the simulation file the program for this sensor will run in simulation mode. The data is not read from an actually existing sensorcontroller but from a *.sim file instead (see separate chapter).

Text file: Similar to simulation file. The data is read from a text file *.txt (see separate chapter).

AC2 Port1 or Port2: For analog sensorcontrollers of type ACnP: If selected, the input field "Unit" is enabled additionally (see Confi-guring AC2nP).

Timeout: Time in seconds the program tries to read data from the controller. For HC1P the value is in-creased to a 8 second minimum, for HR1 to a 30 sec-onds minimum. 4 retries are executed on failure (not relevant for the sources (not relevant for sources "Simulation file ..." and "Text file").


Basic sensor settings cont'd

In the Sensor description field additional custom settings can be configured. See chapter Additional sensor

settings customization using the Sensor description field at the end of this chapter.

- Enable (include in poll): This checkbox must be enabled (green check), so that the sensor is also queried during polling!

- Write data to *.tg file: The green check must be visible in this checkbox, so that the temperature or humidity values are written in the *.tg data file.

- Switch: The switch function is only available for the SCn ports "SC1..SC8" and "Simulation file Temperature", and is described separately in the The Sensor Switch Function appendix.

- Sensor description: A text of your choice with a maximum length of 512 characters.

- Maintenance Plug (36 ohms): If checked: If instead of a PT100 sensor a fixed resistor of 33 to 36 Ohm is assembled to an SC1- or SC8 port (temporarily) the software recognizes the corresponding polled temperature value (≤ -150°C) as "maintenance state" and will not issue an alarm. Thus the device to be monitored can be "pulled" from the sensorcontroller. By applying such a "maintenance plug" there is no need to deactivate the port in the soft-ware.

- Alarm Relay Channel R1 / R2: See separate documentation TG Alarm Relay Channel-en.pdf


Alarm settings - LOW Limit/HIGH Limit settings: Low and high limit for

alarm. Note that the possible valid range for the limit values depend on the selected source: "AC2 ..." and "Text file" support a range from -9999,9 to +9999,9 whereas all other temperature sources can use values from -200 to +650. For Humidity " a value out of a range from 0 .. +99,9 can be entered, for pressure range is +10 .. +1100. Alarm types: Popup window, Send mail and Alarm sound (No sound, PC speaker or WAV file via sound card). For option WAV file you may select own WAV files and test them using the test buttons.

- Alarm mode: "Retry": Alarm is triggered immediately with single (Retry = 0) or only when exceeding or falling below the limits recurs (Retry > 0).

- Mode "Serial" with multiple excess: Alarm is triggered only when the limit has been exceeded multiple times and without interruption (Serial checked) or the number of set excesses (Retry) has been reached with in-terim drop in temperature (Serial unchecked).

- "Event" checked: One-time alarm is triggered only for initial violation of limit, then for new violation only when the value was in the "green zone" in the interim period. "Event" unchecked: Alarm is triggered each time the limit is violated.

- "Mail if Event revoked" checked (only effective if "Event" is checked): If the event status is disabled, an e-mail will be sent to the recipients configured on the "E-Mail settings" tab respectively on the global settings. If required, you may edit the default Subject and Body text for this mail in file TGuard.ini in section [MailIfEventReleased] for Low and High. You can use the placeholders shown on "E-Mail settings" tab: [MailIfEventReleased]

LoSubject=Temperature %loc: %t for first time >= LoLimit (%lo)

LoBody=Sensor label: %lbl^Measured: %dt

HiSubject=Temperature %loc: %t for first time <= HiLimit (%hi)

HiBody=Sensor label: %lbl^Measured: %dt

- Special time settings - Select range with mouse, then click one of the buttons: You are able to mark certain hours of the week for every single sensor at which no alarm action (standard alarm as well as AOF) shall be executed (marked yellow). Or you may set hours where this sensor is even completely disabled (i.e. not polled, marked white). In the sample above, every Monday to Friday from 8 A.M. to 7 P.M. no alarm will be triggered (though the sensor is polled and temperature or humidity data will be written to disk). On Tuesdays between 10 A.M. and 3 P.M. the sensor is disabled because a regular maintenance procedure is per-formed for the device which the sensor monitors. Please note:

Non-alarm hours which are configured under Configuration/General settings (see Configuring the Soft-ware, marked yellow), will have priority over alarm hours configured for a single sensor (marked red).

Consider the general setting Fire AOF during "non alarm hours". If a sensor is manually disabled permanently with its "main switch" on the "Basic settings" tab

( ), any "Special time settings" do not apply.

"Holidays" button: If any holidays are specified, alarm will always be triggered independently of the "non alarm hours" (see Set Public Holidays).


E-mail settings

- E-mail recipients(s) for alarm mails (High and Low): Addresses of the employee in charge of the device and his delegate. Multiple e-mail addresses are sepa-rated by a semicolon (see E-mail recipient(s) also).

- Use own e-mail subject / text: Subject and text for the alarm e-mails can be customized individually. You can use placeholders for various values (see frame "For your information"). The "Preview" button allows checking the resulting e-mail format.

Note: After you change your own subject line or your own e-

mail text you need to click "Apply" first, so that the preview button is re-enabled.

AOF settings

- Enable Alarm On Fail (AOF): Settings for alarm during failure or disruption of a sen-sorcontroller or temperature sensor Alarm options are the same as on the Alarm settings tab.

- Replace "Sensor missing" with own text: Allows individual setting for the Alarm On Fail mes-sage "Sensor missing" (especially for switch function, see appendix, The Sensor Port Switch Function).

- "Test AOF" button: Allows direct testing of AOF using the current settings.

CAM settings

- Enable Custom Alarm Module (CAM): Run external program on alarm: File: Complete path and filename to any external ex-ecutable which is started on alarm. For instance, this may be a customer-specific program that was developed on commission. Parameters: For special command line parameters which the CAM program may require. Append Thermoguard Parameter: On program call 44 Sensor parameters will be appen-ded after those which may be entered in the "Parame-

ters" field. The utility CAMDemo.exe shows all of Ther-

moguard's parameters. The Visual Basic 6 source code of CAMDemo is located on the installation CD.


Relay Interface

NetIO front and rear view

- Trigger COM Relay Interface: The 8-fold Relay Interface from AK-Modul-Bus Corpo-ration is supported. Typical use would be linking Thermoguard to an alarm switchboard with floating distance contacts. The "Relay #" can be configured individually in the 1-8 range. Additionally, one of three Relay switch functions can be selected on availability of violation of limit or device failure:

Short pulse (700ms): One-time short pulse for 0.7 seconds

ON/never OFF: Permanent ON switch, with manual reset function via TGRelIF.exe.

ON/good =>OFF: Permanent ON switch until limit violation or device failure problem removed.

A separate documentation describes the usage of the Relay Interface in detail

- Trigger "NetIO" Internet Power Controller: The "NetIO" is an optional 3

rd party hardware device

from Koukaam Corporation and is directly supported by Thermoguard. It allows to switch one to four 230V~ devices via the network. One single sensor can switch any combination of these four 230V~outlets of one single NetIO Controller - depending which checkboxes under "230V~ OUT" are checked. This means for example that a sensor A can switch OUT#1 and a sensor B can switch OUT#2 of the same NetIO Controller. Thermoguard supports up to 16 separate NetIO Controllers which must be configured (IP, user, password) on the configuration NetIO tab. The desired unit for the sensor is then selected under "Device #". Three alarm modes are available: ON for 2 seconds: ON and OFF after a 2s pause ON/never OFF: Permanent ON switch, you have

to switch off the outlets using the built-in website of the NetIO Controller called by an internet browser.

ON/good =>OFF: Permanent ON switch until limit violation or device failure problem removed.


Calibration

- Enable Calibration: Allows correcting the actually measured temperature and humidity values (T1 and T2 measured) with a measured deviation of the measuring sensor against a specified calibration value (T1 and T2 reference). One- or two-point calibrations are possible ("Mode"): For one-point calibration, the offset is determined; for two-point calibration, the offset and the gradient according to y = ax + b are determined.

Examples of a calibration are synchronization of measuring errors with a 0 °C ice-water mixture according to DIN 60751 or the use of Thermoguard humidity reference cells for a humidity sensor

Additional sensor settings customization using the Sensor description field Format is a leading ## followed by Entry=Data. The following applies: ##Entry=Data can be placed anywhere within the Sensor description field. It can be surrounded by "standard" descriptive text. "Entry" is case sensitive, "Data" is case insensitive. "##" and "=" may be enclosed by one or more Space characters to improve readability. Data itself may contain space characters too. If ##Entry appears more than once, only the first is read. "Data" is read until next ## or until end of line. Please note that in the description field an end of line (created by hitting the ENTER key) cannot be differentiated optically from an automatic word wrap. At present the following entries are supported: ##VariableLimits=Filename Sensor sets its Lo and Hi limits depending on contents of file "Filename". The corresponding separate documen-

tation TG Variable Limits-de.pdf is currently available in German only.

##AOFSubject=Text Here, an own Subject can be defined for an AOF Mail. The placeholders %lbl, %loc and %aof (cause of AOF) are supported. ##RelayPulse=<value in ms> Own length for the Relay Interface impulse (fixed default is 700ms). Valid values are in the range 500 .. 65535. If value is outside this range an error message is logged and the default is set. Note that the custom value is shown after switching to the "CAM settings" tab; e.g. value=1500: "violation => Impulse (1500ms)" #MailSubject=Text The Text which is entered here is not limited to 50 characters as it is using the appropriate field on the "E-Mail settings" tab. All placeholders are supported. In order to become effective checkbox "Use own e-mail subject" on "E-mail settings" tab must be switched OFF!

Example:


Running the Software When running, the Thermoguard monitor pane shows all relevant activities, measuring values, alarm counters and the duration of the operation mode. Thermoguard Monitor: Activity, Sensor details, Uptime info

Tip: When right-clicking the "Log" area of the Thermo-guard monitor window a context menu item that allows

you to manually delete the log window's content appears.

While polling the "Poll indicator" label is replaced by a "stopwatch" information displaying the poll duration.

Activity

- Guard running: Current status, starting and stopping the poll for the sensorcontrollers. "Stop" button : If Thermoguard is running as a ser-vice, the service will be stopped and restarted. Admi-nistrative privileges required!

- Poll indicator: Shows the current poll, and allows instant polling of all sensors via "Poll all" button. As long as the poll is active, label of the button shows "Cancel". If clicked then, poll is canceled immediately. During the poll, properties (label, location, low limit etc.) of the currently polled sensor are displayed. Af-ter all sensors are polled, the sensor is reselected which was selected before the poll. Alternative key-board shortcut: (on numeric keypad)

- "Poll Sensor" button: Polls the currently selected sensor only. Alternative keyboard shortcut: (on numeric keypad)

- Activity log: Reflects the current entries of the Ther-moguard log file. Numbers within frame: a(b) The log currently consists of a lines, it will be purged after b lines. x/y (during poll): Sensor #n of total y sensors is polled currently.

- The Monitor window can be resized horizontally, using the mouse, to dis-play the log file entries in full width and a possibly setup "passport image". It can be resized vertically too, to display more log lines.

- Pressing the key opens the last *.tg file (if there is any at all) containing the recorded data.


Sensor details Shows status values of the selected sensor.

- Alarm On Fail: Displaying the "Alarm On Fail" status: An "Alarm On Fail" event, i.e. sensor or sensorcon-troller failure is saved temporarily (Active=Yes) to avoid a variety of identical alarms. AOF Reset button: Release active AOF status.

- Single sensor poll: As on Activity tab - Status information / Manual reset: Displaying the cur-

rent alarm counters. Right-click on a value to reset the displayed counter for the currently selected or for all sensors. Retry.curr.(max): Current and (maximum, as confi-gured for selected sensor) number of allowed retry attempts. Event state: Displaying the current event status Total # of violations: Total number of violations Total # of alarms: Total number of triggered alarms Last poll: [Date/Time]: Last poll date Simul #: Current "step" in simulation operation. After resetting the value to 0 by right-clicking the next value will be read from the beginning of the simulation file on next poll.

- "Show last *.tg file for selected sensor ()" button: Opens the last data file of the selected sensor using the application which is associated with the *.txt ex-tension (for *.tg and *.sim Thermoguard setup establishes the same file association as for *.txt).

Uptime info

- This tab provides readonly information and display various details regarding system runtime Here, "session" refers to the period between program start and program termination. Total uptime and start and end time of the last ses-

sion is saved to the TGuard.ini file.

Additionally the total number of polls for the current session is displayed.


Thermoguard as a Service

Thermoguard can be used not just as an interactive program. Thermoguard can also be in-stalled as a Windows service. Comparison: Thermoguard as interactive program versus Windows service

Interactive program Service

Manual Windows user login and manual startup of Thermoguard required.

Thermoguard starts automatically along with the operating system. No Windows user login required.

When the Windows user ends his/her Win-dows session, Thermoguard will close.

Thermoguard runs as a service regardless of Windows user login/logoff.

The interactive program allows visual checking and poll options: - Displaying current activity - Displaying and polling measured values - audio and visual alerts

Thermoguard as a service does not allow any visual or audio alerts. It runs completely as a background service. That is why enabling the "Heartbeat e-mail" is recommended for monitoring activity.

Changes to the configuration are directly im-ported.

Thermoguard as a service is configured via the interactive program. To apply the changes the service must be restarted.

The drive mappings of the logged in Win-dows user can be used for network drives.

Ensure that the service account used has access rights to possible setup network drives for log and data files. No drive mappings are allowed for such re-sources. You must use the UNC name in the format "\\server\share".

No local administrator privileges are required to run Thermoguard.

Local administrator privileges are required to control a service (i.e. installing, starting, stop-ping, uninstalling).


Note: Green background color for the password input fields just indicates that the passwords match, not that

the password is correct!

Installation as a service

- The Thermoguard service will not be automatically in-stalled as a service by Setup.

- The service is installed via the "Service" tab of the "Thermoguard Configuration" window. Normally, this is a one-time operation. Administrator privileges are required.

- After clicking the "Install" button, service account data are queried. It is recommended to create a special domain service user account which has proper rights to control a service and read/write access to the fold-ers where *.tg and *.log files reside.

- After uninstalling the service there is no need to rerun Thermoguard Setup.

- Service installation sets the "Startup Type" service property to "Automatic".

The Thermoguard service after installation in the Services Manager under Windows Control Panel

- Notice that you must assign the Thermoguard service a service account ("Log On As") with the corre-

sponding access permissions in case the service should access networking resources (for log and/or

data files). In the example above, account of the fictitious user [email protected] has been

assigned. - The service can also be started/stopped/paused or restarted via the Windows Services Manager. The

buttons on the Thermoguard configuration's Services tab will immediately change their respective status. It is recommended, though, that you perform service control only via the "Service" tab of a Thermoguard program which has been started interactively.


Starting, stopping and restarting the service

- The service can be started or uninstalled again after successful installation. If you entered a wrong password for the service ac-count by mistake, the service will not start. In this case simply uninstall and reinstall the service.

- The interactive program can be shut after starting the service, and the Windows user can be logged off.

- Following successful startup, the service can be stop-ped or restarted.

- To uninstall it, the service must be stopped first.

Important Note Polling the sensorcontrollers and other actions such as saving data or alerts will no longer be executed by the interactive program but by the started service after successful installation and startup of the service. The log output message "Poll request from interactive session denied: The running service polls exclusively!" is not an error message, but an information. This restriction prevents polling the same sensorcontrollers from both the service and the interactive program (a parallel "multi-client-access" is not supported by the sensorcontroller's integrated HTTP-server):

If Thermoguard runs as a service, the interactive program can not execute a poll

Log file The service and the interactive program use the same log file for logging all actions. Service actions are marked by "SV" (Service); interactive program actions by "I"; example output: ...

15.08.2014 17:07:22 (INF) SV ===============================================================

15.08.2014 17:07:22 (INF) SV **Thermoguard START** Version 2.92 - Build of ...

15.08.2014 17:07:22 (INF) SV Program path: C:\Program files\Thermoguard\

15.08.2014 17:07:22 (INF) SV Configuration path: C:\Documents and settings\All ...

15.08.2014 17:07:23 (INF) I Service started successfully.

15.08.2014 17:10:20 (INF) I ShowLastLog: 1 files found.

15.08.2014 17:10:20 (INF) I ShowLastLog: Last log file determined as <C:\Documents and ...

...


Configuration changes The service applies the interactive program's settings every time it is started. All settings can be changed at any time after starting the services, using the interactive program. The service must be restarted in order to apply the changed settings. The interactive program will auto-matically perform restarting the service when clicking "Yes" to confirm the dialog shown below:

- If the service is running this dialog shows up every time the configu-ration changes are confirmed via the "Apply" or "OK" button.

"Heartbeat" Mail Since the service has no "connection to the external environment", running completely as a background service, the "Heartbeat information mail" (also to be found on the "Service" tab) should be enabled to monitor trouble-free functioning, so an e-mail message is sent once every day as a sign of life. Notice the descriptions under Send Heartbeat e-mail.


Part 3: Installing the Hardware Please note that this manual exclusively describes the hardware specifications fitting the

current range which is offered at the time the manual has been printed. Your equipment may differ from these specs. In this case the descriptions in the accordingly

older system manual apply.

Sensorcontroller Model Overview

Temperature

Thermoguard Sensorcontroller SC1eP

Technical Data: Network: Supported Temper. sensors: Measuring range, resolution: Measuring error: Supply voltage:

Power consumption: Power supply: Housing:

10/100 BaseT autosensing 1x PT 100 or PT 1000 with 4-wire technology -200 °C...+650 °C, 1/10 °C 0,3 °C ± 0,2 % (with class A sensor: ±0,15°C, ±0,2%)

Power-over-Ethernet (PoE) or via screw terminal with DC 18V .. 48V (+/-10%) or AC 18Veff .. 30Veff (+/-10%); AVG: 80mA @24VDC, 100mA @20VAC Max: 90mA @24VDC, 50mA @48VDC PoE Class 1 (0.44 - 3.84W) Plug-in Power Supply included: Primary: 100-240 V AC, 50-60 Hz Secondary: 24V DC, 220mA Plastic housing, 105 x 75 x 22 mm, for DIN rail mount

Thermoguard Sensorcontroller SC2e

Technical Data: Network: Supported Temper. sensors: Measuring range, resolution: Measuring error: Supply voltage: Power consumption: Power supply: Housing:

10/100 BaseT autosensing 1-2x PT 100 or PT 1000 with 4-wire technology -200 °C...+650 °C, 1/10 °C 0,26 °C ± 0,2 % (with class A sensor: ±0,15°C, ±0,2%)

DC 12V (-5%) - 34V (+5%) AC 9Veff (-5%) - 24Veff (+5%) Typical 200mA @12VDC, 100mA @24VDC, 100mA @20VAC, Max. 240mA @12VDC Plug-in Power Supply included: Primary: 100-240 V AC, 50-60 Hz Secondary: 24V DC, 220mA Plastic housing, 107 x 88 x 63 mm, for DIN rail mount

Thermoguard Sensorcontroller SC8eP

Technical Data:

Data equal to SC2e, but supports 1-8x PT 100 or PT 1000 with 4-wire technology and additionally Power over Ethernet (PoE) If an external DC power supply is used, make sure that the polarity is correct (terminal 1=-,

terminal 2 = +)


Temperature and Humidity

Thermoguard Sensorcontroller HM1P/HF1P

Technical Data: Network: Sensor included: Measuring range, resolution: Measuring error (typical): Supply voltage: Power consumption: Power supply: Housing:

10/100 BaseT autosensing Combined digital sensor for temperature, relative humidity and barometric pressure (HM1P only), 2m cable -40°C..+80°C, 1/10°C; 0..100% rH, 0,1%; 10..1100hPA, 0,1hPA (HM1P only) ±0,3°C; ±2% rH (@23°C); ±0,8hPa (750..1100hPa, @25°C) Power-over-Ethernet (PoE) or via screw terminal with DC 18V .. 48V (+/-10%) or AC 18Veff .. 30Veff (+/-10%); typical 80mA @24V DC PoE Class 1 (0,44 - 3,84W) Plug-in Power Supply included: Primary: 100-240 V AC, 50-60 Hz Secondary: 24V DC, 220mA Plastic housing, 105 x 75 x 22 mm, for DIN rail mount


Analog Sensors Thermoguard Sensorcontroller AC2aP

Technical Data: Network: Input: Resolution: Measuring error: Supply Voltage: Power consumption: Power supply: Housing:

10/100 BaseT autosensing 2x Current: 0/4..20 mA, 100 Ohm Current input: 2.5 µA max. 0,5 % FSR (Full Scale Range 0..20 mA) TA = 0-60°C Power-over-Ethernet (PoE) or via screw terminal with DC 18V .. 48V (+/-10%) or AC 18Veff .. 30Veff (+/-10%); typical 80mA @24V DC PoE Class 1 (0,44 - 3,84W) Plug-in Power Supply included: Primary: 100-240 V AC, 50-60 Hz Secondary: 24V DC, 220mA Plastic housing, 105 x 75 x 22 mm, for DIN rail mount

Thermoguard Sensorcontroller AC2vP

Technical Data: Network: Input: Resolution: Measuring error: Supply Voltage: Power consumption: Power supply: Housing:

10/100 BaseT autosensing 2x Voltage: 0..10 V, 1 MOhm Voltage Input: 1,25 mV max. 0,5% FSR (Full Scale Range 0..10V) TA = 0-60°C Power-over-Ethernet (PoE) or via screw terminal with DC 18V .. 48V (+/-10%) or AC 18Veff .. 30Veff (+/-10%); typical 80mA @24V DC PoE Class 1 (0,44 - 3,84W) Plug-in Power Supply included: Primary: 100-240 V AC, 50-60 Hz Secondary: 24V DC, 220mA Plastic housing, 105 x 75 x 22 mm, for DIN rail mount


Sensorcontroller Connections: Network and Power Network port

All sensorcontrollers include an Ethernet port with an RJ45 connec-tor, compatible with IEEE 802.3 standard. Using an ordinary 1:1 net-work patch cable, the sensorcontroller can be connected to a hub or switch. All controllers support 10/100BaseT with automatic recog-nition of the data rate ("auto-sensing").

Voltage supply of sensorcontrollers SC1eP, HM1P/HF1P and AC2nP via PoE

Models SC1eP, HM1P/HF1P and AC2nP can be supplied with external power as before using the green screw terminal. However, they are also designed for use in PoE (Power-over-Ethernet) environments in accordance with IEEE802.3af. Power is provided by the network infrastructure using the RJ45 terminal. The devices support both phantom power using data pairs 1/2 and 3/6 as well as power feed using the unused wire pairs 4/5 and 7/8. To enable power management for the supplying components, the sensorcontrollers are identified as a Power Class 1 device with a power consumption of 0.44 to 3.84W.

Voltage supply of sensorcontrollers SC1eP, HM1P/HF1P and AC2nP via power supply

Sensorcontrollers SC1eP, HM1P/HF1P und AC2nP are suppllied by the included power supply at the green terminal with a DC voltage of 24 volt. Correct polarity is important. For information about other supported power sources, see Technical data under Model Overview above.

Voltage supply of sensorcontrollers SC2e und SC8eP

for SC8eP using DC:

terminal 1=-, terminal 2=+

A DC voltage of 24V is fed at terminals 1 and 2 from the included power supply. Poles are irrelevant for SC2e. For SC8eP however make sure of correct polarity if using an external DC power supply: Use terminal 1 for negative (-) and terminal 2 for positive (+) pole! For information about other supported power sources, see Technical data under Model Overview above.

The Serial Port of SC2e/SC8eP is an emergency access only. Do not connect anything here. The Reset button enables resetting the sensorcontroller without in-terrupting the power connection.


Sensorcontroller Connections: Sensors Note: German only: On your installation CD a little information about 4-wire technology is

provided: \06-Vierleitertechnik\TG-Vierleiter.pdf Pin assignment of the 9-pole plug of SC1eP for PT 100 sensors:

A temperature sensor of the PT 100 or PT 1000 type is connected to sen-sorcontroller SC1eP at pins 5-7 and 8-9, using a 9-pole sub-D plug. The length of the connection cable should not exceed 100 meters.

Wiring scheme for PT 100 sensors for SC2e and SC8eP:

Up to two (SC2e) or eight (SC8eP) sensors of type PT 100 can be attached. SC2e does not use terminals "Sensor 3" to "Sensor 8".

After a new sensor has been connected, the sensorcontroller must be reset using the reset button. After reset the sensorcontroller recognizes all sensors automatically.

The length of the connection cable should not exceed 100 meters.


Connecting analog sensors to AC2nP:

One or two analog sensors can be attached to an AC2nP. First connect the (two) sensor's output wires to the 6-pole socket terminal, then fix the terminal with the two screws to the sensorcontroller.

AC2aP:

AC2vP:

Terminal connections for AC2aP: Port 1: [1.1] please do not use! [1.2]: I+ Current input 0/4..20 mA [1.3]: I- Ground

Port 2: [2.1] please do not use! [2.2]: I+ Current input 0/4..20 mA [2.3]: I- Ground

Terminal connections for AC2vP: Port 1: [1.1] please do not use! [1.2]: U+ Voltage input 0..10 V [1.3]: Gnd Ground

Port 2: [2.1] please do not use! [2.2]: U+ Voltage input 0..10 V [2.3]: Gnd Ground


Sensor Model Overview Note: German only: On your installation CD a little information about 4-wire technology is

provided: \06-Vierleitertechnik\TG-Vierleiter.pdf

Temperature sensor Standard

Technical Data: Temperature range: Area of application: Mounting: Type: Connection cable: Max. length of 4-wire cable: Dimensions: Accuracy:

-50 °C to +180 °C Indoor, inside freezers E.g. with self-adhesive plastics socket + cable tie or pipe clamp PT 100, 4-wire connection 2 m solid connection lead Comes with mounted DB-9-plug if ordered with SC1eP else pigtail cable 100 m Length 51 mm, diameter 6 mm DIN 60751 class A

Temperature sensor screw mounting


-50 °C to +200 °C Indoor, inside freezers Screw mounting PT 100, 4-wire connection, aluminum head 10 m solid connection lead, silicone cable with Teflon isolation of inner wire Comes with mounted DB-9-plug if ordered with SC1eP else pigtail cable 100 m 8 x 8 x 40 mm DIN 60751 class A

Low temperature sensor


-90 °C to +200 °C Indoor, inside ultra low freezers Screw mounting PT 100, 4-wire connection, Stainless steel head, 10 m solid connection lead, cable type TT 4xAWG 22 Comes with mounted DB-9-plug if ordered with SC1eP else pigtail cable 100 m 8 x 8 x 40 mm DIN 60751 class A


Very low temperature sensor "KW1"


-190 °C to +180 °C Indoor Pipe clamp recommended PT 100, 4-wire connection, Stainless steel head, sealed 10 m solid connection lead, cable type TT 4xAWG 26, drummed twice 100 m round shape, 5mm diameter, 100mm length DIN 60751 class A

Temperature sensor Indoor


-40 °C to +85 °C Indoor (room temperature) Wall mounting PT 100, 4-wire connection terminal Comes with 5m cable and DB-9-plug if ordered with SC1eP else without connection lead 100 m 70 x 70 x 27 mm DIN 60751 class A

Temperature sensor cold storage


-40 °C to +90 °C Outdoor, (cool) storage areas, machine rooms Wall mounting PT 100, 4-wire connection Comes with 5m cable and DB-9-plug if ordered with SC1eP else without connection lead 100 m 145 x 58 x 34 mm (Housing including sensor) DIN 60751 class A


Connecting the Indoor and Cold Storage Sensor Indoor sensor

Interior view of the indoor sensor

Wiring scheme

The cables are connected to terminal connectors in the indoor sensor case. Two wires are always connected together and directly to the measuring sensor. Please take care of a strain relief too. The connection cables can be extended to a maximum of 100 meters when using the four-wire technology. Vir-tually any four-cored cable can be used. A standard

telephone cable of 4 x 0.6 mm2 cross-section is a sui-table cable, for example. The cables need not necessari-ly be red/red and white/white of course.

Cold storage sensor

Interior view of the cold storage sensor

Inside the case of the cold storage sen-sor, colored cable pairs are connected to two adjacent terminals. Note: The ordering of the terminals may differ from the above scheme with your sensor (e.g. "3-1-2-4")! Please check. Regarding the cabling the above des-cription for the indoor sensor applies as well.


Assigning IP Addresses to Sensorcontrollers Each device in a computer network requires a unique ID. This is the IP address for today's TCP/IP protocol. Thermoguard sensorcontrollers use a static, i.e. permanent IP address. This is allocated to the sensorcontroller once prior to network operation. Each IP address may only be allocated once on a network. Your network administrator will provide the corresponding addresses for the sensorcontrollers. Each network card for a computer, each periphery device on the network, and also each Thermoguard sensorcontroller contains a globally unique hardware address.

This hardware address, also called Ethernet or MAC address, is required for assigning the future IP address. The address is fastened on the outside of the sensorcontroller.

The desired IP address can be assigned to a new sensorcontroller for the first-time as fol-lows:

Via the Thermoguard Software using the "Assign IP address" function Also for changing an already assigned address

Via the operating system's command line using the ARP command


Assigning the IP Address using the "Assign IP Address" Function This is the recommended, most simple, method which can be executed for all sensorcontrol-lers (SCn, AC2nP and HM1P/HF1P). The IP address can be assigned to a new sensor con-troller without existing IP address via network connection by the Thermoguard software, using the "Assign IP address" function on the "Scan local network" menu. This requires a PC with installed Thermoguard software as well as the TCP/IP protocol. PC and sensor controllers must reside in the same network segment. Internally the Thermoguard Software uses the ARP command which is described in the follow-ing chapter. Thus, local administrator privileges are required for assigning the IP address. The procedure has already been described here: Scan local network / Assign IP address Since Version 2.62 this method can also be used, if an IP address has already been assigned to the sensorcontroller, i.e. the entry is not 0.0.0.0. However, older sensorcontrollers may not support this way of chaning an existing IP address. In this case you must use one of the methods described below (use built-in website with SCx respectively the telnet client with obsolete model HC1P).


Assigning the IP Address using the ARP Command This task requires local administrator rights to a PC with installed TCP/IP protocol and which resides in the same network segment as the sensorcontroller. Make a note of the device's MAC address on the sensorcontroller (e.g. 00-C0-3D-00-12-FF). On Windows, open the window to enter commands via Start/Run, enter "cmd", then press OK. Use the "ping" command first to check accessibility of another network user. The computer on which the Thermoguard software should be installed or has already been installed is the ideal destination. In our example, that computer's IP address is 192.168.0.102:

ping 192.168.0.102 <Enter>

You will receive the reply four times after successful test:

Reply from 192.168.0.102: bytes=32 time <10ms TTL=254

(3 more identical lines)

Enter the required static entry for the sensorcontroller's IP address in the computer's ARP table, using the following command. In our example, the sensorcontroller's number is

192.168.0.111:

arp -s 192.168.0.111 00-C0-3D-03-D4-31 <Enter>

Please note the hyphenated input format of the MAC address for the ARP command. To save the IP number permanently in the sensorcontroller, "ping" the sensorcontroller again:

ping 192.168.0.111 <Enter>

You will receive the reply four times after successfully setting up the IP address:

Reply from 192.168.0.111: bytes=32 time <10ms TTL=254

(3 more identical lines)

The sensorcontroller has now imported the IP address permanently into its fixed memory sys-tem. By contrast, when using the ARP -s command without administrator rights, the following error message will be output:

The ARP entry failed: 5

The "ARP -s" command can only be used if no IP address has yet been assigned to the sen-sorcontroller, i.e. the entry is 0.0.0.0.


Changing the IP Address using a Browser For all current sensorcontroller models an existing IP address can be changed using an inter-net browser and the built-in sensorcontroller's website.

Warning: Use the internal website of a sensorcontroller only to modify the basic network settings. These are the IP address and if necessary (e.g. for a remote access scenario) the subnet mask and

the gateway address. All other settings will not be used by the software and should not be changed in any way to avoid possible malfunctions. An exception is the Configu-

ration of an AC2nP which requires performing some additional settings. Enter the sensorcontroller's IP address in an Internet Browser like Microsoft Internet Explorer or Mozilla. Tip: You may use the function Scan local network also as described here: Open a sensorcontroller's built-in internal website In the following example the IP address is 192.168.0.118:

The menu of the sensorcontroller's internal website shows up; model SC8e in this example.

Log on using an empty password.

Continue clicking on "Expertenmo-dus".


The menu Config > Device > Basic Settings > Network allows to enter the desired new IP address or - if needed - the subnet mask and gateway address (for example for a remote access via the internet). Verify that STATIC is the selected option under "BOOTP Client". Click on "Zwischenspeichern". Exit clicking on "Logout".

Menu LogOut: Save all new set-tings by clicking on "Speichern" permanently.


Configuring AC2nP

Any analog sensor (also called "transducer") of the world market can be attached to the analog

sensorcontroller models AC2aP or AC2vP if delivering an output signal of 0..20 mA res-

pectively 4..20 mA (AC2aP) or 0..10 V (AC2vP).

These sensors are available for all possible measurands, e.g. barometric pressure, wind

speed, O2, CO2, light (lux) and of course for temperature and humidity also. Often the sensors

provide a current/mA as well as a voltage/V output at the same time or you can specify the

preferred version on ordering.

In many cases laboratory equipment provide already built-in transducers or can be upgraded

optionally, e.g. for CO2-incubators. Then, usually the temperature as well as the CO2-concen-

tration are available as output signals. Because two sensors can be connected to an AC2 an

incubator featuring these two signals can be integrated into Thermoguard easily.

Thermoguard company does not offer analog sensors, but we will be happy to help you selec-ting the proper transducer sensors for your needs.

After assigning an IP address to your AC2nP, for any connected port of the AC2 you must: 1) in case of a mA port configure if it is a 0..20 mA or 4..20 mA signal and set the Output mode to "I-Input, passive", 2) setting the range and 3) configure the desired unit; to do this, open the internal website of the AC2 as described here: Changing the IP Address using a Browser.

Sample Configuration (screenshots follow on the next pages):

Port 1 of an AC2aP: Attached is a sensor with 4..20 mA output to measure oxygen concentration. Measurement range: From 0% to 30% O2. That means, under "Scale 0%" the value 0 will be entered and under "Scale 100%" the value 30. The unit: here "%O2"; must correspond to the one entered in the Thermoguard Software for the

source "AC2 Port1". Maximum length is 4 characters. There are five invalid characters: + - /

. and ,

Remember to always save your settings.

Port 2 of the same AC2aP: Attached is a Sensor with 4..20 mA output to measure the absolute pressure. Measurement range: From 750 mBar to 1250 mBar. That means, under "Scale 0%" the value 750 will be entered and under "Scale 100%" the value 1250. The unit: here it is "mBar" and must correspond to the one entered in the Thermoguard Soft-

ware for the source "AC2 Port2". Note: Values for "Scale 0%" and "Scale 100%" may be negative.


Sample configuration of Port 1 of an AC2aP:


Sample configuration of Port 2 of an AC2aP:


Important: When configuring the analog Port in the Thermoguard-Software the string entered for Unit must match the one which has been entered in the internal website of the AC2nP!

Associated sample configuration for Port 1 of an AC2 in the Thermoguard Software

Maximum length for the unit field is 4 characters. The five characters + - / . and , are not supported and will be rejected.

No "Sensor missing" recognition with AC2nP

If no transducer is attached to the AC2nP ports, AC2nP will output "0,00mA" respectively "0,00V" - which is a valid value. Hence, analog sensorcontrollers AC2nP do not support AOF of type "Sensor missing"!


Installing the Temperature Sensors For bigger installations installing the temperature and humidity sensor for refrigerators and in-cubators or a climatic test chamber should be carried out by mechanical and electrical engi-neers. However, if you are skilled enough, you can also install the system yourself. Below are some examples of an installation on a refrigerator or incubator.

Material and tools for installation: Cable ties, pin, knife

Step 1: Often, you will find that the cooling device is already equipped with ready made cable feedthroughs which you can use for your sen-sor cables. If this is not the case:

Stab or drill a small hole in the side or back wall of the device.

Refrigerators consist of plastics or HR Foam that can be stabbed easily without great ef-fort.

Where possible, perform your stabs as much from the side or from the top as possible, and take care not to damage refrigerator back walls in refrigerators with integrated cooling cover.

Back view of refrigerator with the new cable drill


Step 2: Measuring sensors response times are a few seconds. Muffling the sensor is therefore a useful idea, so that opening the door of the fridge at short notice will not cause an alarm. Sensor response time can be customized using a sand filling in a plastics box. The sand filling causes response behavior in the tem-perature sensor which corresponds to the actual temperature changes in the interior of a small glass vessel.

The sand quantity has about the same ther-mal capacity as the small glass bottle: If the sensor in the sand filling heats up, the tempe-rature of the fill assets in the glass bottle will also change. So the sensor does not indicate the refrigera-tor's air temperature which changes rapidly on opening it, but the interior temperature of the vessels stored in the fridge.

Step 3: Pull the connection cable from inside to out-side through the hole.


Pull the cable right through, and place the plastics box in the corner. That’s it!

Example of installing a sensor on a side wall. The hole for the cable of the standard sensor was additionally closed with an elastic density material.

The Thermoguard sensorcontroller can now be installed on the back of or within reach of the refrigerator. For permanent laboratory fridges, this can be conveniently carried out on the lab bank near the power supply and the network plugs.

Like any other periphery device, the fridge, too, get its IP address!


Mounting Cases For all sensorcontroller models, Thermoguard provides professional mounting cases optionally. Packaging includes high quality power supplies for DIN rail mounting. Further details upon re-quest.

Mounting case for SC2e and SC8eP. Includes 24V DC power supply.

Mounting case for SC1eP, HM1P/HF1P and AC2nP Includes 24V DC power supply.

Of course sensorcontrollers can also be mounted within existing switchboards equipped with standardized DIN rails. In the field often models SC1eP, HM1PTHF1P and AC2nP are simply fixed using strong double-faced Scotch® tape on the backside of a laboratory device. More pictures of Thermoguard installations can be found on our website: http://www.thermoguard.de/html/galerie.html

http://www.thermoguard.de/html/galerie.html


Part 4: Advanced Information

Alarm Options Visual alarm

On the Thermoguard Server's monitor, a blue-yellow popup window (falling below) or a red-yellow window (exceeding) notifies about the triggering temperature sensor, its location, triggering temperature value, limit, and date and time of limit violation. Retry:x/y addition-ally provides information about the state of the Retry counter. Example: Retry:2/1=> The maximum limit violation tolerance al-lowed without triggering an alarm was 1. However, it was currently violated twice; which is why the alarm was triggered.

A black-yellow window provides information about AOF (Sensor or sensorcontroller failure).

Values for "retry" The setting for "Retry" can be increased to a value > 0 to avoid unnecessary fake alarms due to fast and short-term temperature fluctuations. "Retry" is the number of limits allowed to fall below or exceed without triggering an alarm.

Retry = 0

No limit violation is allowed. The alarm is triggered immediately on initial limit violation. Example: "Retry" = 0. The temperature in the measuring location may fall below or exceed the limit 0 times. The alarm is triggered directly when initially violating the limit.

Retry = 2

The limit may be violated n times without triggering the alarm. The alarm will only be triggered with the n+1 violation. The counter incre-menting the number of limit violations is reset. Following the alarm, a new number of n+1 violations must occur until the alarm is triggered again. Example" = 2. The temperature in the measuring location may fall below or exceed the limit twice. The alarm will only be triggered on the third violation (i.e. the sec-ond retry).


"Serial" mode When the "Serial" checkbox is checked and retry is set to values greater than 0, the alarm will only be triggered when the limit is violated multiple times and serially in complete consecu-tive actions. Whereas these settings will not trigger an alarm when an ordinary value is meas-ured between the three (in the example) necessary limit violations. So occasional values falling below or exceeding the limit do not directly cause an alarm. The counter incrementing the limit violations (Retry) is reset to 0 in "Serial" mode after ordinary measurement or after an alarm.

Serial = checked Retry = 2

An alarm will be triggered when the temperature falls below or ex-ceeds the limit with three consecutive "polls". Example: The poll interval is 10 minutes. The limit is violated three times in suc-cession. The alarm therefore is triggered 20 minutes after the time of the first of the three limit violations.

Serial = unchecked

Whereas when the "Serial" checkbox is not checked, the alarm will be triggered already when the number of set excesses (of the "retry" actions) is reached even with an interim drop in temperature. Example: Serial = unchecked, Retry = 3. The limit is exceeded three times at diffe-rent measuring times in a single day, and then the temperature drops again. The internal counter is set to 3; no alarm is triggered yet. If the limit is exceeded or falls below on any of the days that follow, then the counter will be set to 4; the alarm will then be triggered. The limit violations are incremented regardless of the interim number of correct measurements.

Note: The Retry setting > 0 should always be combined with the Se-rial = checked setting, because alarm behavior will otherwise be hardly logical.


"Event" mode If a device permanently exceeds the set limits, follow-up alarm will be triggered time and again after the initial alarm message. To prevent numerous unnecessary follow-up alarms swamping the screen or e-mail Inbox on permanent limit violation (e.g. open refrigerator door), the "Event" mode can be enabled.

Event mode enabled

A one-time alarm is triggered on violating the limit. If the limit is di-rectly violated again next time a poll is performed, no new alarm will be triggered! The measured value must return to the "green zone" first before a new alarm is triggered on renewed limit violation.

Event mode disabled

The alarm is triggered with each measurement that violates the limit. The configured action is performed each time the limit is violated, e.g. another e-mail is sent each time.

Disabling the event status manually The Thermoguard software remembers the event status for each sensor (separated by LOW and HIGH) for configured, enabled event mode. Alarm is only triggered for disabled event status. At initial limit violation, the event status is set to "active", and will only then be automati-cally disabled once the measured value is in the allowed range. If an alarm should in any event be triggered in active event status at the next poll, the event status in the monitor window can also be manually disabled for the selected sensor or for all sensors on the "Sensor Details" tab:

The monitor window allows you to recognize the event status for each sensor: Event status: Yes or No. Right-click to revoke the status manu-ally.


Examples of alarm scenarios

Example 1:

Retry = 1 Serial = checked Event = checked

Measurement Limit Trials Alarm, Status and Action

1 exceeded 1 The limit may be violated once; no alarm will be triggered 2 normal 0 The counter is set from 1 to 0 after the second measurement. 3 exceeded 1 No limit violation in Serial; no alarm triggered 4 normal 0 The counter is set from 1 to 0 after the fourth measurement

Due to the Retry setting Retry = 1 ("The limit may be violated once") no alarm will be triggered following initial limit violation. The counter is set from 1 to 0 after the second measurement. Due to the Serial = enabled setting, no alarm will be triggered with the third measurement, be-cause the two limit violations in Measurement 1 and 3 were not in a consecutive series. The counter is also reset from 1 to 0 after the fourth measurement.

Example 2:

Retry = 1 Serial = checked Event = checked

Measurement Limit Trials Alarm, Status and Action

1 exceeded 1 still allowed 2 exceeded 2 Alarm, "event status" enabled, Retry counter is reset to 0 3 exceeded 1 still allowed 4 exceeded 2 but no alarm due to enabled event status 5 normal 0 Event status disabled, the alarm is now "released" again 6 exceeded 1 still allowed 7 exceeded 2 Thermoguard triggers the alarm only now

The alarm would be triggered again with the fourth measurement when the event mode is not configured. However, as a rule, one alarm should be enough when initially exceeding the value, because immediate measures to remedy the cause of the limit violation should be taken to avoid recurring limit violations. Tip: Use two simulation samples from the product to experiment with the above default settings and to find out which of them is the suitable one for your environment for each of your individual measuring stations. For better understanding, observe the output/messages in the monitor window or the log file!


Alarm On Fail "Alarm On Fail" = AOF will be triggered when the Thermoguard software has been unable to correctly poll a sensor or sensorcontroller configured as active within the timeout interval. So AOF is triggered for each electric or mechanic damage to the sensor or sensorcontroller. For SC2e or SC8eP sensorcontrollers, the loss of a single sensor is enough. The employee in charge of the devices should immediately undertake to examine the cause on "Alarm on Fail", and to carry out the appropriate correction measures to remedy the cause for

sensor failure. How is "Alarm On Fail" enabled? "Alarm On Fail" can be individually set up and enabled on the "Sensor configuration" page for each sensor. Note that AOF is enabled by default, but not the "Send mail" option!

Alarm On Fail - Enable Alarm On Fail (AOF) mode: Settings for

alarm on failure or disruption of a sensorcontroller or sensor; including help text and test button

What does the "Alarm On Fail" status mean? If a sensorcontroller or sensor fails at enabled AOF, an alarm will be triggered and sent as an e-mail or SMS message. The program remembers the alarm state to avoid triggering or sen-ding a variety of other unnecessary alarms for the same defective sensorcontroller or sensor until the sensorcontroller or sensor is intact again. This state is called "AOF status".

The active status will be revoked when the sensorcontroller and its sensors are intact and the measured values can be read correctly again. When the sensorcontroller fails again, a new Alarm On Fail will be triggered and sent. All alarms are displayed in the monitor window and entered in the current log file as [Sensor-name|Location|ALARM ON FAIL|CAUSE:].


Alarm On Fail active

- The total number of AOF events (in the picture, the number is

1) and the "Active" status (in the picture, "Active: Yes") is dis-played for the selected sensor in the monitor window on the "Sensor details" tab in the "Alarm On Fail" context

AOF Reset

- The "AOF Reset" button is used to manually revoke the "Ac-tive" status for one or all sensorcontrollers. A new Alarm On Fail event will be triggered next time the same or another sen-sorcontroller or sensor fails.

- The current state of the sensorcontroller or sensor can be tested after the correction measures through manually re-voking and repolling using "Poll sensor"

- The "Revoke AOF status for ALL sensors" option that is shown in blue is always available, even if the currently selected sen-sor is not in "Active" status

- The counter for the number of AOFs can be reset by right-clicking "Number"

- Right-clicking "Active" corresponds to clicking "AOF Reset"

Revoke AOF status for sensor nnn?

- The employee in charge of the devices should fix the cause of

the alarm on Alarm On Fail. Following successful fixing of the disruption, the sensor should be tested through polling, and the AOF status should be disabled, so that a new Alarm On Fail event will be triggered again when the sensor fails again. The active AOF status and a manually triggered poll (e.g. for the above testing purpose) using the "Poll sensor" button, dis-plays the "Revoke AOF status for sensor #nnn?" message. The Alarm On Fail status will revoke the status for this sensor when confirming this message.

Revoke AOF status for ALL sensors?

- The active AOF status and a manually triggered poll of all sen-sors using the "Poll all" button displays the "At least one sen-sor is in AOF status. Revoke AOF status for ALL sen-sors?" message. The AOF status for all sensors will be re-voked when confirming this message.


AOF status and event mode: A comparison The function of "AOF active: Yes" can be compared to an active event status. In both cases, no new alarm will be triggered following initial alarm despite other limit violations or defects. Unlike the event mode, which can be optionally enabled or disabled via the "Event" switch, the "AOF active" function is a default setting (though it can be disabled, see below). For automatic, scheduled polls, the sensor will be in "AOF active: Yes" status after "Alarm On Fail" until this is revoked again when the program automatically reads a regular temperature or humidity value (!) Disable AOF status mechanism The "snap-in" function of the AOF status can also basically be disabled for all (!) sensors. This can be done via the "Fire AOF repeatedly" option on the "Miscellaneous" tab:

When this switch is checked (as shown in the picture), an AOF alarm will be triggered for each AOF. Keep in mind that this will send a variety of alarm e-mails in particular for a larger number of sensors, brief poll interval and a longer disruption.

The corresponding log message will be output when this option is checked:

Attention: Already set AOF statuses will not be automatically reset through setting the "Fire AOF repeatedly" switch!

Fire AOF during "non-alarm hours" When this option is checked (default setting) an AOF will be fired during any possibly confi-gured non-alarm hours:


Forwarding E-Mail as SMS to Cell Phones The Thermoguard e-mail alarm function allows sending alarm e-mails as brief SMS messages to cell phones. Most network carriers allow subscribers to receive e-mails as SMS messages. The following cell phone network carriers allowed receiving e-mails as SMS messages:

Germany T-Mobile, Vodafone D2 Switzerland Sunrise

Note: Provider O2 no longer offers the service. Receiving SMS e-mails involves charges for the recipient of the message (i.e. the cell phone owner). The charges depend on the respective network carrier; they currently amount to about 20 Cent (Germany) or Rappen (Switzerland) per message. To receive SMS messages the ap-propriate function must first be activated with all network carriers. Each network carrier will handle this differently. The cell phone's e-mail address consists of the following components, according to the respective carrier: Provider E-mail address for receiving SMS: Example

T-Mobile [T-Mobile phone number]@t-mobile-sms.de [email protected]

Vodafone D2 [D2 phone number]@vodafone-sms.de [email protected]

Sunrise [Sunrise phone number]@gsm.sunrise.ch [email protected]

The phone numbers are usually enabled sending a specific SMS message to a certain phone number of the provider. Enable Disable Note T-Mobile Send an SMS message containing the OPEN text to phone number 8000

Send an SMS message containing the CLOSE text to phone number 8000

T-Mobile cell phone owners could (should!) specify one or more passwords that will then have to ap-pear in the e-mail subject line to enable the deliv-ery of the message. Defining the passwords: Send SMS message containing PW Password1 Pass-word2 ... Password5 to phone number 8000 (Delete: DELPW)

Vodafone D2 Send at least one e-mail message from your cell phone or send a message containing the OPEN text to phone number 3400

Send the CLOSE text to phone number 3400

Receiving e-mail on the D2 net will only work if the D2 brief message switchboard (+49 172 2270333) is set on your cell phone!

Sunrise Send an SMS message containing the EMAIL ON text to phone num-ber 999

Send an SMS message containing the EMAIL OFF text to phone number 999

For more information, see http://www.sunrise.ch, using the search term "hand e-mail"

http://www.sunrise.ch/


For all network carriers, the SMS message is composed of the sender's address and the subject line. When exceeding the total length of 160 characters resulting from this, other characters that the mail item contains will be truncated. Thus the Thermoguard software generally shortens the alarm mail text to avoid truncation. To meet the terms of the T-Mobile (in case of specifying a password) carrier, a self-defining subject line is supported by the Thermoguard software as follows: A separate e-mail subject

line can be entered for each sensor (e.g. as *BODY#).

Entering multiple recipients in the e-mail fields (separated by semicolons) is also allowed. In that case be aware of the fact that all specified recipients – including "non-cell phone addresses" – will receive the self-defined subject line. The following graphics show three ex-amples of valid definitions for Thermoguard SMS Alarm Mail recipients:

The e-mail message is not just sent to the administrator's default e-mail address but also to the administrator's Vo-dafone D2 cell phone.

The e-mail message is sent to the administrator's default e-mail address; in addition, it is sent to the administrator's T-Mobile cell phone. "MyPassword" must be entered in the subject line as a specific subject to make this work in this example, be-cause the administrator has set up the T-Mobile SMS service for their cell phone. Be aware for this configuration that all configured recipients receive this subject!

Note that as an alternative (or in addition) to sending "SMS as e-mail" the usage of a GSM modem is supported. This is described in a separate documentation.

By the way: If sending SMS via a GSM modem the sender will be charged, not the recipient.


The pictures below illustrate Thermoguard SMS on smartphones (7bit, ° sign missing):

Default alarm on exceeding the high limit

Alarm On Fail - notification on malfunction

"Heartbeat" Information

Notes on occasional delays in transmission of SMS brief messages can be found on the Inter-net. Although we were unable to verify this in our tests (with all providers mentioned above),

Thermoguard disclaims all liability for possible technical disruptions by network carriers.

We strongly recommend that you check the function of all alarm functions regularly. A test mail, for example, can be sent by clicking the "Send test mail" button (to be found under Con-

figuration/"Mail" tab).


Supporting "Passport Images" for each Sensor "Sensor passport images" can be integrated into the program for each sensor. In large installa-tions you can quickly see at a glance which measuring station is present in the current selec-tion in the monitor window. The images are displayed in the Thermoguard monitor on both the Activity and the Sensor details tab.

The Thermoguard program searches the

\MM\img subdirectory of the installation di-

rectory (by default, this is %ALLUSERSPRO-

FILE%\Thermoguard Data) for a graphic

file. The name of the file must match the name of the sensor and have one of the fol-

lowing extensions: *.jpg, *.gif or *.bmp.

If the appropriate file is found, the image will be displayed with a maximum of 128x96 pix-els.

If none of the three allowed file types is found, no image will be displayed; no error message will appear either.

Although larger graphics are loaded, only the top left corner will be displayed. Therefore the image size should not exceed 128x96 pixels. For "fatal" errors, , e.g. when the graphic format is invalid, a corresponding log message will appear during the load process.

The ..\MM\img directory contains some

samples that can be used as a template. Filenames must always be manually speci-fied. This must be particularly taken into con-sideration when renaming a sensor label. When, for instance, renaming a sensor from

"Sensor01" to "Sensor01Cellar", the sen-

sor01.jpg graphic file must then also be

renamed to Sensor01Cellar.jpg to en-

sure the same image is displayed.

The monitor window's width can still be reduced, so the area of the "passport images" is not displayed if you do not wish to display this area. If you purchased your Thermoguard system via Thermoguard Germany, you will find a "pass-

port image" of your company logo (if applicable) in the directory \_License of your installation

CD.


Simulation Mode Thermoguard not only provides the option to read measured values from an actual, existing sensorcontroller; it can read simulated values from a text file instead. This enables reproducing user-defined temperature and humidity runs. This is not only conducive to a "controller-less demo mode" of the Thermoguard software. Simulation series also allow checking the effects of various alarm settings in a reproducible manner. Not only regular values, but also AOF can be simulated.

The simulation files with the *.sim file extension must reside in the path set under "Thermoguard Configuration/Data file settings" tab / Simulation file (*.sim) and Text file (*.txt) set-

ting; by default, this is %ALLUSERSPROFILE%\Ther-

moguard Data\sim.

Simulation mode can be enabled for each sensor entered in the Sensor configuration via the Basic Settings tab/Source setting. Simulated temperature or humidity values can be read. The settings options under "IP address" will be hidden when enabling one of these settings. This clarifies that the data is not read by actual, existing controller hardware but from a file.

A simulation file with the following name must reside in the above path for successful sensor simulation mode:

TG_SensorName.sim

This name is not case sensitive; you can also use spaces in the name. If the file is not found, the corresponding error message will appear in the log file and monitor window.

The Source "Simulation file temperature" was enabled for the "MySensor" sensor; a file

named TG_MySensor.sim

was not provided, though.


Simulation file structure and supported values as shown in an example:

[TGSimulation.Values] must always be at the beginning of the file

1 =6.2 regular value without physical unit! 2 =4.4

3 = 4.3 OK, extra spaces are allowed

4 =4,2 commas as a decimal separator are also allowed 5 =4.1

6 =4.1

7 =AOF Alarm On Fail

8 =aof Alarm On Fail, not case-sensitive

09 =4.3 "SimErr" error, please do not add any leading zeros in the first column!

10 =---- "Sensor Missing" Alarm On Fail 11 =3.9

12 =err "SimErr" error

13 =anything "SimErr" error

14 =3.8°C "SimErr" error; only numbers in the 0..9 range or "," or "." may occur! 15 =3.8

16 =restart jump to the beginning; the next value will be the first, (in this example=6.2)

17 =13.8 other values are ignored. Inserting "restart" at

18 =12.7 any position allows shortening the "value cycle" temporarily when required

etc. without having to delete the values (in this example, all lines from 17 =...).

Important note: Numbering in the first column must be serial and complete! Running simulation mode:

Usually, for reasons of saving time, a *.sim file will be run using the manual poll (Poll all or

Poll sensor). To do this, briefly click the corresponding button, and read the values by pressing Enter several times. When keeping the Enter key depressed, the values will be run through very fast (unless an alarm window or anything like it disrupts smooth operation). This allows performing a simulation series in time lapse. Since the progress on the Simul. #: counter can be checked on the monitor window’s Sensor details tab, it is recommended that you use the Poll sensor button on this tab to "step through"

the *.sim file (see below).

Checking simulation progress and resetting the simulation cycle

The values defined in the *.sim file are run through until the "restart" line without user inter-

ference; then the process will start again "at the beginning", reading the first value.

If you want to enforce re-reading the first value of the *.sim file at the next poll, the "simula-

tion step counter" on the Sensor detail tab can be reset to 0 for either the sensor currently se-lected on the monitor or for all sensors; see here also: Sensor details. After restarting Thermoguard, the simulation step counter will be reset to 0 (as any other Sen-sor Details counter).


The Source "Text file" The data source "Text file" functions basically like the simulation mode described in the pre-vious chapter.

As opposed to sources "Simulation file .." the field "Unit" is

enabled for source "Text file".

The source "Text file" can be selected for each sensor entered in the Sensor Configuration using the setting Source on the Basic settings tab.

The measured value is read from a *.txt file which

must reside in the same path as the *.sim files (see

here also: Simulation Mode).

The text filename scheme corresponds to a *.sim file's name scheme, but with the *.txt

extension: TG_SensorName.txt

The Thermoguard software expects a single line with one value only in the text file assuming that this file will be updated on a regular basis by a 3rd party application. This application is responsible for the frequent update of the file! Thermoguard does not recognize if the text file content remains unchanged over a longer period. Unlike simulation files a range of values from -9999.9 to +9999.9 is supported as with the analog sensorcontroller AC2. Just like for the AC2 an unit string can be entered in the Unit field

(there are five invalid characters here: + - / . ,).

Please note the following additional notes:

To use the Text file source a regular customer license is needed, the demo license ("ACME") is not supported

An Alarm On Fail (AOF) will be fired in the following cases: o The text file can not be found o The text file contains a string which can not be converted into a numeric value o The converted value is out of range (i.e. not within -9999.9 .. +9999.9) o Other "unexpected" errors when reading the text file


Tips and Tricks Close all alarm windows quickly

Since closing a variety of open alarm windows individually from the screen is a tedious task, a red-yellow button that allows closing all alarm windows at the same time appears in the monitor window:

Alternatively, the Thermoguard task bar icon's context menu includes the corresponding additional menu item; this can be executed analogous to closing all alarm windows.

Directly display the Thermoguard monitor window

Double-clicking the Thermoguard task bar icon using the left mouse button directly opens the Thermoguard monitor window or it gets the focus in case it's already open.

Quick browsing in the sensor configuration

As shown on the left, the key combinations of the Shift button and a Cursor key or Home/End allow you to browse quickly through the sensor list without having to click the corresponding Ther-moguard arrow button.

For this, no input field (Name, location, IP ad-dress or host name) may be enabled, i.e. the cursor must not blink.


The Sensor Port Switch Function

The Sensor Port Switch Function is contained for backward compatibility only. The new Alarm Relay Channel provides more possibilities for monitoring switch conditions and

thus should be preferred for new installations. It is described in the separate document TG Alarm Relay Channel-en.pdf. The pdf is located in the root directory of your Thermoguard

Installation CD, but copied by setup into the installation target folder as well (by default %ProgramFiles(x86)%\Thermoguard\doc).

- The "Switch" function can be enabled for the SCn ports "SC1", "SC2 or SC8 Port1..2", "SC8 Port 3..8" and for the "Simulation file Temperature".

- The AOF mechanism of Thermoguard is "misused" for the switch function for monitoring the state of a simple switch (e.g. door contact or water level sen-sor) using the Open function as a "pseudo sensor".

When enabling the "Switch" checkbox, the settings of the "Alarm" and "Calibration" tabs will not be available, because they are irrelevant to the use of a sensor as switch.

Installation sample using an SC8eP:

If the switch is closed, the sensorcontroller will be given "the illusion" of a default PT100 sensor by the 100Ω resistor. When the switch disrupts a line to the SC8eP, this will be equal to the "Sensor missing" state for the Thermoguard software, enabling it to respond with an AOF warning as usual. The switch function should not be used for crucial time-dependent monitoring tasks.


- Replace the "Sensor missing" message with a more suitable text for the respective switch.

- The limits are grayed out on the monitor; the only "measurements" taking place are whether the switch is closed ("Closed") or, in case of an error, ("Open").

- "Closed" or "Open" is also written in the *.tg

file.

Resultant alarm e-mail message


Example of water level alarm with water detection unit:

(Note: Unfortunately the shown device is no longer available)

The "Sensor missing" message would be altered accordingly, e.g. to "Water detected!"


Export and Import of sensors as *.scxtpl

Ex- and Import functions for sensors may be useful to manage a larger number of sensor entries. The Import can also be used to pick a "base" sensor type entry from a template file. The context menu of the sensor list provides menu entries for exporting the currently selected sensors and the Import. To make the menu appear (by right clicking the sensor list) the default sort order must be set and the list must contain at least one sensor. The following Export example illustrates the export of all sensors in rooms 215 and 221 of a lab:

The filename can be freely chosen. Standard extension is *.scxtpl. The file format is identical to the *.scx-Format. The created export file (Room215_221.scxtpl in the example) may be imported into another Thermoguard Instal-lation on a different server using the Import function.

After clicking Import in the context menu a source file selection dialog appears. Afterwards a sensor list similar to the main sensor configuration list shows up. It can be sorted by clicking on a column header as well. Only the selected sensors will be imported. They are always appended to the end of the main sensor list. In the following Import example two "base category sensors" are imported from the default template file which is

included in the standard installation (TGuard.scxtpl, located in %ALLUSERSPROFILE%\Thermoguard Data). After

the import the two sensors can be shifted to the desired list position and configured in detail:


The sensor list Search function

The Search function for the Sensor configuration list is called by either clicking on the "Search" button or by pressing + on the keyboard. The "Search" window is not "modal", i.e. all functions of the main sensor list are available while the "Search" window is open. Within the "Search" window enter a search term and repeatedly click the "Search" button or press on the keyboard while the search term text field has the focus. Hits will be highlighted in a sensor's property field directly in blue. If a hit is found in the Sensor description, the "#" column of this sensor is highlighted in red - as in the following example:

Search is always "partial" (a whole word search is not supported) and case insensitive. Searching "kühl" finds "tiefkühltruhe" as well as "kühlschrank" or "KühlSchrank".

If no more hits are found you must click the "Reset" button to start a new search using a diffe-rent search term.

After clicking "Reset" or the Search window's OK button (which closes the Search window) or if the "Thermoguard Configuration" window is closed (which also closes the Search window), the highlighting in the sensor list is revoked. A sensor's highlighting is also revoked if its list posi-tion is shifted using the keys.


Part 5: Appendices

The TG Decrypt Utility

TG Decrypt

The TG Decrypt utility allows decrypting manipulation proof encrypted data (*.tg) and log

files (*.log).

The extension of the decrypted files is *.dec.txt.

You may use the command switch TGDecrypt.exe /b to recall the path settings last used

(saved to file %ALLUSERSPROFILE%\TGDecrypt.ini).

Note: The use of the TG Decrypt utility should be restricted to a legal GMP environment by allocating file permissions to the administrator or the responsible Thermoguard operator.


Ports used / Firewall Thermoguard uses the following ports to communicate with the sensorcontrollers: Protocol Port

TCP 80 TCP 8000 UDP 8513

Port 80 is used to poll the SCn sensorcontroller. Port 8000 is used to poll the HC1P sensorcontroller (obsolete model). Port 8513 is used to poll the license of the SCn sensorcon-troller and for the "Scan local network" function.

If the respective option has been select during installation, an inbound firewall rule is created

for the program TGuard.exe for all (!) ports:


Data Format of the TGuard.scx File

Field Position, dec. Length/bytes Reserved Range Remarks

Label 0000..0029 30

Location 0030..0059 30

Description 0060..0571 512

IPAdr 0572..0586 15

Source 0587 1 0..21 0=SC1, 1=SC2/8Port1, 2=SC2/8Port2, etc. .... 19=HM1/HF1 Temp., 20=HM1/HF1 Humidity, 21=HM1 Atmospheric pressure

MaintenancePlug 0588 1 0,1 Maintenance Plug Support yes/no

Alarm Relay 1 0589 1 0,1 Alarm Relay Channel Relay #1

Alarm Relay 2 0590 1 0,1 Alarm Relay Channel Relay #2

timeout 0591 1 1..99 (seconds)

Reserved 01 0592..0594 3

ParticipateInPoll 0595 1 ("Enabled", included in poll)

DynPort 0596 1 80..90

TgFileOut 0597 1

IsSwitch 0598 1

CalEnable 0599 1

CalMode 0600 1 0=1-point calibration, 1=2-point calibration

MailToName 0601..0800 200

MailToMail 0801..1000 200

MailCcName 1001..1200 200

MailCcMail 1201..1400 200

CalT1Meas 1401..1404 4

LoLimitDeg 1405..1408 4

LoLimitTrials 1409 1

Reserved 02 1410..1412 3

LoLimitSerMode 1413 1

AlarmChanNCorNO 1414 1 0,1 0=NC(normally closed), 1=NO(normally open)

LoLimitEvtMode 1415 1

Reserved 034 1416 1

LoLimitSound 1417 1

Reserved 04 1418 1

LoLimitSoundFile 1419..1678 260

LoLimitMail 1679 1

LoLimitEvtMail 1680 1 0,1 Send mail if Lo event mode released

LoLimitPopUp 1681 1

Reserved 05 1682 1

HiLimitDeg 1683..1686 4

HiLimitTrials 1687 1

Reserved 06 1688..1690 3

HiLimitSerMode 1691 1

Reserved 07 1692 1

HiLimitEvtMode 1693 1

Reserved 08 1694 1

HiLimitSound 1695 1

=>


(Cont. Data Format of the file TGuard.scx)

Field Position, dec. Length/bytes Reserved Range Remarks

Reserved 09 1696 1

HiLimitSoundFile 1697..1956 260

HiLimitMail 1957 1

HiLimitEvtMail 1958 1 0,1 Send mail if Hi event mode released

HiLimitPopUp 1959 1

Reserved 10 1960 1

UseSngSubj 1961 1

Reserved 11 1962 1

SngSubj 1963..2012 50

UseSngBody 2013 1

Reserved 12 2014 1

SngBody 2015..2174 160

UseAOF 2175 1 0,1

Reserved 13 2176 1

AOFPopUp 2177 1 0,1

CAMexecNetIO 2178 1 0,1 Use "NetIO" Internet Power Controller

AOFMail 2179 1 0,1

CAMNetIOno 2180 1 1..16 "NetIO" Gerätenr. 1..16 (IP in TGuard.ini def.)

AOFSound 2181 1

CAMNetIOMode 2182 1 0..2 like CAMRelIFMode (0..2 only)

AOFSoundFile 2183..2442 260

UseCAM 2443 1 0,1

CAMRelIFRel 2444 1 1..8

CAMFile 2445..2704 260

CAMPara 2705..2754 50

CAMxWithParas 2755 1 0,1

CAMexecFile 2756 1 0,1

CAMexec 2757 1 0..6 0=lo+hi+aof, 1=lo+aof, 2=hi+aof, 3=lo+hi, 4=lo, 5=hi, 6=aof

CAMexecRelIF 2758 1 0,1

AOFUseSensMissText 2759 1 0,1

CAMRelIFMode 2760 1 0..2 0=Impulse, 1=ON, NeverOFF, 2=ON on Violation OFF on "Good again", 3=OFF on violation ON on "Good again"

AOFSensMissText 2761..2800 40

HostNotIP 2801 1 0,1

CAMNetIOout 2802 1 1..15 "NetIO" 230V~ Outlets: [combination of 1..4]

HostName 2803..2866 64

CalT1Ref 2867..2870 4

CalT2Meas 2871..2874 4

CalT2Ref 2875..2878 4

CalSampleMeas 2879..2882 4

arrNonAlarm 2883..2924 42 2x3x7 byte bit mask for a sensor's "non alarm hours"

ACUnit 2925..2928 4

CAMRelIFCOM 2929 1 1..16

Reserved 14 2930..2995 66

scxVersion 2996..2999 4 currently "2.90" (last format change)

Total: 2915 85

Grand Total -- 3000 --

The table shows the use of the data record for one single sensor.

A TGuard.scx including, for example, 3 sensors, contains 3 x 3000 = 9000 bytes.


Files installed by Setup

Filename Description File size Version Target directory

System files (will only be installed if not present on target system or if they are older)

asycfilt.dll System file 147.728 2.40.4275.1 system

ChilkatMail.dll Mail component for TLS 2.199.552 7.9.9.0 system

comcat.dll System file 22.288 4.71.1460.1 system

comdlg32.ocx MS Common Dialog Control 152.848 6.1.97.82 system

mcslsudll.dll MCS Language Support Unit 662.528 2.0.21.2 system

mscomct2.ocx MS Windows Common Controls-2 662.288 6.1.97.82 system

mscomctl.ocx MS Windows Common Controls 1.081.616 6.1.97.82 system

mscomm32.ocx MS Comm Control 105.472 6.0.81.69 system

msflxgrd.ocx MS FlexGrid Control 260.880 6.1.97.82 system

Msvbvm60.dll System file 1.386.496 6.0.97.82 system

mswinsck.ocx MS Winsock Control 124.688 6.1.97.82 system

oleaut32.dll System file 598.288 2.40.4275.1 system

olepro32.dll System file 164.112 5.0.4275.1 system

stdole2.tlb System file 17.920 2.40.4275.1 system

tabctl32.ocx MS Tabbed Dialog Control 224.016 6.1.97.82 system

Thermoguard (TG) Main program files

TGuard.exe TG main program (variable) 2.94.0.0 app

TGSvcLd.exe TG services loading program 14.472 - app

CAMDemo.exe TG CAM example 22.664 2.94.0.0 app

SoftwareLicenseAgreement.rtf English license agreement 5.703 - app\doc

SoftwareLizenzVereinbarung.rtf German license agreement 6.810 - app\doc

TGuard.ini.bak TG configuration file, backup (variable) - app\doc

VersionHistory.rtf TG version history (English) (variable) - app\doc

TG Systemhandbuch-de.pdf TG system manual (German) (variable) - app\doc

TG Systemmanual-en.pdf TG system manual (English) (variable) - app\doc

TG GSM Modem-de.pdf Description GSM Modem (German) (variable) - app\doc

TG GSM Modem-en.pdf Description GSM Modem (English) (variable) - app\doc

TG Relais Interface-de.pdf Descr. Relais Interface (German) (variable) - app\doc

TG Relay Interface-en.pdf Descr. Relay Interface (English) (variable) - app\doc

TG Alarmrelais-Kanal-de.pdf Descr. Alarm Rel. Channel (Germ.) (variable) - app\doc

TG Alarm Relay Channel-en.pdf Descr. Alarm Relay Channel (Engl.) (variable) - app\doc

Thermoguard (TG) configuration files

TGuard.ini TG configuration file (variable) - AUP

TGuard.scx TG sensor configuration 6.000 - AUP

TGuard.scxtpl TG sensor template sample 24.000 - AUP

TGuard.lic TG license file 123.123 - AUP

Thermoguard multimedia files

aof.wav Sound file 50.388 - AUP\MM

clock01.wav Sound file 38.662 - AUP\MM

clock02.wav Sound file 53.872 - AUP\MM

cuckoo01.wav Sound file 9.260 - AUP\MM



honk01.wav Sound file 4.236 - AUP\MM



huho.wav Sound file 16.120 - AUP\MM


notify01.wav Sound file 10.600 - AUP\MM






steam01.wav Sound file 13.868 - AUP\MM

synth01.wav Sound file 9.452 - AUP\MM

synth02.wav Sound file 10.158 - AUP\MM

tinkle.wav Sound file 32.492 - AUP\MM

tower01.wav Sound file 9.496 - AUP\MM

trekdoor.wav Sound file 21.686 - AUP\MM

trekwhst.wav Sound file 30.314 - AUP\MM

violhi49.wav Sound file 33.970 - AUP\MM

viollo49.wav Sound file 37.276 - AUP\MM

whistle.wav Sound file 18.020 - AUP\MM

ClimateChamber.jpg Image file 9.845 - AUP\MM\img

FridgeAtLab.jpg Image file 9.960 - AUP\MM\img

Incubator.jpg Image file 9.656 - AUP\MM\img

LabFridge.jpg Image file 8.158 - AUP\MM\img

Liebherr05Min.gif Image file 7.086 - AUP\MM\img

Liebherr30Min.gif Image file 7.086 - AUP\MM\img

SensCableMount.gif Image file 3.138 - AUP\MM\img

SensColdStorage01.gif Image file 4.016 - AUP\MM\img

SensColdStorage02.jpg Image file 7.228 - AUP\MM\img

SensHumid.jpg Image file 10.696 - AUP\MM\img

SensHumidEP.gif Image file 2.430 - AUP\MM\img

SensHumidES.gif Image file 2.498 - AUP\MM\img

SensNTC.gif Image file 2.838 - AUP\MM\img

SensRoom.gif Image file 5.742 - AUP\MM\img

SymbolDeepFreezer.gif Image file 6.148 - AUP\MM\img

SymbolFridge01.gif Image file 7.086 - AUP\MM\img

SymbolFridge02.gif Image file 5.982 - AUP\MM\img

TemplateMaxSize.gif Image file 367 - AUP\MM\img

TG Simulation files

TG_Liebherr05Min.sim Text file 4.684 - AUP\sim

TG_Liebherr30Min.sim Text file 808 - AUP\sim

TG Utilities

TGRelIF.exe TG Relay Interface Utility (variable) 2.94.0.0 app

TGDecrypt.exe TG Decryption Utility (variable) 2.94.0.0 app

TG Report

TGReport.exe TG Report (TGR) (variable) 2.94.0.0 app\TGReport

TGReportVisDesigner.exe TGR Visual Designer (variable) 2.94.0.0 app\TGReport

LPng.dll TGR help file for png format 187.392 - system

EnDeCrypt.dll TGR help file 157.832 1.0.0.0 app\TGReport

TG Report-de.pdf TG Report Manual (German) (variable) - app\TGReport\doc

TG Report-en.pdf TG Report Manual (English) (variable) - app\TGReport\doc

Supporting files

TG-Uninstall.ico Icon for Start/Progr./Uninstall TG 22.486 - app\Uninstall

uninsnnn.dat System file for uninstall - - app\Uninstall

uninsnnn.exe System file for uninstall - - app\Uninstall

system = %SystemRoot%\system32 (by default C:\Windows\system32) (not changeable)

app = by default %ProgramFiles%\Thermoguard (C:\Program Files\Thermoguard) (Target directory, can be changed on

installation by user) AUP = %ALLUSERSPROFILE%\Thermoguard Data (XP/2003: C:\Documents and Settings\All Users\Thermoguard Data,

Vista/Server 2008: C:\ProgramData\Thermoguard Data) (not changeable)


Information on GMP, cGMP, CFR 21 Part 11, FDA The Thermoguard System was expressly invented for usage within a GMP (Good Manufactu-ring Practice) regulated environment and has been acknowledged during several GMP inspec-tions. These days Thermoguard is run by a lot of pharmaceutical companies meeting GMP and U.S. cGMP (current GMP) requirements. The U.S. cGMP is not harmonized with the European GMP respectively PIC/S (The Pharma-ceutical Inspection Convention and Pharmaceutical Inspection Co-operation Scheme) regula-tions and differs from the European GMP regarding various demands. However, GMP or cGMP compliance can not be met solely by purchasing (for instance) Ther-moguard: Being compliant rather demands the introduction and maintenance of a complete general QM system within the standard company IT concept. Such a QM system should cover all processes like purchasing, manufacturing, storing and selling of pharmaceutical products as well as the involved permanent documentation. Thermo-guard products are essential, but not sufficient components for GMP or cGMP compliance. Two examples from the world of IT: Data security: One of the essential requirements of European and U.S. GMP is Data security: Protection against manipulation and unauthorized access. But this not only applies to mea-sured temperature data of the Thermoguard monitoring system, but all other data from manu-facturing, controlling and storing the products: Analytical reception control and other measured values, data of stability studies, in-process controls, specs, manufacturing and approval proto-cols and so on. All these data from production, lab and warehouse must be protected. To meet this require-ment the complete network must be qualified, not only one single application like Thermoguard which creates some data. Securing the whole network and servers against unauthorized physical or logical access must be part of daily IT business. Signature and archiving: According to the US CFR 21 Part 11 requirements for electronic sig-nature and archiving concern all electronic raw data on which continuative decisions are based. If not the whole company works paper based, a company wide electronic signature and archiving application must be implemented. If Thermoguard would implement its own electronic signature this would rather be a typical siloed solution being counterproductive to establishing a company wide application. Advanced products like Nugenesis® from Waters or Cerity ECM from Agilent meet the require-ments. They allow storing and signing of every printed and saved file on any computer within the company's network according to GMP rules - including Thermoguard data files. If running within a GMP or cGMP compliant environment Thermoguard fulfills all GMP or cGMP requirements. If the environment is not GMP or cGMP compliant your Thermoguard won't either be compliant.


Even if running within a cGMP compliant environment, data loggers will not meet the require-ments of FDA inspectors. Information about temperature violations and other critical conditions is obtained far too late. If only data loggers are used for stability studies of pharmaceuticals FDA inspectors will demand additionally that at least once daily a dedicated person must con-trol and record data on site - hence data loggers are without any practical value. Contrary to traditional loggers Thermoguard directly sounds the alarm. The responsible per-sons are sent audio, e-mail or alarm SMS without any further delay - even remotely or during Christmas break. Introducing a QM system is a time consuming project. If you plan building such a QM system we strongly recommend a consultant with expert knowledge and experience in the GMP / cGMP field. Qualified consultant companies like CMC Pharma, Klinkner and Partner, PTS or Concept Hei-delberg provide further information. Dr. Ludwig Huber's homepage is worth a visit, too: www.labcompliance.com.

http://www.labcompliance.com/