Changes for page ZUM-HUB4 Processor Setup

Summary

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

Details

Page properties

Content

...	...	@@ -1,23 +1,23 @@
1		-{{info}}
	1	+(% class="box infomessage" %)
	2	+(((
2	2	This page is for ZUM-HUB4 deployments. For other processors, see our [[normal processor setup page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Processor Setup.WebHome]].
3		-{{/info}}
	4	+)))
4	4
5		-{{error}}
6		-All 4-Series processors require authentication to be configured when first connecting: **the Crestron Agent or Field Tech are responsible for recording these credentials. Chief Integrations cannot provide assistance unless the credentials are known. The only way to connect to a device for which the credentials have been lost is to factory reset the device, which may require redoing the start-up from scratch if the latest configuration was not saved and backed up. **
7		-{{/error}}
8		-
9		-{{error}}
	6	+(% class="box errormessage" %)
	7	+(((
10	10	**IMPORTANT:** When using ShowRunnerCLC™ with a ZUM-HUB4, **DO NOT** discover Zūm Rooms using the Crestron HUB4 Web UI. During discovery, the HUB4 will claim ZUMNET-JBOXs and prevent ShowRunnerCLC™ from auto-discovering or registering the Zūm hardware for itself.
11		-{{/error}}
	9	+)))
12	12
13		-{{error}}
14		-Per Crestron's ZUM-HUB4 firmware v3.009.0039 release notes, updating to firmware versions 3.009.0039 or newer require first updating to 3.008.054. Failure to do so will result in longer ##progreset## times (up to 10 minutes) as well as other potential issues such as keypads becoming unresponsive.
15		-{{/error}}
	11	+(% class="box errormessage" %)
	12	+(((
	13	+Per Crestron's ZUM-HUB4 firmware v3.009.0039 release notes, updating to firmware versions 3.009.0039 or newer require first updating to 3.008.054. Failure to do so will result in longer ##progreset## times (up to 10 minutes) as well as other potential issues such as keypads becoming nonresponsive.
	14	+)))
16	16
17		-{{warning}}
	16	+(% class="box warningmessage" %)
	17	+(((
18	18	ZUM-HUB4 requires firmware version 2.006.0034 or greater for third party software to be loaded.
19	19	(Once installed, running the "##ver##" command should report a FW version of 2.8000.00009 or greater.)
20		-{{/warning}}
	20	+)))
21	21
22	22	{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
23	23	{{toc/}}
...	...	@@ -45,16 +45,8 @@
45	45	** Force waiting to start program: ##startprogafterrouter on##
46	46	** Processor must be rebooted with "##reboot##" command before these take effect, but you can wait to reboot if there are other settings you must change that also require a reboot
47	47	** ShowRunnerCLC™ .puf versions 3.042 and newer automatically run this command when the "Configure ZUM-HUB4" option is selected.
48		-* Here are some things to consider before doing any network configuration on the ZUM-HUB4 processor:
49		-** **Never **connect an external router to the Control Subnet, as doing so will cause the internal DHCP server to shut down.
50		-** **Never **set the LAN IP address to an address that is in the range of the Control Subnet
51		-*** e.g. for a processor with the default 172.22.0.0/20 Control Subnet configuration, the LAN IP address must be below 172.22.0.0 or above 172.22.15.255
52		-** **Always** set devices on the Control Subnet to DHCP so that their IP addresses are managed by the built-in DHCP server. Only set static IP addresses on the Control Subnet if you really know what you are doing.
53		-*** If setting static IP addresses on the Control Subnet for any reason: **always** assign an address within the Control Subnet range, but **never** use the first two or the last address in the range
54		-*** e.g. for a processor with the default 172.22.0.0/20 Control Subnet configuration, IP addresses must be in the range 172.22.0.3 through 172.22.15.254
55		-**** 172.22.0.0 is not a valid address, 172.22.0.1 is taken by the processor, 172.22.0.2 is taken by the DHCP server (default gateway), and 172.22.15.255 is the broadcast address for the Control Subnet
56	56	* Determine whether the lighting control hardware will be connected to the ZUM-HUB4's LAN port or the Control Subnet port:
57		-** If the system is standalone (not integrated with building LAN), then lighting hardware can be connected to either the LAN port or the Control Subnet port, but it is still recommended to use the Control Subnet for Crestron hardware as the ZUM-HUB4 has a built-in router that will assign IP addresses via DHCP:
	49	+** If the system is standalone (not integrated with building LAN), then lighting hardware can be connected to either the LAN port or the Control Subnet port, but it is still recommended to use the Control Subnet for Crestron hardware as the ZUM-HUB4 has a router built-in that will assign IP addresses:
58	58	*** If connecting lighting hardware to the LAN port, then you must configure the LAN as a static IP (example is for a **10.0.0.0(% style="color:darkgoldenrod" %)/24(%%)** subnet, with a processor IP address of (% style="color:blue" %)**10.0.0.10**(%%)):
59	59	**** Disable DHCP: ##dhcp 0 off##
60	60	**** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.10**(%%)##
...	...	@@ -131,10 +131,3 @@
131	131
132	132	ZUM-HUB4 Currently does NOT support XPANEL:
133	133	The XPanel does not launch from the Showrunner HUB webpage. To access the XPanel, extract the VTZ file from the showrunner™ puf file and launch. Select Options>Host Settings and input the Host IP, IPID, Port 41794, check SSL, and Open. Type in the username and password and wait for the XPanel to connect.
134		-~{~{/error}}
135		-
136		-= **Connecting ShowRunnerCLC™ to SSL Connects Devices** =
137		-
138		-Due to SSL Management, Processors and Secondary network hardware with SSL enabled will require CS Authentication to be enabled and setup.
139		-
140		-Follow these steps to setup [[SSL User Configuration>>doc:SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Appendix.SSL User Configuration.WebHome]]