Skip to Content

Changes for page Processor Setup

Last modified by Alexander Mott on 2024/12/02 19:04
From version 31.1
edited by Alexander Mott
on 2022/09/16 21:01
Change comment: There is no comment for this version
To version 37.1
edited by Alexander Mott
on 2022/10/19 18:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,17 +5,19 @@
5 5  
6 6  (% class="box warningmessage" %)
7 7  (((
8 -SHOWRUNNER™ is tested against current Crestron firmware releases.  Please use at least the recommended firmware builds.
8 +SHOWRUNNER™ is tested against current Crestron firmware releases. **Please use at least the recommended firmware builds.**
9 +
9 9  * 3-Series: PUF 1.8001.0146
10 10  * 4-Series: PUF 2.7000.00052.01
11 11  * VC-4: 2.7000.00047
12 12  
13 -**Note:**
14 +**Notes:**
15 +
14 14  * Static IP or properly setup DHCP/DNS implementation required.
15 15  * Auto-Assigned/Link-Local IP address range of 169.254.x.x not supported (Crestron xPanel issue)
16 16  )))
17 17  
18 -{{box title="**Contents**"}}
20 +{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
19 19  {{toc/}}
20 20  {{/box}}
21 21  
... ... @@ -52,11 +52,12 @@
52 52  *** Configure your DHCP server software to assign IP addresses in the desired range
53 53  *** Once the processor is assigned an IP address, connect to it via Text Console at the assigned IP address
54 54  *** Run the above commands to disable DHCP and assign a static IP address to the processor
55 -* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4/ZUM-HUB4), additional setup is required
57 +* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4), additional setup is required
56 56  ** Connect to the processor via Text Console and run the command: ##startprogafterrouter on##
57 57  *** This will force the processor to wait until the router has started before attempting to load the showrunner™ program, avoiding potential license validation issues if the processor boots up before the router.
58 58  ** The previously listed "ipa," "ipm," etc. commands will configure settings for the processor's LAN port, which should be connected to the building LAN or third party network.
59 -** Lighting control hardware (e.g. TSWs, DIN-CENCN-2s, etc.) should be connected to the Control Subnet port. The processor acts as a DHCP server on the Control Subnet, with addresses that are determined automatically based on the LAN configuration.
61 +** Lighting control hardware (e.g. TSWs, DIN-CENCN-2s, etc.) should be connected to the Control Subnet port. The processor acts as a DHCP server on the Control Subnet, with addresses that are determined automatically based on the LAN configuration. 
62 +*** Lighting hardware can be connected via the LAN port, however for proper functionality you must run the command: ##securegateway default##
60 60  ** The Control Subnet will automatically configure itself based on the LAN configuration, but it can optionally be configured manually:
61 61  *** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox:
62 62  **** Set routing to "Manual" with the start address and subnet size
... ... @@ -96,7 +96,7 @@
96 96  *** Click the "Send" button and click "Yes" to upload the program
97 97  *** Once it is done loading, you should be able to run the ##sr ver## command and see the currently installed version of SHOWRUNNER™
98 98  * Once SHOWRUNNER™ is loaded, you can connect to the UI by navigating to the processor’s IP. A license and configuration file are still required.  
99 -** **3-Series processors require authentication enabled** (SSL self can be used but steps will need to be repeated)
102 +** **3-Series processors require authentication enabled** ("##ssl self##" command followed by a reboot can be used but steps will need to be repeated)
100 100  ** If stuck on "Connecting to Processor" you will need to accept the certificate
101 101  * For jobs with multiple processors, SHOWRUNNER™ will need to be loaded to each processor
102 102