tridium jace integration user manual version 2.0 sonnet & tridium jace integration user manual...

of 47

Sontay® SonNet & Tridium JACE Integration

User Manual

Version 2.0

March 2014

of 47

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 integration of the Sontay® SonNet radio sensor system to Tridium JACE. 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

of 47

Table of Contents: Overview .................................................................................................................................................. 4 Environmental .......................................................................................................................................... 4 Battery Fitting and Replacement .............................................................................................................. 4 Disposal of Batteries ................................................................................................................................. 4 Devices Types ........................................................................................................................................... 5

Battery Powered Nodes ............................................................................................................. 5 24V Powered Routers ................................................................................................................. 7 230Vac Powered Routers ........................................................................................................... 9 24V Powered Routers ................................................................................................................. 9 The System Receiver ................................................................................................................ 10 The RF‐IOM .............................................................................................................................. 10

The Radio Network ................................................................................................................................. 12 Network Planning Considerations ............................................................................................ 13

The Radio System ................................................................................................................................... 15 Security ................................................................................................................................................... 15 How the Self‐Healing Tree Network is Formed ...................................................................................... 15 Propagation Of Radio Signals in Buildings .............................................................................................. 16 Extension Aerials .................................................................................................................................... 17 SonNet‐Tridium JACE Driver Action Menus ........................................................................................... 18

Network Action Menu .............................................................................................................. 18 Receiver Action Menu .............................................................................................................. 18 Router Action Menu ................................................................................................................. 19 RF‐IOM Action Menu ................................................................................................................ 20 Sensor Action Menu ................................................................................................................. 21

Managing a Tridium JACE SonNet Wireless Network ............................................................................. 23 Requirements ........................................................................................................................... 23 Installing the SonNet Driver to a Tridium JACE ........................................................................ 23 Adding a SonNet Network........................................................................................................ 24 Prerequisites ............................................................................................................................ 24

Commissioning a SonNet Network ......................................................................................................... 25 Commissioning an Existing Network ........................................................................................ 25 Commissioning a New Network ............................................................................................... 26

Configuring Network Devices ................................................................................................................. 27 Device Prefixes ......................................................................................................................... 27 Receiver .................................................................................................................................... 27 Routers ..................................................................................................................................... 28 RF‐IOMs .................................................................................................................................... 29 Writing Output RF‐IOM Values ................................................................................................ 30 RF‐IOM Fallback Values ............................................................................................................ 30 End Devices (EDs) ..................................................................................................................... 32 The VFC Activation Count Point ............................................................................................... 33

Commissioning Multiple Networks on the Same Site ............................................................................ 34 Pre‐commission each network away from site ........................................................................ 34 Commission each network individually on site ........................................................................ 34

Best Practise Points ................................................................................................................................ 35 Trouble‐Shooter’s Guide ......................................................................................................................... 36 Estimating Network Coverage in the Absence of a Site Survey ............................................................. 41

Attenuation Properties of Common Building Materials .......................................................... 42 Strategy Tips ........................................................................................................................................... 43 Alarms .................................................................................................................................................... 47

of 47

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.

of 47

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.

of 47

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.

of 47

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

of 47

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.

of 47

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

of 47

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. 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‐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Ω) 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. 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

of 47

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 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

of 47

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

of 47

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.

of 47

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

of 47

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. Niagara WorkPlace AX 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

Scatteri

ation of Radio

opagation of m

ation

ing

Re

Transmit

o Signals in Bu

microwave rad

eceiver

tter

uildings

dio signals in a

Radio signal attenuated mmaterials typespecially ste

Reflection Depending otransmitter to ‘Multipath’ sreducing ove

Scattering th

of 47

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,

of 47

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.

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. FAput

b. TRUto

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 drivt the receiver UE = The drivput the receival 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 ninto auto com

ver will not finver into auto cmunications –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

of 47

ermines whethe nodes alreadymmissioning mnd nodes alrecommissioninThis 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 commissionemode. ady commissing mode. nd 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

ed to a receiv

ioned to a rec

ally 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

ver without h

ceiver withou

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

aving to

ut having

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

of 47

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.

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 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 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

ommand gets

of 47

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

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

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

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

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

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

of 47

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

of 47

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

of 47

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.

of 47

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

of 47

“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>

of 47

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

of 47

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

of 47

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

of 47

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

of 47

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.

of 47

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

of 47

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

of 47

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.

of 47

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 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 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.

of 47

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 to 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 JACE driver 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.

of 47

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 when commissioning

ED has joined network but has yet to pass configuration data

to the receiver None ‐ normal operation

ED stays in "Unknown" category when commissioning for more

than 30 minutes ED hardware error

Check ED options fitted (SP pot, thermistor, RH&T element)

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 "Get all data" 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

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

of 47

System Router



Router has not been authorized to the receiver

Manually authorize router to receiver or use auto‐commissioning


Check aerial on router


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 when commissioning

Router has joined network but has yet to pass configuration

data to the receiver None ‐ normal operation

Router stays in "Unknown" category 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


of 47

RF‐IOM



RF‐IOM has not been authorized to the receiver

Manually authorize RF‐IOM to receiver or use auto‐commissioning


Check aerial on RF‐IOM


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 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 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.


Input LED ON

Normal. This denotes that the input has been set up and a VFC digital input, but is in the ON

state.


Input type changed but the change is not shown

RF‐IOM not reset after change has been made.

Press the reset button on the RF‐IOM

of 47

System Receiver


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

LED D604 flashing occasionally Reception of network data None ‐ normal operation

of 47

System Receiver RF‐RXS‐N


Network LED flashing once per second




devices


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


Network LED flashing once per second




devices


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

of 47

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.

of 47

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

of 47

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

of 47

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

of 47

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>

of 47

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

of 47

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.

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.