SE7000/SE8000 Room Controllers
ZigBee Pro Wireless Integration Guide
Get Control. Get Efficient. Get Value
Page 2
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Table of Contents
Who Should Read this Page .................................................................................................................................. 3
About this Guide ....................................................................................................................................................... 3
SE7000 Series / SE8000 Series ........................................................................................................................... 5
ZigBee Pro ................................................................................................................................................................. 6
ZigBee Pro Protocols .............................................................................................................................................. 6
Trust Center ............................................................................................................................................................... 7
Trust Center Link Keys ............................................................................................................................................ 7
Distribution of the Network Key ............................................................................................................................ 7
Design and Deployment .......................................................................................................................................... 7
Working with ZigBee Pro ........................................................................................................................................ 8
Extended PAN ID (EPID) ......................................................................................................................................... 8
Security and Trust Center ...................................................................................................................................... 8
Application Link Keys .............................................................................................................................................. 8
Trust Center Link Keys ............................................................................................................................................ 9
Joining a Network .................................................................................................................................................... 9
Applications in ZigBee Pro ....................................................................................................................................14
Sensors and Aggregator ........................................................................................................................................14
Sensor and Actuator ...............................................................................................................................................14
Client and Server .....................................................................................................................................................14
Gateway and Proxy .................................................................................................................................................14
Client and Server .....................................................................................................................................................14
Gateway and Proxy .................................................................................................................................................14
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
ZigBee Pro Network ..............................................................................................................................................15
ZigBee Pro Message Flow .....................................................................................................................................15
Setting Device Data Points ...................................................................................................................................19
Change of Values ................................................................................................................................................... 20
Procedures - Integrate Room Controller and Manager ..................................................................................21
Procedure - Configure SE7200, SE7300, SE7600 and SER7300 Series ...................................................21
Procedure - Configure SE8000 Series ...............................................................................................................21
Procedure - Login to Manager ............................................................................................................................ 22
Analog Outputs Properties .................................................................................................................................... 46
Analog Hardware Values Properties .................................................................................................................... 47
Analog Inputs Properties ....................................................................................................................................... 49
SE720xx Integration – Graphic User Interface (GUI) objects ....................................................................... 51
SE73xxX Integration – Graphical User Interface (GUI) Objects.................................................................... 52
SE8000X Integration – Graphical User Interface (GUI) Objects ................................................................... 53
SE8000X Integration – Graphical User Interface (GUI) Objects ................................................................... 53
Tips and Things You Need To Know ................................................................................................................... 54
3
Page 4
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Who Should Read this Guide
This guide is for integrators of SmartStruxure™ Lite solutions. It provides important information for getting you started with the
set-up and configuration of your building efficiency management system.
Ensure you follow the instructions to ensure a successful and trouble-free installation at the client’s site.
Plan and Prepare
The information contained here helps you work effectively and minimizes the likelihood of any critical issues occurring during
installation. Successful integration of your SmartStruxure Lite system requires proper preparation and planning. Planning in
advance saves resources, prevents wasted effort, and saves time and money for you and your customer.
About this Guide
This guide provides instructions for the physical integration of a SER7000/SE8000 Series model the with the following
Multi-purpose Manager (MPM):
• MPM-UN
• MPM-VA VAV
• MPM-GW
For more information visit our website at www.documentation.smartstruxurelite.com
Overview
This guide focuses on full integration of Multi-purpose Managers (MPM) and Room Controller with a built in Wireless Controller
Driver Card in a ZigBee Pro adapter environment.
4
Page 5
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Multi-purpose Manager
Multi-purpose Manager (MPM) Devices are flexible lines of site and zone Managers. They allow you to install and manage
integrated solutions for HVAC, lighting, and metering. They are also a quick and efficient link between multiple devices based on
many standard protocols.
The Building Expert web building energy management system is embedded in MPM Devices.
Multi-purpose Managers are fully programmable and are designed with wireless lighting and HVAC applications in mind. They can
also be used to control a wide range of ZigBee Pro compatible devices such as light sensors, light switches, relays, thermostats,
card readers, and magnetic door contacts.
MPM-UN
The MPM-UN is an electronic device designed to monitor and control various devices for building automation applications. The
Manager consists of a printed circuit board housed in a plastic shell casing.
5
5
External connectors are available for the following:
• 6 universal inputs
• 4 analog outputs
• 2 binary outputs (dry contact)
• LAN (Ethernet cable)
• RS-485 device (Modbus)
• CANbus
• Power supply
The device has wireless modules to enable bidirectional communication with ZigBee Pro devices. Managers can communicate
with each other wirelessly using their ZigBee Pro modules.
MPM-GW
The MPM-GW wireless Manager is an electronic device designed to integrate wireless solutions to wired building automation
systems.
Small buildings system gateways can integrate wireless devices based on ZigBee Pro protocols and standards into building
automation systems.
The MPM-GW is a printed circuit board housed in a plastic shell casing. Unlike the MPN-UN and MPM-VA, there are no physical
(wired) I/Os on this Manager.
Page 6
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
The following connectors are concealed in a casing:
• LAN
• CANbus
• Power supply
The MPM-GWs have embedded ZigBee Pro wireless modules to enable bidirectional communication with ZigBee Pro devices. The
Managers can also communicate with each other wirelessly using their ZigBee Pro modules.
MPM-VAV
The MPM-VAV Manager is designed to monitor and control various devices for building automation purposes, including VAV
boxes. It can also control various devices for building automation applications.
6
External connectors are available for the following:
• 6 universal inputs
• 4 analog outputs
• 2 binary outputs (dry contact)
• 1 damper actuator
• 1 pressure sensor
• LAN (Ethernet cable)
• RS-485 device (Modbus)
• CANbus
• Power supply
The device has a pressure sensor and is equipped with an optional damper actuator. The device also has optional embedded
EnOcean and ZigBee Pro wireless modules to enable bidirectional communication with their respective protocol. The Managers
can communicate with each other wirelessly using their ZigBee Pro modules.
Room Comfort Controllers
The Room Comfort Controller allows for simple management of multiple equipment controllers from one convenient location.
The device is compatible with terminal equipment controllers including fan-coil units, rooftop units, and heat-pump models. You
can also adjustment set points, central system modes, global overrides, broadcasting of outdoor temperature, and central alarm
reporting.
The wireless communication card can be separately installed in the Room Controller for use with Schneider Electric MPM
Controllers. The communication card and associated wireless communicating controllers encourages the use of existing wiring
utilized by existing electronic Controller type controls.
SE7000 Series SE8000 Series
Page 7
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
ZigBee Pro Overview
ZigBee Pro is a specification for a suite of high level communication protocols used to create personal area networks built from
small, low-power devices. Though low-powered, ZigBee Pro devices often transmit data over longer distances by passing data
through intermediate devices to reach more distant ones. This is accomplished by creating a mesh network, such as a network
with no centralized control or high-power transmitter/receiver able to reach all of the networked devices.
ZigBee Pro is a standard which is suitable for wireless sensor and controller networks. In ZigBee Pro, a device, node, or
Controller is determined to have joined a network if it can obtain a ZigBee Pro network address from a parent device, provided
it passes the necessary security protocols. This ZigBee Pro address is a value which is not initially exposed or available for the
integrator to see.
Devices, nodes, and Controllers can calculate and assign addresses for their surrounding devices by a distributed address
assignment scheme. This assignment is flexible, but it does somewhat restrict the number of attached devices and the possible
depth of the said network for any given device on the network.
ZigBee Pro is a mesh type network. The ZigBee Pro coordinator, or MPM with wireless communication card, is responsible for
initializing, maintaining, and controlling the network. For mesh networks, devices communicate with each other in a multi-hop
fashion. The network is formed by one ZigBee Pro coordinator and extended by multiple ZigBee Pro routers. A device can join a
network as an end device by associating with the coordinator or a router.
A ZigBee Pro network typically has the following three types of devices:
• ZigBeeProCoordinator:heart of the network. There must be one and only one coordinator per network. Its role is to act as a trust center and
to allow and approve all routers and end devices attempting to join its network.
• ZigBeeProRouter: the link in the network. It routes packets between other nodes, providing extended network range. A router device is always
on to provide routes for other devices acting as a parent for end devices.
• ZigBeeProEndDevice: only has the functionality to achieve a specific task and communicate with a parent node (either coordinator or router).
It cannot relay data from other devices.
7
Addresses
Once a device, node, or Controller is assigned a ZigBee Pro address and has joined the active ZigBee Pro network, it saves its
assigned ZigBee Pro address to flash memory. The address gets reused afterwards, even in the event of a power failure or a
network re-start. The only time a device, node, or Controller requires a new ZigBee Pro address is if the network gets re-started
with either a new PAN ID or a new Channel value. This causes the currently assigned and saved ZigBee Pro address (stored in
flash) to get erased, and forces the MPM to try to re-join a new network.
ZigBee Pro is used in applications that require low data rate, long battery life, and secure networking.
ZigBee Pro Protocols
ZigBee created many protocols based on IEEE 802.15.4, which ultimately led to the evolution of ZigBee Pro. ZigBee Pro is a
vertical stack from the application layer down to 802.15.4 and the network layer uses the same addressing as 802.15.4. The
network layer supports a mesh network of routers that are continually powered. Also supported are end devices that do not route
messages on the mesh, but can receive and send through a parent routing node. An end device node is referred to as a ZigBee
End Device or ZED.
Routes in ZigBee Pro are always created through broadcast discovery and are always self-healed dynamically from the point of
failure. As well, ZigBee Pro supports a single Network Key where all messages are encrypted and decrypted at every hop. Nodes
may also have local keys, called Application Link Keys, which are used to communicate end-to-end to other nodes.
ZigBee Pro supports a Trust Center from which security keys are distributed.
ZigBee Topology
ZigBee Pro runs over 802.15.4 spread spectrum and is designed to coexist with WiFi. ZigBee is a mesh, where messages hop
from router node to router node. However, sleeping devices do not route but may send messages and receive messages buffered
in a parent device. A parent may change during a sleeping devices lifetime. Routes are fixed, until there is a route failure, upon
which a new route is reestablished. Temporary interference is handled by spread spectrum and retries.
Page 8
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
ZigBee Security
Security is enforced by the Trust Center service, which currently resides on a single node.
There are two kinds of keys:
1. Network Key protects the network from outside access.
2. Application Link Key protects transactions between a pair of nodes, or from other nodes in the same network.
Schneider Electric products have only an Application Link Key from a device to the Trust Center.
Network Key
All messages are encrypted by a Network Key, and every node in the network must know the Network Key. The Network Key is
a shared secret, but may change over the life of the network. At every hop along its route to its destination, the Network Key is
used to decrypt the message for processing, and then re-encrypt the message before forwarding
Trust Center
A Trust Center decides if a device can join the network. The Trust Center sends the Network Key to a device that is joining the
network. The Network Key is encrypted with the device’s Trust Center Link Key. The Trust Center may have an address list to
prevent or allow nodes to join the network. The Trust Center then sends the joining node a unique Trust Center Link Key that the
Trust Center keeps in a database.
Trust Center Link Keys
The Trust Center Link Key is an intrinsic Application Link Key that is stored in every node and always used when a node talks to
the Trust Center. Each device may have a unique Trust Center Link Key, however, all Trust Center Link Keys may be the same
shared secret value. The Trust Center Link Key defines the trust relationship between the node and the Trust Center.
8
Distribution of the Network Key
The Network Key is transported to the device using the Trust Center Link Key (TCLK). By default every device has a well known
default TCLK, and the initial transport of the Network Key is vulnerable at installation time. When installation is complete, the Trust
Center sends a new random TCLK to the device.
Wireless Mesh Networks
The wireless card and related network ready wireless controllers series operate using the ZigBee Pro/IEEE 802.15.4 physical layer
for communication.
The following shows general characteristics of the wireless physical communication layer:
• Uses a wireless physical layer of 2.4GHz with a data rates of 250 kbps
• Yields high throughput and low latency
• Mesh Topologies
• Fully handshake protocol for transfer reliability
The following shows IEEE 802.15.4 and ZigBee Pro networks and application support layer:
• Low cost installation deployment
• Ease of implementation
• Reliable data transfer
• Short range operation
• Very low power consumption
• Appropriate levels of security
The MPM with wireless communication card acts as network coordinator device for the IEEE 802.15.4/ZigBee Pro network used
with the Schneider Electric wireless controllers. These features of the network physical layer include receiver energy detection,
link quality indication, and clear channel assessment. Both contention-based and contention-free channel access methods are
supported with a maximum packet size of 128 bytes, which includes a variable payload up to 104 bytes. Also employed are
64-bit IEEE and 16-bit short addressing, supporting over 65,000 nodes per network. These properties of the physical layer
are used and employed in Schneider Electric devices, but are hidden to the installed/user for ease of configuration and
commissioning of the network database.
Page 9
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Design and Deployment
IMPORTANT: It is highly recommended you do a proper field survey with the Schneider Electric necessary survey tools to establish
connectivity limitations and architecture layout on ALL job sites considered for deployment with wireless controller products.
Deployment Tool
The Schneider Electric wireless survey tools are intended to verify and validate the deployment and use of Schneider Electric
wireless controllers on a potential job site. The survey tool shows a numerical percentage value on the LCD screen, which
represents the wireless network ZigBee Pro RSSI dBi value (Receiving Signal Strength Indicator).
The following should be used as a RSSI dBi indicator:
• Any value from 10 to 100% indicates good ZigBee Pro connectivity.
• Any value below 10% could indicate an extra Router (VRP 5000W/1000W) may need to be installed.
Design Considerations
When setting-up a ZigBee Pro wireless environment, a per floor horizontal architecture is recommended over a vertical one.
Transmitting from one floor to the other may be possible in certain applications (such as going through stair ways), however
horizontal configuration is preferred. It is recommended to be use at least one coordinator per floor.
Radio transmissions can not travel through steel. If floors are constructed with steel joists or other steel materials, it is highly
unlikely the wireless controller transmissions can penetrate between floors.
To properly avoid network interference with standard 802.11 WiFi devices in the 2.4GHz spectrum range, it is recommended to
use 802.15.4 channels 15, 20, and 25 only. The 802.11 WiFi transmissions overlap and may interfere with other channel selections
allowed by 802.15, channels 11 to 24. There should be a clear line of sight distance between 2 nodes, and the maximum distance
between each node (Controller) should be under 100 feet (30m) as shown below.
9
Page 10
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Working with ZigBee Pro
ZigBee Pro has a number of optimizations designed specifically for larger networks comprised of thousands of devices. The
following shows you how to work effectively with ZigBee Pro
Network Layer
A ZigBee Pro network is a set of wireless 802.15.4 nodes cooperating to form a mesh network over which messages hop, from
node to node, to reach a destination. The ZigBee Pro network layer uses the same addressing as 802.15.4 (8-byte EUI46 MAC
and 2-byte short address). Network and routing layers (above 802.15.4) support higher level addressing, discovery, and routing.
Extended PAN ID (EPID)
A ZigBee Pro network is identified by its Extended PAN ID (EPID), which is an 8-byte value. An EPID should be unique for all
networks within range of each other, across all radio channels. The ZC lets you choose a random PAN ID from its EPID, and the
2-byte PAN ID (not EPID) is used for normal traffic. Nodes ignore messages with the wrong PAN ID.
The PAN ID links specific Room Controllers to specific ZigBee Pro Coordinators. For every Controller reporting to a Coordinator,
you must set the same channel value both on the Coordinator and the Room Controller(s).
Channels
The Channel links specific Room Controllers to specific ZigBee Pro Coordinators. For every Room Controller reporting to a
Coordinator, you must set the same channel value both on the Coordinator and the Room Controller(s).
It is recommended to use Channels 15, 20, and 25. The default value of 10 is not a valid channel, and the valid range of available
channel is from 11 to 25.
10
Router, End Device, Coordinator, Trust Center
When a ZigBee Pro node attempts to join a network, it scans all channels for existing ZigBee Pro networks. Any ZigBee
Coordinator can form a network by choosing a Channel, PAN ID, and EPID, which often is its own MAC address (EUI64). A ZigBee
Coordinator is automatically assigned the short address 0x0000 referred to as the ZigBee Coordinator or ZC.
ZigBee Pro Coordinators and Routers are the nodes that participate in routing messages on the mesh. ZigBee Pro Routers and
are always powered on.
A ZigBee Pro End Device (ZED) does not route messages for other devices. A ZED is usually asleep but can send a message to
the ZigBee Pro network where it then gets routed. A ZED only receives messages by polling its parent as long as the parent is
within one hop (radio range) of the ZED.
A ZigBee Pro Trust Center (TC) stores and distributes security keys in the network. The Trust Center is a powered device in the
network with sufficient resources to provide Trust Center services. Security material can be transmitted out of band (on the wire) to
the Trust Center.
Broadcasting
ZigBee Pro supports broadcasting, but network broadcasts are discouraged for normal operation because a broadcast message
must be propagated to all nodes in the network, which generates a lot of traffic. In addition, all nodes must repeat the message,
and each node must wait until there is a clear channel to transmit. A broadcast is limited by a radius value that decrements for
each hop.
Security and Trust Center
Security is enforced by the Trust Center service, which currently resides on a single node, and has the following two key types:
• Network Key: protects the network from outside access.
• Application Link Key: protects transactions between a pair of nodes and from other nodes in the same network.
Network Key
All messages are encrypted by a Network Key and every node in the network must know the Network Key. The Network Key is a
shared secret, but may change over the life of the network.
At every hop along its route to its destination, the Network Key is used to decrypt the message for processing, and then reencrypt the message before forwarding. A Trust Center decides if a device can join the network and sends the Network Key to
the device attempting to join the network. The Trust Center may have a list of MAC addresses to prevent or allow nodes to join
the network. The Trust Center may also require devices attempting to join the node have a unique Trust Center Link Key the Trust
Center has in a database.
Page 11
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Application Link Keys
An Application Link Key is used to encrypt only the application payload of the message. The payload is only decrypted at the
destination, and is therefore secure from any other nodes that come across the message along the route. Application Link Keys
are distributed to a pair of nodes by the Trust Center, and each node keeps a table of Application Link Key/node entries.
Trust Center Link Keys
The Trust Center Link Key is an intrinsic Application Link Key stored in every node and always used when a node talks to the
Trust Center. Each device may have a unique Trust Center Link Key, or all Trust Center Link Keys may be the same shared secret
value.
The Trust Center Link Key defines the trust relationship between the node and the Trust Center. If all Trust Center Link Keys are
the same in every node, then every node on the network can decrypt Trust Center messages from each node. Conversely, if all
Trust Center Link Keys are unique, then each node must communicate individually to the Trust Center securely.
The Trust Center Link Key has a default value which provides no security. To secure the network, the Trust Center Link Key must
be changed during a node’s commissioning time. The Trust Center must also be informed so it can communicate with the node
over its lifetime.
A Trust Center Link Key may become vulnerable under the following conditions:
1. A new secret Trust Center Link Key is transported to a new node at commissioning and gets encrypted with the default Trust
Center Link Key.
2. A new node joins the network, is sent to the Network Key, and encrypted with the node‘s Trust Center Link Key.
11
3. The Trust Center decides to roll (change) the Network Key it transports to each node using each node’s Trust Center Link
Key.
Joining a Network
To join a network, the network needs to be ‘open’ (permit join parameter selected). Any router node may open itself, however the
node that wants to join must be in range of an open node. Once a node successfully joins a network, an announcement is sent to
all nodes. The Trust Center authorizes the new node on the network and transports the Network Key to the newly joined node. If
the Trust Center does not authorize the node, the node is not permitted to join the Network. The Network Key is encrypted with
the Trust Center Link Key that the Trust Center stores for all nodes.
Application Layer
All standard messages are sent and received using the cluster identifier.
Endpoint
A ZigBee Pro endpoint is a port or instance of a device type. A node or device is defined by a single ZigBee Pro radio and stack,
and a ZigBee Pro device type is defined as having particular clusters that it supports.
To address an application message, one of the following options are present in the message:
• [short address] [endpoint] [cluster]
• [broadcast address] [endpoint] [cluster] (used for generic clusters)
Endpoints have a device type and a list of clusters that support the function of the device.
ZigBee devices have up to 240 endpoints. Applications may use endpoints numbered 1-240 and there is no correlation between
application and endpoint number. Endpoint 0 is reserved for use by the ZigBee Device Object (ZDO) for network discovery
and binding services. Endpoint 0xFF is the broadcast endpoint. Each endpoint provides one simple descriptor that describes
the device type, application profile identifier, and a list of input and output clusters. A ZigBee Pro application profile is an interoperable domain, such as the ZigBee Pro Building Automation.
Page 12
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Cluster
An endpoint supports a limited number of clusters. Duplicate clusters on an endpoint are not allowed. Clusters have mandatory and
optional attributes. An attribute is a data value stored on a device and has a particular data type.
Clusters can only communicate to another cluster with the same cluster identifier to form a communication transaction. One
counterpart of the communication is the output cluster (client cluster), and the other counterpart is the input cluster (server cluster).
Usually, the client sends a request and the server responds, however the server can also send unsolicited alarms, reports, etc. Clusters
communicate with commands that are either specific to the cluster or work globally across all clusters. Commands to read, write, and
report cluster attributes (data) are global commands. The support of cluster attributes and commands may be mandatory or optional.
Supported Cluster
12
PartNumberBasicIdentifyGroupsScenesThermostat
SE7657BXXXXXXXXXX
SE7656BXXXXXXXXX
SE7652AXXXXXXXXX
SE7652HXXXXXXXXX
SE7652BXXXXXXXXX
SE7605BXXXXXXXXX
SE7600BXXXXXXXXX
SE7600AXXXXXXXXX
SE7600HXXXXXXXXX
SE7607BXXXXXXXXXX
SE7350CXXXXXXXXXX
SE7300CXXXXXXXXX
SE7355CXXXXXXXXXX
SE7305CXXXXXXXXX
SE7350FXXXXXXXXXX
SE7300FXXXXXXXXX
SE7355FXXXXXXXXXX
SE7305FXXXXXXXXX
SE7200CXXXXXXXX
SE7200FXXXXXXXX
SE7300AXXXXXXXXX
SE7305AXXXXXXXXX
SE7350AXXXXXXXXXX
SE7355AXXXXXXXXXX
SE7600FXXXXXXXXX
SE7652FXXXXXXXXX
SE7606EXXXXXXXXX
SE7656EXXXXXXXXX
SE7600WXXXXXXXXXX
SE7652WXXXXXXXXXX
Temperature
Measurement
Thermostat
UI
Conguration
Occupancy
Sensing
FanControl
Measurement
Note: The end point number for all devices is 10
Relative
Humidity
Attributes Supported in Specified Clusters for Thermostat Clusters
0x0000ZCL Version-Read Only1Specifies the version number of the ZigBee Cluster Library.
0x0001Application Version-Read Only1Specifies the version number of the application software.
0x0002Stack Version-Read Only0x30Specifies the version number of the ZigBee Stack.
0x0003HWVersion-Read Only0Specifies the version number of the hardware.
0x0004ManufacturerName-Read OnlyViconicsSpecifies the manufacturer name.
0x0005ModelIdentifier-Read Only-Specifies the model number.
0x0007PowerSource-Read Only-Specifies the sources of power available to the device.
0x0010LocationDescription-Read/Write-Describes the physical location of the device.
0x0012DeviceEnabled0x00=Disabled,0x01=EnabledRead/WriteEnabledSpecifies if the device is enabled or disabled.
0x01
0x02
BASIC CLUSTER
Ultrasonic
NOT USED
PIR and ultrasonic
NOT USED
Read Only
Specifies in the occupancy
sensed.
Specifies the type of
occupancy sensor.
Page 15
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
FAN CONTROL CLUSTER
Attribute
ID
0x0000FanMode
0x0001FanModeSequence
Attribute IDAttribute NameAccessDefaultFunction
0x0000Identify TimeRead/Write0x0000Specifies the time in seconds that the device will continue to indentify itself.
Attribute Name
Range /
Index
0x00Off
0x01Low
0x02Medium
0x03High
0x04On
0x05Auto
0x06Smart
0x00Low/Med/High
0x01Low/High
0x02Low/Med/High/Auto
0x03Low/ High/Auto
0x04On/Auto
Text DescriptionAccessDefaultFunction
IDENTIFY CLUSTER
Read/WriteAutoSpecifies the current speed of the fan.
Read/WriteLow/Med/High/AutoSpecifies the possible fan speeds available.
15
GROUPS CLUSTER
Attribute IDAttribute NameRangeAccessFunction
0x0000NameSupport
Attribute IDAttribute NameAccessFunction
0x0000SceneCountRead OnlySpecifies the number of scenes currently in the devices scene table.
0x0001CurrentSceneRead OnlyHolds the Scene ID of the scene last invoked.
0x0002CurrentGroupRead OnlyHolds the Group ID of the scene last invoked.
0x0003SceneValidRead Only
0x0004NameSupportRead Only
0=Not Supported
1=Supported
Read OnlyIndicates if group names are supported.
SCENES CLUSTER
Indicates whether the state of the device corresponds to that associated with CurrentScene
and CurrentGroup attributes. True indicates they are valid, false indicates not valid.
Indicates if scene names are supported. Value of 1 indicates they are supported, 0 indicates
not supported.
Attributes
Attributes are data values referenced by a 2-byte identifier. Cluster commands can access attributes. The Read Attribute and
Write Attribute commands use a list of attribute identifiers that must exist under the same cluster. Because each wireless message
targets a single endpoint and single cluster, it is not possible to address multiple attributes of different clusters on the same or
different endpoints.
Reporting
Reporting is a publish/subscribe service that can be supported by any cluster with any attribute. Reporting pushes attributes
to a data sink, without having the sink device(s) poll for the data. Polling can add latencies in any network, especially a wireless
network. The report service uses global cluster commands that allows a configuring device to create a subscription to data on the
reporting device that sends the data to a sink device.
Reporting parameters can be thresholds and intervals. Any device can read the report parameters from the reporting device,
including the destination(s) of the reports. Reporting can send many attributes, but from only one cluster in a single message.
Page 16
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Applications in ZigBee Pro
Architecture relies on the correct management of symmetric keys and the correct implementation of methods and
security policies. The architecture of an application may be decided before or after the project is started.
Sensors and Aggregator
Architecture must be considered in cases where several sensors push data to a single or a few aggregators. To operate,
there must be a powered ZigBee Pro infrastructure of ZigBee Pro Routers so sensors, which are sleeping end devices,
have a network to join. This infrastructure can consist of repeaters only, but could also be partially or completely
comprised of common powered actuators such as lights, pumps, valves, and thermostats.
The aggregators are usually part of an overall management system that may or may not do actual control. Control may
be local and the system only sets parameters the local controllers use.
Sensor and Actuator
Robust control is local when the actuator and sensor are close together. In this architecture, the sensor pushes data to
the actuator. The actuator may mirror the data for the system aggregators and send it on behalf of the sensors.
Aggregators may gather data from other networks in the system, process the data, and push it out to the actuators for
local control parameters.
Client and Server
This architecture defines the roles of a conversation between two devices. Both devices may always play the same role
or different roles depending on the service or transaction.
16
Gateway and Proxy
Gateway architecture is used when ZigBee Pro networks are added to existing wired systems that are orders of
magnitude faster than a wireless mesh. A gateway proxies ZigBee Pro data. If it had to read the data from the ZigBee
network each time the system requested it, this would delay the higher speed system. Therefore, data is stored in a
proxy format that is easy to translate to the wired system. The wired system sees the data as being hosted by the
gateway, and the gateway handles the asynchronous updates from the ZigBee Pro network.
Page 17
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
ZigBee Network Diagrams
The ZigBee Pro network is a collection of ZigBee Pro routers (ZR) that create a mesh. The mesh allows messages to hop from
router to router to a destination. The ZigBee Pro coordinator (ZC) is also a router and provides the security Trust Center which
allows, or disallows, nodes to join the network. ZigBee Pro end devices (ZED) are powered sleeping sensors that wake up
periodically to sense and send data. A ZED only receives messages from a routing parent when it wakes up, but does not route
messages.
ZigBee Pro Network
17
ZigBee Pro Message Flow
A request/response transaction may take many hops through the network, but is transparent to the application layer. Sleeping
devices can add long latencies depending on sleep parameters, however there is no guarantee of an immediate response from a
sleeping device.
Page 18
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
18
Deployment
Facilitating proper development and deployment of ZigBee Pro ensures active device support. It also allows for interaction with
other devices sharing the same ZigBee pro network, as well as to actively poll devices to gain information not unavailable through
passive sniffing, and send/receive ZigBee Pro standard and proprietary messages. The following shows various scenarios to assist
you in deploying your ZigBee Pro installation.
Ensure the minimum distance between any node and any WiFi devices (routers, adapters, laps-tops) is at least 3ft (1m). The
preferable distance is 10ft (3m) or more.
The following should be observed when setting-up your device in a ZigBee Pro wireless environment:
• Ensure at least one controller is within 30 ft of the MPM Coordinator for every cluster of 10 Wireless Room Controllers installed.
• Always try to position, if possible, the MPM near the center of all associated wireless controllers.
• Always try to position the MPM near to and in line of sight to as many wireless controllers as possible.
• Try to avoid metal, brick walls, or concrete obstructions between wireless devices.
• Ensure the antenna on the MPM is always perpendicular to the floor.
• Avoid placing controllers near metal or enclosed in metal boxes. If the MPM needs to be installed inside a metal cabinet, use the remote antenna
accessory.
Non line of sight distance for typical gypsum wall partitions made with metal stud frame should be under 30ft (10m).
Deployment Scenarios
Schneider Electric has identified 10 scenarios for setting up a ZigBee Pro wireless environment.
Scenario 1 - 10
NOTE: At the time of writing, this information is not available
Page 19
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
19
Integrate ZigBee Pro with Room Controller and Manager
Integrating a Room Controller with a Manager involves several steps, all of which must be followed to ensure correct integration
between the two devices. Manual setting of the Room Controller is required before you can integrate it with a Manager. Once the
Room Controller is correctly configured, Building Expert allows you to integrate it with a MPM.
Online/Offline Configuration
Device data points for the integrated Device can be set either Online or Offline. Online or Offline configuration is determined by the
Integrator but can involve User preference, installation environment, availability of equipment, or security issues.
Online Room Controller Database Creation with Live Integration Binding Onsite
Online Configuration lets the Integrator install, integrate, and configure every Room Controller with a Manager in real time. Building
Expert lets you set all device data points and save the data to your Manager for immediate use. Online configuration requires you bind
the Room Controller to a Manager at the time of integration. The Bind process instructs the Manager to locate all Devices and record
their COM address and IEEE Mac Address immediately during the binding process. Once this is done, the integration is complete and
any data point or COV polled to the Manager gets saved and takes immediate affect between the Room Controller and the Manager.
Offline configuration follows the exact same principles as Online configuration. The major difference is there is no binding between
the Room Controller and the Manager database as the integration is not done at the customer site. Assigning Object values and
COV status in Offline Configuration is the same as for Online Configuration. Once the Analog or Binary values are assigned to the
data points, all data can be saved directly to the Managers database. However, since the Room Controller and Manager are not
yet integrated, no wireless communication exists between the two Devices. Although the data is stored in the Managers database,
no action is taken as the Manager does not poll the Room Controller nor receive any broadcasts from the Room Controller until
binding between the Room Controller and the Manager is complete. Once you bind the Room Controller and the Manager,
wireless operation exists between the two Devices.
Offline Configuration is typically used in large scale deployment jobs where creating databases, GUIs, alarms, trend logs, etc,
involves a large investment of time.
Room Controller or Manager Replacement in Field
A Room Controller or a Manager can be replaced in the field at any time. Field replacement involves replacing a defective device
with a new device. The new device must be identical in model number and must be configured identically to the defective device
for the replacement to be successful.
If replacing a Room Controller in the field, the new device must have the identical COM address, PAN ID, and Channel as the defective
device to be recognized by the Manager. The new Room Controller can be configured Offline and switched out directly in the field with
the defective device. As soon as the Manager polls the Room Controller or receives a broadcast from the Room Controller after binding,
it recognizes the parameters in the replaced device and treats it with identical behavior as for the defective device.
While a Room Controller is getting replaced, the Manager continues to poll for the device at its regular 30 second intervals unless
the Room Controller is set as the broadcaster.
Room Controller Configuration
You must first configure the Room Controller before you can set-up the ZigBee Pro wireless environment and integrate the device
with a MPM. The Room Controllers require 24 VAC and the MPM can be powered by either 24VAC or 24VDC. The power supply
must be VAC if you want to share power source between the Manager and Room Controller.
The COM address parameter for a Room Controller is required for communication purposes in a SmartStruxure™ Lite network.
The COM address of each Room Controller must be set to a unique number. This ensures the easiest and fastest way to identify a
specific room controller deployed at the site.
The COM address can be any value between 0 - 254, with the default value set as 254.
Room Controllers join ZigBee Pro networks as routers. You must set two communication parameters,
PAN ID and Channel, to enable communication between the Room Controller and the Manager. The
PAN ID and Channel settings must be the same values for all Room Controllers in the same network.
These settings must also be identical to the PAN ID and Channel settings in Building Expert. Any Room
Controller with a PAN ID or Channel setting different than the settings in Building Expert will not get
discovered on the network when you attempt to discover and bind the Device.
A valid PAN ID can be any value between 1 - 1000, with the default value being 0. The Channel setting
can be any Channel between 10 - 25
Page 20
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Integration
Once you have configured your Room Controller, you must login to Building Expert to integrate the Room Controller with the
Manager. To integrate any Room Controller with a Manager, the Manager must know the Device exists. Building Expert allows you
to add any SE7000 or SE8000 series Room Controller to your solution. Once the device is added, you can use Building Expert
to integrate it with the Manager. It is essential you add the correct Room Controller model when adding a Device to your solution.
Building Expert does not allow you to integrate an incorrect model with your Manager.
You can add more than one Device to your solution, including different model types, before integrating them with your Manager.
However, it is recommended to not add more than 20 Room Controllers per Manager each with 20 data points. This is due to
the available number of data points which should not exceed more than 400. For example, 20 Room Controllers each with 20
data points, or 10 Room Controllers each with 40 data points, falls in the accepted range per Manager. As well, on a ZigBee Pro
network, a maximum of 25 nodes (1 monitor and 24 routers) is the recommended maximum.
The Manager and Room Controllers are not end devices. The Manager can be configured as either a coordinator or router on a
ZigBee Pro network. The Room Controllers are usually configured as routers except when they are used in a network without any
Manager. In this condition, the Room Controller must be configured as the coordinator.
20
Integration with Manager using Building Expert
When all Devices are added to project, Building Expert lets you integrate them with the Manager. You can only integrate one Room
Controller at a time with your Manager. You must individually select the Room Controller you want to integrate from the list of
available Devices.
Binding
After selecting the Device, you must use Building Expert to Bind the Device with the Manager. Binding involves the Manager using
a wireless protocol to search for the COM address and Extended Node ID to integrate itself with the Device. Once the Manager
locates the two parameters, the Binding process completes the integration of the Room Controller and the Manger.
Page 21
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Setting Device Data Points
After integrating the Room Controller with the Manager, you must set the Device data points in Building Expert. There are two
types of Device data points you can set; Required for Block Programming and Others. You must set the Required for Block
Programming with the Device data points.
Setting Device data points involves assigning an
Analog Value or Binary to from the drop-down menu.
Once all the required Device data points for all Room
Controllers are set, you can set as many of the
Other Device data points as you want, provided the
combined total of all Device data points for all Room
Controllers does not exceed 400 data points per
Manager.
You can not assign the same Analog Value to more
than one Object, and Analog Values should be set
sequentially in your project.
All Objects with an assigned Device data point show in Building Expert. You can modify the value for any data points by clicking
on it and making the desired modification directly in Building Expert.
21
Page 22
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Change of Values
value changed, the Manager receives the COV(s) and reads the result based on preset conditions to determine the Present Value
of the Room Controller. If any action is necessary based on the COV, the Manager sends instructions to the necessary device.
Selecting the COV toggle box allows the Manager to subscribe to a specific data point and receive any change in data
instantaneously, rather then waiting for the next 30 second poll interval. When COV is toggled, the Room Controller becomes the
broadcaster and sends any change of data point indicating a change in the Present Value immediately to the Manager. For
example, if the Occupancy of a room changes, the Room Controller automatically broadcasts the data point to the Manager
letting it know immediately the state of the room occupancy. By enabling a COV for a data point, the regular 30 second polling of
that data point/object is no longer in effect, and therefore, the Manager relies on the Room Controller to inform the it of any COV
and report its Present Value.
The Room Controller continues to send any COV to
the Manager at the time the COV occurs as long as
the COV stays toggled. If the data point is toggled
off, any immediate COV is not broadcasted to the
Manager. In this condition, the Manager will only
learn of any present value changes at the next 30
second poll interval.
Note: A single Manager can only subscribe to a
maximum COV of 20 Objects per Room Controller.
22
Page 23
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
Procedures - Integrate Room Controller and Manager
The following procedures show how to integrate a SE7000/SE8000 series Room Controller with a Multi-purpose Manager in a
ZigBee Wireless Pro environment.
Procedure - Configure SE7200, SE7300, SE7600 and SER7300 Series
1. Press and hold MENU/OVERRIDE for 8 seconds until PswrdSet shows.
2. Using up or down arrow, set Password to any value between 0 - 1000.
3. Push YES/OVERRIDE when you set Password.
4. PressNO/OVERRIDE until PANID shows.
23
5. Using up or down arrow, set PANID to any value between 0 - 500.
6. Push YES/OVERRIDE when you set PAN ID. Record value for later use.
7. Push YES/OVERRIDE until Channel shows.
8. Using up or down arrow, set Channel to any value between 11 - 25.
9. Push YES/OVERRIDE when you set Channel. Record value for later use.
Procedure - Configure SE8000 Series
1. On right side of date, touch and hold this point for 3 seconds to enter setup mode.
2. Push Network button.
Page 24
SE7000/SE8000 Room Controllers ZigBee Pro Wireless Integration Guide
Schneider Electric | IG-SE7000SE8000ZP-A4.EN.03.2014.v2 March 2014
3. Set unique COMaddress.
4. Using up/down arrows, enter COM address value.
5. Set ZigBeePan.ID.
6. Using up/down arrows, enter ZigBee pan. ID value.