Changes for page Processor Setup

Last modified by Alexander Mott on 2024/12/02 19:04

From version 22.1
edited by Alexander Mott
on 2022/06/30 15:32
Change comment: There is no comment for this version
To version 36.1
edited by Alexander Mott
on 2022/10/04 22:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,23 +1,28 @@
1 1  (% class="box errormessage" %)
2 2  (((
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]].
3 +This page is for typical 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 -3-Series: PUF 1.8001.0146
10 -4-Series: PUF 2.7000.00052.01
11 -VC-4: 2.7000.00047
12 -)))
8 +SHOWRUNNER™ is tested against current Crestron firmware releases. **Please use at least the recommended firmware builds.**
13 13  
14 -(% class="box infomessage" id="HNotes" %)
15 -(((
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)
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)
19 19  )))
20 20  
20 +{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
21 +{{toc/}}
22 +{{/box}}
23 +
24 +(% class="row" %)
25 +(((
21 21  **ShowRunner Installation Tutorial:**
22 22  
23 23  [[https:~~/~~/www.youtube.com/watch?v=xuJ94cMCCa8>>url:https://www.youtube.com/watch?v=xuJ94cMCCa8]]
... ... @@ -28,7 +28,7 @@
28 28  
29 29  [[https:~~/~~/www.youtube.com/watch?v=H8CLZ7bp0eI>>url:https://www.youtube.com/watch?v=H8CLZ7bp0eI]]
30 30  
31 -=== IP Configuration ===
36 += IP Configuration =
32 32  
33 33  * Connect to the processor via USB and set the processor’s IP Address per your network requirements
34 34  ** 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,16 +54,19 @@
54 54  *** 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.
55 55  ** 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.
56 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**##
62 +** The Control Subnet will automatically configure itself based on the LAN configuration, but it can optionally be configured manually:
63 +*** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox:
64 +**** Set routing to "Manual" with the start address and subnet size
65 +**** 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
66 +*** Using Text Console commands (example for a **100.64.0.0/20** subnet, with a processor IP address of **100.64.0.1**)
67 +**** Set CS IP: ##csrouterprefix **100.64.0.0/20**##
68 +**** Reboot the processor: ##reboot##
61 61  * If the job has multiple processors, then these steps must be repeated for all processors on the job
62 62  ** For jobs with Central Control, the IP addresses of the processors matters
63 63  ** 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
64 64  ** 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
65 65  
66 -=== Program Load ===
74 += Program Load =
67 67  
68 68  * Download the latest build of SHOWRUNNER™ from the[[ Chief Integrations Portal>>https://files.chiefintegrations.com/index.php/s/WHNzXrrZbB5jC3E]]
69 69  * 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
... ... @@ -81,19 +81,20 @@
81 81  ** Run the command ##sr ver##
82 82  ** If the console returns with the newly installed version of SHOWRUNNER™, then the installation was successful
83 83  ** If the console returns with "Bad or Incomplete Command (sr)" then the installation was not successful
84 -*** Rename the .puf file to be a .zip file and open the archive
92 +*** Rename the downloaded .puf file to be a .zip file and open the archive
85 85  **** Some file archivers (such as 7-Zip) allow you to right click on the PUF file and open the archive without changing the filetype
86 86  *** Extract the "CI.Lighting.ShowRunner.cpz" file
87 -*** In Toolbox, connect to the processor via Text Console and click the lightning bolt icon and select "SIMPL Program..."
88 -*** Under the "Send" section, browse your PC and select the extracted .cpz file
95 +*** In Toolbox, connect to the processor via Text Console, click the lightning bolt icon, and select "SIMPL Program..."
96 +**** Alternatively, navigate to Functions>SIMPL Program...>SIMPL Program (Program01)...
97 +*** Under the "Send Program" section, browse your PC and select the extracted .cpz file
89 89  *** Click the "Send" button and click "Yes" to upload the program
90 90  *** Once it is done loading, you should be able to run the ##sr ver## command and see the currently installed version of SHOWRUNNER™
91 91  * 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.  
92 -** **3-Series processors require authentication enabled** (SSL self can be used but steps will need to be repeated)
101 +** **3-Series processors require authentication enabled** ("##ssl self##" command followed by a reboot can be used but steps will need to be repeated)
93 93  ** If stuck on "Connecting to Processor" you will need to accept the certificate
94 94  * For jobs with multiple processors, SHOWRUNNER™ will need to be loaded to each processor
95 95  
96 -=== License and Configuration Deployment ===
105 += License and Configuration Deployment =
97 97  
98 98  * Download the SrConfig.json or CiLightingConfig.json configuration file from the link provided by Chief Integrations
99 99  * Obtain and download the license from [[https:~~/~~/portal.chiefintegrations.com>>url:https://portal.chiefintegrations.com]]
... ... @@ -137,7 +137,7 @@
137 137  ***** 3-Series processors will take 45 to 90 restart
138 138  ***** 4-Series processors should restart considerably faster
139 139  
140 -=== Set System Time ===
149 += Set System Time =
141 141  
142 142  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:
143 143  
... ... @@ -159,3 +159,4 @@
159 159  ** Navigate to Setup>System Settings>Location and System Clock
160 160  ** Adjust the time, timezone, and location as necessary
161 161  ** Click Apply to save the changes
171 +)))