Skip to Content
Last modified by Alexander Mott on 2023/12/08 18:37
From version 13.6
edited by Alexander Mott
on 2023/03/24 20:34
Change comment: (Autosaved)
To version 10.8
edited by Alexander Mott
on 2023/03/24 18:52
Change comment: (Autosaved)

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -*General Overview and Design Considerations
1 +*Design Considerations
Content
... ... @@ -12,8 +12,6 @@
12 12  
13 13  Zūm Wired systems consist of ZUMNET-JBOX-* room controllers and a number of connected ZUMLINK-* devices. ZUMLINK-* devices can be ZUMLINK-JBOX-* load controllers, ZUMLINK-OCC-* presence detectors, or ZUMLINK-KP-R-W keypads (wall switches). ZUMNET-JBOX-* and ZUMLINK-JBOX-* devices have additional inputs for third-party presence detectors, 0-10V analog photocells, and contact-closure local override.
14 14  
15 -ZUMNET-JBOX-* room controllers can be operated in App mode or CNET mode, with an additional setting to be either the Primary room controller or a Secondary load controller.
16 -
17 17  == App Mode ==
18 18  
19 19  Lorem
... ... @@ -24,22 +24,14 @@
24 24  
25 25  == Primary vs Secondary Mode ==
26 26  
27 -(% class="box infomessage" %)
28 -(((
29 -Note: the terminology used for these modes was modified in .puf firmware v1.03.27 (device firmware v1.002.00026). Hardware delivered with older firmware will require the use of different commands to change modes during start-up.
30 -)))
25 +ZUMNET-JBOX-* devices can be set to be either the primary room controller or a secondary load controller.
31 31  
32 -ZUMNET-JBOX-* devices can be set to be either the Primary room controller or a Secondary load controller. There must only be one Primary ZUMNET-JBOX on a given Zūm Link bus, and in a networked system the Primary ZUMNET-JBOX is the one that should be connected to the Zūm Net.
27 +Note that on older versions of firmware, these modes were referred to as "master" and "slave" mode. The terminology was updated in .puf v1.03.27 (device firmware v1.002.00026), but as of February, 2023 the FW
33 33  
34 -* In Primary mode, the ZUMNET-JBOX acts as the Zūm Link host, and is able to detect all connected Zūm Link devices. If connected to in Crestron Toolbox, a Primary ZUMNET-JBOX can be used to view and manually address any connected ZUMLINK-* devices. While in App mode, a ZUMNET-JBOX in Primary mode is the logical room controller for the space and is the device that should be used for configuration via the Zūm App.
35 -* In Secondary mode, the ZUMNET-JBOX acts as if it were a ZUMLINK-JBOX. It does not process any room control logic, and when connected to via Crestron Toolbox it will not be able to see any other ZUMLINK-* devices. Using Secondary mode is rare, and should only be used in cases where a spare ZUMNET-JBOX is being used to add a load to another ZUMNET-JBOX or replace a ZUMLINK-JBOX that has been lost or damaged.
29 +== Security ==
36 36  
37 -As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* preconfigured in Secondary mode, though this may change in the future.
31 +Lorem
38 38  
39 -== Security Considerations ==
40 -
41 -Although unlikely, it is technically possible that
42 -
43 43  = Control Paradigms =
44 44  
45 45  Designs for Zūm Wired systems are broadly categorized as either "standalone" or "networked" designs. Both standalone and networked systems should be designed with one ZUMNET-JBOX-* per room or logical control space connected to a number of ZUMLINK-* devices within that same space. In networked systems, there is also a control processor which provides centralized control of the entire system. ZUMNET-JBOX-* must be daisy-chained together with Zūm Net and then connected back to the processor. In standalone applications, there is no processor and no Zūm Net cabling connecting different rooms to each other.
1679688568997-208.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -6.9 KB
Content