Changes for page Processor Setup
Last modified by Alexander Mott on 2024/12/02 19:04
From version 37.1
edited by Alexander Mott
on 2022/10/19 18:04
on 2022/10/19 18:04
Change comment:
There is no comment for this version
To version 23.1
edited by Alexander Mott
on 2022/06/30 16:52
on 2022/06/30 16:52
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,28 +1,23 @@ 1 1 (% class="box errormessage" %) 2 2 ((( 3 -This page is for typicalprocessor setup;for ZUM-HUB4 deployments, see our [[dedicated ZUM-HUB4 page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUM-HUB4 Processor Setup.WebHome]].3 +This page is for ordinary processor setup. For ZUM-HUB4 deployments, see our [[dedicated ZUM-HUB4 page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUM-HUB4 Processor Setup.WebHome]]. 4 4 ))) 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.** 9 - 10 -* 3-Series: PUF 1.8001.0146 11 -* 4-Series: PUF 2.7000.00052.01 12 -* VC-4: 2.7000.00047 13 - 14 -**Notes:** 15 - 16 -* Static IP or properly setup DHCP/DNS implementation required. 17 -* Auto-Assigned/Link-Local IP address range of 169.254.x.x not supported (Crestron xPanel issue) 8 +SHOWRUNNER™ is tested against current Crestron firmware releases. Please use at least the recommended firmware builds. 9 +3-Series: PUF 1.8001.0146 10 +4-Series: PUF 2.7000.00052.01 11 +VC-4: 2.7000.00047 18 18 ))) 19 19 20 -{{box cssClass="floatinginfobox" title="**CONTENTS**"}} 21 -{{toc/}} 22 -{{/box}} 23 - 24 -(% class="row" %) 14 +(% class="box infomessage" id="HNotes" %) 25 25 ((( 16 +Notes 17 +Static IP or properly setup DHCP/DNS implementation required. 18 +Auto-Assigned/Link-Local IP address range of 169.254.x.x not supported (Crestron xPanel issue) 19 +))) 20 + 26 26 **ShowRunner Installation Tutorial:** 27 27 28 28 [[https:~~/~~/www.youtube.com/watch?v=xuJ94cMCCa8>>url:https://www.youtube.com/watch?v=xuJ94cMCCa8]] ... ... @@ -33,7 +33,7 @@ 33 33 34 34 [[https:~~/~~/www.youtube.com/watch?v=H8CLZ7bp0eI>>url:https://www.youtube.com/watch?v=H8CLZ7bp0eI]] 35 35 36 -= IP Configuration = 31 +=== IP Configuration === 37 37 38 38 * Connect to the processor via USB and set the processor’s IP Address per your network requirements 39 39 ** When connecting to a 4-Series processor or a 3-Series processor with authentication enabled for the first time, it will prompt for the creation of an admin-level CWS user ... ... @@ -54,25 +54,21 @@ 54 54 *** Configure your DHCP server software to assign IP addresses in the desired range 55 55 *** Once the processor is assigned an IP address, connect to it via Text Console at the assigned IP address 56 56 *** Run the above commands to disable DHCP and assign a static IP address to the processor 57 -* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4), additional setup is required 52 +* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4/ZUM-HUB4), additional setup is required 58 58 ** Connect to the processor via Text Console and run the command: ##startprogafterrouter on## 59 59 *** 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. 60 60 ** 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. 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## 63 -** The Control Subnet will automatically configure itself based on the LAN configuration, but it can optionally be configured manually: 64 -*** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox: 65 -**** Set routing to "Manual" with the start address and subnet size 66 -**** E.g., a setting of "100.64.0.0/20" will have the processor at 10.64.0.1 with an IP mask of 255.255.240.0 and a default gateway and DNS server at 100.64.0.2 67 -*** Using Text Console commands (example for a **100.64.0.0/20** subnet, with a processor IP address of **100.64.0.1**) 68 -**** Set CS IP: ##csrouterprefix **100.64.0.0/20**## 69 -**** Reboot the processor: ##reboot## 56 +** 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. 57 +** The Control Subnet can be configured manually in the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox 58 +*** Set routing to "Manual" with the start address and subnet size 59 +*** E.g., a setting of "10.0.0.0/24" will have the processor at 10.0.0.1 with an IP mask of 255.255.255.0 and a default gateway and DNS server at 10.0.0.2 60 +** The Control Subnet can also be configured to e.g. **10.0.0.0/24** using Text Console command: ##csrouterprefix **10.0.0.0/24**## 70 70 * If the job has multiple processors, then these steps must be repeated for all processors on the job 71 71 ** For jobs with Central Control, the IP addresses of the processors matters 72 72 ** Chief Integrations will provide an SRTakeoff.xlsx spreadsheet with an IP Table tab that lists the IP address for each processor. If these IP addresses must be changed during startup, then it will be necessary to also change the IP addresses in the Remote System Definition in the configuration file 73 73 ** See the[[ CoAP Setup Guide>>doc:SHOWRUNNER™ Integrations Guide.Integration Options.CoAP with Crestron S# Library and Modules.CoAP ShowRunner to ShowRunner Setup Instructions.WebHome]] for details 74 74 75 -= Program Load = 66 +=== Program Load === 76 76 77 77 * Download the latest build of SHOWRUNNER™ from the[[ Chief Integrations Portal>>https://files.chiefintegrations.com/index.php/s/WHNzXrrZbB5jC3E]] 78 78 * Connect your computer to the same network as the processor. Make sure your computer’s IP settings are compatible with the lighting network and do not conflict with any devices already on the network ... ... @@ -93,17 +93,17 @@ 93 93 *** Rename the downloaded .puf file to be a .zip file and open the archive 94 94 **** Some file archivers (such as 7-Zip) allow you to right click on the PUF file and open the archive without changing the filetype 95 95 *** Extract the "CI.Lighting.ShowRunner.cpz" file 96 -*** In Toolbox, connect to the processor via Text Console ,click the lightning bolt icon,and select "SIMPL Program..."87 +*** In Toolbox, connect to the processor via Text Console and click the lightning bolt icon and select "SIMPL Program..." 97 97 **** Alternatively, navigate to Functions>SIMPL Program...>SIMPL Program (Program01)... 98 98 *** Under the "Send Program" section, browse your PC and select the extracted .cpz file 99 99 *** Click the "Send" button and click "Yes" to upload the program 100 100 *** Once it is done loading, you should be able to run the ##sr ver## command and see the currently installed version of SHOWRUNNER™ 101 101 * 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. 102 -** **3-Series processors require authentication enabled** ( "##sslself##"commandfollowedby a rebootcan beused but steps will need to be repeated)93 +** **3-Series processors require authentication enabled** (SSL self can be used but steps will need to be repeated) 103 103 ** If stuck on "Connecting to Processor" you will need to accept the certificate 104 104 * For jobs with multiple processors, SHOWRUNNER™ will need to be loaded to each processor 105 105 106 -= License and Configuration Deployment = 97 +=== License and Configuration Deployment === 107 107 108 108 * Download the SrConfig.json or CiLightingConfig.json configuration file from the link provided by Chief Integrations 109 109 * Obtain and download the license from [[https:~~/~~/portal.chiefintegrations.com>>url:https://portal.chiefintegrations.com]] ... ... @@ -147,7 +147,7 @@ 147 147 ***** 3-Series processors will take 45 to 90 restart 148 148 ***** 4-Series processors should restart considerably faster 149 149 150 -= Set System Time = 141 +=== Set System Time === 151 151 152 152 It is important for the device clock to be accurate in order for scheduled events to trigger at the appropriate time. If Toolbox is still open, this can be done easily: 153 153 ... ... @@ -169,4 +169,3 @@ 169 169 ** Navigate to Setup>System Settings>Location and System Clock 170 170 ** Adjust the time, timezone, and location as necessary 171 171 ** Click Apply to save the changes 172 -)))