radio sensor system user manual version 4.2 august 2015
TRANSCRIPT
Page 1 of 83
Sontay® SonNet Radio Sensor System
User Manual
Version 4.2
August 2015
Page 2 of 83
Audience This manual is intended for specifiers, users and installers of the Sontay® SonNet radio sensor system. Content This manual provides a complete reference for the Sontay® SonNet radio sensor system. Related Documents The Sontay® SonNet radio sensor system Site Survey Kit Quick Start Guide The Sontay® SonNet radio sensor system Site Survey Kit Manual The Sontay® SonNet radio sensor system Quick Start Guide The Sontay® SonNet radio sensor system product datasheets
Page 3 of 83
Table of Contents:
Overview .................................................................................................... 5 Environmental .............................................................................................. 5 Battery Fitting and Replacement ........................................................................... 5 Disposal of Batteries ........................................................................................ 5 Devices Types ............................................................................................... 6
Battery Powered Nodes .......................................................................... 6 24V Powered Routers............................................................................. 8 230Vac Powered Routers ........................................................................ 10 The System Receiver ............................................................................. 11 The RF‐IOM ...................................................................................... 12
The Radio Network ........................................................................................ 14 Network Planning Considerations .............................................................. 15
The Radio System .......................................................................................... 17 Security .................................................................................................... 17 How the Self‐Healing Tree Network is Formed ........................................................... 17 Propagation Of Radio Signals in Buildings ................................................................ 18 Extension Aerials .......................................................................................... 19 FAQs ........................................................................................................ 20 Configuration & Monitoring Software .................................................................... 22
Important – Disabling Driver Signing Verification .............................................. 22 Windows 7 64‐bit ................................................................................ 22 Windows 8 ....................................................................................... 23 Windows 8.1 ..................................................................................... 23 Windows 10 ...................................................................................... 23 Installing CMS .................................................................................... 24 Starting CMS ..................................................................................... 27 Importing a Saved Layout ....................................................................... 28 The CMS Desktop Environment ................................................................. 29 Logging On as an Administrator ................................................................. 30 Changing the Administrator Password .......................................................... 30 Auto Configuration Mode ....................................................................... 31 Listing Devices ................................................................................... 32 Changing Device Labels .......................................................................... 33 Creating Analogue Output Channel Mapping .................................................. 34 Viewing Device Properties ...................................................................... 35 Changing Device Configurations ................................................................ 37 Configurable Parameters ........................................................................ 37 RF‐IOM Configuration ........................................................................... 39 RF‐IOM Status Tab ............................................................................... 39 Changing the input configuration ............................................................... 40 Changing the output configuration ............................................................. 41 Manually Authorising a New Node ............................................................. 42 Removing a Node from the Network ........................................................... 42 Using the Graphical Map Display ................................................................ 43 Setting the Map Display Background Image .................................................... 43 Adding Devices to the Map Display ............................................................. 44 Icon Plan ......................................................................................... 44 Device Status ..................................................................................... 45 Link Status ....................................................................................... 45 Auto Updating ................................................................................... 46
Page 4 of 83
Manual Refreshing Of Data ...................................................................... 46 Communications Log ............................................................................ 47 Changing Display Units .......................................................................... 47 Configuration Log ................................................................................ 48 Using CMS To Document A Wireless Network .................................................. 49 Saving and Opening Layouts .................................................................... 49 Receiver Print Preview ........................................................................... 50
SonNet‐Tridium JACE Driver Action Menus .............................................................. 51 Network Action Menu ........................................................................... 51 Receiver Action Menu ........................................................................... 51 Router Action Menu ............................................................................. 52 RF‐IOM Action Menu ............................................................................ 53 Sensor Action Menu ............................................................................. 54
Managing a Tridium JACE SonNet Wireless Network .................................................... 56 Requirements .................................................................................... 56 Installing the SonNet Driver to a Tridium JACE ................................................. 56 Adding a SonNet Network ....................................................................... 57 Prerequisites ..................................................................................... 57
Commissioning a SonNet Network ....................................................................... 58 Commissioning an Existing Network ............................................................ 58 Commissioning a New Network ................................................................. 59
Configuring Network Devices ............................................................................. 60 Device Prefixes ................................................................................... 60 Receiver .......................................................................................... 60 Routers ........................................................................................... 61 RF‐IOMs .......................................................................................... 62 Writing Output RF‐IOM Values .................................................................. 63 RF‐IOM Fallback Values ......................................................................... 63 End Devices (EDs) ................................................................................ 65 The VFC Activation Count Point ................................................................. 66
Commissioning Multiple Networks on the Same Site .................................................... 67 Pre‐commission each network away from site ................................................. 67 Commission each network individually on site ................................................. 67
Commissioning a SonNet System: A Step‐By‐Step Guide ................................................ 68 Best Practise Points .................................................................................. 70 Trouble‐Shooter’s Guide .................................................................................. 71 Estimating Network Coverage in the Absence of a Site Survey .......................................... 77
Attenuation Properties of Common Building Materials ........................................ 78 Strategy Tips ............................................................................................... 79 Alarms ..................................................................................................... 83
Page 5 of 83
Overview The wireless nodes are based on direct‐sequence spread spectrum communication in the 2.4 ‐ 2.5GHz band, compliant with IEEE 802.15.4‐2006. All nodes have a unique MAC address, equivalent to a unique serial number. All nodes have a PCB‐mounted on/off switch or jumper. All nodes retain their configuration properties across a power failure. Environmental
Storage temperature range of ‐10 to +80°C Storage relative humidity range of 0 to 90% (non‐condensing). Ambient (operating) temperature range of ‐10°C to +50°C Ambient (operating) relative humidity range of 0 to 90%, (non‐condensing).
Battery Fitting and Replacement When a battery is installed, or when it is replaced, observing the correct polarity is very important. Fitting the battery incorrectly may result in permanent damage to the device. Recommended batteries are 3.6Vdc 2.4Ah AA size Lithium‐Thionyl Chloride types for space housing sensors, or 3.6Vdc 2.1Ah 2/3 A size Lithium‐Thionyl Chloride types for plant housing sensors, and are not rechargeable. This type of battery should be stored in a clean, cool (not exceeding +30°C), dry and ventilated area. Disposal of Batteries ‐ Warning! Fire, Explosion and Burn Hazard Do not short‐circuit, crush, disassemble, heat above 100°C (212°F), incinerate, or expose the battery contents to water. Do not solder directly to the cell. NB ‐ All batteries must be disposed of in accordance with EC Directive 2006/66/EC, amended by EU Directive 2008/12/EC.
Page 6 of 83
Devices Types Battery Powered Nodes Battery powered sensor nodes are used in conjunction with the Sontay® RF‐RX20, RF‐RX40, RF‐RXS and RF‐RXS‐N receiver units, and if required (depending on installation topography), Sontay® RF‐RR series of routers. Data is transmitted back to the receiver at configurable time intervals, or on a configurable change in measured value. Each sensor retains these configurations if the battery becomes discharged or requires replacement. The sensors automatically find the best path back to the receiver, which may be directly to the receiver or via “parent” routers. To power a battery powered node, jumper J400 must be fitted. To switch off, remove J400. Battery powered nodes are available in 4 formats:
Space mounting temperature, with setpoint, momentary switch, fan speed, VFC input and CO2 options
o NB ‐ setpoint, momentary switch and fan speed options are not available with the CO2 option
Space mounting RH&T, with setpoint, momentary switch, fan speed, VFC input and CO2 options o NB ‐ setpoint, momentary switch and fan speed options are not available with the CO2
option
Plant mounting temperature
Plant mounting RH&T Space Mounting Specification: Radio Output: Frequency 2.4GHz 16 channels, automatically selected, direct‐sequence spread spectrum Compliance IEEE 802.15.4‐2006 Aerial Characteristics: Gain 1.2dBi VSWR 1.5:1 Data Encryption: AES 128 Power Output: 0dBm (1mW @ 50Ω) Accuracy:
Temperature ±0.3°C Optional RH ±3% RH Battery Type: 3.6V AA 2.4Ah Li‐SOCl2, non‐rechargeable Battery Life: >3 years (depending on configuration) Housing: Material: ABS (flame retardant) Dimensions: 115 x 85 x 28mm Environmental: Operating: Temperature: ‐10°C to +50°C RH: 0 to 90%, non‐condensing Storage: Temperature: ‐10°C to +80°C RH: 0 to 90%, non‐condensing Country of origin: UK Refer to product datasheets for installation instructions.
Page 7 of 83
Plant Mounting Specification: Radio Output: Frequency 2.4GHz 16 channels, automatically selected, direct‐sequence spread spectrum Compliance IEEE 802.15.4‐2006 Aerial Characteristics: Gain 2.0dBi VSWR 2:1 Data Encryption: AES 128 Power Output: 0dBm (1mW @ 50Ω) Accuracy:
Temperature ±0.3°C Optional RH ±3% RH Battery Type: 3.6V AA 2.4Ah Li‐SOCl2, non‐rechargeable Battery Life: >3 years (depending on configuration) Housing: Material: ABS (flame retardant type VO) Dimensions: 115 x 85 x 28mm Mounting: Holes 4mm spaced 85mm apart Protection: IP65 Environmental: Operating: Temperature: ‐10°C to +50°C RH: 0 to 90%, non‐condensing Storage: Temperature: ‐10°C to +80°C RH: 0 to 90%, non‐condensing Country of origin: UK Temperature Sensor Types: Duct Outside air Outside air with solar radiation shield
Immersion Strap‐on Flying lead
Refer to product datasheets for installation instructions.
Page 8 of 83
24V Powered Routers 24V powered routers are used in conjunction with the Sontay® RF‐RX20, RF‐RX40, RF‐RXS and RF‐RXS‐N receiver units, RF‐IOM IO modules and RF‐RS series of battery powered radio sensors, and are used to route signals from battery powered nodes and other routers to the receiver module, where the signal strength of a direct path is not sufficient for reliable communications. NB Each router can support a maximum of 16 “children”, which can consist of a maximum of 8 battery powered nodes and 8 routers, or up to 16 routers if there are no battery powered nodes. Consideration should be given on network planning for redundancy in case of router failure or damage. Data is transmitted back to the receiver at configurable time intervals, or on a configurable change in measured value. Each sensor retains these configurations if the battery becomes discharged or requires replacement. Routers automatically find the best path back to the receiver, which may be directly to the receiver or via other “parent” routers. To power a router, jumper J200 must be fitted. To switch off, remove J200. 24V powered nodes are available in 5 formats:
Space mounting temperature, with setpoint, momentary switch, fan speed, VFC input, PIR and CO2 options
o NB ‐ setpoint, momentary switch and fan speed options are not available with the CO2 option
Space mounting RH&T, with setpoint, momentary switch, fan speed, VFC input, PIR and CO2 options o NB ‐ setpoint, momentary switch and fan speed options are not available with the CO2
option
Plant mounting with no sensor functions
Plant mounting temperature
Plant mounting RH&T Space Mounting Specification: Radio Output: Frequency 2.4GHz 16 channels, automatically selected Direct‐sequence spread spectrum Compliance IEEE 802.15.4‐2006 Aerial Characteristics: Gain 1.2dBi VSWR 1.5:1 Data Encryption: AES 128 Power Output: +10dBm (10mW @ 50Ω) Accuracy:
Temperature ±0.3°C Optional RH ±3% RH Power Supply: 24Vac/dc Housing: Material: ABS (flame retardant) Dimensions: 115 x 85 x 28mm Environmental: Operating: Temperature: ‐10°C to +50°C RH: 0 to 90%, non‐condensing
Page 9 of 83
Storage: Temperature: ‐10°C to +80°C RH: 0 to 90%, non‐condensing Country of origin: UK Refer to product datasheets for installation instructions. Plant Mounting Specification: Radio Output: Frequency 2.4GHz 16 channels, automatically selected, direct‐sequence spread spectrum Compliance IEEE 802.15.4‐2006 Aerial Characteristics: Gain 2.0dBi VSWR 2:1 Data Encryption: AES 128 Power Output: +10dBm (10mW @ 50Ω) Accuracy:
Temperature ±0.3°C Optional RH ±3% RH Power Supply: 24Vac/dc Housing: Material: ABS (flame retardant type VO) Dimensions: 115 x 85 x 28mm Mounting: Holes 4mm spaced 85mm apart Protection: IP65 Environmental: Operating: Temperature: ‐10°C to +50°C RH: 0 to 90%, non‐condensing Storage: Temperature: ‐10°C to +80°C RH: 0 to 90%, non‐condensing Country of origin: UK Temperature Sensor Types: Duct Outside air Outside air with solar radiation shield
Immersion Strap‐on Flying lead
Refer to product datasheets for installation instructions.
Page 10 of 83
230Vac Powered Routers The 230Vac powered RF‐RR‐MPR routers can be used in conjunction with the Sontay® RF‐RX20, RF‐RX40, RF‐RXS and RF‐RXS‐N receiver units, RF‐IOM IO modules, 24V powered RF‐RR routers and RF‐RS series of battery powered radio sensors, and are used to route signals from battery powered nodes and other routers to the receiver module, where the signal strength of a direct path is not sufficient for reliable communications. NB Each router can support a maximum of 16 “children”, which can consist of a maximum of 8 battery powered nodes and 8 routers, or up to 16 routers if there are no battery powered nodes. Consideration should be given on network planning for redundancy in case of router failure or damage. NB ‐ the RF‐RR‐MPR 230Vac has no sensor capability. Specification: Radio Output: Frequency 2.4GHz 16 channels, automatically selected Direct‐sequence spread spectrum Compliance IEEE 802.15.4‐2006 Aerial Characteristics: Gain 2.0dBi VSWR <2:1 Data Encryption: AES 128 Power Output: +10dBm (10mW @ 50Ω) Power Supply: 85 – 240Vac @ 50/60 Hz Housing:
Material: ABS (flame retardant) Dimensions: 116 x 106 x 52mm
Environmental: Ambient: Temperature: ‐30°C to +70°C RH: 0 to 90%, non‐condensing Protection: IP30
Page 11 of 83
The System Receiver The SonNet® receiver collects data from all other devices on the radio network, including measurements from sensors, link quality for all links formed in the network, battery levels for all battery powered devices, hours run for all devices and the current status of all devices. NB Each receiver can support a maximum of 16 “children”, which can consist of a maximum of 12 battery powered nodes and 4 routers, or up to 16 routers if there are no battery powered nodes. A USB socket is provided for connection to a PC or laptop running the Sontay SonNet CMS software (not RF‐RXS‐N). NB ‐ If the USB port of an RF‐RXS receiver is connected, the 9‐way serial port is temporarily disabled until the USB port id disconnected again. Receivers are available in 4 formats:
RF‐RX20 ‐ 20 x 0‐10Vdc analogue outputs RF‐RX40 ‐ 40 x 0‐10Vdc analogue outputs RF‐RXS ‐ Serial output and USB port for use with CMS RF‐RXS‐N ‐ Option card for Tridium JACE controllers
Receiver Specification: Radio Output: Frequency 2.4GHz 16 channels, automatically selected Direct‐sequence spread spectrum Compliance IEEE 802.15.4‐2006 Aerial Characteristics: Gain 2.0dBi VSWR 2:1 Data Encryption: AES 128 Power Output: +10dBm (10mW @ 50Ω) Analogue Outputs:
RF‐RX20 20 x 0‐10Vdc analogue outputs @10mA max. each RF‐RX40 40 x 0‐10Vdc analogue outputs @10mA max. each Analogue Output ranges: Temperature ‐10°C to +70°C RH 0% to +100% Setpoint 0% to +100% Switch 0Vdc = OFF, 10Vdc = ON Power Supply: 24Vac/dc Environmental: Operating: Temperature: ‐10°C to +50°C RH: 0 to 90%, non‐condensing Storage: Temperature: ‐10°C to +80°C RH: 0 to 90%, non‐condensing Country of origin: UK Refer to product datasheets for installation instructions.
Page 12 of 83
The RF‐IOM The RF‐IOM has no “intelligence”, but merely acts as local I/O with connectivity to typical HVAC equipment such as fan coil units (FCUs) and variable air volume (VAV) boxes. The RF‐IOM reads its digital and analogue inputs and transmits the values wirelessly to a BMS controller via either a SonNet V2 serial receiver or a SonNet option card receiver. The RF‐IOM receives its output values wirelessly from a BMS controller via either a SonNet V2 serial receiver or a SonNet option card receiver. Additionally, the RF‐IOM has full router functionality. Typically, a simple system will consist of;
Battery powered EDs
Powered routers (if required)
SonNet V2 serial receiver or a SonNet option card receiver
RF‐IOMs The EDs (and routers, where applicable) operate in the normal way. Data from the receiver is made available to the controller via a serial link. The SonNet data points are then used by the controller as part of a control strategy, which will typically calculate heating and cooling demands, damper positions etc. These calculated control values will then be passed back to the receiver via the serial link and passed from the receiver over the wireless network to the RF‐IOM. The RF‐IOM outputs are defined as points in the JACE so that their values can be set by the control strategy via the receiver. Note that the RF‐IOM cannot be used with the RF‐RX20 or RF‐RX40 receivers. RF‐IOM Specification: Radio Output: Frequency 2.4GHz 16 channels, automatically selected Direct‐sequence spread spectrum Compliance IEEE 802.15.4‐2006 Aerial Characteristics: Gain 2.0dBi VSWR 2:1 Data Encryption: AES 128 Power Output: +10dBm (10mW @ 50Ω) Power Supply: 24Vac/dc Inputs: 4 x universal inputs; 4‐20mA (loop or externally powered), into 750Ω maximum impedance 0‐10Vdc, into 4k7Ω minimum impedance Resistive, 1.5kΩ min to 60kΩ max Digital, VFC Outputs: 4 x 0‐10Vdc linear, @ 20mA per output LED Indication: Network Data Digital input Housing: DIN Rail H86mm x W58mm x L104mm (excluding aerial) Environmental: Operating: Temperature: ‐10°C to +50°C RH: 0 to 90%, non‐condensing
Page 13 of 83
Storage: Temperature: ‐10°C to +80°C RH: 0 to 90%, non‐condensing Country of origin: UK
The Rad A Sontperman Routerssensorsother roat all tipowere
The recbattery RF‐IOMbe batte
dio Network
tay® SonNet nently powere
s, though pers functions. Roouters. RF‐IOMmes to allow ed sensors onl
ceiver can sup powered nod
Ms and routersery powered
radio systemed routers.
rmanently poouters, RF‐IOMs and routesignals from ly “wake” for v
pport a maxides, plus up to
s can support nodes, plus up
m is comprise
wered, can aMs and sensors are require“child” nodevery short per
mum of 16 do 4 routers.
a maximump to 8 routers
Page 14 of 83
ed of a rece
also have senors can eithered to be perms to be instanriods to send
directly conne
of 16 directlys.
eiver, battery
nsing elementr communicatmanently powntly forwardedata.
In the schem5 children eTheir parentchildren andnumber of the receiver.
ected “child”
y connected “c
powered se
ts, accomplishte directly witered as they d to their “pa
matic above, reach, all battet is the receid R8 has 4 chnetwork dev.
devices, of w
child” devices
There can bof 8 layenetwork annodes per nRX series of
ensors, RF‐IO
hing both routh the receiveneed to stay arent” nodes.
routers R2 to ery powered iver. Router Rhildren, givingvices of 50, i
which only 12
s, of which on
be a maximumrs of routernd a maximumnetwork withf receivers.
Ms and
uter and er or via “awake” . Battery
R7 have sensors. R1 has 6 g a total ncluding
2 can be
nly 8 can
m depth rs in a m of 150 the RF‐
Note thand rou When pThis eapowereneededremovedevices See thesensor s Networ When pbe capa Exampl Conside
hat battery pouters, and not
planning a Sonsy‐to‐use paced sensors andd to ensure rees any guessws required.
e Sontay® SonNsystem Site Su
rk Planning Co
planning a Soable of handlin
e:
er a network w
owered device through othe
nNet radio neckage allows d the receivereliable commuwork from pl
Net radio sensurvey Kit Man
onsiderations
nNet radio syng the conseq
with a require
es can only roer battery pow
twork, it is reinstallers to tr prior to instaunications beanning a syst
sor system Sitnual for full de
s
stem, it is alwquences of a r
ement for 16 E
Page 15 of 83
oute their signwered device
commended ttest signal stralling the full etween all devtem and allow
te Survey Kit Qetails.
ways worth corouter failing o
EDs:
nals to the reces.
that the Sontarengths betwesystem. It canvices on the nws the instal
Quick Start Gu
onsidering theor being dama
1. At directly comaximum orphaned.
2. A sgives no red
ceiver directly
ay® SonNet Siteen locations n also identifynetwork backler to order
uide and The
e placement oaged.
least one rouonnected EDlimit of 12.
single router dundancy if th
y or through
te Survey Kit s required fory whether rouk to the receivexactly and o
Sontay® SonN
of routers, and
uter is requireDs will exce Four EDs
(R1) will wohe router shou
RF‐IOMs
be used. r battery uters are ver. This only the
Net radio
d should
ed, as 16 eed the will be
ork, but uld fail.
Page 16 of 83
3. Opand R2.
4. If network caorphaned Erouter.
timal networ
either of thn still be mEDs can re‐r
rk uses 2 rou
he routers fmaintained, aroute via th
uters, R1
fail, the s the 2 e other
Page 17 of 83
The Radio System The radio system used by the Sontay SonNet devices is divided into 3 sections or ‘layers’.
1. The radio layer is where physical control of the radio signal is done. This conforms to international standard 802.15.4, and determines the frequency of the radio signals, the number of ‘channels’ available for use, the bandwidth and power level of the signal etc. There are 16 channels available, and the best one is automatically selected by the receiver. The frequencies used are in the ISM (Industrial, Scientific and Medical) 2.4GHz band, with a maximum data rate of 250kb/s. 2. The network management layer is where the self‐healing tree functionality is run, which controls network topology. ‘ZigBee’ is an example of a network management MESH protocol. SonNet does not use ZigBee, but instead uses a ‘self‐healing tree’ protocol to control network topology. 3. The application layer determines what the device does – i.e. makes it a temperature sensing device, a router or a receiver. SonNet devices use specific applications, and include features such as configuration properties.
Security All SonNet system devices have the same, unique network identifier. Only devices with the correct ID will be allowed to join the network. The ID used by system devices is different from the ID used for site survey kit (SSK) devices. Hence, SSK devices cannot join a system network and vice versa. When a SonNet system network has been formed, it can be ‘locked’ to prevent any unauthorised devices joining, even if they are SonNet devices. The CMS can be used to subsequently authorise extra SonNet system devices if required. All data transmitted by SonNet devices is encrypted. How the Self‐Healing Tree Network is Formed The network is formed based on 3 rules, and in a specific order of priority.
1. How many ‘tiers’ a device is away from the receiver. If a device can communicate directly with the receiver, it will, even if the link quality is poorer than if it went through a router. If a device has a choice of more than one router, it will always choose the router closest to the receiver (the least number of tiers away), even if the link quality is poor. 2. The number of ‘child’ devices a router already has. A RF‐IOM or router can have a maximum of 16 ‘children’. If a device has a choice of more than one router of the same tier level, it will always choose the router with the least number of children, even if the link quality is poor. 3. Signal Strength (link quality). Finally, if a device has a choice of more than one RF‐IOM or router of the same tier level and the same number of children, it will choose the router with the best link quality. If, for any reason, a device (ED, RF‐IOM or router), loses its preferred path back to the receiver, it will automatically search for an alternative – still obeying the 3 rules above in sequence. If, despite employing Direct Sequence Spread Spectrum (DSSS) techniques, interference on the currently occupied channel prevents communications, the receiver will automatically look for another channel which is clear. All other devices, having lost their links to the receiver, will then also automatically scan the 16 channels until they find the receiver again, and the network will re‐form without user intervention.
Propaga The pro Attenua
Reflecti
Scatteri
ation of Radio
opagation of m
ation
ion
ing
Re
Transmit
o Signals in Bu
microwave rad
eceiver
tter
uildings
dio signals in a
Radio signal attenuated mmaterials typespecially ste
Depending otransmitter to ‘Multipath’ sreducing ove
Scattering th
Page 18 of 83
a building can
strength is attmuch more pically used ineel.
on the buildino the receiver
signals can herall received s
e radio signal
be affected in
tenuated whewhen passinn constructio
ng, radio signar, rather than
have the effesignal strength
can also redu
n several ways
en it passes thg through otn, such as br
als can take mjust one single
ect of cancellh.
uce its signal s
s:
hrough air. Sigther media, rick, stone, wo
many paths fe path.
ling each oth
strength.
gnals are such as ood and
from the
her out,
Page 19 of 83
Extension Aerials
When using the RF‐AERIAL‐PM2 or RF‐AERIAL‐PM5 extension aerials, it is important to observe some basic rules for siting and mounting.
1. Always ensure there is a much clear space around the aerial as possible. 2. Generally speaking, where possible mount the aerial as high as possible on the same floor as the
routers and EDs 3. Don’t mount between metal surfaces (for example steel I‐beams) in ceiling spaces 4. Wherever possible, mount the aerial on a metal ground plane (such as the top of a metal panel)
5. The coaxial cable used for the RF‐AERIAL‐PM2 or RF‐AERIAL‐PM5 extension aerials is semi‐rigid and should not be bent at too sharp an angle or too tight a radius. It is recommended that the minimum bending radius is 5cms
6. Always mount the aerial vertically. This produces the optimum radiation pattern and signal strength 7. Extension aerials can be used with receivers and RF‐IOM modules. 8. Aerial extensions should not exceed 5m to prevent excessive loss of signal.
Page 20 of 83
FAQs
a. How is access to the sensor network locked at the CMS? Nodes are only allowed to join the network if the receiver allows them to. This is true even if the nodes are identified as SonNet Nodes and have the correct encryption key. There are two methods to configuring the receiver to accept nodes on to the network. In order to authorise a node the CMS must be in administration mode (File‐>Switch Admin Mode must be ticked).
• Auto Commissioning Mode The CMS allows the receiver to be switched to auto commissioning mode. In this mode any nodes that can correctly identify themselves as SonNet nodes will be allowed to join the network. Any nodes that do join will be added to the CMS textual display.
• Manual Mode In manual mode individual nodes can be removed from or added to the authorised node list from the CMS. Manual mode is the default mode.
A node can then be authorised by Options‐>Authorise (add) a new node or selecting the same option on the right click menu in the Textual or Graphical parts of the application display. The user must type the MAC address (found on the PCB or product housing) of the new node into the dialog that appears and can also give the node a textual name (up to 10 characters)
b. Why do some menu items disappear if the CMS application is idle for some time? The CMS has a timeout that operates when in Admin mode. If there is no activity for some time the CMS application will exit admin mode and some admin menu items will be disabled or removed. The timeout can be set in Options‐> Change Idle Time. Admin mode can be entered again in File‐>Switch Admin Mode
c. The CMS application right click menu has stopped being provided. Why? This probably means that the CMS has detected that the receiver has been disconnected from the PC. This will be indicated on the status bar at the bottom left side of the CMS application window "Receiver Disconnected". In this state many of the CMS facilities are disabled until the Receiver is connected again.
d. How are the network node names stored, are they persistent? The node names are stored in the receiver’s non‐volatile memory. Therefore these will be the same even if a different PC is attached to the system, or the receiver is reset or power cycled.
Page 21 of 83
e. In the CMS application, what is an “Unknown” node? The application will list all nodes that have been added to the system as unknown initially. As soon as a node is added (either manually or by the use of auto commissioning mode) a request is sent to it to establish what type of node it is and what capabilities it has. As a result a node will be categorized as unknown until a response is received from it. If the node remains off‐line or does not respond for any other reason it will remain in this category. The CMS will send a request each time it is started if there are still unknown nodes in the system.
f. What are the ranges of the RF‐RX20 and RF‐RX40 receiver 0‐10Vdc outputs? Temperature ‐10°C to +70°C RH 0% to +100% Setpoint 0% to +100% Switch
0Vdc = OFF (False) 10Vdc = ON (True)
CO2 0 – 2000ppm Fan Speed 0Vdc = Off 2.5Vdc = Lo 5.0Vdc = Med 7.5Vdc = Hi 10.0Vdc = Auto
VFC 0Vdc = OFF (False) 10Vdc = ON (True)
PIR 0Vdc = Unoccupied (False) 10Vdc = Occupied (True)
Configu The CM
R E
R
R
It can a
The CM
NB It is
Impo Prior to Window
bcdeditbcdedit
uration & Mon
MS is connecte
Receiver outpED node para
o Configo User‐d
Router node po Configo User‐d
RF‐IOM node o Defaulto Send oo Analogo Input ao User‐d
lso be used fo
Enabling or Manually adProviding a Monitor devMonitor linkView logs fo
MS installation
Microsoft® SSontay® SonSontay® dev
important th
rtant: DO
o installing CM
ws 7 64‐bit
From the Stadministrat
Run the follo
t.exe ‐set loadt.exe ‐set TEST
Restart the desktop:
nitoring Softw
ed, via USB, to
put channel mmeters, includuration settinefined labels parameters, inuration settinefined labels parameters, it measuremeon value changgue output falalarm levels efined labels
or;
disabling autodding or remotext and grapvice status k and battery or receiver con
procedure in
SQL Server 20nNet CMS vice USB devic
at the CMS in
O THIS FIRS
MS, driver sign
tart menu, tyor.
owing comma
doptions DDISATSIGNING ON
PC. When lo
ware (CMS)
o a Sontay® RF‐
apping (not Rding; gs
ncluding; gs
including; nt data transmge settings l‐back values
omatic configoving nodes hical display o
quality nfiguration ch
stalls 3 compo
05 Express Ed
e drivers
stallation be c
ST – Disablin
ing may need
ype cmd.exe i
ands in the sh
ABLE_INTEGRI
ogged, the fo
Page 22 of 83
‐RX20, RF‐RX4
RF‐RXS)
mission time
uration mode
of the wireless
hanges
onents:
dition SP2
completed pri
ing Driver Sig
d to be disable
n the search
hell.
ITY_CHECKS
llowing will b
40 or RF‐RXS
e
s network
ior to connect
gning Verific
ed.
bar. Right cli
be displayed i
receiver, and
ting the PC to
cation
ck on cmd.ex
in the bottom
is used to con
o the receiver.
xe and choos
m right corne
nfigure:
e run as
er of the
Window
Window
Window
MicrosoSonNetNote thKnowlethe Win<Install
ws 8
Place the mbar to appe
Click Change
Click “Gene
Scroll down
Click “Troub
Click “Advan
Click “Wind
Click Restart
After the PC
The PC will r
ws 8.1
Place the mbar to appe
In the SearcOptions' Clic
Click 'Restar
After the PC
The PC will r
ws 10
Select “Rest
Hold down t
Once the co
From the op
From the op
Click the “Re
After the coenforcemen
The PC will r
oft® SQL Servet CMS and finahat there is aedge Base artindows Installe> button.
mouse (do notar, Then click
e Pc Settings.
ral”.
, and click “Re
bleshoot”.
nced Options”
ows Startup S
t.
C restarts, sele
reboot autom
mouse (do notar.
ch Box start tock on it.
rt Now' Under
C restarts, sele
reboot autom
tart” from the
the SHIFT key
omputer has r
ptions availab
ptions availab
estart” button
omputer has nt”. Choose “D
reboot autom
er 2005 Expreally the Sontayan issue with icle KB954459er Cleanup U
t click) at the the Settings (
estart now” u
”
Settings”
ect “Disable D
matically
t click) at the
o type 'Advan
r Advanced St
ect “Disable D
matically
e power option
while you clic
ebooted, choo
le, choose “Ad
le, choose “St
n
restarted, a lDisable driver
matically
ss Edition SP2y® device USB SQL Server 29 for full detatility to unins
Page 23 of 83
bottom‐rightGear icon).
nder “Advanc
Driver Signatur
bottom‐right
nced Start Up
tart Up'
Driver Signatur
ns menu from
ck Restart.
ose the “Trou
dvanced optio
tartup Setting
list of startupsignature enf
2 is installed f device driver2005 Express ails). To overcstall MSXML6
t‐corner of th
ed Startup”.
re Enforcemen
t‐corner of th
' and you sho
re Enforcemen
m the Start Me
ubleshoot” op
ons”
s”
p settings is aforcement” by
first, if not alrers. Edition SP2
come this, the SP2. When t
e screen and
nt” from the l
e screen and
uld see 'Chan
nt” from the l
enu.
tion.
available. “Disy pressing the
eady installed
and MSXML e CMS installathis message
wait for the
ist.
wait for the
nge Advanced
ist.
sable driver s F7 key.
d, followed by
6 SP2 (see Mation will offeappears, click
pop‐out
pop‐out
d Startup
ignature
y Sontay®
Microsoft er to run k on the
Installin
When tthe <Ac
ng CMS
the SQL Serveccept> button
er 2005 Expre.
ess Edition SP2
Page 24 of 83
2 installation
The instcontinu The nexthe “Wethe <Ne
NB It installation bthe PC to thwhich you connected tois complete. The CMS Windows XPThe CMS irequired proincludes Mic NB Youwith an adminstall the SServer Expre If SQL Servealready instinstallation w
window appe
tallation of SQes until comp
xt step in the ielcome to theext> button to
is importanbe completedhe receiver. Enare installingo the receiver
is compatibSP2 or later, Vinstallation Cogramme filerosoft® SQL Se
must be logministrator leSontay® CMS ss SP2.
r 2005 Exprealled on youwill be execute
ears, read the
QL Server 200lete.
installation pre SonNet CMS o continue.
nt that thd prior to connsure that thg the CMS r until the ins
ble with MVista and WinCD comes wes and driveerver Express
gged in to Wevel user accand Microso
ess Edition SPur PC, the foed.
e EULA and th
05 Express Edi
rocedure will dS Setup Wizard
e CMS nnecting he PC on is NOT tallation
icrosoft® ndows 7. with all ers, and SP2.
Windows count to oft® SQL
P2 is not ollowing
hen click
tion SP2
display d. Click
Select <
SonNet
<I Agree> and
t files are copi
then click the
ed to your PC
e <Next> butto
C.
Page 25 of 83
on to continue.
A separconnect To insta
rate window tion.
all these, click
opens to allo
the <Next> b
ow the install
utton to conti
Page 26 of 83
lation of the
inue.
Whebutt
2 device driv
en the installaton.
vers required
ation is compl
for the USB
lete, click the
receiver
<Close>
Starting When adevice. each tim
There a
g CMS
a receiver is fFollow these me a new rece
are 2 drivers to
first connectesteps to instaeiver is conne
o be installed,
ed to a USB pall the drivers cted to the PC
, follow the sa
Page 27 of 83
port and switcfor the receivC, as each USB
Whenbutto
ame procedur
ched on, the ver. NB ‐ This pB port on a re Select the op Select the oautomaticall
n prompted,on to continue
re for both dri
device managprocedure wilceiver has a u
ption shown (
ption shown ly”)
click the e.
vers.
ger will detecll need to be funique ID num
(“No, not this
(“Install the s
<Continue A
ct a new followed mber.
time”)
software
Anyway>
When t
Importi When fuseful if
If no layto and c
the CMS is sta
ing a Saved La
first run, the f an existing la
yout file is reqclick the <Ope
rted, the PC c
ayout
CMS may alsoayout has bee
quired, click then> button im
com port conn
o ask if the uen saved on a
he <Cancel> bmport it.
Page 28 of 83
nected to the
user requires site where th
button to cont
receiver USB
a saved XML e PC running
tinue, otherwi
port needs to
layout file toCMS has been
ise navigate to
o be defined.
o be importedn replaced.
o the saved la
d. This is
yout file
The CM The CM
and a g
MS Desktop En
MS desktop is d
raphical “map
nvironment
divided into 2
p” display.
parts, a textu
Page 29 of 83
ual hierarchica
al display
Logging
Changin
g On as an Ad
ng the Admin
ministrator
nistrator Passw
To en<View To en<View
To mmodifadmi<Swit
word
Page 30 of 83
nable the texw> then <Text
nable the grapw> then <Grap
make any chafy the grapnistrator. To dtch Admin Mo
The login boNB The desensitive). T
To change th<File> thenpassword, en<Update> bu
xt display patual Display>
phical display phical Display
nges to devihical display,do this, from ode>
ox appears. Tyefault admin This can be cha
he admin passn <Change nter your newutton to subm
anel, from th
panel, from t>
ice configurat you must the menu ba
ype in your alevel passw
anged once yo
sword, from tPassword>. w password ait the change,
he menu bar
the menu bar
tion or to crfirst log on
ar choose <Fi
dmin level paword is admiou have logge
the menu barEnter the
and confirm. C, or click <Can
choose
r choose
reate or n as an le> then
assword. in (case ed in.
r choose existing Click the ncel>.
Auto Co IMPORT When areceive If this inetwor To placadminis From thdenotes
The stalocked.
When trecommmake co To takeadminis From thbeside t This sec
ommissioning
TANT!
a new radio sr in automatic
s not done, trk without ma
ce the receivestrator.
he menu bars that this spe
atus bar of CM
the network mended that onfiguration c
e the receivestrator.
he menu bar,this option, an
cures the netw
g Mode
system netwoc commission
the network ianually autho
er and netwo
r, select <Optecial mode is e
MS displays w
has formed the receiver changes while
r and netwo
, select <Optind denotes th
work and ensu
ork is being cing mode for t
is treated as rising each de
ork in automa
tions> and clenabled
whether the r
Netw Auto‐
completely, and networke in auto‐comm
rk out of au
ons> and clichat this specia
ures that unau
Page 31 of 83
commissionedthe network t
secure, and wevice (this inv
atic commissi
ick <Auto‐com
receiver is in
work Locked
‐commissionin
and all devick be taken oumissioning mo
uto‐commissio
ck <Auto‐comal mode is disa
uthorised nod
d for the firstto form.
will not allowvolves enterin
ioning mode,
mmissioning
auto‐commis
ng mode
ces can be vut of auto‐comode. This may
oning mode,
mmissioning Mabled.
des cannot joi
time, it is ad
w any nodes ong the device
ensure you
Mode>. A tic
sioning mode
iewed in themmissioning mcause netwo
ensure you a
Mode>. There
n the network
dvisable to p
or routers to MAC address
are logged o
ck beside this
e or if the ne
e CMS, it is mode. Do NOrk errors.
are logged o
should not b
k.
lace the
join the s).
on as an
s option
twork is
strongly OT try to
n as an
be a tick
To prevout afteor to ch
Removibe chan List Dev In the tdevices
Each ca The “Ueither bhas detare fittebe place Note thdisplay
vent leaving Cer the time sehange the time
ing the tick thnged.
vices
text display pas are divided in
Receiver
ategory can be
nknown” cateby auto‐commtermined the ed (such as seed in its appro
hat for the RF(see screen sh
MS in an admet in the “Chaneout value, fr
he Enable Idle
anel on the lento 4 main ca
e expanded to
egory is initiamissioning or mtype of devicetpoint). Wheopriate catego
‐IOM, if an inhot above).
min state whennge Idle Timeom the menu
Time Out box
eft of the windtegories, rece
Routers
o view more d
lly populated manual authoe trying to jon CMS has deory.
put is in an a
Page 32 of 83
n not supervis” setting expiu bar choose <
x disables adm
dow, a list of eiver, routers,
etail or collap
by devices worization. Devioin (for exampetermined this
larm conditio
sed, the admires. To disable<Options> the
min timeout f
all devices onRF‐IOMs and
EDs
psed to hide d
which are joinces are held iple, a router os information,
on, that input
n log‐in statue this feature n <Change Idl
eature. The ti
n the networkbattery powe
etail.
ing the netwon the unknowor node) and w the device w
will be displa
us automatica(not recommle Time>
imeout value
k can be foundered sensor no
RF‐IOMs
ork for the firwn category uwhich option
will then autom
ayed in red in
lly times mended),
can also
d. These odes.
rst time, ntil CMS s, if any, matically
the text
Changin NB ‐ Doerrors. Each derouter a
In the < NB The
ng Device Lab
o NOT try to m
evice, when fia more meani
<Name> box, t
re is a limit of
bels
make configura
rst depicted iingful label, ri
type in the ne
f 10 ASCII cha
ation changes
n the CMS, haght click on th
ew name you r
racters for sen
Page 33 of 83
s while in auto
as a default lahe router and
require and cl
nsor names.
o‐commission
abel, such as “choose <Prop
lick the <Chan
ing mode. Th
“Router1” or “perties>
In the <the newand clbutton. NB TheASCII chnames. To give meaningon the <Propert
nge> button.
is may cause
“Sensor2”. To
<Name> box, w name you lick the <C
ere is a limiharacters for
e a sensor gful label, rigsensor and
rties>
network
give the
type in require
Change>
t of 10 r router
a more ght click choose
Creatin Do NOT Each seThese v Parame
To map
Repeat
g Analogue O
T try to map o
ensor has at lvalues need to
eters which ca
TemperaturRelative HumSetpoint levMomentaryCO2 PIR Status (rVFC status Fan Speed V
o OFo Lowo Meo Hi o Au
these parame
this operation
Output Chann
output channe
east one meao be “mapped
n be mapped
e midity vel y switch status
routers only)
Value. The follF = 0V w = 2.5V ed = 5.0V = 7.5V to = 10.0V eters, first sel
n for all device
el Mapping (n
els while in au
asured value, ” or assigned
to an output
s
owing output
ect the senso
e parameters,
Page 34 of 83
not RF‐RXS)
to‐commissio
and with opto a unique 0
channel are:
t voltages repr
r (or router w
, and for all de
oning mode. T
tions fitted ca0‐10Vdc outpu
resent the fan
with sensing el Right‐c<Prope Select tab. Using twhich Using tthe out Click button<Closemappin
evices.
This may cause
an have up tout channels on
n speed status
ement).
click on the deerties> from th
the <Analogu
the <Functiondevice param
the <Channel tput channel t
the <Set A to accept t> button to exng changes.
e network err
o 4 measuredn the receiver
s;
evice, and selehe drop‐down
e Channel Ma
n> list box, selemeter to map.
No.> list box, to map to.
Analogue Mthe changes,xit with accep
ors.
d values. .
ect n menu.
apping>
ect
select
Mapping> or the pting the
To remo<Chann Viewing
ove an analognel No.> list bo
g Device Prop
gue channel mox.
perties
mapping, follow
Page 35 of 83
w the steps ab
Toma
Tvi<
A
P M So St Li R A
bove, but sele
view the currappings, expa
he specific proiewed by rightProperties> in
Available route
arent (if appliMAC address oftware versiotatus ink Quality untime
Any active alar
ect <No Mapp
rent analoguend the receive
operties of ant‐clicking a den the drop‐dow
er properties a
cable)
on
ms
ping> from the
e output chanver in the text
ny device can evice and selewn menu.
are:
e
nel display.
be cting
Page 36 of 83
Availa
Parent MAC a Softw Status Link Q Runtim Batter Any m Any ac
Availa
MAC a Softw RF cha Runtim Autho
ble sensor pro
t (if applicableaddress are version s Quality me ry level measured valuective alarms
ble receiver p
address are version annel used me orised nodes
operties are:
e)
es
properties are:
Changin Do NOTerrors. Batterypoweretransmievery 5 Considerequiremay reconnec Temper Setpoinmomen
When aexit wit
ng Device Con
T try to make
y powered noed devices, as it its value eve minutes.
eration shouled level of consult in havingting the CMS
rature in a roo
nt values are ntary switch, V
all changes arthout acceptin
nfigurations
e configuratio
des have conthese will affeery 10 second
d be given tontrol to maximg to wait for to a receiver.
om doesn’t no
only sent if VFC and PIR; d
e complete, cng the change
on changes w
nfigurable parect battery lifds, the battery
o each device mise battery the set inter.
ormally change
the value cdata is only tra
click the <Chas.
Page 37 of 83
while in auto‐c
rameters. Thefe. For examply life will be le
and how oftlife. Howeverrval time to e
e by a signific
changes by a ansmitted on
nge> button t
commissionin
e setting of thle, if a temperess than if the
ten it should sr, setting a traelapse before
ant amount in
configurablea change of st
Temperconfiguchange configu Configu To viewsensor the r<PropeSelect t
to accept the
g mode. This
hese can be irature sensor sensor were s
send values aansmission ine current data
n a few minut
e level. The status (ON or O
rature, RH anred to sendof value”. Trable by the a
urable Parame
w or changnode paramrequired derties> from thhe <Configura
Measureme
Temperature
RH change t
Setpoint thr
PIR Off Dela
Clear VFC Co
changes, or t
s may cause
important forin a room is sset to transm
and still mainnterval to a hia is shown w
tes, RH even le
same is true OFF).
nd CO2 can d on a “sigThese values administrator.
eters
ge battery pmeters, right‐evice and he drop‐downation> tab.
ent interval
e change thre
threshold
reshold
ay
ount
the <Close> b
network
r battery set up to it values
ntain the igh level when re‐
ess so.
for the
also be gnificant are also
powered click on
select n menu.
eshold
utton to
Where
When aexit wit
a CO2 device
all changes arthout acceptin
is to be config
e complete, cng the change
gured, the fol
click the <Chas.
Page 38 of 83
lowing config
nge> button t
uration settin
to accept the
gs are availab
Measureme
Temperature
RH change th
CO2 change
CO2 Auto ca
PIR Off Delay
Clear VFC Co
changes, or t
ble;
nt interval
e change thre
hreshold
threshold
alibration func
y
ount
the <Close> b
shold
ction
utton to
RF‐IOM RF‐IOM
M Configuratio
M Status Tab
on
Page 39 of 83
To cthe nam<Cha NBchar Infotab
hange the na<Name> box
me you requange> button
There is a racters for dev
rmation displinclude;
MAC add
Firmware
Parent M
Status
Link qua
Device ru
Current i
Current i
Current o
ame of an RF‐ox, type in tuire and cl.
limit of 1vice names.
ayed on the <
dress
e version
MAC address
lity (to parent
untime
input types
input values
output values
‐IOM, In he new ick the
0 ASCII
<Status>
t)
s
Changin Each of
NB ‐ Aftupdate
ng the input c
f the 4 inputs c
4‐20mA cur
0‐10Vdc
Resistance (
Digital input
fter making chthe input ma
configuration
can be set as
rent (loop pow
(between the
t (volt free co
hanges to the pping.
either;
wered or 3‐w
limits of 1.5kΩ
ntact only)
input mode j
Page 40 of 83
ire)
Ω and 60kΩ)
jumpers, the r
To enof vaappro To seenter appro To enalarmbox fo To sevaluesappro Notes
1where
2COV aFor ethen tare al Imporafter c
reset button m
able or disabalue actions, opriate box for
et a new methe requi
opriate box.
nable or disas, tick or un‐or each input.
t high alarms, enter the opriate box.
s:
. Alarm leve an input is s. The units are dependenxample, if anthe units for Cso in mA.
rtant! Click tchanges are m
must be press
ble significanttick or un‐t
r each input.
easurement ired level
ble high and‐tick the app
m, low alarm required leve
vels are not aset as VFC for alarm levnt on the inpn input is setCOV and alar
the <Change>made.
sed for the RF
t change tick the
interval, in the
d/or low propriate
or COV el in the
available
vels and put type. t to mA, m levels
> button
F‐IOM to
Changin Each of Output
ng the output
f the 4 outputs
values can be
t configuration
s is fixed as a
e written usin
n
linear 0‐10Vd
g the Output
Page 41 of 83
dc output.
Configurationn tab.
To set anrequired <Current<Change Fall‐back Fall‐back analogueif the RF‐parent update ccircumstaensure ocases, an NB ‐ FallRF‐IOM parent should be To set a level, enappropriaclick the
n output to avoltage inValues> b
> button.
k Settings
settings can e outputs to p‐IOM loses coreceiver andorrect controances, it maoutputs are fo OFF state).
l‐back values loses commreceiver. Cae given to the
fall‐back outnter to requate <Fall‐bac<Change> but
a new level, n the appbox and cl
be used to fopre‐determineommunicationd therefore ol values. Unday be desirorced to 0V (
WILL be usemunications areful conside values used.
tput value touired voltage ck Values> btton.
enter to propriate ick the
orce the d values ns to the cannot
er these rable to (in most
ed if the to the deration
o a new in the
box and
Manua When commisprohibit
You wilthe dev
Removi
Click <R
lly Authorisin
adding an adssioning mettive.
l need to mavice. Ensure th
ing a Node fro
Remove> to su
ng a New Nod
dditional nodthod is not
ke a note of the new device
om the Netwo
ubmit the deta
e
de to an exisused unless
the unique 16e is powered o
ork
ails, or click <C
Page 42 of 83
sting system,the number
To manuallyon at admi<Options> afrom the dro
6‐digit MAC aon.
Enter this appropriateor click <Can
To remove aclick on <Optnode> from (routers, RF‐Iname (label).
Cancel> to dis
it is strongof new nod
y authorise a inistrator leveand then seleop‐down men
ddress of the
MAC addresbox fields anncel> to disca
node from ttions> and ththe drop‐dowIOMs or sens.
scard the actio
ly recommendes to be ad
new node(s),el. From the ect <Authorisenu.
e new node, fo
ss and a ded click <OK> trd the informa
the network, hen select <Dwn menu. Selors) and then
on.
nded that thdded become
, you must be menu bar, e (add) a new
found on the
evice label ito submit theation.
from the meDe‐authorise (ect the devicn select the d
he auto‐es time‐
e logged click on w node>
label on
nto the e details,
enu bar, remove) ce group evice by
Using th Apart fquickly By defa A typicanetwor Setting To set a
he Graphical
from the textdetermine ho
ult, there is n
al image to uk has been ins
the Map Disp
a background
Map Display
t hierarchical ow the netwo
o graphic ima
use for the mstalled.
play Backgrou
image for the
display, the rk is functioni
age set as a ba
ap display wo
und Image
map display,
Page 43 of 83
CMS offers aing.
ackdrop for th
ould be a flo
you must be
Frsedo
a graphical en
e map display
or plan of th
logged on at a
rom the menuelect <Set Baown menu.
Browse tofile forma
Bitmap (.b JPEG (.jpg
nvironment w
y.
e environmen
administrator
u bar, click onckground Ima
o the image ts currently su
bmp) g)
which allows
nt in which t
r level.
n <Options> aage> from th
file requiredupported are:
users to
he radio
and then he drop‐
d. Image :
Adding To add the grap Add thautoma Differeneasy. Thin alarm Icon Pla A schedthen se The foll
Devices to th
a device to thphic backgrou
he receiver tatically genera
nt icons are uhe icons also dm.
an
dule of what eelect <Icons> f
owing pop‐up
he Map Displa
he map displaund.
o the graphated, showing
used to depicdepict the sta
each icon andfrom the drop
p window is d
ay
ay, simply “dra
ic first, thenthe true netw
ct the receivetus of the dev
d icon colour c‐down menu.
isplayed:
Page 44 of 83
ag‐and‐drop”
n routers folwork architect
er, routers andvice, and chan
can be quickly.
a device from
lowed by bature.
d battery pownge to reflect
y found from
m the text hie
attery powere
wered node, whether a de
the menu bar
erarchical disp
ed nodes. Li
making identevice is OK, off
r, click on <He
play onto
inks are
tification f‐line, or
elp> and
Device A quickdisplay.
NB Whhas bee Link Sta The link
Status
k check on a
ere link qualiten sent to a de
atus
k status is rep
device status
ty, hours run evice, but the
resented grap
s can be mad
and battery ledevice has no
phically by the Green: Indic Red: Indicate
Am
Page 45 of 83
de by hoverin
Displayed
Device na All sensor Battery le
evel are showot yet respond
e colour of the
cates good link
es marginal li
A quick check mouse cursor
g the mouse
parameters a
me (label) r values vel (battery d
wn in italics, thded.
e link drawn.
k quality.
nk quality.
on any link stover a link on
cursor over a
are device dep
evices only)
his denotes th
tatus can be mn the map disp
a device on t
pendent, but
hat a request
made by hoveplay.
the map
include:
for data
ering the
Auto U The CM
Auto up
Manua NB ‐ Doerrors. Node oCMS to
pdating
MS can be conf
pdating can al
l Refreshing O
o NOT try to u
or network da an existing n
figured to upd
so be disabled
Of Data
update device
ata can be mnetwork.
date at a user From thUpdate accordindiscard t
d. From thUpdate <Auto U<Cancel
e information
anually refres
When redata wilits inform To ensuInforma To manu<Refresh To manuthe textInforma
Page 46 of 83
configurable
he menu bar,Time> from ngly. Click <Othe change.
he menu bar,Time> from tUpdate> box> to discard th
while in auto
shed. This is
e‐connecting l only be refremation by tim
re all data is tion or Refres
ually refresh nh Node Inform
ually refresh t or graphication> from th
rate.
, click on <Othe drop‐dow
OK> to submit
, click on <Othe drop‐dow. Click <OK> he change.
o‐commissioni
an important
the CMS to aeshed to the Cmed transmiss
sent as soon sh Network In
node data, rigmation> from
network dataal display) ane drop‐down
ptions> and wn menu. Adjt the change,
ptions> and n menu. Remto submit t
ng mode. Thi
t feature whe
a receiver on CMS as and wion.
as possible, uformation opt
ght click on a the drop‐dow
a, right click ond then selecmenu.
then select <just the upda or click <Ca
then select <move the tick fthe change,
is may cause
en re‐connec
an existing nwhen a device
use the Refretions.
node and thewn menu.
on a blank spct <Refresh N
<Change ate time ncel> to
<Change from the or click
network
ting the
network, updates
sh Node
en select
pace (on Network
Commu The CMdiagnos By defa
To viewwill appcommu
Changin To displ
unications Log
MS can keep sing network p
ult, the comm
w the communpear at the bounications log
ng Display Un
lay temperatu
g
a log of all cproblems.
munications lo
nications log, fottom of the mwindow.
nits
ures in °F inste
ommunicatio
og is enabled.
From tCommufrom ththe cha
from the menmain CMS win
ead of °C, click This chantext d
Page 47 of 83
ons on the ne
If you want to
the menu bar,unication Loghe <Enable Cange, or click
nu bar choose ndow. To close
k on <Options
change affecge limit valuedisplay and pr
etwork. This c
o disable this f
, click on <Opg> from the dCommunicatio<Cancel> to d
<View> then e this view, cl
s> then tick <D
cts mouse‐ovees, temperaturint preview.
can be helpfu
feature,
ptions> and throp‐down men Log> box. Ciscard the cha
<Communicaick the cross i
Display Fahren
er temperature values show
ul in finding f
hen select <Cenu. Remove Click <OK> toange.
ations Log>. A in the top righ
nheit>.
ure values, sigwn in the hie
faults or
onfigure the tick
o submit
window ht of the
gnificant rarchical
Configu The condevices
Results or analo Results
uration Log
nfiguration los. To view the
shown can bogue output m
can also be fi
og allows the communicatio
e filtered to smappings.
iltered within
user to view ons log, from
show only spe
a user‐defina
Page 48 of 83
a concise listhe menu bar
ecific “key fiel
able date rang
t of any chanr choose <Vie
lds” such as w
ge.
nges made tow> then <Con
when a config
o the configurnfiguration Lo
uration was c
ration of g>.
changed,
Using C Saving a When aand as t Saving display. To save
To open
A librar
CMS to Docum
and Opening
a network is cthe basis for c
a layout reco
a layout, click
n a saved layo
y of site layou
ment a Wirele
Layouts
commissionedcomparison w
ords the backd
k on <File>
out, click on <F
uts can be form
ss Network
d, it is very uswhen checking
drop (if used)
then <Save
File> then <
med as a refer
Page 49 of 83
seful to save g the current s
) and the pos
Layout>
<Load Layo
rence.
the graphicalstatus of netw
sition and size
out>
map layout twork topology.
e of each dev
to use as a re
vice icon on t
eference
the map
Receive To genethe rece
A documfor exam
er Print Previe
erate a compreiver object, a
ment is autommple.
ew
rehensive textand from the
matically gene
t document ofmenu select <
erated, which
Page 50 of 83
f network dev<Print Pre
can be printe
vices, from theeview>.
ed on paper fo
e hierarchical
or an O&M m
display, right
manual, or to .
‐click on
PDF file,
SonNet Networ
i.
ii.
iii.
iv.
Receive
i.
ii. iii.
iv.
v. vi.
vii. viii. ix.
x.
t‐Tridium JAC
rk Action Men
Set System is placed in
a. FASon
b. TRUSon
Assert Seriaparameters Assert Optcommunica(COM3) Assert Optcommunica(COM4)
er Action Men
Ping – This cupdate the Get RuntimeGet Softwarand stores tDe‐authorisOnly works Get All DataGet RF Chainclusive) Enable AutoDisable AutoAuthorise Nusing auto cMap Netwonetwork
E Driver Actio
u
Lock – This coauto‐commisLSE = The drintay CMS) witUE = The driventay CMS) wital Card Commfor the RF‐RXtion Card Slotions parame
tion Card Slotions parame
u
command reqreceiver runtie – This commre Version – Tthe result as pse Node – Thiswhen auto coa – This commnnel – This co
o Commissiono CommissionNode – This ccommissioningork – This com
on Menus
ommand detesioning modever will find thout having ter will not finthout having tmunications –XS receiver ot1 Communters for the R
ot2 Communters for the R
quests the recme field mand requestsThis commandproperties s command deommissioning mand refreshesommand gets
ing Mode – Thning Mode – Tommand is ug)
mmand is used
Page 51 of 83
ermines whethe nodes alreadto put the recd nodes alreato put the recThis comman
nications – TF‐RXS‐N optio
nications – TF‐RXS‐N optio
ceiver runtime
s the receiverd gets the ma
e‐authorises ais off) s all data, excs the current
his commandThis commandused to manu
d to discover a
her the driver
y commissioneiver into autady commissioeiver into autnd automatica
This commaon card receiv
This commaon card receiv
e, as a metho
r runtime and jor and minor
and removes
luding the “pa2.4GHz RF ch
sends a requd sends a requally authorise
and update th
can only find
ned to a receo commissiononed to a receo commissionally sets up se
nd automativer connected
nd automativer connected
d on checking
updates the rr versions of t
the receiver f
arent” properhannel (valid
est to enable uest to disablee a node or n
e parent node
d nodes if the
eiver (for examning mode. eiver (for examning mode. erial commun
cally sets ud to slot 1 on t
cally sets ud to slot 2 on t
g comms, but
receiver runtithe receiver f
from the netw
rty channels are
auto commise auto comminodes (as opp
e of all device
receiver
mple, by
mple, by
nications
p serial the JACE
p serial the JACE
t doesn’t
me field irmware
work (NB
11 – 26
ssioning ssioning posed to
es on the
Router A
i.
ii. iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
Action Menu
Ping – This update the Get RuntimeGet Softwarand stores tDe‐authorisOnly works Get All Dat“parent” proGet Parent parent Get Sensor C
a. Hab. Hac. Had. Hae. Mef. Sig
beig. Sig
trah. Sig
traSet MeasurmeasuremeSet Significaresults in thSet Significavalue being Set Significameasured v
command reqrouter’s runtie – This commre Version – Tthe result as pse Node – Thiwhen auto cota – This comoperty LQI – This co
Configurations Temp – Whes RH – Wheths Setpoint – Ws Switch – Wheas Interval – g Temp – Theing transmitteg RH – The nsmitted immg Setpoint – Thnsmitted immrement Interent values [Limant Temperate measured vant RH – This transmitted iant Setpoint –value being tra
quests the rome field mand requestsThis commandproperties s command dommissioning mmand refres
ommand gets
n – This commether the nodher the node hWhether the nhether the nodThe time betwe significant ced immediatesignificant chmediately he significant mediately val – This cmits: 10 to 900ture – This covalue being tracommand setmmediately [– This commanansmitted imm
Page 52 of 83
outer runtime
s the router’s d gets the ma
de‐authorises is off) shes all the d
radio link str
mand requestsde has a temphas an RH sennode has a setde has a momween transmihange in temly hange in RH
change in set
ommand set0 seconds] ommand setsansmitted immts the significa[Limits: 3% to nd sets the sigmediately [Lim
, as a method
runtime and ajor and mino
and removes
data specific
rength (LQI =
the followingerature sensosor fitted tpoint adjustmmentary switchssion of meas
mperature wh
which resul
point which r
ts the norma
s the significamediately [Limant change in10%] gnificant chanmits: 1% to 25
d on checking
updates the ror versions of
s the router fr
to the select
Link Quality
g configuratioor fitted
ment pot fittedh fitted surement valuich results in
ts in the me
esults in the m
al time betw
ant change inmits: 0.1°C to RH which res
nge in setpoin5%]
g comms, but
runtime field f the router f
rom the netw
ted router, e
Index) to the
n properties;
d
ues the measure
easured valu
measured valu
ween transmis
n temperatur1.0°C] sults in the m
nt which resul
doesn’t
irmware
work (NB
xcluding
e node’s
ed value
e being
ue being
ssion of
re which
measured
ts in the
xii.
xiii.
xiv.
xv.
xvi.
RF‐IOM
i.
ii. iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
Set CO2 Autsensor elemhours, the calibrate theSet CO2 MaEnsure ambSet CO2 Signmeasured v= 400ppm] Set PIR Off detects no seconds] Clear VFC CPoint on pag
M Action Menu
Ping – This update the Get RuntimeGet Softwarand stores tDe‐authorisOnly works Get All Dat“parent” proGet Input CconfiguratioGet OutputconfiguratioSet Input configuratioSet OutputconfiguratioGet Child Noparent Get Parent parent
to Calibrationment. Over a plowest level e sensor outpanual Calibratbient CO2 is atnificant Setpovalue being tra
Delay – This coccupancy. [
Count – This cge 66.
u
command reqRF‐IOM’s runte – This commre Version – Tthe result as pse Node – Thiswhen auto cota – This comoperty Configurationon Configuratioon Configurationon Configuratioon ode List – This
LQI – This co
– This commperiod of 24 h(which is ass
put at 400ppmtion – This cot 400ppm befooint – This comansmitted imm
command set[Limits: 10 se
ommand clea
quests the RFtime field mand requestsThis commandproperties s command dommissioning mmand refres
– This comm
n – This com
n – This com
on – This co
s command ge
ommand gets
Page 53 of 83
and enables ahours, the sensumed to be m. ommand perfore performinmmand sets thmediately [Lim
ts the off delaeconds to 30
ars the VFC in
‐IOM runtime
s the RF‐IOM’d gets the ma
e‐authorises is off) shes all the d
mand refresh
mmand refres
mmand send
mmand send
ets radio link
radio link str
automatic basnsor system reduring a pe
forms a manung this commahe significant mits: 100ppm
ay, which starminutes, 10
nput counter.
e, as a metho
s runtime andajor and mino
and removes
data specific
hes all the d
hes all the da
ds any chang
ds any chang
strength (LQI
rength (LQI =
seline calibratecords CO2 levriod of no oc
ual calibrationand. change in CO
m to 800ppm, 2
rts counting wsecond steps
See also The
d on checking
d updates the r versions of t
the RF‐IOM f
to the select
ata specific t
ata specific to
ges made to
ges made to
= Link Quality
Link Quality
tion (ABC) for vels, and oncccupancy) is
n of the CO2
O2 which resul20ppm steps,
when the PIR s steps, defa
VFC Activatio
g comms, but
e runtime fieldthe RF‐IOM f
from the netw
ted router, e
to the RF‐IO
o the RF‐IOM
o the RF‐IOM
the RF‐IOM
y Index) to the
Index) to the
the CO2 e per 24 used to
2 sensor.
ts in the , default
element ult = 30
on count
t doesn’t
d irmware
work (NB
xcluding
M input
M output
M input
output
e node’s
e node’s
Sensor A
i.
ii. iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
Action Menu
Ping – This update the Get RuntimeGet Softwarstores the reDe‐authoriscommissionGet All Dataproperty Get Sensor C
a. Hab. Hac. Had. Hae. Mef. Sig
beig. Sig
trah. Sig
traSet MeasurmeasuremeSet Significaresults in thSet Significavalue being Set Significameasured v
command rerouter’s runtie – This commre Version – Tesult as propese Node – Thisning is off) a – This comm
Configurations Temp – Whes RH – Wheths Setpoint – Ws Switch – Wheas Interval – g Temp – Theing transmitteg RH – The nsmitted immg Setpoint – Thnsmitted immrement Interent values [Limant Temperate measured vant RH – This transmitted iant Setpoint –value being tra
equests the Eme field mand requestsThis commanderties s command d
mand refreshe
n – This commether the nodher the node hWhether the nhether the nodThe time betwe significant ced immediatesignificant chmediately he significant mediately val – This cmits: 10 to 900ture – This covalue being tracommand setmmediately [– This commanansmitted imm
Page 54 of 83
D’s runtime,
s the ED’s rund gets the ma
e‐authorises
es all the data
mand requestsde has a temphas an RH sennode has a setde has a momween transmihange in temly hange in RH
change in set
ommand set0 seconds] ommand setsansmitted immts the significa[Limits: 3% to nd sets the sigmediately [Lim
as a method
ntime and updajor and mino
and removes
a specific to th
the followingerature sensosor fitted tpoint adjustmmentary switchssion of meas
mperature wh
which resul
point which r
ts the norma
s the significamediately [Limant change in10%] gnificant chanmits: 1% to 25
on checking
dates the runtr version of th
the ED (NB O
he selected ED
g configuratioor fitted
ment pot fittedh fitted surement valuich results in
ts in the me
esults in the m
al time betw
ant change inmits: 0.1°C to RH which res
nge in setpoin5%]
g comms, but
time field he ED’s firmw
Only works wh
D, excluding “
n properties;
d
ues the measure
easured valu
measured valu
ween transmis
n temperatur1.0°C] sults in the m
nt which resul
doesn’t
ware and
hen auto
“parent”
ed value
e being
ue being
ssion of
re which
measured
ts in the
Page 55 of 83
xi. Get Battery Level – This command requests the battery status xii. Get Battery Runtime – This command requests the ED’s battery runtime xiii. Get Parent LQI – This command get link strength (LQI = Link Quality Index) to the node’s parent xiv. Set CO2 Auto Calibration – This command enables automatic baseline calibration (ABC) for the CO2
sensor element. Over a period of 24 hours, the sensor system records CO2 levels, and once per 24 hours, the lowest level (which is assumed to be during a period of no occupancy) is used to calibrate the sensor output at 400ppm.
xv. Set CO2 Manual Calibration – This command performs a manual calibration of the CO2 sensor. Ensure ambient CO2 is at 400ppm before performing this command.
xvi. Set CO2 Significant Setpoint – This command sets the significant change in CO2 which results in the measured value being transmitted immediately [Limits: 100ppm to 800ppm, 20ppm steps, default = 400ppm]
xvii. Set PIR Off Delay – This command sets the off delay, which starts counting when the PIR element detects no occupancy. [Limits: 10 seconds to 30 minutes, 10 second steps steps, default = 30 seconds]
xviii. Clear VFC Count – This command clears the VFC input counter. See also The VFC Activation count Point on page 66.
Managi Require
1. 2.
Installin If not pcopy it <C:\Nia
ing a Tridium
ements
Tridium JACNiagara AX Wa. RF‐RXS b. RF‐RXS
ng the SonNe
re‐installed, dto the <Modu
agara\Niagara
1. Start Ni2. From th
JACE SonNet
CE 2xx series oWorkbench ‐ V3.5.34 or l‐N ‐ V3.6.43 o
t Driver to a T
download a coules> folder on
a‐3.5.34\mod
iagara Workbhe platform tr
t Wireless Net
or 6xx series
ater or later
Tridium JACE
opy the SonNen the PC runn
ules>
ench and log ree, open <Sof
Page 56 of 83
twork
et driver file “ing Niagara W
into the JACEftware Manag
“sonnet.jar” frWorkbench. Fo
platform ger>
rom www.sonor example;
ntay.com and
Adding Prerequ
1.
2. 3.
4.
3. From th4. Click th
reboot.5. After th
<Config
a SonNet Ne
uisites:
The RF‐female)
o
The RF“Install
Observcard fitt
o
Double‐clickManager wiFrom the <TClick the <Onetwork dri
a. At win
To set th<SonNetNet
a. If ab. If a
Coopt
he list of modhe <Commit> . he JACE has reg> branch to s
twork
‐RXS must be ). Do not use aNB The RS‐2RXS is conne
‐RXS‐N shouling the SonNe
ing power supted. Observe thechild devicenode.
k the <Driverindow. Click tType to Add> OK> button, enver. this point, thndow. he default twork> folder
an RF‐RXS serian RF‐RXS‐N mmunicationtion card slot
ules and drivebutton. The d
ebooted, log ihow the <Driv
connected toa null modem232 port of thected.
d be installedet option card
pply polarity,
e red networkes yet, if it is
rs> folder in he <New> butdrop‐down bonsure the new
he new SonNe
communicatior in the <Statio
The Net
ial receiver is option card s> or <Assertis used.
Page 57 of 83
ers, locate anddriver will be
nto the JACE vers> branch.
o COM1 of them serial cable. the RF‐RXS wi
d in either Sld”
switch on the
k LED. If it is bon steadily t
the <Stationtton. ox, scroll doww driver is ena
et network m
ons parameon\Config\Dri
twork System
being used, sreceiver is
t Option Card
d select <sonninstalled. NB
station. Expan
e JACE by a se ill not commu
ot1 (COM3) o
e RF‐RXS, or p
blinking on anhen the rece
n\Config > na
wn and select <abled and the
may be shown
ters for thivers> navigat
right‐click <A
elect <Assert being used, d Slot2 Comm
net> ‐ this action w
nd the station
erial cable (9‐
unicate if the
or Slot2 (COM
power up the
nd off it meaniver already h
vigation tree
<SonNet Netwn click the <O
n in orange in
e receiver, ion tree, then
ction> menu
Serial Card Coselect <Asser
munications>,
will cause the
n tree and exp
pin D male to
e USB port on
M4) of the JA
JACE with th
ns the receivehas at least o
e to open the
work> OK> button to
n the Driver M
right‐click n select <Actio
ommunicationrt Option Cadepending o
JACE to
pand the
o 9‐pin D
n the RF‐
ACE. See
e option
r has no one child
e Driver
add the
Manager
on the ons>
ns> rd Slot1 on which
Thetha The
Commi
A So
Commi
To crece
e default foldeat the “Discov
e new SonNet
ssioning a So
onNet networ
1. An exisexamplmoved
2. A comp
ssioning an Ex
commission aneiver’s networ
1. Right‐cliselect <A
2. Using th
ers “Receiver”ver” button ha
t network is n
nNet Networ
rk can be com
sting networke, where thefrom one JACpletely new ne
xisting Netwo
n existing netwrk, requires ve
ck on the <SActions> thene drop‐down
”, “Routers”, “as no function
ow ready for
k
missioned in
k, where the e network haCE to another)etwork, where
ork
work, where rery little mana
SonNetNetwo <Set System list, select “Fa
Page 58 of 83
“Sensors” andnality in the So
commissionin
2 ways using t
receiver alreas been comm) e the receiver
routers and seagement.
ork> folder inLock> alse” and then
d “Unknown” onNet Device
ng.
the JACE drive
ady has child missioned usin
r has no child
ensor end dev
the <Station
n click OK.
When the coparameters new SonNetlook similar SonNet Devwindow, theshown in wh
are created aManager.
er;
nodes joinedng CMS or th
nodes
vices (EDs) hav
n\Config\Drive
ommunicatiohave been set network shoto this. In the
vice Manager e receiver shohite.
automatically.
d to the recehe receiver h
ve already joi
ers> navigati
ns et, the ould e
ould be
Note
iver (for as been
ned the
on tree,
The exiscomple It is recset to T Commi
To crece
sting networkete.
ommended thTrue.
ssioning a Ne
commission a eiver’s networ
k devices will a
hat when all e
ew Network
new networkrk, or to add n
appear in thei
existing nodes
k, where no ronew devices to
1<Station\<Actions>
2“Commis
3mode it iuntil all d
4<Station\<Actions>
Page 59 of 83
ir respective f
s have appear
outers and seno an existing n
1. Righ\Config\Driver> then <Enabl2. Powssioning A Son3. NB Ws important Ndevices have jo4. Righ\Config\Driver> then <Disab
folders. This m
red in the driv
nsor end devicnetwork.
t‐click on trs\SonNetNetle Auto Commer up routenNet System: SWhile the reNOT to use othoined the nett‐click on trs\SonNetNetble Auto Comm
may take seve
er, the System
ces (EDs) are p
the <Receivtwork> navigmissioning Moers and EDsStep‐By‐Step”eceiver is in her <Action> mwork. the <Receivtwork> navigmissioning Mo
The new netappear in thfolders. This may takcomplete.
ral minutes to
m Lock proper
present on th
ver> folder gation tree,ode> s as require”, pages 68 ‐ 6auto commimenu functio
ver> folder gation tree,ode>
twork devicesheir respective
ke several min
o
rty be
e
in the select
ed (see 69) issioning ns. Wait
in the select
s will e
nutes to
Configu Device When Snames w Each pr
There is NB It is name cDisplay Receive
1.
2.
3. 4.
5. 6.
uring Network
Prefixes:
SonNet devicewhich take th
refix denotes a
“U” denotesdevice)
“S” denotes
“IO” denote
“R” denotes
“X” denotes
s no prefix for
strongly recoan be configuName” from
er
Right‐click otree, select Right‐click otree, select Note that soNB After a This is normNote the staNote the sta
k Devices
es are first shohe format of a
a specific type
s that the dev
s that the devi
es that the dev
s that the dev
s that the dev
r the receiver
ommended thured for each dthe menu.
on the <Rece<Views> thenon the <Rece<Actions> theoftware versioperiod of tim
mal, as these vatus, last faultatus of the au
own in the navprefix followe
e of device:
vice is unknow
ice is a battery
vice is an RF‐I
ice is a router
ice is a router
name.
at the device device. To set
eiver> folder n <Property Sheiver> folder en <Get All Daon numbers, Rme, the RF chaalues are not t cause and lato commissio
Page 60 of 83
v tree or the ded by the MA
wn (i.e. the re
y powered en
OM
r without sens
r with sensing
name is kept t a display nam
in the <Statiheet> in the <Statiata> RF channel anannel and recupdated unlest update timoning feature.
device’s propeAC address of t
eceiver doesn
nd device (ED)
sing capabiliti
capabilities
as the defaultme, right‐click
ion\Config\Dr
ion\Config\Dr
d receiver runceiver runtimeess requestedmes.
The
erty page, thethe device.
’t have full inf
)
es
t name. A usek on the device
rivers\SonNet
rivers\SonNet
ntime are nowe values will b.
e Receiver Pro
ey have defau
formation yet
er friendly dispe and select “
tNetwork> na
tNetwork> na
w all displayedbe displayed
operty Page
lt
t for the
play “Set
avigation
avigation
d. as stale.
Routers
1.
2. 3.
All the rstronglyconfigudevice’s To mak
s
Expand theselect a rouEnsure the rRight‐click o
router’s “poiny recommendred for each ps property she
ke changes to
e <Routers> fter from the lreceiver is NOon the router
nts”, such as “ded that pointpoint. To set aeet and select
the router’s C
folder in theist, select <Vi
OT in auto comand select <A
“Temp” for the names are kea display namet “Set Display
Config propert
Page 61 of 83
e <Station\Coews> then <Pmmissioning mActions> then <
e measured teept as the defe, right‐click oName” from
ties, refer to t
onfig\Drivers\SProperty Sheetmode. <Get All Data>
A typica
1.numberdisplaye
2.values aas tempThis is are upd
3.and last
4.5.
NB Wherouter, quickly, “awake”period w(if any) tthrough30 seco
emperature vfault names. Aon the point inthe menu.
the Router Act
SonNetNetwot>.
>
al router’s pro
Note that rs and runted. NB After a
apart from mperature) will normal, as oated unless reNote the sta update timesNote the parNote the par
en a request fthe request as the rout
”. However, will depend othe request ah. Normally, thnds maximum
alue, have deA user friendlyn either the na
tions Menu on
ork> navigatio
operty page
software time are n
period of tmeasured valube displayed
only measuredequested. atus, last faus. rent of the rorent LQI value
for data is mashould be prers are permthe exact r
on how manynd reply havehe response im.
efault names. y display nameav tree or the
n page 52.
on tree,
version now all
time, all es (such as stale. d values
ult cause
uter. es
ade to a rocessed manently esponse y routers e to pass is within
It is e can be e
RF‐IOM
1.
2. 3.
Ms
Expand the RF‐IOM fromEnsure the rRight‐click o
<Io> folder inm the list, selereceiver is NOon an RF‐IOM
n the <Stationect <Views> thOT in auto comand select <A
Page 62 of 83
n\Config\Drivhen <Propertymmissioning mActions> then
A typical RF‐Ioutput config
1. Noteinput measur
2. The output fallbachannels in th
3. Noteinput jumperthe inout jum
4. Notechannel.
5. To srequired leve
6. To sthe required
7. Notedependent oto mA, then tmA.
vers\SonNetNey Sheet>. mode. <Get All Data
A typical Rthe points
1. Nnumbers a
2. Napart frotemperatuis normalupdated u
3. Nand last up
4. N5. N
OM’s propertguration param
e the measurerements onlyoutput configck values. Thehe event that e the input chr settings. NBmpers while the the low and
et a new meael in the approet high alarm,level in the apes: The units fn the input tythe units for C
etwork> navig
>
RF‐IOM’s props expanded.
Note that and runtime aNB After a perom measureure) will be dil, as only munless requestNote the statpdate times. Note the parenNote the paren
ty page, showmeters expan
ement interva
guration paramese are writtethe RF‐IOM gannel Types –– it is importahe RF‐IOM is phigh alarm le
surement inteopriate box. , low alarm orppropriate bofor alarm leveype. For exampCOV and alarm
gation tree, s
perty page, sh
software are now all disriod of time, ad values (sisplayed as stmeasured valted. tus, last fau
nt of the RF‐IOnt LQI values
wing the input nded.
al. This pertain
meters are foen to the outpgoes offline. – these reflectant NOT to chpowered. evels for each
erval, enter th
r COV values, ox. els and COV arple, if an inpum levels are al
select an
owing
version splayed. all values such as ale. This ues are
lt cause
OM.
and
ns to
r the ut
t the ange
input
he
enter
re ut is set so in
Writing
Values outputschange steps. To set tfinally e RF‐IOM FallbackIOM gooutputs To set fvalues f
Importaby right
g Output RF‐IO
for the RF‐IOs can have a sis sent imme
the SCV for aexpand Write
M Fallback Val
k values are does offline (bus can be set to
fallback valuefor each outp
ant!!! After mt‐clicking the R
OM Values
M output chaignificant chadiately. Each
n output, expParameters. E
ues
efault values ut remains powo a “safe” valu
s for each outut.
making changeRF‐IOM and fr
annels are wrnge value (SCoutput chann
pand the outpEnter the requ
which are wrwered). This iue if the contr
tput, expand t
es to the fallbrom the Actio
Page 63 of 83
ritten, by defaCV) set. If the onel can be con
put channel inuired SCV in t
itten to the Rs a safety merol strategy ca
the Output Co
ack values, it on Menu selec
ault, every 5 moutput value cfigured for a d
n the points lhe Sig Change
F‐IOM outputechanism so thannot be upda
onfiguration P
is essential tocting Set Outp
minutes. Howchanges by mdifferent SCV
ist, then expae Trigger box (
t channels in that plant contated from the
Parameters an
o write the neput Configurat
wever, like inpmore than the value, down t
and Proxy Ext(highlighted a
the event thattrolled by the RF‐IOM.
nd enter the r
ew data to thtion.
puts, the SCV, the to 10mV
tensions, above).
t the RF‐ RF‐IOM
required
e device
RF‐IOM The defdefault measur To acce High an
Note th10Vdc t If an inpVFC inp Importathe dev NB – It seconds
M Input Config
fault measureis 900 secondred input valu
ess input confi
nd low alarm l
hat the alarm the alarm leve
put is set as aput are sent im
ant!!! After mvice by right‐c
is strongly res to prevent u
guration
ement intervads. Like EDs, ife will be sent
iguration prop
evels can also
levels are in els are also in
a VFC type, thmmediately.
making any chlicking the RF‐
ecommended unnecessary ra
al determines f an input valimmediately.
perties, expan
o be set for ea
the same unVdc. Similarly
e input value
hanges to the‐IOM and from
that the defaadio traffic.
Page 64 of 83
how often thue exceeds a . Each input h
nd the Input C
ach input.
its as the inpy, SCV values a
will be eithe
e input configm the Action
ault measurem
he RF‐IOM seconfigurable as its own SCV
Configuration
ut type. So, fare in the sam
r 0 (OFF) or 1
uration, it is eMenu selectin
ment interval
nds it measusignificant chV.
Params sectio
for example, ime units as the
(ON). Change
essential to wng Set Input C
be left at the
red input valuhange value (S
on.
if Input 1 is see input type.
es of input sta
write the newConfiguration.
e default valu
ues. The SCV), the
et for 0‐
ate for a
w data to
e of 900
End Dev
1.
2. 3.
All the stronglyconfigudevice’s
vices (EDs)
Expand theselect a senEnsure the rRight‐click o
sensor’s “poiy recommendred for each s property she
e <Sensors> fsor from the lreceiver is NOon the sensor
ints”, such asded that pointpoint. To seeet and select
folder in thelist, select <ViOT in auto comand select <A
s “Temp” for t names are ket a display nt “Set Display
Page 65 of 83
e <Station\Coiews> then <Pmmissioning mActions> then
the measuredept as the defame, right‐clName” from
onfig\Drivers\SProperty Sheemode. <Get All Data
1. Nonumbers, device runt
2. Napart frotemperatuis normal,updated un
3. Nolast update
4. No5. No
NB When ED, the re“wakes” toBecause ofretrieve tperiod wilinterval timany routhave to ptransmissio
d temperaturfault names. Aick on the pothe menu.
SonNetNetwot>.
>A typical EDs
ote that battery levetime are now B After a perim measuredre) will be dis, as only mnless requesteote the statuse times. ote the parenote the paren
a request forequest is buo take and senf this, it may the requestell depend onme (default ers (if any) thpass through on cycle the re
re value, haveA user friendlyoint in either
ork> navigatio
s property pa
software el and runtimall displayed.iod of time, ad values (ssplayed as st
measured valed. s, last fault ca
nt of the sensont LQI values
r data is maduffered until nd its measurtake some mied data. Then the measu900 secondhe request a and when equest is mad
e default namy display namr the nav tree
on tree,
ge
version me and . ll values such as ale. This ues are
ause and
or.
de to an the ED
rements. nutes to e exact urement s), how nd reply in that
de.
mes. It is e can be e or the
Page 66 of 83
The VFC Activation Count Point The VFC Activation Count Point can be used as a “backup” to count VFC input True state activations, in the event that the ED or router can carry on counting input pulse even if the ED or router goes offline. When the ED or router comes back online, the VFC counts totalled in strategy can be compared with the total held in the VFC Activation Count Point, to be sure no pulses have been missed while the ED or router has been offline. The total held in the VFC Activation Count Point can be reset to 0 (see pages 53 and 55). To make changes to the EDs Config properties, refer to the Sensor Actions Menu on page 54.
Page 67 of 83
Commissioning Multiple Networks on the Same Site It is quite a common requirement to need to commission several SonNet networks on the same site, for example one per floor in a multi‐storey building. To avoid the possibility of SonNet wireless nodes intended for one network appearing on another, 2 commissioning methods are available. Method 1: Pre‐commission each network away from site. This entails adding routers and EDs in the normal way to a receiver.
If using an RF‐RXS, this can be done either by using CMS or with the receiver connected to the RS‐232 port of a JACE.
If using an RF‐RXS‐N, this can only be done with the receiver connected to a JACE option card slot.
1. Using Niagara AX or a web browser, set System Lock property to TRUE 2. Place the receiver into auto‐commissioning mode and power up all routers and EDs required on the
receiver’s network to join. 3. When all devices have joined the network, take the receiver out of auto‐commissioning mode. 4. Perform a “get all data” request on all devices 5. Power off all routers and EDs associated with the receiver 6. Power off the receiver 7. Repeat this process for each receiver/network 8. Take all SonNet devices to site and install 9. Power up each receiver in turn together with its associated routers and EDs, and using Niagara AX or a
web browser set the System lock property for each network to FALSE 10. All pre‐configured routers and EDs will join their respective receivers without the need to place any
receiver into auto‐commissioning mode on site. Method 2: Commission each network individually on site. This entails adding routers and EDs in the normal way to a receiver.
If using an RF‐RXS, this can be done either by using CMS or with the receiver connected to the RS‐232 port of a JACE.
If using an RF‐RXS‐N, this can only be done with the receiver connected to a JACE option card slot.
1. Using Niagara AX or a web browser, set System Lock to property FALSE 2. Place only one receiver at a time into auto‐commissioning mode and power up all routers and EDs
required on the receiver’s network to join. 3. When all devices have joined the network, take the receiver out of auto‐commissioning mode. 4. Perform a “get all data” request on all devices NB It is important to ensure all receivers NOT being commissioned have auto‐commissioning disabled. Nodes which are already commissioned to an existing network must have reliable communications to that network to prevent them looking for other networks to join. Ensure all nodes on a commissioned network have a good link quality index (LQI) to their parents. In extreme cases, it may be prudent to temporarily power off “vulnerable” nodes while commissioning another network nearby.
Page 68 of 83
Commissioning a SonNet System: A Step‐By‐Step Guide (CMS Method)
1. Mount the receiver using the DIN carrier clip. NB ‐ it is extremely important that if the receiver is to be mounted in an enclosed panel (metal or plastic) that an external aerial extension is used. Two are available from Sontay, a 2 metre version RF‐AERIAL‐PM2 and a 5 metre version RF‐AERIAL‐PM5 (see page 18). If the aerial is to be mounted on top of the receiver panel, the extension bulk head jack should be mounted through a hole (preferably on the top of the panel) and secured in place with the star washer and hex nut. If the aerial is to be mounted remotely, the extension lead should be passed through a protective cable gland on the panel. The connector on the other end of the extension should be screwed hand tight onto the aerial connector located on the receiver PCB. Do NOT over tighten.
2. Fit the receiver aerial to the receiver PCB mounted connector, or if using an aerial extension, to the bulk head jack connector.
3. Ensure, where possible, that the receiver aerial is aligned vertically, and as far away from obstructions as possible.
4. Ensure that the receiver power supply polarity is correct if using a 24Vdc supply. 5. Mount all routers in their appropriate positions, as determined by the site survey. Ensure that the
power supply polarity is correct if using a 24Vdc supply. 6. Ensure, where possible, that the router aerials are aligned vertically, and as far away from
obstructions as possible. 7. Do NOT switch on the router(s) until all SonNet devices are installed and ready for commissioning. 8. NB ‐ RF‐IOMs have router functionality. Mount all RF‐IOMs in their appropriate positions, as
determined by the site survey. Ensure that the power supply polarity is correct if using a 24Vdc supply.
9. Ensure, where possible, that the RF‐IOM aerials are aligned vertically, and as far away from obstructions as possible.
10. Do NOT switch on the RF‐IOM(s) until all SonNet devices are installed and ready for commissioning. 11. Mount all end devices (EDs) in their appropriate positions.
a. Ensure that each space housing ED is mounted with the tamperproof screw at the bottom. This ensures the integral PCB aerial is in the correct alignment.
b. Ensure that each plant housing ED is mounted with the aerials aligned vertically, and as far away from obstructions as possible.
12. Do NOT switch on EDs until the receiver and ALL routers are installed and commissioned. 13. Connect the receiver’s USB connector to a laptop or PC with CMS installed. 14. Switch on the receiver. If this is the first time the receiver has been commissioned, note that the
red LED near the reset button is flashing. This indicates that the receiver has no child devices on the network.
15. If required, install the 2 drivers required for CMS (see page 25). Windows 7 64‐bit users, please see page 21
16. Start CMS by double‐clicking the desktop icon. Select the required com port (see page 26). Log on at admin level (see page 29).
17. If required, add a background image to CMS map display (see page 42). 18. Using CMS, ensure that the receiver appears in the hierarchical display. Add to the map display by
drag‐and‐drop. 19. Place the receiver in auto‐commissioning mode (see page 30). 20. Referencing the site survey plans, switch on all the routers and RF‐IOMs using the PCB jumper,
starting with those closest to the receiver (i.e. “layer 1”). Carry on with the next layers of routers and RF‐IOMs until all routers and RF‐IOMs are switched on.
21. Using CMS, ensure that all the routers appear in the hierarchical display. a. Note that initially, the routers and RF‐IOMs will be shown in the “Unknown” category in
the hierarchical display. This is normal. b. Ensure that each router moves to the “Router” category in the hierarchical display.
Depending on the number of devices on the network, this may take a couple of minutes.
Page 69 of 83
c. Ensure that each RF‐IOM moves to the “RF‐IOMs” category in the hierarchical display. Depending on the number of devices on the network, this may take a couple of minutes.
22. Add all routers and RF‐IOMs to the map display by drag‐and‐drop. Note that if a device is shown in blue in the hierarchical display, it has NOT been added to the map display. This is a quick way to see which have yet to be added to the map display. Ensure all are shown as on‐line. Note that the radio network links are displayed on the map display. Ensure all links are depicted in green (good link quality) and note the LQIs (see page 45).
a. If any routers or RF‐IOMs don’t show as on‐line or are not in the “Router” or “RF‐IOMs” categories in the hierarchical display, check that the PCB fuse is intact (0Ω on a multimeter) and that the correct power supply is present.
b. If any router’s or RF‐IOM’s link is shown in red, check for obstructions between it and its parent, check to see that the aerial is fitted and is vertical.
23. In the hierarchical display, right‐click on each router and RF‐IOM and select “Refresh Node Information” from the menu. This will cause the router or RF‐IOM to transmit not only its measurements, but also all its configuration data as well. NB ‐ This extra data is NOT normally transmitted, but must be requested using CMS. Where hours run is shown in italics, this denotes that a request for data has been sent to a device, but the device has not yet responded.
24. Referencing the site survey plans, switch on all the EDs by fitting the power jumper and remount into the housing (for space housing devices).
a. If this is the first time the ED has been switched on (or after replacing an EDs battery), hold down the reset button on the ED’s PCB while powering up by fitting the power jumper. This resets the battery hours run to 0.
25. Using CMS, ensure that all the EDs appear in the hierarchical display. a. Note that initially, the EDs will be shown in the “Unknown” category in the hierarchical
display. This is normal. b. Ensure that each ED moves to the “Sensor” category in the hierarchical display.
Depending on the number of devices on the network, this may take several minutes. 26. When all EDs have joined the network ‐ even if still shown in the “Unknown” category ‐ use CMS to
disable auto‐commissioning mode. NB ‐ this is very important, as trying to change configuration properties while in auto‐commissioning mode may cause network errors.
27. Add all EDs to the map display by drag‐and‐drop. Note that if a device is shown in blue in the hierarchical display, it has NOT been added to the map display. This is a quick way to see which have yet to be added to the map display. Ensure all are shown as on‐line. Note that the radio network links are displayed on the map display. Ensure all links are depicted in green and note the LQIs.
a. If any EDs don’t show as on‐line or are not in the “Sensor” category in the hierarchical display, check that the correct battery is fitted, observing polarity.
b. If any EDs link is shown in red, check for obstructions between it and its parent, check to see that the aerial is fitted and is vertical (for plant housing EDs) or that the housing is mounted correctly (for space housing EDs).
28. In the hierarchical display, right‐click on each ED and select “Refresh Node Information” from the menu. This will cause the ED to transmit not only its measurements, but also its hours run and battery hours run data as well. NB ‐ This extra data is NOT normally transmitted, but must be requested using CMS. Where hours run and battery level are shown in italics, this denotes that a request for data has been sent to a device, but the device has not yet responded.
29. When the installed network is finally formed, briefly press the receiver reset button and ensure the network reforms properly. This may take several minutes, depending on the number of network devices.
30. When the network topology has been verified and all devices are working correctly, user configuration can begin (see pages 36 ‐ 39).
31. Map all receiver analogue outputs needed to the required device measurements (see page 33). 32. When configuration is complete, save the map display layout (see page 49). 33. Generate a report of the completed network to document it for future reference (see page 50).
Page 70 of 83
Best Practise Points:
1. Always conduct a site survey, and ensure that if you plan to use an external extension aerial on the system receiver (for example, if the receiver is to be in a metal panel), you use the same external extension aerial on the SSK receiver for the survey. Document the survey thoroughly, and leave a copy on site.
2. When planning where routers and RF‐IOMs are going to be needed, plan for “redundancy”, i.e. what happens to all the EDs connected to a router if the router fails? Backup routers are worth considering. See pages 14 ‐ 15.
3. Don’t switch on EDs until they’re ready to be commissioned. If they’re powered on without a parent in range, they will eventually sleep to preserve battery life, only “waking” occasionally to scan for a parent. This may slow commissioning down. If an ED has been powered up for more than 20 minutes without a parent, power‐cycle it. Pressing the reset button on an ED DOESN’T reset the ED, it only resets the battery hours run time.
4. Generally speaking, wireless works best in a horizontal plane, so expect reduced signal strength if he receiver is on a different floor to the routers/RF‐IOMs/EDs. A good rule of thumb is have the receiver on the same floor as its children, though this isn’t always the case.
5. 2.4GHz wireless signals don’t go through metal! Plan to circumvent metal obstructions where possible.
6. If the installation environment is one where obstructions are likely to change regularly (in a warehouse, for example!), try to conduct the site survey under a “worst‐case” scenario ‐ i.e. assume that at some point, there’s going to be an obstruction between the ED/router/RF‐IOM and its parent at some time. Simulate it, if possible.
7. When commissioning the installed system, turn the receiver on first, then all the routers and RF‐IOMs ‐ starting with “layer” nearest the receiver and working outwards. It’s worthwhile checking all the routers are OK in CMS before finally powering up the EDs.
8. When EDs first join a network, values such as hours run and battery hours run will not be displayed ‐ the values are shown as question marks. This is normal, these values need to be requested from the device (right‐click on device and select “Refresh Node Information”).
9. Remember that when a receiver scans all 16 channels for the best one, the channel chosen is the best where the receiver is. On “long” networks with several “layers” of routers, the channel chosen by the receiver may not always be the quietest at the far end of the network. When the installed network is finally formed, press the receiver reset button and ensure the network reforms properly. This will ensure that, in the event that the receiver needs to change channels (for example), it will work seamlessly.
10. As each network is commissioned, save the layout ‐ even if there isn’t a background graphic loaded. This is a good aid to quickly viewing network topology.
11. Document each network! In CMS, right‐click on the receiver in the hierarchical display and select “Print Preview” from the menu and print (to paper or a file, such as .PDF) the preview document. This gives a reference to call on at a later date if required.
Page 71 of 83
Trouble‐Shooter’s Guide
System ED
Symptom Cause Actions
No connectivity to receiver
ED has not been authorized to the receiver
Manually authorize ED to receiver or use auto‐commissioning
No radio connection Check aerial on receiver
Receiver not switched on Switch receiver on
ED not switched on Switch ED on
Incorrect battery polarity Check battery polarity
Flat ED battery Change ED battery
After switching on, if an ED cannot join a network after
about 20 minutes, it will go into "sleep" mode to preserve battery life, only waking
occasionally
Power‐cycle the ED (switch it OFF and back ON) after ensuring all routers and the receiver are powered, and the routers have successfully joined the
network
ED appears in "Unknown" category in CMS when
commissioning
ED has joined network but has yet to pass configuration data
to the receiver None ‐ normal operation
ED stays in "Unknown" category in CMS when commissioning for
more than 30 minutes ED hardware error
Check ED options fitted (SP pot, thermistor, RH&T element)
In CMS, ED doesn't show hours run, firmware version, battery hours run or last update time
Normal. To help preserve battery life, an ED doesn't send this information unless it is
requested
Request information using the "Refresh Node Information" method
ED connects directly to the receiver, even though there's a
router between them
Normal. An ED will ALWAYS join a network using the least number of "hops" to the
receiver.
None ‐ normal operation. The ED will re‐join the network via the router if it loses its direct path to the receiver
Only 12 EDs connect directly to my receiver
Normal. The maximum number of directly connected EDs a receiver will allow is 12
If there are more than 12 EDs, at least one router must be used
Only 8 EDs connect directly to my router
Normal. The maximum number of directly connected EDs a
router will allow is 8
If there are more than 8 EDs, at least one additional router must be added
I replaced the battery in my ED, but the battery hours run doesn't show as having been reset in CMS
Normal. Updated ED information hasn’t been
requested
Request information using the "Refresh Node Information" method
The battery hours run reset procedure wasn't carried out when the battery was replaced
Power OFF the ED, press and hold the PCB button near the battery WHILE
powering the ED ON
My ED was switched on in error before the receiver and routers, but hasn't joined the network
After switching on, if an ED cannot join a network after
about 20 minutes, it will go into "sleep" mode to preserve battery life, only waking
occasionally
Power‐cycle the ED (switch it OFF and back ON) after ensuring all routers and the receiver are powered, and the routers have successfully joined the
network
Page 72 of 83
System Router
Symptom Cause Actions
No connectivity to receiver
Router has not been authorized to the receiver
Manually authorize router to receiver or use auto‐commissioning
No radio connection Check aerial on receiver
Check aerial on router
Receiver not switched on Switch receiver on
Router not switched on Switch router on
Incorrect supply polarity Check supply polarity
Router fuse Check router fuse is OK, replace if
necessary
Router appears in "Unknown" category in CMS when
commissioning
Router has joined network but has yet to pass configuration
data to the receiver None ‐ normal operation
Router stays in "Unknown" category in CMS when
commissioning for more than 3 minutes
Router hardware error Check router options fitted (thermistor,
RH&T element)
Router connects directly to the receiver, even though there's a
router between them
Normal. An router will ALWAYS join a network using the least number of "hops" to the
receiver.
None ‐ normal operation. The router will re‐join the network via the other router if it loses its direct path to the
receiver
Only 4 routers connect directly to my receiver
Normal. The maximum number of directly connected routers a receiver will allow is 4, if there are 12 directly connected EDs
None ‐ normal operation
Only 8 routers connect directly to my router
Normal. The maximum number of directly connected routers a router will allow is 8 if there are
8 directly connected EDs
None ‐ normal operation
Page 73 of 83
RF‐IOM
Symptom Cause Actions
No connectivity to receiver
RF‐IOM has not been authorized to the receiver
Manually authorize RF‐IOM to receiver or use auto‐commissioning
No radio connection Check aerial on receiver
Check aerial on RF‐IOM
Receiver not switched on Switch receiver on
RF‐IOM not switched on Switch RF‐IOM on
Incorrect supply polarity Check supply polarity
RF‐IOM fuse Check RF‐IOM fuse is OK, replace if
necessary
RF‐IOM appears in "Unknown" category in CMS when
commissioning
RF‐IOM has joined network but has yet to pass configuration
data to the receiver None ‐ normal operation
RF‐IOM stays in "Unknown" category in CMS when
commissioning for more than 3 minutes
RF‐IOM hardware error Check RF‐IOM
RF‐IOM connects directly to the receiver, even though there's a
RF‐IOM between them
Normal. An RF‐IOM will ALWAYS join a network using the least number of "hops" to
the receiver.
None ‐ normal operation. The RF‐IOM will re‐join the network via the other RF‐IOM or router if it loses its direct
path to the receiver
Only 4 RF‐IOMs connect directly to my receiver
Normal. The maximum number of directly connected RF‐IOMs a receiver will allow is 4, if there are 12 directly connected EDs
At least one more RF‐IOM or router must be added
Only 8 RF‐IOMs connect directly to my router
Normal. The maximum number of directly connected RF‐IOMs a RF‐IOM or router will allow is 8 if there are 8 directly connected
EDs
At least one more RF‐IOM or router must be added
Input LED flashing
Normal. This denotes that the input has been set up and a VFC digital input, but is in the OFF
state.
None ‐ normal operation
Input LED ON
Normal. This denotes that the input has been set up and a VFC digital input, but is in the ON
state.
None ‐ normal operation
Input type changed but the change is not shown in CMS
RF‐IOM not reset after change has been made.
Press the reset button on the RF‐IOM
Page 74 of 83
System Receiver
Symptom Cause Actions
LED D603 flashing once per second
The receiver has found no children on the network
Check aerial and extension co‐ax (if fitted)
If commissioning a network, ensure the receiver is in auto‐commissioning mode, or manually authorize new
devices
Ensure network devices are switched on and in range
LED D603 on receiver not lit at all
No power to receiver Check power to receiver
Receiver not switched on Switch on receiver
Receiver fuse
Check power supply polarity if using a DC supply
Check receiver fuse is OK, replace if necessary
No analogue output voltages Output(s) not mapped Map analogue outputs with CMS
LED D604 flashing occasionally Reception of network data None ‐ normal operation
Page 75 of 83
CMS
Symptom Cause Actions
CMS doesn't start
No receiver connected to PC Connect receiver to PC using USB cable
Receiver not switched on Switch on receiver
Drivers not installed Install drivers
Another instance of CMS is already running on the PC
Only one instance of CMS can run at a time
Some menu items are greyed out
Not logged in as admin Log in at admin level
Admin level timed out Log in at admin level
Auto‐commissioning mode is enabled.
Disable auto‐commissioning mode
Map display not visible Graphical display not selected Select graphical display
Text display not visible Text display not selected Select text display
Device in Sensor tree is shown in blue
Device not on map display Drag‐and‐drop onto map display
Device in Router tree is shown in blue
Device not on map display Drag‐and‐drop onto map display
Links in map display are not in colour
Not logged in as admin Log in at admin level
When reconnecting to a receiver, device values don't appear
immediately Normal
Wait for devices to report latest values to the receiver
When first commissioned, ED parameter values such as hours
run are shown as "?" Normal
Request extra information using the "Refresh Node Information" method
After changing a battery, an EDs battery hours run value hasn't
changed Normal
Request extra information using the "Refresh Node Information" method
When I request node information, the data doesn't come back
immediately
Normal ‐ an ED will only send this data the next time it wakes
Wait for devices to report latest values to the receiver
Device didn't accept label change and turned red in the map display
Tried to change label while in auto‐commissioning mode
Disable auto‐commissioning mode. Wait for device to return to normal, or
power cycle
Device didn't accept transmit time change
Tried to change label while in auto‐commissioning mode
Disable auto‐commissioning mode. Wait for device to return to normal, or
power cycle
Page 76 of 83
System Receiver RF‐RXS‐N
Symptom Cause Actions
Network LED flashing once per second
The receiver has found no children on the network
Check aerial and extension co‐ax (if fitted)
If commissioning a network, ensure the receiver is in auto‐commissioning mode, or manually authorize new
devices
Ensure network devices are switched on and in range
LEDs on receiver not lit at all No power to receiver Check power to JACE
No communications SonNet driver configured for
wrong JACE slot Configure SonNet driver for correct slot
(see page 51)
Data LED flashing occasionally Reception of network data None ‐ normal operation
System Receiver RF‐RXS
Symptom Cause Actions
Network LED flashing once per second
The receiver has found no children on the network
Check aerial and extension co‐ax (if fitted)
If commissioning a network, ensure the receiver is in auto‐commissioning mode, or manually authorize new
devices
Ensure network devices are switched on and in range
LEDs on receiver not lit at all
No power to receiver Check power to receiver
Receiver not switched on Switch on receiver
Receiver fuse
Check power supply polarity if using a DC supply
Check receiver fuse is OK, replace if necessary
No communications via RS‐232 port
USB port connected to PC Disconnect USB
Data LED flashing occasionally Reception of network data None ‐ normal operation
Page 77 of 83
Estimating Network Coverage in the Absence of a Site Survey The theoretical transmission distance that can be achieved between two wireless devices can be calculated from a few “key” parameters;
Transmission power of device. This is the wireless device's transmission power and is typically measured in dBm. With greater transmission power, greater distances can be achieved.
Receiver sensitivity of device. This is the wireless device's receiver sensitivity and is typically measured in dBm. With greater receiver sensitivity, the device is able to receive weaker signals, which means greater distances can be supported
Antenna gain. The gain for an antenna is typically measured in dBi and basically indicates how much the signal is boosted by the antenna.
Frequency. The frequency is typically measured in MHz or GHz and indicates which electromagnetic band is used for wireless communication.
The formula for calculating the theoretical transmission distance is based on the Friis Transmission Equation for free space loss. The Friis Transmission Equation can be modified to give range, as follows:
10 /
41.88 ∗
where: r = range in km Pt = Transmit power (dBm) Pr = receiver gain (dBm) Gt = transmitter aerial gain (dBi) Gr = receiver aerial gain (dBi) f = frequency (MHz)
SonNet Routers, RF‐IOMs and Receivers
Frequency 2400 MHz
Tx power 10 dBm
Tx antenna gain 3 dBi
Rx antenna gain 3 dBi
Rx sensitivity ‐102 dBm
Theoretical Range (km) 7.9km
SonNet End Devices
Frequency 2400 MHz
Tx power 0 dBm
Tx antenna gain 1.2 dBi
Rx antenna gain 1.2 dBi
Rx sensitivity ‐96 dBm
Theoretical Range (km) 0.8km
Note that this gives the theoretical transmission distance that can be achieved. Certainly, there are likely to be significant differences between the theoretical transmission distance and the actual results in the field, as these calculations are based on an unobstructed line‐of‐sight signal with no electronic interference.
Page 78 of 83
However, the real world presents many variables that result in less “ideal” wireless performance, such as building obstructions and reflected signals. Therefore, it is always preferable to conduct a thorough site survey in order to determine what is actually happening to the wireless signals in the field. Before conducting a site survey, however, it may be helpful to evaluate the different options available for the wireless hardware. The formula provides a straightforward way to perform this evaluation and whether the desired transmission distance it can be achieved and so make an informed decision when selecting SonNet devices for different wireless applications. Attenuation Properties of Common Building Materials
Building Material 2.4 GHz Attenuation
Solid Wood Door 4.5cm 6 dB
Hollow Wood Door 4.5cm 4 dB
Interior Office Door w/Window 4.5cm /1.3cm 4 dB
Steel Fire/Exit Door 4.5cm 13 dB
Steel Fire/Exit Door 6.4cm 19 dB
Steel Rollup Door 3.8cm 11 dB
Brick 8.9cm 6 dB
Concrete Wall 45.7cm 18 dB
Cubical Wall (Fabric) 5.7m 18 dB
Exterior Concrete Wall 6.4cm 53 dB
Glass Divider 1.3cm 12 dB
Interior Hollow Wall 10.2cm 5 dB
Interior Hollow Wall 15.2cm 9 dB
Interior Solid Wall 12.7cm 14 dB
Marble 5.1cm 6 dB
Bullet‐Proof Glass 2.5cm 10 dB
Exterior Double Pane Coated Glass 2.5cm 13 dB
Exterior Single Pane Window 1.3cm 7 dB
Interior Office Window 2.5cm 3 dB
Safety Glass‐Wire 0.6cm 3 dB
Safety Glass‐Wire 2.5cm 13 dB
Strategy
1.
An examof the kheater t In this eswitch) battery If RF‐IOpotenti The simstate (i.module
Note tha 0V us This ens
2.
Thereforequest
y Tips
When usingsafeguards tits parent re
mple of this iskey interlockinto be powere
example, the is connected.
OM1 goes offlally unsafe to
mple Niagara W.e. it goes offe (FALSE in thi
hat in the eveing the appro
sures that the
It should besent, wheth
ore, other parted. As simple
g wireless dethat can take eceiver.
s where an RFng safety featud on.
fan status (ta to a VFC inp
line, the cont switch the he
Workbench stfline), it will cs case), rather
nt that RF‐IOMpriate fall‐bac
e heater batte
e remembereher by transmi
rameters, suche strategy to re
evices to conprotective act
F‐IOM analoguures would be
aken from, forut on RF‐IOM
trol strategy aeater battery o
rategy below cause the Boor than the nor
M2 goes offlinck value settin
ry will be swit
d that only mssion time or
h as battery request this inf
Page 79 of 83
ntrol critical tion in the eve
ue output is ue to ensure th
r example, a M1 and the ou
and RF‐IOM2 on.
monitors theoleanSelect tormal control s
ne, the outpung.
tched off if eit
measured valusignificant ch
runtime, pareformation on
Right‐click omenu, and updated and
plant, it is aent a wireless
used to switchhat the supply
Sontay PA‐93utput from RF
no longer kn
e status of RF‐o output the vstatus derives
t controlling t
ther of the RF
ues from an Ehange of value
nt LQI and dea timed inter
Addwira twh
on the triggethen right‐cl
d select <Link
always advisadevice loses
on an electriy fan is runnin
0 air DP switc‐IOM2 is used
nows if the fa
IOM1, and if value held in from strategy
the heater can
F‐IOMs goes o
ED, router or e.
evice runtime,val basis can b
d a “Dailyresheet, and stime of day en there’s lea
er, select <Liick on the Sfrom “trigger
able to add communicatio
ic heater battng before allow
ch or PM‐CSXd to driver the
an is running,
it goes into a the BooleanW
y.
n be configur
offline.
RF‐IOM are n
, are NOT senbe achieved.
y Trigger” set its param(probably a
ast activity).
ink Mark> frSonNet devicname”>.
strategy ons with
ery. One wing the
X current e heater
, so it is
“Down” Writable
ed to go
normally
nt unless
to the meters to at night,
rom the e to be
Now, w NB If seare stag
3. Add a Sthe Boo
when the trigge
everal SonNetggered by at le
Strategy can
StatusDemux olean Writable
er module fire
t devices are teast 15 minut
n be used to o
module to thee.
es, it will caus
to be updatedtes, to avoid h
on a wiresheet
e wiresheet, w
Right‐click o
Page 80 of 83
e a “Get All D
d this way, it iheavy network
t to show the
with a Boolea
on a SonNet d
Select <and “Geside. ORuntimspecificupdated SpecificData>, aand con
ata” comman
is strongly reck traffic.
status of a So
an Writable. L
device, select
Right‐cland seleselect <Status” Click th If requWritabla True status. A <Boobe addalarmin
<Fire Trigger>et All Data” oOther optionse> or <Get Paally what id. Click the <O
c updates are as less netwonsumes less ba
d to be sent t
commended t
onNet device.
ink the <Dow
<Link Mark> f
ick on the Sect <Link from<Status> on thon the Statuse <OK> button
ired, the face can be chanstatus, and
oleanChangeOded to the Bg purposes.
> on the trigon the SonNes are to selearent Lqi>, if tis required OK> button.
preferable to ork traffic is geattery power
to the SonNet
that the upda
wn> slot to an
from the men
StatusDemux m “device namhe device sidesDemux modn.
cets of the nged to “OFFLONLINE for
OfStateAlarmEBoolean Writa
ger side et device ect <Get hese are to be
<Get All enerated in EDs.
t device.
te times
input of
nu.
module me”> and e and “In ule side.
Boolean LINE” for a False
Ext> can able for
4. Two Nuand thesensor) The inpavailabl
Two Nuand thesensor) The inpavailabl
Scaling a 4‐2
umeric Writabe lower 0°C, fo. The example
put value fromle from the Ou
5. Scaling
umeric Writabe lower 0°C, fo. The example
put value fromle from the Ou
20mA RF‐IOM
bles are used tor a temperate below uses a
m the RF‐IOMut slot of the
a voltage RF‐
bles are used tor a temperate below uses a
m the RF‐IOMut slot of the
Input
to set the uppture sensor, oan upper of 10
M is linked to Scaled Curren
IOM Input
to set the uppture sensor, oan upper of 10
M is linked to Scaled Voltage
Page 81 of 83
per and lower the upper co00 and a lowe
InA slot of tnt Value modu
per and lower the upper co00 and a lowe
InA slot of te Value modu
r ranges (for eould be 500Paer of 0, typica
he Subtract1 ule.
r ranges (for eould be 500Paer of 0, typica
he Multiply3ule.
example, thea and the lowl for an RH sen
module, and
example, thea and the lowl for an RH sen
module, and
A Boolean Wto offer scalior 0‐10Vdc in
e upper could wer 0°C, for a pnsor.
the scaled o
e upper could wer 0°C, for a pnsor.
the scaled o
Writable can bing for either nputs.
be 40°C pressure
output is
be 40°C pressure
output is
e used 0‐5Vdc
As a rulB and Cmethod
It will suffixeIf any vIt is imdevicesand wiA devictimeouresponTo ensset acc
6. Scaling
le, for greatesC are specificd. The final Su
7. Stale V
be noticed d stale. Thvalues aren’tmportant to s (routers orll therefore eces measureut period. Tynse time is seure this doecordingly;
Right‐click navigation
Expand the
a Resistive RF
st accuracy, thc to a 10K3Aubtract modul
Values
that some pis is becauset updated wiremember tr EDs). Confieventually bed values wiypically, an Eet to 1 minutesn’t happen
on the <Stree, then se
e <Tuning P
F‐IOM Input fo
he precision of1 thermistor, e can be omit
points showe the driver lothin this timthat, under guration pare marked asll be markedED has its dte (for examp, it is strong
SonNetNetwelect <ViewsPolicies>
Page 82 of 83
or a 10K3A1 T
f the module but others c
tted if °K is req
wn in the recooks for valu
me they are mnormal conrameters ands stale. d as stale if efault transple), the meagly recomme
work> foldes> then <Prsection, the
Thermistor
facets shouldcould be usedquired, rather
ceiver, routeues to be upmarked as staditions, onlyd other data
they are nomission timeasured valueended that th
er in the <operty Shn expand the
toremtoaftrmpath
be set to 12. d, according tthan °C.
er and ED pdated with aale. y measured a are not sen
ot updated we set to 900es will be mahe receiver r
<Station\Ceet> e <Default
Set tho 16 minuteeflects longemay require to the driveffected not ansmission
many routersass its mhrough to get
The 3 coefficto the Steinh
property shea configurab
values are nt unless req
within the re0 seconds, soarked as staleresponse tim
Config\Dri
t Policy> s
he <Stale es (or a valuest time a to pass inforer, which monly by its time but bs it may n
measurementt to the rece
cients, A, hart‐Hart
eets are le time.
sent by quested,
esponse o if the e. meout is
ivers>
section.
Time> ue that device
rmation may be default by how eed to t data eiver.
Alarms Alarms
s
s can be set u
Open the wiresheet.
Drag a newclass.
Next, dragmonitoring
up using the
<Alarm> paCall it “SonN
w <Console
g alarm exteg. In the alar
<Alarm> pa
alette and dNet Alarms”.
eRecipient
ensions fromm extension
Page 83 of 83
alette.
drag a new .
t> onto the
m the alarms property s
<Alarm Cl
wiresheet a
palette ontheet, set the
lass> onto
and link it to
to points we alarm class
the Alarm
o the SonNe
which require to SonNet A
Service
et alarm
e alarm Alarms.