SE7000/SE8000 Room Controllers
ZigBee Pro Wireless Integration Guide
Get Control. Get Efficient. Get Value
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
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
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.
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
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.
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.
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
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.
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.
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