Skip to Content

Changes for page Zūm Discovery

Last modified by Alexander Mott on 2025/04/03 17:35
From version 15.1
edited by Alexander Mott
on 2023/03/29 21:00
Change comment: There is no comment for this version
To version 9.1
edited by Alexander Mott
on 2022/10/05 16:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +5,3 @@
1 -(% class="box errormessage" %)
2 -(((
3 -Cresnet Discovery is not working on ZUMNET-JBOXs. Crestron has acknowledged a fix has been sent to QE. Discovery must be fixed before SHOWRUNNER™ can auto-discover hardware.
4 -)))
5 5  (% class="box warningmessage" %)
6 6  (((
7 7  This article is about automatically building a SHOWRUNNER™ configuration using the Zūm Discovery feature of SHOWRUNNER™. For instructions on configuring Zūm Wired rooms using the Crestron Zūm App, see [[this page>>SHOWRUNNER™ Setup Guide.Wiring Guide.Zūm Wired System Overview.Crestron Zūm App Overview.WebHome]].
... ... @@ -12,6 +12,8 @@
12 12  {{toc/}}
13 13  {{/box}}
14 14  
11 +(% class="row" %)
12 +(((
15 15  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™.
16 16  
17 17  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.
... ... @@ -20,10 +20,10 @@
20 20  
21 21  == Notes and Limitations ==
22 22  
23 -(% class="box warningmessage" %)
21 +(% class="box errormessage" %)
24 24  (((
25 25  * SHOWRUNNER™ version 3.014 or newer required
26 -* Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081)
24 +* Zūm Wired firmware version 1.02.10 or greater required
27 27  * Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands
28 28  * Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release)
29 29  * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
... ... @@ -52,21 +52,21 @@
52 52  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
53 53  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
54 54  1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery
55 -1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program
56 -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
57 57  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
58 58  1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox
59 59  1. Run the command: ##sr discover zumnet true false##
60 -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
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
61 61  1. Run the command: ##sr discover zumnet true true##
62 -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
63 -1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area
59 +1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware on the previously discovered Zūm Net devices
64 64  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
65 -1. If all steps have been performed successfully, then you should be able to use the ##sr show area##, ##sr show load##, ##sr show keypad##, and ##sr show occ## commands to see that the ZUMNET and ZUMLINK hardware has been discovered correctly.
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
66 66  
67 67  = Zūm Wireless Discovery =
68 68  
69 69  == Notes and Limitations ==
67 +)))
70 70  
71 71  (% class="box errormessage" %)
72 72  (((
... ... @@ -86,6 +86,8 @@
86 86  1. **Claim All RF Gateways** - SHOWRUNNER™ will find all CEN-GWEXERs [ZUMNET-GATEWAY] on the network and will claim them as its own. **DO NOT** use this method if there are gateways used by different SHOWRUNNER™ or other Crestron systems on the same local network.
87 87  )))
88 88  
87 +(% class="row" %)
88 +(((
89 89  == Manual RF Gateway Assignment Instructions ==
90 90  
91 91  Use this method if you have multiple SHOWRUNNER™ instances on the same network or have gateways used by other Crestron systems.
... ... @@ -307,3 +307,4 @@
307 307  Removed Loads: 0
308 308  Zum Discovery Finished
309 309  }}}
310 +)))