Instillation Guide 1
Instillation Guide 1
ThermoServer / Client 5
Administrator Guide
System Overview and Troubleshooting
Module Installation Guide
Network Devices
www.oceasoft.com
Administrator Guide for Cobalt Wireless Monitoring System
Notices
Safety instructions
IMPORTANT NOTE: Do not use this product for protection or as part of an automated
emergency system or for any other application that involves protecting people and/or
property. Customers and users of Oceasoft products are responsible for making sure
that the product is fit for the intended usage. Do not open the product casing and do not
disassemble or modify internal components in any manner. Oceasoft products do not
contain any internal components that require user intervention or repair. If the device
shows signs of improper operation, disconnect it immediately from its power source and
contact Oceasoft technical services.
Battery warning
Some Cobalt products contain a lithium battery. Make sure you observe
polarity (+/-) when inserting batteries into Cobalt devices. Reversing polarity
by inserting the batteries incorrectly can cause the product to heat up and
may lead to a battery liquid leak. Use only batteries recommended by
Oceasoft. Do not change battery types, such as alkaline and magnesium,
or use batteries of different brands or even different types of batteries of the same brand.
Incorrect batteries may cause the device to heat up, and may result in a fire or battery
liquid leakage. Never dispose of batteries in a fire. Do not charge regular batteries that
are not specifically rechargeable. When batteries are low, or if the battery-operated
device in question remains unused for a long period of time, remove the batteries from
the device to avoid any risk of battery liquid leakage. Never leave batteries within reach
of children. In case of a battery leak, avoid all contact with the liquid present on the
batteries. Rinse with clear water immediately if the battery liquid comes into contact with
the eyes, mouth or skin. Contact a doctor or emergency service immediately. Battery
liquid is corrosive and can damage vision, or cause blindness or chemical burns.
• Do not disconnect the IP receiver from its connection to your intranet system.
Disconnection will prevent the transmission of data (including alarms) from the
modules.
• Loss of power to the receiver will also prevent the transmission of data
(including alarms) from the modules. Ensure the receiver is plugged into an
Uninterruptable Power Supply (UPS) at all times.
2 | Administrator Guide
Administrator Guide for Cobalt Wireless Monitoring System
USB receivers
All Cobalt USB products and drivers are tested thoroughly. However, it is not possible
to test and qualify all computers and configurations. Our experience has shown there
are some variations in USB implementations by computer manufacturers. It is therefore
important for users to avoid unnecessary risk by testing the products and validating
processes internally to ensure stability and reliability of USB communications in their
environment.
User precautions
Here is a non-exhaustive list of known issues that may affect the Cobalt USB receiver.
Please consider these and other risks when qualifying your system.
• USB plugs cannot be physically secured to USB ports. Ensure that your USB
cable is fastened and routed so it will not be accidentally unplugged.
• If your USB receiver is physically disconnected from the USB port on your
computer after configuration, it is imperative to plug it back into the same port.
Otherwise, the system may not recognize the receiver and communication with
the receiver could be lost.
• Do not unplug the USB receiver, even temporarily, to attach another peripheral
USB device such as a camera, printer, MP3 player, etc. The new device may
update the USB drivers on your computer and cause the system to not
recognize the receiver when it is returned to the previously configured port.
FCC statement
This paragraph pertains to 915 MHz Cobalt™ wireless modules. This device
complies with Industry Canada license-exempt RSS standard(s). Operation is subject to
the following two conditions: (1) this device may not cause interference, and (2) this
device must accept any interference, including interference that may cause undesired
operation of the device.
Administrator Guide | 3
Administrator Guide for Cobalt Wireless Monitoring System
Caution: Any changes or modifications not expressly approved by Oceasoft could void
the user's authority to operate the equipment.
WEEE compliance
Oceasoft products comply with the essential requirements and other relevant provisions
of the Waste Electrical and Electronic Equipment Directive 2002/96/EC (WEEE
Directive).
Environmental protection
RoHS compliance
The wireless device is in compliance with the restriction of the use of certain hazardous
substances in electrical and electronic equipment Directive 2002/95/EC (RoHS
Directive). Do not dispose of this product with household trash. Oceasoft recycles this
product under certain conditions. Please contact us for more information.
Oceasoft assumes no responsibility for any loss or claims by third parties which may
arise through the use of this product. This document is non-contractual and subject to
change without notice.
Oceasoft and its distributors shall not be held responsible either directly or indirectly for
cost, damage, expenses and legal fees, or personal injury related to the use of Oceasoft
products, even in the case of faulty design or manufacturing of said products. Other than
the warranty on the products’ original mounting brackets, Oceasoft products are
provided as-is without any additional warranty, explicit or implied, with respect to files,
their suitability for a particular application, their quality, their commercialization or any
other related aspect.
The seller’s and creator’s liability with respect to the product warranty is strictly limited
the amount paid by the client for said product. Under no circumstances shall the seller
or creator assume responsibility for any damage or prejudice whatsoever, direct or
indirect, specific or consequential, particularly with respect to any down-time, loss of
data, or any other financial loss resulting from the use or impossibility to use the
products, even if Oceasoft is aware of the potential occurrence of said prejudice. The
product seller and creator advise each product user to verify the results of using these
files, and neither the seller nor the creator shall be held liable for any damage related to
4 | Administrator Guide
Administrator Guide for Cobalt Wireless Monitoring System
using the delivered product. Oceasoft informs all future buyers and user of its products
that without the above limitations, Oceasoft products would not be able to exist.
Do not open the product casing and do not disassemble or modify internal components
in any manner whatsoever. Oceasoft products do not contain any internal components
that require user intervention or repair. If the product or device shows signs of improper
operation, disconnect it immediately from its power source and contact Oceasoft
technical services so that the device can be examined under proper conditions.
Warranty statement
Oceasoft warrants the functions of the Cobalt 2 Monitoring system in accordance with
our standard warranty as described in the Terms and Conditions of Sale applicable to
your purchase of this product. Unless otherwise agreed to in writing, Oceasoft warrants
that the product will conform to published specifications for a period of two years from
the date of delivery.
For additional details concerning this warranty, please consult the Warranty section of
our standard Terms and Conditions of Sale.
Our calibration is carried out according to COFRAC guidelines and are not COFRAC-
certified calibrations. Our calibration tools are verified on a regular basis by L.N.E., a
COFRAC-certified laboratory. Please contact us for information on calibration carried
out by the COFRAC Laboratory.
Administrator Guide | 5
Administrator Guide for Cobalt Wireless Monitoring System
• All Cobalt products using an AC adapter should also be plugged into the UPS.
• Weekly manual system testing (e.g., disconnect a sensor from its module,
verify the communications system is working) should be should be performed
as defined in your Standard Operating Procedure (SOP).
© 2017 OCEASOFT S.A. All rights reserved. Oceasoft, the Oceasoft logo, Cobalt,
ThermoServer and ThermoClient are the exclusive property of Oceasoft. All other
brands mentioned are the property of their respective owners.
6 | Administrator Guide
Administrator Guide for Cobalt Wireless Monitoring System
Table of contents
Administrator Guide | 7
Administrator Guide for Cobalt Wireless Monitoring System
8 | Administrator Guide
Administrator Guide for Cobalt Wireless Monitoring System
Administrator Guide | 9
Administrator Guide for Cobalt Wireless Monitoring System
10 | Administrator Guide
Administrator Guide for Cobalt Wireless Monitoring System
Administrator Guide | 11
Administrator Guide for Cobalt Wireless Monitoring System
12 | Administrator Guide
Administrator Guide for Cobalt Wireless Monitoring System
Figure 47 – The USB modem plugged directly into a serial port ...........................................94
Figure 48 – Sample network with client/server architecture and wireless modules .............105
Figure 49 –Cobalt hardware and ThermoServer/ThermoClient software architecture ........107
Figure 50 – Service Discovery Protocol (SDP) for automatic wireless configuration ..........112
Figure 51 – Over-using Level 1 modules as repeaters radically shortens battery life .........114
Figure 52 – Adding a repeater preserves battery life in Level 1 modules ...........................114
Figure 53 – A second Level 1 module can serve as a backup repeater..............................115
Figure 54 – The Level 1 repeater represents a critical path for this network branch ...........115
Figure 55 – The network branch can be optimized by placing the receiver appropriately ...116
Figure 56 – Networks may also be optimized by adding receivers .....................................116
Figure 57 – Place devices for best wireless performance by placing them appropriately ...119
Figure 58 – Avoid signal attenuation due to angle of penetration .......................................119
Figure 59 – Placing the receiver to achieve clearest signal ................................................120
Figure 60 – Respect minimum distance between devices ..................................................120
Figure 61 – Cobalt module LCD screen overview ...............................................................126
Figure 62 – Cobalt module indicating high alarm condition .................................................127
Figure 63 – Cobalt module automatic wireless setup sequence using SDP feature ...........128
Figure 64 – Typical product serial number sticker...............................................................130
Figure 65 – Using ThermoClient to test alerts (Tools Alert test) .....................................136
Administrator Guide | 13
SECTION 1 – Cobalt module
installation and specifics
Administrator Guide for Cobalt Wireless Monitoring System
All Cobalt 2 modules share common features and are configured in nearly the same
manner as each other. Specific features for the different Cobalt 2 module are described
in the following chapters, namely:
• Wireless range:
• Indoors: 25-100 meters (82-328 ft.); up to 400 meters (1,312 ft.) with 3
repeaters
• Power output: 25 mW (867, 868 and 915 MHz), 10 mW for 434 MHz
Mounting holder
Insert the provided battery, if not already installed, making sure to respect the polarity
(see image printed inside battery slot). We recommend that you use a manual
screwdriver, being careful not to over-tighten the screws.
Figure 2 – Remove back cover and insert battery (respect +/- polarity)
You may refresh the Cobalt display with the latest sensor readings by performing a short
press on the module’s push-button. Simply press the button briefly to update and view
the current reading.
Make sure you only press the button briefly, as a long-press will
active the automatic wireless network search feature.
• Make sure the wireless module is not placed on an electrical conduit or cable
tray (such as for computer network cables).
• For best results, place the module so that it faces the general direction of the
receiver antenna.
• Keep about 20 cm (8 in.) clear space around the module. A module that is
“stuck” between two refrigerators may not communicate effectively.
When routing a cable (if necessary) for any Cobalt sensor, avoid
direct contact with or close proximity placement of the sensor
cabling with any high voltage wiring. Cabling should be placed with
no less than a minimum of 5 cm (2 inches) distance from high
voltage components. Also, avoid running the sensor cable in
parallel with high voltage wiring.
1. Examine the general layout of your site to determine the placement of your
Cobalt modules. The extent of your pre-installation site survey depends on the
number of modules to install. Feel free to contact your sales representative for
more information on this topic.
1. Place all modules in their final locations before running wireless setup.
2. Begin activation by pressing on the module’s button for 3 seconds (until
“Searching” is displayed on the screen), starting with the modules closest to
your receiver, working your way “out” in concentric circles. This enables each
Cobalt module to establish the optimal connection to your receiver.
2. Remove the protection from the adhesive pad on the magnet and place the
magnet on the back of the holder.
3. Place the holder and magnet down on a flat surface and press down strongly
for 30 seconds to firmly attach the magnet.
Cobalt 2 modules feature an automatic wireless setup feature that enables you to add a
new Cobalt 2 module to your wireless network just by pressing the button on the front of
your module.
For greater control over module installation, and for larger wireless monitoring systems,
it is preferable to install modules manually via the ThermoClient software.
• Cobalt mounting kit with plastic holder, magnet, screws, cable ties, plastic
cable holders and Velcro®
This is particularly relevant when you have carried out a mapping study and determined
the ideal location for the sensor. In that case, make sure that the sensor does not
interfere with loading and unloading your product(s) and that the location does not
represent a risk for either your product(s) or the sensor.
Installation through the door gasket on freezers may cause ice build-
up inside the freezer and/or on the freezer door. This may result in
damage to the freezer door if not properly maintained. When used
with incubators, use of the flat cable may cause condensation, which
could potentially increase the risk of contamination.
2. Clean the surface for the sensor using alcohol to remove any grease or dirt.
3. Attach one of the plastic cable holders to the sensor, remove the protective strip
from the adhesive, and place the holder on the clean spot inside the enclosure.
4. Place the sensor / flat ribbon cable connector on the inside of the chamber in
the same manner, as shown here:
5. Your mounting kit includes a plastic holder that can be mounted using the
provided magnet, screws or Velcro®. Choose the method that is most
appropriate for your situation and place the Cobalt module as described in How
to place your Cobalt module for best performance on pg. 18. For example:
6. Attach or coil the excess cable neatly. We also recommend that you secure the
cable to the unit to prevent the module from falling if it becomes dislodged from
the unit or holder.
• Cobalt mounting kit with plastic holder, magnet, screws, cable ties, plastic
cable holders and Velcro®
• Documentation CD-ROM
Push-button
The Cobalt module collects and stores humidity (RH) and temperature readings from
the connected sensor module at regular intervals and transmits them to a computer
running the ThermoServer/ThermoClient system management software. This software
enables you to completely configure your Cobalt modules as well as handle alarms,
alerts, data storage and more quickly and reliably.
• Wireless range: Indoors: 25-100 meters (82-328 ft.); up to 400 meters (1,312
ft.) with 3 repeaters
• Measurement ranges:
o Temperature: -40°C to +100°C (-40°F to 212°F)
o Relative humidity from 0 – 100%
2. Mount the Cobalt module in the desired location using the provided plastic
holder, which you may mount using a magnet or Velcro® tape. Choose the
method that works best for your location and place the Cobalt module as
described earlier in How to place your Cobalt module for best performance on
pg. 18.
3. Use the provided plastic cable holders to attach or coil the excess cable neatly.
When routing the cable for the Cobalt sensor, avoid direct contact with
or close proximity placement of the sensor cabling with any high voltage
wiring. Cabling should be placed with no less than a minimum of 5 cm
(2 inches) distance from high voltage components. Also, avoid running
the sensor cable in parallel with high voltage wiring.
For all other manufacturers’ equipment, contact the manufacturer of the
instrument for instructions regarding proper placement of the sensor.
• Cobalt mounting kit with plastic holder, magnet, screws, cable ties, plastic
cable holders and Velcro®
• Sensor mounting kit with 2 wire-ties and 4 plastic holders with adhesive
backing
• Documentation CD-ROM
• Wireless range indoors: 25-100 meters (82-328 ft.); up to 400 meters (1,312
ft.) with 3 repeaters
Cobalt PT100 modules are typically installed on the outside of freezers, ovens, and
nitrogen tanks with the sensor placed inside the chamber via the appropriate built-in
configuration.
The Cobalt module and PT100 sensor are already connected to each other when you
receive them. They have been calibrated as a “pair” before delivery. If you change either
the module or the sensor in the future, you must recalibrate the new pair.
As mentioned above, the Cobalt wireless monitoring system supports three different
PT100 temperature sensors, each designed for a different application and temperature
range. Placement of your PT100 sensor(s) depends on the equipment you intend to
monitor, as described below.
In all cases described in this section, the plastic male connector (Figure
13 on pg. 32) must be at room temperature.
Note: When routing the cable for any Cobalt sensor, avoid direct contact with or close
proximity placement of the sensor cabling with any high voltage wiring. Cabling should
be placed with no less than a minimum of 5 cm (2 inches) distance from high voltage
components. Also, avoid running the sensor cable in parallel with high voltage wiring.
Your equipment may be different than that described here. Contact the manufacturer of
your equipment for instructions regarding proper placement of the sensor.
When using PT100 sensors with ovens, kilns and incubators, we recommend that you
insert only the sensor into the chamber. The sensor can withstand +350°C but high
temperatures can affect the gray cable. The cable supports temperatures up to +350°C
if firmly attached (no movement) or up to +250°C if the cable is moved regularly.
The sensor length is designed to ensure that the sensor at the end of the sensor reaches
properly into the space being monitored.
When possible, route the sensor through the same access port used by the unit control
sensor or an accessory port, such as that shown below in Figure 7. Mount the Cobalt
sensor as close to the unit control sensor as possible.
When possible, route the sensor through the same access port used by the unit control
sensor or an accessory port, such as that shown below in Figure 8.
When routing the Cobalt sensor through the same port used by the control sensor,
Oceasoft recommends installing the sensor only after the freezer has reached a thawed
state.
To negate the possibility of condensation dripping on the electronics, avoid routing the
cable in close proximity to any electrical enclosures.
Mount the Cobalt sensor as close to the unit control sensor as possible. When possible,
we recommend mounting the Cobalt sensor within 5 cm (2 inches) of the control sensor.
When mounting the Cobalt sensor, avoid direct contact with the wall of the freezer. This
will ensure the sensor is mounted to permit measurement of air temperature only.
The orange cable, which supports temperatures from -200°C to + 50°C, may be placed
inside the freezer. Make sure you attach the sensor using the provided cable-ties and
reseal any openings you may have unsealed to insert the sensor using permagum
sealant.
PT100 sensors for Oceasoft LN2/cryogenic tanks must be mounted, when applicable, in
close proximity to the unit display sensor.
As an example, some freezers have an access panel on the back of the unit in which
you may route the sensor cable up the back wall. Place the cable under the tank gasket
utilizing the notch at the 12 o’clock position. We recommend the installation of
permagum sealant where the cable passes through the notch.
Depending on whether storing in vapor or liquid phase, place the sensor at a depth
suitable for proper temperature monitoring.
Here is a detailed description of the parts of the various PT100 sensors (sold separately).
The Cobalt module and its wireless features are powered by the unit’s
battery. Although the AC adapter plugs into the Cobalt module, this
power is used only by the external CO2 / temperature sensor.
• Cobalt mounting kit with plastic holder, magnet, screws, cable ties, plastic
cable holders and Velcro®
• Documentation CD-ROM
• Resolution: 0.0625°C
• IP44 protection, plastic casing (ABS, Polycarbonate) with PTFE filter, 0 to 90%
RH non condensing for indoor use
Cobalt collects and stores CO2 and temperature readings from the connected sensor
module at regular intervals and transmits them to a computer running the
ThermoServer/ThermoClient system management software. This software enables you
to completely configure your Cobalt modules as well as handle alarms, alerts, data
storage and more quickly and reliably.
IMPORTANT NOTICES:
Do not place the Cobalt wireless module inside the incubator.
Remove the CO2 / temperature sensor from inside the incubator if you
decontaminate the incubator (which produces a heat level not
supported by the sensor).
• CO2 / temperature sensor (which draws current from the Cobalt wireless
module on AC power)
• Wireless range: indoors: 25-100 meters (82-328 ft.); up to 400 meters (1,312
ft.) with 3 repeaters
• Operating temperature range for wireless module and sensor: 0°C to +50°C
Cobalt wireless modules connect to remote devices (e.g., sensors and sensors) to
monitor their status, transmitting information wirelessly to a central database managed
by Oceasoft ThermoServer software. Alerts can be sent automatically in case these
readings indicate specific alarm conditions configured in the software.
Push-button
Power /
Temperature
sensor plug CO2 detector opening communication cable
plug to Cobalt module
Figure 18 – Cobalt CO2 sensor
2. Make sure that the sensor unit stays in an upright position as shown here:
3. Mount the Cobalt module on the exterior of the incubator door using the provided
plastic holder, which you may mount using a magnet or Velcro®. Choose the
method that is most appropriate for your situation, and place the Cobalt module
as described in How to place your Cobalt module for best performance (pg. 18),
for example:
4. Connect the sensor and wireless module cables by joining the connectors (being
careful to not unscrew them).
5. Use the provided plastic cable holders to attach or coil the excess cable neatly.
When routing the cable for the Cobalt sensor, avoid direct contact with
or close proximity placement of the sensor cabling with any high voltage
wiring. Cabling should be placed with no less than a minimum of 5 cm
(2 inches) distance from high voltage components. Also, avoid running
the sensor cable in parallel with high voltage wiring. Feel free to contact
the manufacturer of the instrument for instructions regarding proper
placement of the sensor.
• Clear Tygon® hose (diameter: 4 mm; length 50 cm) which can be connected to
your existing pressure monitoring system
• Cobalt mounting kit with plastic holder, magnet, screws, cable ties and plastic
cable holders and Velcro®
This module is typically placed in the room in which the ambient pressure is considered
as “normal.” A tube is placed on one of the module’s inputs to measure the pressure in
another room. The Cobalt differential pressure module is particularly suitable for use in
monitoring “clean” and “dirty” laboratory areas.
For example, in Case 1 the tube is placed in an area where the pressure should be
higher than where the module is placed, such as in a “clean” room (whose higher
pressure pushes outward into the normal room in order to keep microbes from entering).
Case 2 shows the opposite. The tube is placed in an area where the pressure should
be lower than where the module is placed, such as in a “dirty” room (whose lower
pressure keeps microbes from escaping out into the normal room).
Cobalt collects and stores pressure readings at regular intervals and transmits them to
a computer running the ThermoServer/ThermoClient system management software.
This software enables you to completely configure your Cobalt modules as well as
handle alarms, alerts, data storage and more quickly and reliably.
• Wireless range (indoors): 25-100 meters (82-328 ft.); up to 400 meters (1,312
ft.) with 3 repeaters
Push-button
“High” input
“Low” input
• Resolution: 0.25 Pa
• Span shift due to temperature variation: < 0.5% of reading per 10°C
• Cobalt mounting kit with plastic holder, magnet, screws, cable ties, plastic
cable holders and Velcro®
• Documentation CD-ROM
• Wireless range: Indoors: 25-100 meters (82-328 ft.); up to 400 meters (1,312
ft.) with 3 repeaters
o Line-of-sight: approximately 700 meters (2,300 ft.)
Cobalt modules for 4-20 mA and 0-5 V monitoring are typically installed in a convenient
location at room temperature.
Push-button
Connect the 2-wire cable extending from the Cobalt module to the appropriate output on
your current-generating device (for 4-20 mA and 0-5V modules only). The black wire
from the Cobalt module is the ground (-); the yellow wire is for the signal from your
connected device (+).
Please check your device’s operating instructions for specific pin indications.
• Cobalt mounting kit with plastic holder, magnet, screws, cable ties and plastic
cable holders and Velcro®
• Documentation CD-ROM
Typical devices that provide a dry contact output include alarm units, door open/close
sensors, and switches. The Cobalt module can be configured to detect either a “normally
closed” or “normally open” state to correspond with the device to monitor. The Cobalt
module indicates open or closed in large characters on its LCD display.
• Wireless range indoors: 25-100 meters (82-328 ft); up to 400 meters (1,312 ft)
with 3 repeaters
I press the button for 3 seconds but my Cobalt does not connect to my receiver;
what should I do? Try bringing the module closer to your receiver. If it works closer,
then you may need to use a repeater in order for the wireless signal to reach the Cobalt
module in its final location. Also check to make sure the receiver is working properly.
The Cobalt module shows a strong signal, but I’m still not getting any readings
from my sensor? This is usually due to a loose cable or improperly connected sensor.
Check the cable between the Cobalt module and sensor. Try a different sensor.
What if I only see one of the two modules (on a dual-sensor device) in
ThermoClient? Make sure the cable is in good condition and that the connection
between the two devices is tight.
Why don’t I get any temperature readings with an external sensor, even though
the Cobalt module shows a strong signal? This is usually due to a loose cable or
improperly connected temperature sensor. Check the cable between the Cobalt module
and the sensor. Unplug the sensor and plug it back in. Make sure there are no exposed
wires. Try a different sensor if possible.
The diagram below shows how these elements fit together in a typical layout:
• USB receiver: plugged directly into a USB port on the server computer. The
USB receiver is not covered in this document, but is described in detail in the
Installation guide for ThermoServer/ThermoClient® 5 and USB Wireless
Receiver document provided with your solution.
• Standalone repeater: a wireless range extending device that bridges the gap
between a module and a receiver that are beyond wireless range. A repeater
is transparent with respect to the data being transmitted.
11 USB receiver
The USB receiver is described in detail in the Installation guide for
ThermoServer/ThermoClient® 5 and USB Wireless Receiver document provided with
your solution.
50 | USB receiver
Administrator Guide for Cobalt Wireless Monitoring System
12 TCP/IP receiver
The Oceasoft TCP/IP Network Receiver plugs into your local Ethernet network and
collects data wirelessly from various types of Cobalt modules, including temperature,
humidity and other sensors, and transfers it to the ThermoServer data monitoring
software.
Network receivers are particularly useful when you need to read sensors in one or more
groups of Cobalt modules that are located remotely from the ThermoServer computer
used to monitor the data.
• External antenna
• Mounting kit
A network receiver:
• Transmits configuration and on-demand read requests from the client software
to end-modules
• Has a range from 25-100 meters (65-325 ft.) indoors up to approximately 700
meters (2,300 ft.) in line of sight
TCP/IP receiver | 51
Administrator Guide for Cobalt Wireless Monitoring System
Connection activity
and power indicators
AC adapter plug
The following diagram shows two examples of a typical installation with network
receivers.
The Oceasoft network receiver enables you to access remote modules from the
ThermoClient monitoring application. Once installed, this receiver operates
transparently as if it were connected directly to your ThermoServer computer, like a USB
receiver. The only difference is that the network receiver resides on your Ethernet
network and communicates via TCP/IP.
52 | TCP/IP receiver
Administrator Guide for Cobalt Wireless Monitoring System
The ThermoClient software enables you to connect directly to the receiver in order to
include it in your Cobalt monitoring system.
Choose the mode that best matches your network requirements. Namely:
• Auto-connect mode requires that the computer’s firewall (and the site firewall if
the receiver is located at a remote site) allow incoming connections from the
receiver’s IP address. This mode is useful when the receivers are located outside
the physical network on which ThermoServer is installed. In this case, the TCP/IP
receivers may use the host network’s fixed IP address without having one of their
own. The firewall is thus relatively easy to configure.
This process is described in detail later in this section (see 12.5 Configuring TCP/IP
receiver parameters).
TCP/IP receiver | 53
Administrator Guide for Cobalt Wireless Monitoring System
• You have experience with networks, notably TCP/IP address and port
configurations. If not, contact and work with your system administrator.
12.3.1 General requirements and recommendations
• The AC adapter used for your network receiver should also be plugged into
the UPS.
• Weekly manual system testing (e.g., pull a sensor, verify that the communication
system is working) should be performed as defined in the Standard Operating
Procedure (SOP).
• If you are storing cold products, Oceasoft recommends use of a back-up cooling
system (e.g., CO2 or LN2) to maintain freezer chamber temperature below the
critical level should a power failure occur. Contact your local sales
representative for more information.
Please see the ThermoClient 5 Software User Manual for an in-depth description of
Cobalt end-point module configuration, alerts, notification, data management and
general system features.
54 | TCP/IP receiver
Administrator Guide for Cobalt Wireless Monitoring System
• UPS sized appropriately for your power and system requirements. Make sure
you follow the manufacturer’s maintenance recommendations.
For smooth installation, we recommend that you temporarily disable your firewall during
installation. (A firewall is a security system that acts as a protective shield between your
network and the outside world.)
This must be done by a user with Administrator rights. Contact your system administrator
for help if you are unsure or if you do not have Administrator rights.
Disabling your firewall is a temporary action just for installation. See Appendix -
Configuring your local firewall on pg. 60) for the long-term solution, which involves
configuring firewall ports, or contact your system administrator for assistance.
TCP/IP receiver | 55
Administrator Guide for Cobalt Wireless Monitoring System
• To avoid electrical interference, place the receiver at least 80 cm (31 in.) away
from electrical outlets, wiring and network cabling.
• For best signal propagation, place the receiver in an open area at a slightly
elevated location (i.e., not directly on the ground), about 2 meters (6.5 ft.) high.
The Oceasoft network receiver is a standalone device that requires a wall power source
for operation. To activate your receiver:
1. Screw the provided antenna onto the network receiver without forcing it.
2. Place the receiver as described in the previous section, and use the wall-mount
adapter or Velcro® tape to adhere it.
3. Plug the AC adapter into the electrical power outlet or UPS.
4. Insert the adapter’s AC adapter plug into the network receiver. The network
receiver’s two red LEDs light up for a couple of seconds, and then one of them
turns off.
5. Use the provided RJ-45 Ethernet cable to plug the receiver into your network.
To configure your TCP/IP receiver, use your Web browser to connect directly to the
network receiver and then configure its basic parameters, as described below.
For this configuration, you need to plug in the provided AC adapter, and
connect your network receiver either into the network directly using a
regular RJ-45 Ethernet cable or into your computer using a crossed-
cable. The receiver does not need to be placed in its final location for this
operation, but it does need to be accessible over the network.
Oceasoft Network Receivers are delivered with a default IP address to ensure that you
can access them. The default IP address is: 192.168.0.100. You can request a different
IP address to be pre-configured when you order your product.
56 | TCP/IP receiver
Administrator Guide for Cobalt Wireless Monitoring System
The process described in this section requires that you know an available
static IP address. This IP address must be in the same IP class as
192.168.0.x. Contact your system administrator for assistance.
TCP/IP receiver | 57
Administrator Guide for Cobalt Wireless Monitoring System
1. Under Active Connection, use the Active Connect pull-down menu to select
Auto Start.
2. Under Passive Connection, make sure the Accept Incoming pull-down menu
is set to No.
3. Leave all other settings at their default values on this screen (provided in the
Appendix for your information), except for those in Endpoint Configuration,
which should be set as follows:
58 | TCP/IP receiver
Administrator Guide for Cobalt Wireless Monitoring System
TCP/IP receiver | 59
Administrator Guide for Cobalt Wireless Monitoring System
Windows 7:
Click on System And Security Windows Firewall Advanced Settings
Inbound Rules New Rule and add rules for the ports below.
If you have installed other firewall software, check the firewall’s user
manual for specific instructions that may apply, or check with your
system administrator.
If you are having problems, you may check whether or not this is the case by temporarily
disabling your anti-virus software to see if that resolves the issue. Follow specific
instructions for your operating system and application.
Anti-virus applications generally place an icon in the Windows task tray in the lower right-
hand corner of your screen. For example, to disable an anti-virus application such as
Norton AntiVirus or McAfee, right-click on the application’s icon in the lower right-hand
corner of your screen, next to the system clock. This should display a pop-up menu in
which you will see a Preferences, Open or Disable option.
The actual steps for disabling anti-virus software differ from vendor to vendor. Check the
documentation for your application or check with your system administrator for help.
60 | TCP/IP receiver
Administrator Guide for Cobalt Wireless Monitoring System
Some routers and switches automatically disconnect idle IP connections. In that case it
is important to make sure that network traffic occurs more often than the idle disconnect
time in your network equipment.
• Configure the Transfer interval in ThermoClient to be lower than this value for
one or more modules.
TCP/IP receiver | 61
Administrator Guide for Cobalt Wireless Monitoring System
You may restore these default settings by clicking on Apply defaults, (see left-hand
menu bar in Figure 30, page 57).
Network:
Server:
62 | TCP/IP receiver
Administrator Guide for Cobalt Wireless Monitoring System
Channel 1 / Connection:
Configurable Pins:
TCP/IP receiver | 63
Administrator Guide for Cobalt Wireless Monitoring System
• Is the antenna plugged in? The network receiver may be configured correctly
using the provided software, but if you don’t plug in the antenna, the device
range is significantly shorter and the device may appear not to function.
• Is the receiver’s red light turned on? If not, make sure the AC power
adapter is plugged in to a functioning outlet.
When I click on Test SmartSvc availability, “not present” is displayed. What can I
do?
• Check with your IT department to make sure the local TCP ports are open.
When I click on receiver firmware version, nothing is displayed. What can I do?
• To eliminate network-related issues, try plugging the receiver directly into your
ThermoServer computer using a crossed RJ-45 cable.
When I try to add the receiver in ThermoClient, why do I get a message saying that
the “port number is already in use”? Make sure you do not have any other receivers
using the specified TCP port. By default, the first port to specify in the TCP port for
ThermoServer field in ThermoClient is 11001. You must increment this number so each
receiver in your network has a unique TCP port.
64 | TCP/IP receiver
Administrator Guide for Cobalt Wireless Monitoring System
12.11 Specifications
• ISM (Industrial Scientific Medical) band with 4 frequencies: US/CAN 915 MHz;
Europe 868 MHz; APAC 434 MHz; India and other countries 867 MHz
• Power adaptor with 1.85 meter (6 ft) cable length and four different
international plugs, 50/60 Hz, 100-240V AC
TCP/IP receiver | 65
Administrator Guide for Cobalt Wireless Monitoring System
13 Power-over-Ethernet (POE)
TCP/IP receiver
13.1 Introduction
The Power-over-Ethernet version of the Oceasoft TCP/IP Network Receiver receives
electrical power directly from your Power-over-Ethernet (PoE) enabled network. Plugged
into your local Ethernet network, this PoE receiver collects data wirelessly from various
types of Cobalt end-point modules, including temperature, humidity and other sensors,
and transfers it to the ThermoServer data monitoring software.
Network receivers are particularly useful when you need to read one or more groups of
Cobalt modules that are located remotely from the ThermoServer computer used to
monitor the data.
Antenna
Connection activity
and power indicators
AC adapter plug
The following diagram shows two examples of a typical installation with network
receivers.
The difference is that the receiver resides on your Ethernet network and communicates
via TCP/IP. The ThermoClient software enables you to connect directly to the receiver
in order to include it in your Cobalt monitoring system.
For smooth installation, we recommend that you temporarily disable your server
computer’s firewall during installation. (A firewall is a security system that acts as a
protective shield between your network and the outside world, or your computer and the
rest of the network).
This must be done by a user with Administrator rights. Contact your system administrator
for help if you are unsure or if you do not have Administrator rights.
Disabling your firewall is a temporary solution just for installation. See Appendix -
Configuring your local firewall on pg. 60) for the long-term solution, which involves
configuring firewall ports, or contact your system administrator for assistance.
• To avoid electrical interference, place the receiver at least 80 cm (31 in.) away
from electrical outlets, wiring and network cabling.
• For best signal propagation, place the receiver in an open area at a slightly
elevated location (i.e., not directly on the ground), about 2 meters (6.5 ft.) high.
1. Screw the provided antenna onto the network receiver without forcing it.
2. Place the receiver as described in the previous section, and use the wall-
mount adapter or Velcro® tape to adhere it.
3. Plug the Ethernet cable into your PoE enabled Ethernet network (or plug the
AC adapter into the electrical power outlet or UPS and insert the adapter’s AC
adapter plug into the network receiver).
If you use the AC adapter, we highly recommend you use a UPS for
your receiver(s).
4. The network receiver’s two LEDs light up for a couple of seconds. If the
connection to your network switch is good, one of the LEDs will remain green
(100 Mbps) or orange (10 Mbps).
For this configuration, you need to plug in the provided AC adapter, and
connect your network receiver either into the network directly using a
regular RJ-45 Ethernet cable or into your computer using a crossed-
cable. The receiver does not need to be placed in its final location for this
operation, but it does need to be accessible over the network.
Oceasoft PoE network receivers are delivered with a default IP address to ensure that
you can access them. The default IP address is: 192.168.0.100.
2. Type 192.168.0.100 in the address bar, and then press Enter on your
keyboard.
Depending on your receiver, you may have to enter a login/password. Enter the
following to continue (case sensitive characters) and then click on OK.
In this screen, you will need to adjust settings under both Accept Mode and
Connect Mode.
2. Check to make sure that the information in the DNS Cache zone is correct,
notably that the IP address and Domain Name correspond to the
ThermoServer computer.
If this information is correct, then the PoE network receiver is ready to use in your Cobalt
Monitoring System.
13.11 Specifications
• ISM (Industrial Scientific Medical) band with 4 frequencies: US/CAN 915 MHz;
Europe 868 MHz; APAC 434 MHz; India and other countries 867 MHz
• Channel width: 50 kHz
14 Standalone repeater
A repeater device extends the range between wireless modules and receivers in your
Cobalt monitoring system. These instructions describe how to add the new repeater to
your existing network quickly and easily.
• Antenna
• Documentation CD-ROM
• Wireless range:
o Indoors: 25-100 meters (82-328 ft.); up to 400 meters (1,312 ft.) with 3
repeaters
o Line-of-sight: approximately 700 meters (2,300 ft.)
14.3 Specifications
• ISM (Industrial Scientific Medical) band with four frequencies: US/CAN 915
MHz; Europe 868 MHz; APAC 434 MHz; India and other countries 867 MHz
Standalone repeater | 77
Administrator Guide for Cobalt Wireless Monitoring System
Oceasoft receivers can be plugged directly into a PC’s USB or serial port, or they may
be connected directly to your Ethernet network using an RJ-45 cable. Standalone
wireless repeaters are placed between a receiver and remote Cobalt modules to extend
the overall wireless range. The following diagram provides two examples of how
repeaters may be placed in typical installations.
This diagram shows that up to 3 repeaters may be used to increase overall wireless
range to reach remote end-point modules
78 | Standalone repeater
Administrator Guide for Cobalt Wireless Monitoring System
For optimal operation, follow these recommendations when physically placing your
device:
• To avoid electrical interference, do not place the repeater within 80 cm (31 in.)
of electrical outlets, wiring and network cabling.
• For best signal propagation, place the repeater in an open area at a slightly
elevated location (i.e., not directly on the ground), about 2 meters (6.5 ft.) high.
• Plug the AC adapter for your repeater into an Uninterruptable Power Supply
(UPS) for reliable operation.
Your repeater is a standalone device that requires mains power for operation. To
activate your repeater:
Standalone repeater | 79
Administrator Guide for Cobalt Wireless Monitoring System
How can I tell if the repeater is working correctly? The repeater’s two LEDs turn on
briefly when you plug in the AC adapter, and one remains on to indicate that the device
is running. If one light blinks continually, there may be a problem with the AC adapter. If
both lights are off, make sure the AC adapter is plugged in.
I entered the repeater address in ThermoClient, but its signal remains at 0% when
I run a test. What should I do? Check the repeater’s RF address (“S/N” on the label)
in ThermoClient. Make sure the repeater and receiver are both powered on. Try bringing
the repeater closer to the receiver. Test your receiver with another end-module.
The repeater shows a strong signal, but the end-point module shows 0%. What
should I do? Check the end-point’s RF address (“S/N” on the label) in ThermoClient.
Test the end-point module by physically placing it within 3 meters (9.8 ft.) of your receiver
(without passing through the repeater). If the end-point module is functioning correctly,
try placing the repeater in a different location. Consider using additional repeaters if the
end-point module is far away.
80 | Standalone repeater
Administrator Guide for Cobalt Wireless Monitoring System
| 81
Administrator Guide for Cobalt Wireless Monitoring System
15 Alert Devices
The Cobalt wireless monitoring system can alert you if readings on your sensor modules
exceed range limits that you specify. You may receive alerts by phone, fax, e-mail, text
message, and alerts can trigger a wireless siren or dry contact alert device.
The OCEASOFT Alarm Management System (AMS) is an integral part of the Cobalt
software solution, watching over your data to make sure it stays within the target range.
• Dry contact device: a wireless device that can be used to activate other type
of alert devices.
82 | Alert Devices
Administrator Guide for Cobalt Wireless Monitoring System
16 Wireless siren
16.1 Package contents
• Oceasoft wireless siren
• AC power adapter with 1 meter (3.3 ft.) cable and 4 international plug sizes;
100/240V (50/60 Hz) AC 12V DC – 1A
• Documentation CD-ROM
• Power output: 25 mW (867, 868 and 915 MHz), 10 mW for 434 MHz.
• Wireless range up to 200 meters (650 ft) in open space, from 8 meters (26 ft)
to 30 meters (98 ft) indoors, and up to 120 meters (390 ft) indoors with 3
repeaters
Wireless siren | 83
Administrator Guide for Cobalt Wireless Monitoring System
Oceasoft wireless siren modules are used to raise alerts if alarm conditions are detected
in your Cobalt wireless monitoring system. Alarms can be configured in the Oceasoft
ThermoClient software for any or all of your end-point modules and/groups.
For example, you can configure a Cobalt temperature monitoring module to trigger an
alarm if the temperature exceeds or drops below a specified limit. The alarm limits and
values depend on the type of Cobalt module you are using. The siren is triggered when
an alarm is detected by the software.
Flashing light
Siren speaker
AC adapter plug
Volume control
84 | Wireless siren
Administrator Guide for Cobalt Wireless Monitoring System
Oceasoft sirens connect wirelessly to one or more wireless receivers, just as the other
wireless modules in your network:
The computer running the monitoring system software triggers the siren wirelessly via
the receiver when it detects an alarm condition in a wireless module or repeater.
Wireless siren | 85
Administrator Guide for Cobalt Wireless Monitoring System
If you have to remove this plug from the siren, pull gently so you do not
damage the unit or plug.
I clicked on the Test button on the Alarm test screen, but nothing happens. What
should I do? Make sure the alarm service is running on the
ThermoServer/ThermoClient computer. Next, make sure the unit is plugged in correctly
to the AC power adapter and that the adapter is plugged into a live outlet.
Will test alarms be recorded in my alarm history? No. Test alarms act like real
alarms, but they have a time/date stamp of 12/30/99 at 00:00 so you can identify these
events as tests easily. Also, they are not recorded in the alarm log.
What kinds of module alarms trigger the siren? Sirens are triggered when
ThermoClient software detects an alarm condition of any kind from a sensor or repeater.
This includes technical alarms (i.e., low battery, sensor failure, wireless communication
failure) and “limit” alarms (i.e., readings exceed upper or lower limits specified in the
software).
86 | Wireless siren
Administrator Guide for Cobalt Wireless Monitoring System
I moved my siren. Why doesn’t it work anymore? First, make sure the unit is plugged
in correctly to the AC power adapter and that the adapter is plugged into a live outlet.
Also, due to its casing, the wireless range on the siren is about half that of the Cobalt
end-point modules and repeaters. Make sure your device is still within wireless range by
running a signal strength test in ThermoClient (press F8 or click on Alarms). Click on
the plus (+) sign, click on the siren you wish to check, and click on Power.
Wireless siren | 87
Administrator Guide for Cobalt Wireless Monitoring System
For example, you can configure a Cobalt temperature monitoring module to trigger an
alarm if the temperature exceeds or drops below a specified limit. The alarm limits and
values depend on the type of Cobalt module you are using. The TCP/IP Dry Contact
device receives a signal over the network when an alarm is detected by the software,
and then triggers an alarm on the connected dry contact device(s).
AC adapter plug
If your TCP/IP Dry Contact device is used to control two connected devices, both of the
devices are controlled identically at the same time.
• The server’s Alarm Management System connects to the IP dry contact device
on its port IP 30704. The outgoing port must therefore be open on your
firewall.
It is important to identify the two logical states implemented by the IP dry contact alert
device:
• Normal state
• Alarm state
When plugging the dry contact device into another external device, it is possible to
choose the physical state for each of the logical states. This means that you can choose
the "normal" logical state that corresponds to dry contact being open or closed.
Normal state
Under normal operation, after installing and activating the system, the alert device is in
a normal state when the following conditions are all met:
• No new, non-acknowledged alarms are present for any of the sensor groups to
which the device is assigned
• Power is supplied as required by the device
• The device is connected properly to the network
• The AMS (or “Gestion Alarme”) service must be running
Alarm state
The dry contact alert device is in an alarm state when at least one of the following
conditions arises:
• An alarm occurs in one of the sensor groups to which the device is assigned
• Power to the device is cut
• The device loses its connection with the network for more than 5 minutes
• The AMS service is stopped
• AC power adapter
o 1 meter (3.3 ft.) cable
o 4 international plug sizes
o 100/240V (50/60 Hz) AC 24V DC - 0.4A
• Mounting clip
• Size: 102 x 54 x 30 mm
• Plastic enclosure: ABS (UL 94HB) RAL 9002/7032 with IP43 protection for
indoor use
• Electrical
o Coil power, nominal: 0.2W
o Breaking capacity: 250VAC / 5A
For optimal operation, follow these recommendations when placing your device:
• To ensure that the AC adapter does not get unplugged accidently, use a
power socket that is also elevated from the floor and/or shield the cord in a
protective conduit that is fixed to the wall or contained within the wall.
• The TCP/IP Dry Contact device is a critical device in your wireless monitoring
system. Therefore, we recommend that you keep it plugged it into an
Uninterruptible Power Supply or safety plug.
The next step is to use your Web browser to connect directly to the Dry Contact in order
to configure its basic parameters.
Oceasoft TCP/IP Dry Contact devices are delivered with a default IP address to ensure
that you can access them over your network. The default IP address is: 192.168.0.110.
To adapt the TCP/IP Dry Contact device for use in your network, do the following:
1. Click on Network in the left-hand panel, and fill in the IP Address, Subnet
Mask, Default Gateway and DNS Server fields to match your network. Contact
your system administrator if necessary.
2. Click on OK to save your network settings.
3. Click on Apply Settings in the left-hand panel to save your configuration
changes to the network receiver. You may close your browser after the
configuration is saved.
4. Re-start the receiver by unplugging the AC adapter and plugging it back in.
17.5 Troubleshooting
If you are having difficulties with your configuration, take a look at these frequently asked
questions before contacting technical support.
I clicked on the Test button on the Alarm test screen, but nothing happens. What
should I do? Make sure the alarm service is running on the
ThermoServer/ThermoClient computer. Next, make sure the unit is plugged in correctly
to the AC power adapter and that the adapter is plugged into a live outlet.
Will these alarms be recorded in my alarm history? No. Test alarms act like real
alarms, but they have a time/date stamp of 12/30/1899 at 00:00 so you can identify these
events as tests easily. Also, they are not recorded in the alarm log.
What kinds of module alarms trigger the TCP/IP Dry Contact device? TCP/IP Dry
Contact devices are triggered when ThermoClient software detects an alarm condition
of any kind from a sensor or repeater. This includes technical alarms (i.e., low battery,
sensor failure, wireless communication failure) and “limit” alarms (i.e., readings exceed
upper or lower limits specified in the software).
18 Telephone modem
This section describes how to install the modem on your ThermoServer computer and
configure it using the ThermoClient software.
Connects modem to
your telephone line
• Telephone cable
1Direct SMS text messaging service via modem is available in France only. Contact your
Oceasoft representative for information on the OCEAlert offer for a global Internet-based alert
solution.
Telephone modem | 93
Administrator Guide for Cobalt Wireless Monitoring System
• Fax: EIA 578 (Class 1) with V.17, V.29, V.27ter, V.21, Group 3
The following diagram shows how the Oceasoft USB modem is installed on the
ThermoServer computer.
The modem must be connected to a USB port on the ThermoServer computer and into
a dedicated analog telephone line.
In your Cobalt solution, the ThermoServer application receives data from the end-point
modules being monitored, such as temperature, CO 2, or humidity sensors. One of the
major advantages of the ThermoServer solution is that it alerts users or groups of users
in case measured values from end-point modules exceeds defined limits. The
ThermoClient software application is used to define these limits as well as the recipients
of related alerts.
94 | Telephone modem
Administrator Guide for Cobalt Wireless Monitoring System
Do not plug the modem into your computer until you have
installed the software, and do not allow MS Windows to
automatically search for modem drivers before installing the
drivers provided by Oceasoft.
It is essential for the correct drivers to be installed from the
Oceasoft CD-ROM
1. Insert the provided Oceasoft installation CD-ROM into the drive. If the
installation application does not start automatically, navigate to the drive using
the Windows Explorer and double-click on the Start.exe in the root of the CD-
ROM.
2. Click on Install phone modem driver.
3. Click on Next to run the installation wizard and then on Continue anyway.
4. Click on Finish to complete the process and close the wizard.
5. Plug the modem into an available USB port on the ThermoServer computer.
6. Windows installs the software automatically. When the installation is finished,
the wizard displays a message in the task bar’s notification area indicating that
a U.S. Robotics V.92 USB Voice Modem is installed.
7. The modem is now ready for use.
Telephone modem | 95
Administrator Guide for Cobalt Wireless Monitoring System
3. In the Modems section, check to make sure that a device U.S. Robotics V.92
USB Voice Modem is present. Right-click on the device name Properties
and make sure the device status is indicated as “This device is working properly”
(you may also wish to note the modem’s COM port number for later use). Then
click on Cancel to close the window.
4. In the Sound section, check to make sure that a device Unimodem Half-
Duplex Audio Device is present. Right-click on the device name Properties
and make sure the device status is indicated as “This device is working
properly”. Then click on Cancel to close the window, and exit the Computer
Management window.
18.7 Troubleshooting
If you are having difficulties with your configuration, take a look at this section before
contacting technical support.
• Make sure that the USB cable is correctly plugged into your computer and that
the telephone cable is correctly plugged into a dedicated wall jack.
• Try testing the modem with a different phone cord and/or wall jack if possible.
• Try a different USB port on your computer. If a USB hub is being used, try
plugging directly into the USB port on the computer.
• Shut down and restart your computer. Make sure the Modem and Audio
device are correctly installed (see Confirming driver installation in Windows, pg
95).
96 | Telephone modem
Administrator Guide for Cobalt Wireless Monitoring System
The actions described here must be carried out on the server computer running
ThermoServer for your Cobalt® wireless monitoring system.
The initial installation is valid for a period of three months, during which time you may
use the service freely. Please contact your authorized reseller to subscribe to the service
and continue accessing OCEACloud with ThermoClient Mobile on your smartphone or
tablet after that time
3. Your Cloud connection identifier is shown in the Cloud ID field. Use this
ID in ThermoClient Mobile to connect to the Cloud on your smartphone.
If your server computer does not have ThermoClient installed, you may still
obtain your Cloud ID manually. To do this:
[Disk]:\Thermo\thermoserver
CLOUDID=XXXXXXXX
4. Close the configuration file without saving any changes.
Your installation is complete at this point and you may now use the
ThermoClient Mobile application. In ThermoClient Mobile, connect to your data
stored on OCEACloud using your regular ThermoServer system login,
password, and the appropriate Cloud ID.
The following changes need to be made for each instance of ThermoServer that you
wish to synchronize with your OCEACloud account.
[Disk]:\Thermo\thermoserver_Instance2
2. Edit the ThermoServer.ini configuration file:
[CLOUDIDGEN]
DBName=thermoCloudIdGen
DBport=33006
DBhost=temperatureweb.com
DBuser=oceacloud
DBpwd=TmFmZSQ1Mw
[HTTPOPTIONS]
useproxy=
proxyhost=
proxyport=
proxyuser=
proxypwd=
4. Save your changes and then close the configuration file.
For each additional instance of ThermoServer that you wish to synchronize with
OCEACloud, you must perform these steps to install the service and register it with
a different name for each instance.
[Disk]:\Thermo\thermoserver_Instance2
[Disk]:\Thermo\thermoserver_Instance2
[a to z] [A to Z] [0 to 9] and [ _ ]
Note: At this point, it is normal for the services to not be running. Do not
start them yet.
1. Right-click on Computer
3. Right-click on the services and select Properties Log On, and make
sure that the checkbox "Allow service to interact with desktop" is not
selected (not checked).
19.3.5 Getting your Cloud ID using ThermoClient (Windows)
3. Your Cloud connection identifier is shown in the Cloud ID field. Use this
ID in ThermoClient Mobile to connect to the data from the first instance
of ThermoServer on the Cloud with your smartphone.
If your server computer does not have ThermoClient installed, you may still
obtain your Cloud ID for the first instance manually. To do this:
[Disk]:\Thermo\thermoserver
2. Open the file: ThermoServer.ini.
CLOUDID=XXXXXXXX
4. Close the configuration file without saving any changes.
20 Software licenses
The software functions for a period of three months from its initial installation without a
license. To continue using the software after that time you will need a license.
For more information about licenses, or to generate a final license file, please contact
your authorized sales representative.
21.1 Overview
The Cobalt wireless monitoring system lets you track various physical parameters
remotely, such as temperature, differential pressure, CO2 levels, and more. This section
describes the components used in the Cobalt wireless monitoring system. To start, the
diagram below shows the basic layout of a Cobalt wireless network
Cobalt wireless modules are equipped with internal or external sensors. They collect
data (readings) on a regular basis and transmit the information wirelessly to a receiver
that, in turn, transmits it to the central database managed by ThermoServer. The server
collects the readings from the wireless Cobalt modules. Wireless repeaters may be
used, if necessary, to extend the range between sensors and the receiver.
The ThermoClient application enables you to manage system configuration and all
actions related to sensors, data, and users. Installed on PCs in your network,
ThermoClient accesses the server with the central database containing sensor readings
and all other system information.
At any time, your Cobalt monitoring system may alert you in case of an anomaly, such
as a temperature reading that has gone outside an acceptable range, or another type of
technical problem, such as a low module battery or disconnected sensor. ThermoClient
offers many different options to handle alerts, including a highly visible screen display to
show problems prominently. Color coding enables you to identify the severity of an alert
on-screen quickly. Other alert features include the use of wireless sirens, dry contact
devices, voice and text messages on your telephone, e-mail, fax, and more.
Receivers / repeaters
• USB receiver (plugged into computer running
ThermoServer)
• TCP/IP receiver (located on the same TCP/IP network
as the computer running ThermoServer
• Standalone repeater (placed between receiver and
wireless module)
Alert devices
• Wireless siren (audio/visual alert)
• Dry contact device
• Telephone modem (voice message alert or SMS text
message)
• ThermoClient
(installed on as many computers as required)
• ThermoServer
(one central server per site)
• Alarm Management System
(service running on server computer)
• SmartService
(running on the server, one instance per receiver,
named “emul_<receiver name>” for each receiver)
• MySQL
(database that stores all system information and
collected data)
• WatchDog (optional)
Utility service that ensure proper system operation
by monitoring the database (you will find the
software and user guide on the ThermoServer /
ThermoClient CD-ROM starting with version 5.0 of
the solution)
Version Architecture
Windows® Server 2016 64-bit
Windows® Server 2012 and 64-bit
2012 R2
Windows® Server 2008 and 32-bit and 64-bit
2008 R2
Windows® Server 2003 32-bit and 64-bit
Windows® 10 (*) 32-bit and 64-bit
Windows® 8 32-bit and 64-bit
Windows® 7 32-bit and 64-bit
(*) Requires Windows 10 version 1607 with cumulative update KB3206632 or higher
• Copied and pasted from the computer running ThermoServer to the desired
location on your own hard drive
As a standalone application, this application does not require the presence of other
installed files, such as DLLs, to operate.
21.3 Services
To check the status of service applications on the computer running ThermoServer:
Please refer to your specific computer operating system documentation for information
on accessing services.
By default, these services are configured to restart automatically when your computer
boots, ensuring reliable intervention-free operation.
21.3.1 MySQL
Notes:
• Check with your IT service for advanced tools or help with additional MySQL
configuration.
21.3.2 SmartService
One instance of the SmartService service runs for each receiver configured in your
ThermoServer/ ThermoClient system. This service ensures the independent and
simultaneous operation of each receiver.
21.3.3 ThermoServer
ThermoServer is the heart of the Cobalt wireless monitoring system. This application
transmits the data collected from Cobalt modules (via receivers) to the MySQL database.
It manages all system settings, users, and alarms. By default, ThermoClient applications
connect to ThermoServer via the TCP port 11000. This port may be changed if
necessary.
Starting with version 5.0, ThermoServer no longer has a user interface of its own. All
system configuration is handled from within ThermoClient (with key features limited to
the ThermoClient instance running on the server computer).
21.3.5 WatchDog
• Checking at regular intervals to make sure that data is being collected in the
system database as expected.
22 Preventive Maintenance
Guidelines
This section describes specific product considerations and actions to help you ensure
optimal operation of your Cobalt monitoring system over time.
This section describes how Cobalt modules can be added automatically using an
integrated Service Discovery Protocol (SDP). The diagram below shows the basic
operating procedure for the SDP process:
This table presents our recommendations for adding modules for an initial installation:
In the example below, each of the Level 1 modules (those closest and directly connected
to the receiver) are repeaters for several Level 2 modules. Here, the system could be
optimized by adding a repeater. In this case, with automatic reconnection activated in
ThermoClient, battery life in the Level 1 modules is protected, yet the Level 1 modules
could serve as repeaters if there is a problem with the dedicated repeater.
In the example below, only one of the Level 1 modules (those closest and directly
connected to the receiver) is setup as a repeater. If the Level 1 module acting as a
repeater stops communicating, the Level 2 modules automatically reconfigure their route
to the receiver via the other Level 1 module.
On the other hand, the load in this case could be balanced better by configuring two of
the Level 2 modules on one of the Level 1 modules, and the other Level 2 module on
the second Level 1 module.
The configuration below illustrates a situation that can be improved by moving or adding
a receiver. In this case, the last link between the Level 1 module and the receiver can
be considered a critical path for multiple modules. In this example below the data load
will shorten the module battery life. In addition should the level one module fail, there
will be no additional path for automatic reconnection.
Figure 54 – The Level 1 repeater represents a critical path for this network
branch
This same network branch can be optimized by placing the receiver in a more central
location. This also reduces battery consumption in Level 1 modules.
Another option is to add another receiver (depending on the real number of end-points
in your network).
In order to set up the wireless paths in your monitoring system, it is useful to keep in
mind some of the basics of Hertzian radio wave propagation, particularly when setting
up repeaters to achieve optimal range. In real-world environments, signals are
attenuated by absorption, reflection, refraction, and diffraction.
When a radio wave encounters an obstacle, part of its energy is absorbed, while part
continues to propagate in an attenuated manner. Part may also be reflected. Signal
attenuation during transmission is referred to as power loss. Attenuation increases with
distance. In addition, when radio waves collide with obstacles, the attenuation value
depends largely on the type of obstacle. Metallic obstacles reflect radio waves strongly,
while water largely absorbs the signal.
The weakening of wireless signals is largely due to the properties of the environment
crossed by the radio waves. This table shows some sample attenuation properties for
various materials:
• Hollow, lightweight walls loosely filled with insulating wool on metal foil
• Raised flooring
Fire-safety walls and doors, elevator shafts, staircases and supply areas should be
considered as obstacles with a screening effect. Avoid this effect by repositioning the
receiver or module (see first image below) to avoid the radio shadow; or by using a
repeater (second image below).
Angle of penetration
The angle at which the transmitted signal penetrates the wall is very important. The
effective wall thickness – thus the signal attenuation – varies according to the angle of
penetration (first image below). Signals should be transmitted as directly as possible
through walls. Wall niches should be avoided. Avoid an undesirable angle of penetration
by repositioning the receiver or by using a repeater (second image below).
Receiver placement
Receivers should not be installed on the same side of the wall as the module. Near a
wall, the radio waves are likely to be subject to interfering dispersions or reflections.
Consequently, position the receiver on the opposite or connecting wall.
The distance between receivers and other transmitters (e.g. GSM / DECT / wireless
LAN) or high-frequency sources of interference (computers, audio and video equipment)
should be at least 40 centimeters.
Oceasoft products use the license-free ISM band (Industrial Scientific Medical). This
frequency is reserved for remote monitoring-type applications, and is different from
those used for cellular telephones and wireless land-line phones (DECT), and those
used for Wi-Fi and Bluetooth wireless protocols. There is therefore no risk of frequency
interference or disturbance with these types of devices. The wireless system used in
Oceasoft products complies with current international standards and regulations for
each country in which they are sold.
For optimal operation, follow these recommendations when physically placing your
device:
• Do not place the module at a distance less than 40 cm (16 in.) of another
module.
• Make sure the wireless module is not placed on an electrical conduit or cable
tray.
• For best results, place the module so that it faces the general direction of the
receiver antenna.
• Keep about 20 cm (8 in.) of clear space around the module. A module that is
placed between two refrigerators of close proximity may not communicate
effectively.
22.1.3.1 IQ/OQ
3. Make sure you return your sensors and modules to their original state when
done.
When preparing Cobalt modules for use in sterile environments, you may clean the
module with a soft cloth using a variety of products, described in the table below. The
different parts of the Cobalt module that may be sensitive to such products are:
Transparent
window over LCD
Casing
Radiation
Radiation
Solvents
Alcohols
Carbons
Gamma
Organic
Strong
Alkalis
Alkalis
Hydro
Weak
Fuels
UV
Module casing:
Polycarbonate/ABS E G G F P P P P G F
Alloy PC/ABS
Seal / button:
Saturated Styrenic
Block Copolymer E G E G P F P P P F
Thermoplastic
Elastomer SEBS
Transparent
Window
G G G G P F P F F F
Acrylic/Polycarbonat
e Alloy PC/PMMA
Temperature Power /
sensor plug CO2 detector opening communication
cable plug
• All Cobalt products that use a power adapter should also be plugged into a
UPS.
• Weekly manual system testing (e.g., disconnect a sensor from its Cobalt
module, verify that the alarm system is working) should be performed as
defined in your Standard Operating Procedure (SOP).
• If you are storing cold products, Oceasoft recommends use of a back-up cooling
system (e.g., CO2 or LN2) to maintain freezer chamber temperature below the
critical level should a power failure occur. Contact your local sales
representative for more information.
• When routing cable for the Cobalt sensor (if necessary), cabling should be
placed with no less than a minimum of 5 cm (2 inches) distance from high
voltage components. Also, avoid running the sensor cable in parallel with high
voltage wiring.
Cobalt modules must be handled with care to avoid damaging them. In particular, avoid
dropping the modules or other equipment and do no subject them to undue shock, even
light shock. Make sure that any cables used for Cobalt modules, repeaters, and
receivers (sensor, power, and network cables…) are firmly attached and will not be
yanked unintentionally.
• Do not spray CO2 modules with liquid cleaners. Use a soft cleaning cloth as
described in the preceding section.
22.1.3.4.2 Differential pressure module care
• Disconnect the plastic tubes from the Cobalt module before decontaminating a
room in which pressure is being monitored. This is to avoid potential damage
to the internal sensor by intaking aggressive solvents or cleaning products.
Cobalt modules offer a simple interface comprised of an LCD screen and a pushbutton,
as described here (for normal operation):
= 10% = 0%
= 40% = 30%
= 70%
= 50%
= 100%
= 70%
= 100%
Sensor name or
serial number Latest sensor reading
(also displays
status message
for alarms) Multi-function push-
button
1. Short-press for on
demand read and to
display first sensor
then second sensor
(on 2-sensor
modules)
2. Long-press (at least
3 seconds) triggers
attempt to connect
via SDP (this can be
done any time, but
Figure 61 – Cobalt module LCD screen overview
we recommend only
doing it upon initial
installation). This
also starts
datalogging with
default values if not
currently running.
In case of a sensor alarm, the LCD on the Cobalt module displays information
concerning the detected alarm.
Alarm icon
Alarm description
The module displays a specific message for each alarm that is detected. These
messages appear on the bottom line of the LCD.
HIGH VALUE A reading is above the high limit value (after time delay, if
configured).
LOW VALUE A reading is below the low limit value (after time delay, if
configured).
SENSOR FAIL The sensor is not working, or no sensor was detected.
22.1.4.3 Short-press
22.1.4.4 Long-press
A long-press of three seconds or more on the Cobalt module button initiates automated
module installation into your monitoring network using the integrated Service Discovery
Protocol. The sensor is then visible within the ThermoClient application. The long-press
also begins logging readings in module memory if the module had been stopped.
Datalogging starts with the parameters already present in memory (in particular, the
reading interval, alarm limits, and correction values). Default parameters are used if the
long-press is done before any other module configuration.
35=Temperature/humidity
F: Frequency: 4 or 6 = 915 MHz; 3 = 868 MHz or 867 MHz (refer to module label); 9
= 434 MHz
• 2: Not used
• 4: CO2 / Temperature
• 5: 4-20 mA
• 6: Dry contact
• 7: 0-5V
• 8: Not used
• 9: Not used
• A: Pt100 sensor
• B to F: Not Used
For example: 051750610000 = first digital temperature module operating at 915 MHz,
manufactured in 2010 and programmed with bench #5.
• Regular PT100 sensor, typically used for -80°C ULT Freezers: blue (-
100/+150°C)
22.1.4.7 Battery
When evaluating battery life, the system does not actually query a module to check the
current battery strength. This method would actually consume battery power
unnecessarily and is incompatible with our goal to provide extremely long battery life in
Cobalt modules. To estimate remaining battery capacity, the system performs a
calculation based on wireless activity, sensor readings, and standby time.
Here are other relevant details regarding the batteries in Cobalt modules.
Construction and visual aspect The LS 17500 cell is constructed using concentric
electrode “bobbin” technology. Cell is hermetically
sealed with a sturdy glass-to-metal seal (≤ 10-7
atm.cc/sec under 1 atm. He). When inspected by
the naked eye, the LS 17500 cell should not show
any trace of dents, swelling, corrosion or
electrolyte leakage. Marking should be readable.
The table below shows the storage capacity for readings in Cobalt module memory
based on the sample rate (measurement frequency).
22.2.2 Daily
• Launch the ThermoClient application every day. Make sure that all sensors are
read at least once per day by one or more users.
• Alarm because datalogging is stopped for the sensor (not consistent with
configuration stored in the ThermoClient application), see instructions for error
code -991 (later in this document). Make sure that no alerts are related to a
technical problem with the receiver:
o Alarm caused by an absence of communication with the receiver: See
instructions for error code -996 (later in this document).
o Alarm caused by an absence of communication with the Smart-Service for
the receiver in question: see instructions for error code -995 (later in this
document).
o Make sure that no alerts are related to technical alarms on alert devices
(or labeled "Media error").
o Absence of communication with the telephone modem: see instructions
for error code -994 (later in this document).
• Check the alarm list to see which alarms must be acknowledged, then
acknowledge the alarms for which the problem has been resolved.
22.2.3 Weekly
• Generate a technical alarm for a receiver fault in order to make sure that the
configured alert chain operates as expected.
• If you have one or more critical devices, generate a technical alarm for an
module fault. Run this alarm for a group containing one or more critical
devices.
• Generate a limit alarm for a group that contains critical devices. Make sure that
the alert is transmitted reliably for each alarm you generate.
22.2.4 Monthly
ThermoClient can be used to run a wireless performance test, checking all modules in
a user’s view. All modules must have a signal strength of 50% or higher. Repeat the
operation for modules whose signal is weaker than 50% (by double-clicking on the line
with module(s) in question) to check the signal strength again. If you get the same results
three times, you can conclude that the signal is in fact too weak.
• Generally speaking, you can improve signal quality by adding one or more
repeaters, or sometimes simply by moving the various elements in the wireless
path slightly, or moving the module itself as described earlier in this document.
• For networks with 15 modules or less, you may improve signal strength by re-
running the automatic installation procedure using the SDP sequence
described earlier. ATTENTION: this process could result in changes to the
wireless path for your modules, which may also change sensor group
configuration. If you run automatic installation, you must check to make sure
that a given module’s alert strategy, based on its sensor group, is configured
properly.
Generate a report
• Create a monthly sensor report. The average, highest, and lowest values are
important pieces of information to ensure the proper operation of your devices.
Complete system backup
• For the Cobalt CO2 module, unplug the AC adapter and make sure battery is
still functional. If not, change the battery and re-transfer module settings.
Make sure you download data from the module before unplugging
the AC adapter, as if the battery is indeed empty, any new
readings stored in module memory will be lost.
• For wireless sirens, run test alarms on a regular basis (such as before long
vacations) and change the batteries yearly.
Calibration
• Check the status of all cables, particularly flat cables. There must be no visible
damage. Mounting systems must be secure and hold modules and sensors
firmly.
Database archive
• Use ThermoClient to archive your data. This will also generally improve overall
system performance.
UPS maintenance in compliance with manufacturer recommendations
• Flat cables should be changed every five years, even if they appear intact on
the outside. Cable wear may be hidden inside.
23 Troubleshooting
23.1 Technical alarms
Complete list
140 | Troubleshooting
Administrator Guide for Cobalt Wireless Monitoring System
Troubleshooting | 141
Administrator Guide for Cobalt Wireless Monitoring System
142 | Troubleshooting
Administrator Guide for Cobalt Wireless Monitoring System
Troubleshooting | 143
Administrator Guide for Cobalt Wireless Monitoring System
24 Contact information
Depending on your support license, you may contact OCEASOFT technical support for
assistance. You may contact OCEASOFT technical support directly.
3. Click on Attach trace files if you want to include technical trace files as a .ZIP
file attachment with your e-mail. This information is often very helpful for support
staff.
E-mail: [email protected]
E-mail: [email protected]
www.oceasoft.com