Changes for page Zūm Discovery

Summary

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

Details

Page properties

Content

...	...	@@ -8,8 +8,6 @@
8	8	{{toc/}}
9	9	{{/box}}
10	10
11		-(% class="row" %)
12		-(((
13	13	If Zūm Wired or Wireless devices have been configured using Crestron's Zūm App, then it is possible to automatically build a SHOWRUNNER™ configuration file using the Zūm Discovery feature that is built into SHOWRUNNER™.
14	14
15	15	There are certain pre-requisites and limitations when building a SHOWRUNNER™ configuration this way, and it may sometimes be necessary make some adjustments to the final configuration, such as changing keypad types and moving loads between areas.
...	...	@@ -21,7 +21,7 @@
21	21	(% class="box errormessage" %)
22	22	(((
23	23	* SHOWRUNNER™ version 3.014 or newer required
24		-* Zūm Wired firmware version 1.02.10 or greater required
	22	+* Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081)
25	25	* Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands
26	26	* Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release)
27	27	* One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
...	...	@@ -50,16 +50,16 @@
50	50	1*. If the SHOWRUNNER™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses
51	51	1. Optionally, manually configure the ZUMNET-JBOX IP table to point at the processor if you want to keep track of which ZUMNET-JBOX is at each IP-ID
52	52	1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery
	51	+1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program
	52	+1*. Full control from SHOWRUNNER™ is only possible if all ZUMNET-JBOXs are in CNET mode. Odd behavior may result from conflicts between SHOWRUNNER™ and internal logic if the ZUMNET-JBOXs are not put into CNET mode
53	53	1. Repeat from step 3 until all ZUMNET-JBOXs that are to be controlled by SHOWRUNNER™ have static IP addresses and unique CIDs for any hosted devices
54	54	1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox
55	55	1. Run the command: ##sr discover zumnet true false##
56		-1*. This command tells SHOWRUNNER™ to discover all ZUMMNET-JBOXs on the network, configure their IP tables, and then add corresponding areas and loads to the configuration
57		-1*. One area will be created per ZUMNET-JBOX
	56	+1*. This command tells SHOWRUNNER™ to discover all ZUMMNET-JBOXs on the network, configure their IP tables, and then add corresponding IP Devices to the configuration
58	58	1. Run the command: ##sr discover zumnet true true##
59		-1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware on the previously discovered Zūm Net devices
	58	+1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware (including the internal ZUMNET-JBOX load controller) on the previously discovered Zūm Net devices and then add corresponding areas, loads, sensors, etc. to the configuration
	59	+1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area
60	60	1*. This command **does not** bring in Cresnet devices: those must be added to the configuration manually until this issue is fixed in the Zūm Wired firmware
61		-1. Put all ZUMNET-JBOXs into CNET mode in order to allow full control from SHOWRUNNER™
62		-1*. Odd behavior may result from conflicts between SHOWRUNNER™ and internal logic if the ZUMNET-JBOXs are not put into CNET mode
63	63
64	64	= Zūm Wireless Discovery =
65	65
...	...	@@ -304,4 +304,3 @@
304	304	Removed Loads: 0
305	305	Zum Discovery Finished
306	306	}}}
307		-)))