**Crestron Zūm Wired and SHOWRUNNER™
Lorem
See Figure 1 for details.
See Figure 2 for details.
The SHOWRUNNER™ Advantage
Lorem
Exclusive Features
Lorem
Suitable for a Range of Applications
Lorem
Ease of Start-Up and Documentation
Every SHOWRUNNER™ job comes with a number of Chief Tools™ to simplify the start-up process and enable Agents and Technicians to for networked Zūm Wired systems. These tools include:
- SRTakeoff spreadsheet provides the Technician with one location to view device addresses, record serial numbers, and track any issues discovered during start-up
- Zūm Wired Load Script generator enables technicians to easily create load scripts to streamline necessary configuration tasks based on the DeviceSummary.txt generated by Toolbox
See the Starting Up Zūm Wired with SHOWRUNNER™ page for more information on starting up Zūm Wired systems with SHOWRUNNER™.
Support and Continued Development
Lorem
Best Practices for Zūm Wired with SHOWRUNNER™
Though it is possible to design a Zūm Wired system to use the standard ZUM-HUB4 program and then import rooms from SHOWRUNNER™, it is not recommended as it adds the expense of a custom program without taking advantage of any of the added functionality that SHOWRUNNER™ has to offer.
Instead, to take full advantage of everything that SHOWRUNNER™ has to offer, follow these best practices:
- Design the system to use SHOWRUNNER™ as the main program
- Set ZUMNET-JBOX-* devices in CNET mode after any App-specific configurations have been made
Zūm
SHOWRUNNER™
Feature Comparison Tables
SHOWRUNNER™ vs Default Program vs Standalone
The below table compares some SHOWRUNNER exclusive features against networked systems using the default program and standalone systems using Zūm App mode.
Feature | Networked (SHOWRUNNER™) | Networked (HUB4) | Zūm App (Standalone) |
---|---|---|---|
Hardware Requirements | |||
Requires ZUMNET-JBOX-* | Y | Y | N |
Requires 3 or 4-Series Control System | Y (Can use a number of different 3 and 4-Series processors) | Y (Requires ZUM-HUB4) | N |
Requires Physical Presence in Room to Change Scenes | N | TBD | Y |
Maximum Rooms | TBD | 1000 | N/A |
User Interfaces | |||
Web Browser | Crestron SmartGraphics XPanel | HTML5 UI | N |
iOS/Android | Y, Crestron App (Paid Upgrade) or HTML5 UI (Device Web Browser) | N | Y* |
Touchscreens (Crestron TSW series) | Y | N | N |
Features | |||
Scene Recall | Y | Y | Y |
Override Fade Time for Scene Recall | Y | TBD | TBD |
Scene Save | Y | TBD | Y |
Load Control | Y | TBD | Y |
Demand Response | Y | Y | N |
Enable/Disable Occupancy | Y | Y | Y |
Override Occupancy Logic | Y | TBD | N |
Override | Y | TBD | N/A |
Plug Load On/Off | Y | Y | By Hardware |
Integration with Non-Zūm Crestron Hardware | Y | N | N |
Custom Zūm Keypad Programming | Y | TBD | Y, within the limits of the hardware |
New Feature Release Cycle | Aggressive | 6-12 months | 6-12 months |
Room Organization | Organize According to Defined Nodes, multiple levels | Category/Room | N/A |
Room Discovery | Automatic Discovery of ZUMNET and ZUMLINK devices (Pending) | Automatic Discovery of ZUMNET and ZUMLINK devices | N/A |
Network Topology |
| Single Handoff to LAN w/ Control Subnet | N/A |
Network Addressing |
| Control Subnet | N/A |
Firmware Updates | PUF Tool Automatic Support on Roadmap | Automatic, Internet Connection Required | N/A |
Floorplans | Y | N | N/A |
Calendar/Scheduling | |||
Logic Type | Event Driven Profile Support (Under Development) | Pattern assigned to Category | N/A |
Astronomical Clock | Y | Y, Per Category | N/A |
Holidays | Pattern | Hard Coded | N/A |
Custom Patterns | Y, Advanced Scheduler License | N | N/A |
Integrations | |||
A/V Integration: API | Y | Limited | N/A |
A/V Integration: Crestron EISC | Y | N | N/A |
A/V Integration: RS-232 | Y | TBD | N/A |
BACNET | Y, SHOWRUNNER™ and Crestron Licenses Needed | Y | N/A |
BACNET Features | Per Area Status: | Per Room Status: | N/A |
BACNET Settings Scope (What Points are Exposed) | Per Area | Global | N/A |
BACNET Points Supported | Depends on Crestron License and Hardware | 1000 | N/A |
Crestron Fusion | Y | N | N/A |
Export to Zūm Floor Hub | Y, Licensed | N/A | N/A |
GLPAC | Y | N | N/A |
System to System Link | Y | N | N/A |
Minimum ZUM-NET Firmware | CNET Mode: ZUM-WIRED 1.02.10 puf | See Crestron, expected to be v1.01 | See Crestron, expected to be v1.01 |
Minimum SHOWRUNNER™ Version | CNET Mode: 3.016 | N/A | N/A |
ZWMS (Zum Wired Master/Slave Mode) | MASTER | MASTER | MASTER or SLAVE |
ZWMODE | CNET or ZUM (ZUM Support Pending official release from Crestron) | ZUM | ZUM |
Caveats
- Consult Chief Integrations to verify sequence of operations if there are any concerns.
- Additional caveats:
Occupancy status is not reported to ShowRunner when ZUMNET/ZUMLINK JBOXs come online. This has been acknowledged as a bug by Crestron in firmware v1.001.054 and v1.00.009 and is pending a fix from Crestron.Fixed in 1.02.010 firmware and Device Database 200.150.002, ShowRunner 3.016 has been updated with these fixes from Crestron.Raw Occupancy reporting does not work. A delay of 5 seconds to 5 minutes between sensor vacancy and reported vacancy to ShowRunner. ShowRunner attempts to set 30 seconds (v3.003 to v3.009) or 5 seconds (v3.010 and later) but it is not always honored. This has been acknowledged as a bug by Crestron in firmware v1.001.054 and v1.00.009 and is pending a fix from Crestron.Fixed in 1.02.010 firmware and Device Database 200.150.002, ShowRunner 3.016 has been updated with these fixes from Crestron.- 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.
FAQ:
- I want to have a single connection to the building and have all of my Crestron devices on the Control Subnet (same topology as a ZUM-FLOOR-HUB) and use ShowRunner™ Total Control?
Use a CP4N in lieu of the ZUM-FLOOR-HUB. A DIN-AP4 is not required. Crestron can supply a DIN-EN-6X18 with CEN-SW-POE-16 and CP4N racked in a 2RU mount plus 3 DIN rails. See Design Details. - Do I need a Crestron BACnet license when using ShowRunner for BACnet integration?
If over 50 BACnet points are needed then a license (SW-3SERIES-BACNET-50+) will be needed for each Crestron processor that will provide BACnet points to the BMS.
Out-of-the-Box vs App vs Default Program vs Custom Program
Below is a Feature Comparison Table taken from the v3.05.02 Zūm Wired firmware release notes.
Feature | Out of the Box Functionality | Zūm App (Standalone) | Networked (HUB4) | Custom Prog. | Notes |
Keypads | Scn recall / OFF | * | * | * | Affect all load controllers excluding Plug controllers |
Presence detectors (Occ sensors) | Scn 1 / Scn 16 | * | * | * | Presence detectors affect all load controllers |
Programmable scenes | ✓ | * | * | ||
Occupancy/Vacancy logic | ✓ | * | * | ||
Daylight Harvesting | ✓ | * | * | J-box analog input support only, ZUMLINK- Daylight sensor via custom programming only. | |
Customized Button Functions* (Tap/Double-Tap/ Hold) | ✓ | * | * | none, Off, On, Toggle, Scene 1-16, Export button to Hub | |
Create a room configuration Template | ✓ | * | * | ||
Apply room configuration template | ✓ | ✓ | Identical hardware rooms required | ||
Universal 2-wire phase dimming up to 16A | ✓ | * | * | ZUMLINK-EXP-DIMU support & Zūm App discovery/configuration | |
DALI addressing, Broadcast and groups support (Zūm Mode) | ✓ | * | * | Allows control as Broadcast or 16 DALI Groups | |
Device Firmware updating via Zūm APP(BLE). | ✓ | Requires primary controller at ver. 1.2.60 | |||
DALI addressing and DALI group support (CNET Mode) | ✓ | Allows addressing, grouping and control of 16 Dali Groups using Simpl #, Simpl Windows | |||
CNET / Zūm Mode Auto Switch | ✓ | Automatically switches from CNET to Zum Mode when control system goes offline | |||
Load shedding | ✓ | * | |||
Global/Multi/Cross-room KP | ✓ | * | Scenes, plug load and Occupancy enable/disable | ||
Timeclock event triggers | ✓ | * | |||
DALI Type 6 TC | ✓ | ||||
DALI Type 8 TC | ✓ | ||||
Touch screen | * | ✓ | Hub4 support with mirror room modules | ||
Shades | ✓ | ||||
AV integration | * | ✓ | Hub4 support with mirror room modules | ||
Energy Monitoring | ✓ | ||||
Floor Map * denotes that can be used but not required to achieve functionality | * | ✓ | Hub4 support with mirror room modules |