Changes for page **General Overview and Design Considerations

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -12,16 +12,41 @@
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.
	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	16
17	17	== App Mode ==
18	18
19		-Lorem
	19	+(% class="box warningmessage" %)
	20	+(((
	21	+add more here
	22	+)))
20	20
	24	+If devices in App Mode are being used as part of a networked system running a custom program, then any configuration changes made through the Zūm App should be made while the device is disconnected from the processor. The easiest ways to accomplish this are to either disconnect the Cat5e/Cat6 cable at the processor, or stop the program running on the processor using Text Console commands.
	25	+
21	21	== CNET Mode ==
22	22
23		-Lorem
	28	+Using ZUMNET-JBOX-* devices in CNET Mode is only possible on a networked system with a processor that is running a custom program. While in CNET Mode, ZUMNET-JBOX-* devices do not process any local logic and cannot be connected to through the Zūm App in order to be configured. This is because while in CNET Mode, ZUMNET-JBOX act as a "dumb" Cresnet-to-Ethernet bridge with a built-in load controller. They report all Zūm Link traffic back to the control processor and do not do any "thinking" on their own. Any attached ZUMLINK-KP or ZUMLINK-OCC-* devices will not work without the processor if the ZUMNET-JBOX is in CNET Mode.
24	24
	30	+CNET Mode has some benefits over App Mode. Compared to App Mode, CNET Mode offers direct control of all hardware which enables the system to meet a wider range of sequences. Additionally, CNET Mode offers increased security as it is not possible to connect to a device with the Zūm App while it is in CNET Mode.
	31	+
	32	+The two main drawbacks of using CNET Mode are the requirement for a networked system with a custom program and the loss of local control in the event that connection to the control processor is lost, however the introduction of the Zūm Mode Auto Switch feature in .puf firmware v1.04.05 (device firmware v1.004.00005) has eliminated this second drawback by enabling devices to automatically switch between CNET and Zūm Modes when connection to the processor is lost or regained.
	33	+
	34	+//As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured in CNET mode, though this may change in the future.//
	35	+
	36	+== Zūm Mode Auto Switch ==
	37	+
	38	+Zūm Mode Auto Switch is a feature introduced in November of 2022 with .puf firmware v1.04.05 (device firmware 1.004.00005). This feature is intended to address concerns that arose from projects using custom programs with ZUMNET-JBOX-* devices in CNET Mode. Previously, if a device in CNET Mode lost connection to the processor, then it would be impossible to maintain any sort of control over the lighting. With Zūm Mode Auto Switch enabled, a ZUMNET-JBOX running in CNET Mode will automatically switch to App Mode and process local logic in the event that it loses connection to the processor.
	39	+
	40	+Enabling this feature eliminates the biggest drawback of designing a system to use ZUMNET-JBOX-* devices in CNET Mode.
	41	+
	42	+//As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured with Zūm Mode Auto Switch disabled, as this feature is only intended to be used with systems that are running custom programs.//
	43	+
	44	+== Security Considerations ==
	45	+
	46	+Any ZUMNET-JBOX that is running in App Mode with an attached ZUMLINK-KP can be connected to via the Crestron Zūm App, which is publicly available in the Google Play store. Although unlikely, it is technically possible that a bad actor could download the Zūm App and interfere with the lighting controls. Crestron ships all ZUMNET-JBOX-* devices with a default PIN that is intended to be changed during commissioning, however there is no guarantee that the technician who configured the Zūm Wired hardware knew or remembered to do this.
	47	+
	48	+One way to counteract this security risk is to design the system to operate with the ZUMNET-JBOX-* devices in CNET Mode. In CNET Mode, it is impossible to connect to any devices using the Zūm App. Leaving the Zūm Mode Auto Switch function disabled will add another layer of security in exchange for a loss of localized control when the system is experiencing issues, as devices will stay in CNET Mode even when connection to the control processor is lost.
	49	+
25	25	== Primary vs Secondary Mode ==
26	26
27	27	(% class="box infomessage" %)
...	...	@@ -34,24 +34,32 @@
34	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	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.
36	36
37		-As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* preconfigured in Secondary mode, though this may change in the future.
	62	+//As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured in Secondary mode, however they have announced their intention to begin shipping hardware on newer firmware preconfigured in Primary mode.//
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.
46	46
47	47
	69	+(% class="box warningmessage" %)
	70	+(((
48	48	The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-*
	72	+)))
49	49
	74	+(% class="box warningmessage" %)
	75	+(((
50	50	In standalone applications, each room has one ZUMNET-JBOX-* with a number of connected ZUMLINK-* devices. There is no Zūm Net connecting different rooms,
	77	+)))
51	51
	79	+(% class="box warningmessage" %)
	80	+(((
52	52	Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
	82	+)))
53	53
	84	+(% class="box warningmessage" %)
	85	+(((
54	54	Depending on which control paradigm is selected, there will be various impacts to the hardware cost, start-up cost, start-up complexity, ease of maintenance, control capabilities, integration with third-party systems, available user interfaces, and the ability to meet a provided sequence of operations.
	87	+)))
55	55
56	56	== Standalone ==
57	57
...	...	@@ -65,7 +65,7 @@
65	65
66	66	Lorem
67	67
68		-=== Networked with SHOWRUNNER™ ===
	101	+=== Networked with Custom Program ===
69	69
70	70	Lorem
71	71