SHOWRUNNER™ provides a number of benefits over using the default program. These benefits are covered in detail on our Crestron Zūm Wired and SHOWRUNNER™, but one of the largest benefits are the tools included with SHOWRUNNER™ to make Zūm Wired start-ups go as smoothly as possible.

App Mode (Zūm Discovery)

SHOWRUNNER™ includes a Zūm Wired Discovery feature that makes it easy to import Zūm Rooms that have been configured in App Mode into an existing SHOWRUNNER™ configuration. The process for starting up a system using this method is the same as starting up any other networked installation in App Mode, but with the added steps of installing SHOWRUNNER and importing Zūm Rooms into the configuration.

Installing SHOWRUNNER™ on different processors is covered in our startup pages, while importing Zūm Rooms is covered in the Zūm Wired Discovery page.

CNET Mode (SHOWRUNNER™ Total Control)

Using SHOWRUNNER™ to control a networked Zūm Wired installation with ZUMNET-JBOXs running in CNET mode is the recommended way of using SHOWRUNNER™ with Zūm Wired. This is also the only way to gain control of legacy Cresnet devices (such as GL-EXP-DIMU-CN, C2N-IO, and GLS-PART-CN) that are connected to a ZUMNET-JBOX, as these Cresnet devices are not recognized or supported by the Crestron Zūm App.

The steps for configuring a networked Zūm Wired installation with SHOWRUNNER™ are:

1. Install SHOWRUNNER™ and configure the processor per our startup guides
   • If using a processor without a dedicated Control Subnet, follow the additional steps detailed below
2. Verify that all expected ZUMNET-JBOX-* devices are reporting online using the Device Discovery tool in Toolbox
   • Your laptop and the ZUMNET-JBOXs should all be connected to the Control Subnet
   • If there are missing ZUMNET-JBOXs, verify with the EC that the devices are powered and that the Zūm Net cabling is correct
   • Recall that any ZUMNET-JBOX that is unpowered or disconnected will prevent downstream ZUMNET-JBOXs from coming online
3. Once all hardware is online, use the Device Discovery Tool in Toolbox to export a Device Summary file
   • These steps can still be followed even if not all the hardware is online
   • If not all the hardware is online, then these steps will need to be repeated and the loadscripts run just for the previously offline devices
   • Alternatively, if there are only a few previously offline devices, then they can be  configured and updated manually
4. Add columns for hostname ("Host", J) and IP-ID ("IP-ID", K) as shown below
5. Fill out these columns for each of the ZUMNET-JBOXs in the device summary
   • Columns L through O are optional unless static IP addresses are required, as covered below
   • If this information has already been filled out in the SHOWRUNNER™ Takeoff IP Table sheet, then it is easy to copy/paste from the takeoff into the Device Summary .csv by sorting and filtering the two documents by MAC address
6. Use the modified Device Summary file and Chief Integrations' Zūm Wired Loadscript Tool to generate loadscripts for:
   • Convert to Primary & App Mode
   • Update FW
   • Convert to CNET Mode
     • Optionally, generate Convert to CNET + Autoswitch On if automatic switching between CNET and App mode is desired
   • IP Config (DHCP)
7. Run the "Convert to Primary & App Mode" loadscript
   • This loadscript connects to each ZUMNET-JBOX by their default hostname and updates their "zwmode" settings
   • Devices will reboot
   • Verify that all devices report completing successfully in the Loadscript Manager tool before proceeding to the next step; re-run the loadscript for specific devices as necessary
8. Connect to a handful of ZUMNET-JBOXs to verify that all ZUMLINK-* devices have been given unique CIDs
9. Run the "Update FW" loadscript
   • This loadscript connects to each ZUMNET-JBOX by their default hostname and updates their firmware
   • This loadscript must be located in the same folder as the firmware .puf file
   • Devices will reboot
   • Verify that all devices report completing successfully in the Loadscript Manager tool before proceeding to the next step; re-run the loadscript for specific devices as necessary
     • If the script has been re-run multiple times and has failed each time, connect to the ZUMNET-JBOX and verify that all the ZUMLINK-* hardware appears correctly
     • Attempt to run the .puf file separately without a load script
     • If you encounter devices that report as "UNDEFINED" model types, see our FAQ on this topic (https://wiki.chiefintegrations.com/FAQ/My%20ZUMNET-JBOX%20or%20ZUMLINK%20device%20reports%20as%20an%20UNDEFINED%20model%20type%3F/)
10. Once FW updates are complete, verify all ZUMNET-JBOX actually took the FW update by using Device Discovery Tool to export a Device Summary and observe that the reported FW for all devices matches the FW version in the .puf file
    • Because ZUMNET-JBOX update their own firmware after attached ZUMLINK-* devices, if a ZUMNET-JBOX is up-to-date then all ZUMLINK-* devices should also be updated
    • If ZUMLINK-* devices have conflicting CIDs or are not online, then they will not update
11. If using 

• use chief tools tm tool to generate various zum wired load scripts
• if firmware is old, run "zwms master/zum (def. hostname)" loadscript to make all ZUMNET JBOX primary and in app mode in order to enable discovery of devices on zumlink
  • devices will reboot
  • per crestron, 1.0006.00012 and newer ship in primary mode (tbd if they will ship in app mode?)
• connect to a few devices in device discovery tool to ensure that all zumlink devices were automatically readdressed and there are no conflicting cids
  • firmware 1.0001.00081 is new enough that this works correctly
• run "fw update (def. hostname)" loadscript to update the fw for all devices
  • will take up to several minutes per room, but will be able to do up to 10 rooms simultaneously
  • devices will reboot, possibly multiple times
  • check loadscript manager for any failures and re-run script for those devices if necessary (a rebooting zumnet box will temporarily disrupt online status for downstream zumnet jboxs and potentially interrupt the firmware update)
• run device discovery again to confirm that all zumnet boxes were updated
• if app mode backup is desired, configure the boxes using the app now
• run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames
  • devices will reboot
  • devices will now have new hostnames, so any further loadscripts should use (new hostname) versions
• run "cnet mode (def. hostname)" loadscript to put devices into CNET mode
  • if app mode backup is desired, also run "autoswitch enable (def. hostname)" loadscript
  • devices will reboot
• if using a processor without control subnet, run the "static ip config (new hostname)" script
  • this loadscript is necessary, as the showrunner DHCP server is only intended for commissioning. It must always be manually started after program restart and should not be used in production
  • (will probably need a lot of extra steps + alterations to how we make configs since static IPs require a lot more information as well as corresponding modifications to SrConfig.json)
• once done, commission job essentially as normal showrunner job
  • (sr commissioning guide is incomplete) 
  • connect to each zumnet jbox and address zumlink devices per the takeoff
    • if devices are not online, then troubleshoot why and update firmware through device tree view once they are online
  • occ timeouts can be adjusted through UI; other settings (ie reach) should be adjusted through app
  • photocells etc are set up through UI
  • loads teseted and verified through UI; can be moved around between controllers as necessary
    • loads don't need to be in the same room as the zumnet that controls them
  • keypads can use standard SR types or be fully customized
  • set up schedule, etc.
• once done, save and back up configuration file

Tools for Statically Configured Lighting Networks

Unlike installations using the default program, SHOWRUNNER™ offers the opportunity to reduce the cost of hardware by enabling the use of any 3 or 4-Series processor, rather than being restricted to using the ZUM-HUB4 exclusively. Some of these other processors (DIN-AP4, RMC4, etc.) do not include a Control Subnet with built-in router, which requires the use of static IP addresses if the lighting network is to remain independent and there is no router specified to manage traffic on the lighting network. SHOWRUNNER™ includes several built-in features to assist with these sort of startups without requiring a Technician to bring their own router.

This section does not apply to processors with a built in Control Subnet (CP4N, AV4, PRO4, ZUM-HUB4, etc.) or lighting networks that are fully integrated with a managed building LAN. 

The steps for statically configuring a networked Zūm Wired installation with SHOWRUNNER™ are:

1. Configure the static IP address for the processor and install SHOWRUNNER™
2. Use SHOWRUNNER™'s built in DHCP server
   • If you want to use specific static IP addresses for specific ZUMNET-JBOXs, use the SHOWRUNNER™ UI and set the DHCP range outside of the range you intend to use for the ZUMNET-JBOXs
   • If arbitrary static IP addresses are acceptable, then use the default IP address range
3. Proceed with the standard CNET Mode start-up procedure from step 2
4. Once the standard start-up procedure has been completed, export a new Device Summary file
5. Change the Device Summary filetype to ".csv" and open in Microsoft Excel
6. Add columns for hostname ("Host", J), IP-ID ("IP-ID", K), static IP address ("IPA", L), static IP subnet mask ("IPM", M), default gateway ("DEFR", N), and domain name server ("DNS", O) as shown below
7. Fill out these columns for each of the ZUMNET-JBOXs in the device summary
   • If there is no default gateway or DNS, use the processor's IP address instead
   • "IP-ID" column is optional
   • If this information has already been filled out in the SHOWRUNNER™ Takeoff IP Table sheet, then it is easy to copy/paste from the takeoff into the Device Summary .csv by sorting and filtering the two documents by MAC address
8. Use the modified Device Summary file and Chief Integrations' Zūm Wired Loadscript Tool to generate a loadscript that connects to devices by their hostname and sets their static IP settings
   • Up to 10 devices can be configured simultaneously
   • Devices will reboot once this script is run
   • Verify that all devices report completing successfully in the Loadscript Manager tool before proceeding to the next step; re-run the loadscript for specific devices as necessary
9. If desired, export a new Device Summary file as a record that this step was completed successfully
10. If desired, disable the processor's DHCP service (the service will not resume if the processor reboots or the program restarts)