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)
WARNING: Cresnet Discovery is not currently working on ZUMNET-JBOXs. Crestron has acknowledged a fix has been sent to QE. Discovery must be fixed before SHOWRUNNER™ can auto-discover hardware.
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)
Lorem
cross reference/update to old zumnet startup?
basic steps:
- configure your processor per chief's startup guide
- get all zumnet jbox online
- use built in dhcp from processor control subnet
- if using proc without control subnet, use showrunner dhcp
- (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)
- use crestron toolbox device discovery to create a Device Summary
- use chief tools tm tool to generate various zum wired load scripts
- (need to determine exact process for this; will need to add IP-ID and new hostname to device summary somehow)
- (will likely generate two versions of the loadscripts; one connecting by default hostname and one connecting by new hostname)
- (intend to require SR license for zwired LS generator, if only to get the proc mac address)
- 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
- zumnet boxes update last, so if a zumnet jbox is updated then this means that all of the zumlink devices that were online have also been 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
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:
- Configure the static IP address for the processor and install SHOWRUNNER™
- Use SHOWRUNNER™'s built in DHCP server
- If it 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
- Proceed with the standard CNET Mode start-up procedure
