所需积分/C币:9 2019-07-01 11:39:39 896KB PDF
收藏 收藏

APL12955-7 Z-Wave Multi channel basics 2018-03-06 Z-WAVE MULTI CHANNEL BASICS Z-Wave enables a variety of monitoring and control applications. Sensors can send data to a gateway Wall controllers may report button presses to a scene controller or control actuators directly. A Z-Wave node is conceptually an application resource in a plastic box communicating via a z-Wave radio Composite devices pack multiple application resources in the same plastic box, thus sharing the same Z-Wave radio Application resources can always be addressed individually This is made possible by a range of Command Class and Device Type specifications Within a network, a Z-Wave node is identified by its NodelD. the nodeld essentially represents the plastic box and the radio Multi-resource devices are organized as multi Channel Endpoints. Each application resource is identified by its own unique End Point. The plastic box itself is referred to as the Root Device Point. Further, the destination End Point may be structured as a multicast mask, targeting up to 7Eno o Multi Channel Encapsulation allows a sending node to specify a source End Point and a destination El Points by one command If a device implements no actuator functionality, it may not always be necessary to structure resources as multi channel end points A multi-sensor with two distinct sensor types is one example. Another example is a remote control that sends Central Scene Notifications to a central gateway via the Lifeline association group The remote control may advertise additional association groups, each representing a push button for direct actuator control. Without an icon type for each End Point, a graphical management tool has to render such input elements graphically based on the AGI Profile, e.g. Control: Key o1 Wall controllers, that only transmit commands, represent a gray zone. a remote control manufacturer may consider the wall controller to be just a remote control in a different form factor. This manufacturer sees no value in end points A manufacturer of wall switches with built-in dimmers may consider the wall controller to be a downscaled wall switch where the load controlling hardware is omitted. This manufacturer may prefer to apply the same End point structure to similar products for development and support reasons Multi Channel Encapsulation is used for transmission from one end point to another, from an end point to a root device as well as from a root device to an end point In case of similar sensor types in the same device end points are needed to distinguish the sensor reports from the individual sensor resources. aGi allows the controller to determine the nature of the sensor e. g. Indoor temperature 7→1: Tamper Alarm 71→10: MultilevelSensor Report(23°C) 72→10: Multileve SensorReport(4°C) Example 1: Two identical sensor resources distinguished via the Source End Point The wall controller below implements one End point for each button silabs. com Building a more connected world Page 3 of 7 CONFDENTAL APL12955-7 Z-Wave Multi channel basics 2018-03-06 5.1→7,2: Basic set Example 2: End Point 1 of one node controlling End Point 2 of another node The next wall controller implements no End Points. All association groups are provided by the root Device 50÷7.2: Basic set 12 Example 3: Root device of one node controlling end point 2 of another node Note that while the wall controller in EXample 3 implements no end Points itself, it still has to support Multi channel communication in order to control actuator end points in other devices Multi Channel Encapsulation is not used between Root Devices 5→7: Basic set Example 4: Root Devices communicating without Multi Channel encapsulation Historically, there could be only one application resource in one plastic box. In such a simple device, functionality relating to the plastic box, e.g. battery level, and application functionality, e.g. light control are all accessed via the nodeld Thus, the application functionality of a simple device resides in the root device, while a multi channel device has no application functionality in the root device Backwards compatibility is maintained in Multi Channel devices by the Root Device advertising application functionality, even though the functionality is actually provided by one or more End points functionality of more End Points to the root Device. As an example the root device of a composife or End Point 1 implements the primary functionality of the device, but the product designer is free to min sensor may mirror the management function of two sensor End points causing both End points to send sensor reports. silabs. com Building a more connected world Page 4 of 7 CONFDENTAL APL12955-7 Z-Wave Multi channel basics 2018-03-06 7→1: Tamper Alarm 7-1: MultilevelSensorReport/23'C 71: Multilevel Report(78%rel. humidity) Example 5: Root Device mirrors two End Points in composite sensor Mirroring multiple end point sensor resources in the root device requires that the resources issue different commands. a receiving device has no way to distinguish identical reports In the same way, the Root device of a power strip forwards commands to all three End Points of the device 5→7: Basic Set Example 6: Root Device mirrors three End Points in power strip One cannot be sure that a command to the root device mirrors all end points the multi channel multicast feature may be used to send a Set command to the first 7 End Points. Alternatively, one may communicate to each individual end point this works for set as well as get commands Management tools may have a need to present expanded views of Multi Channel devices, e.g. in the floor plan view of a smart home deployment. Such tools hide Root device application functionality to compensate for the backwards compatibility mirroring of End Point functionality to the Root Device. This way, the power strip can be presented the way it really works silabs. com Building a more connected world Page 5 of 7 CONFDENTAL APL12955-7 Z-Wave Multi channel basics 2018-03-06 B Example 7: Expanded representation of power strip An Aggregated End Point allows a Multi Channel device to implement functionality relating to multiple End points Aggregated End Points are used for reporting the accumulated consumption of physical resources via Meter and Multilevel Sensor Command Classes. Examples include Electrical power, water and gas Aggregated End Points are not intended for control. End Points are controlled via multicast or individual End Point addressing The example below shows a power strip with aggregated metering -;---四图 4 2 Example 8: Expanded representation of power strip with aggregated metering silabs. com Building a more connected world Page 6 of 7 CONFDENTAL APL12955-7 Z-Wave Multi channel basics 2018-03-06 The power strip reports the total power consumption in response to a request to the aggregated End Point 1.0→>7.4: Meter get 7.4>1.0: Meter Report(73kWh) Example 9: Aggregated End Point of Power strip reports accumulated value The presence of Multi Channel End Points is discovered by the Root Device advertising support for the Multi Channel Command Class. The gateway does not implement End Points. Therefore, it does not advertise support for the Multi Channel Command Class even though it can talk to End Points 7>*: Node Information(Multi Channel CC) 4 Example 10: Power strip advertises that it implements end points Next step is to query the available End Points 1→7: End point get 7→1:EndP。 int Report(3,1) EXample 11: Power strip advertises available End Points The power strip advertises that three individual End Points implement application functionality. Further, one Aggregated End Point is advertised Each of the End Points are queried for supported Command classes silabs. com Building a more connected world Page 7 of 7 CONFDENTAL APL12955-7 Z-Wave Multi channel basics 2018-03-06 1→7: Capability Get(1) 7→1: Capability report(…) Example 12: Power strip advertises End Point capabilities The same Capability Get command is used for individual End Points and for Aggregated End Points One may query which individual End Points are members of an Aggregated End Point 17: Aggregated Members Get(4) 7-1: Aggregated Members Report(. Example 13: Power strip advertises Aggregated End Point members The power strip advertises that Aggregated End Point 4 relates to the individual End Points 1, 2 and 3 silabs. com Building a more connected world Page 8 of 7 CONFDENTAL APL12955-7 Z-Wave Multi channel basics 2018-03-06 REFERENCES [1] SDS12657Z-Wave Command Class Specification, A-M [2 SDs12652 Z-Wave Command class specification, N-Z 3 SDS11847 Z-Wave Plus Device Types Specification 4] SDs11846 Z-Wave Plus role T ypes Specification silabs. com Building a more connected world Page 9 of 7 CONFDENTAL Do you have an innovative idea te p the worle 是 pHen Smart Connected Energy-Friendly. □ 口■■ Products Qualit Support and Community www.silabs.com/products www.silabs.com/quality communitysilabs.com Disclaimer Silicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and" Typical parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice and limitation to product information, specifications, and descriptions herein and does not give warranties as to the accuracy or completeness of the included information. Silicon Labs shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses granted hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life support System without the specific written consent of Silicon Labs. A "Life Support System"is any product or system intended to support or sustain life and/or health, which, if it fails can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including(but not limited to)nuclear, biological or chemical weapons or missiles capable of delivering such weapons Trademark Information Silicon Laboratories Inc. Silicon Laboratories, Silicon Labs@, SiLabse and the Silicon Labs logos, bluegigae, Bluegiga Logo, Clockbuilder, CMEMse, DSPLlo, EFMa EFM32@, EFR, Ember@, Energy Micro, Energy Micro logo and combinations thereof, "the world,'s most energy friendly microcontrollers", Emberb, EZLinke, EZRadioB, EZRadioPROB Gecko, ISOmodemR, Micrium, Precision 32R, ProSLICO, Simplicity Studio@, SiPHYO, Telegesis, the Telegesis LogoR, USBXpressQ, Zentri, Z-Wave and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited All other products or brand names mentioned herein are trademarks of their respective holders Silicon Laboratories inc 400 West Cesar chavez Austin . TX 78701 USA SilicOnLabshttp://www.silabs.com

试读 10P APL12955-Z-Wave-多通道基础.pdf
立即下载 低至0.43元/次 身份认证VIP会员低至7折
APL12955-Z-Wave-多通道基础.pdf 9积分/C币 立即下载

试读结束, 可继续读1页

9积分/C币 立即下载