Skip to Content

Changes for page Processor Setup

Last modified by Alexander Mott on 2024/12/02 19:04
From version 26.1
edited by Alexander Mott
on 2022/07/07 13:32
Change comment: There is no comment for this version
To version 20.1
edited by Alexander Mott
on 2022/06/30 15:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,13 +6,9 @@
1 -(% class="box errormessage" %)
2 -(((
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 -)))
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.
3 +showrunner™ is tested against current Crestron firmware releases.  Please use at least the recommended firmware builds.
9 9  3-Series: PUF 1.8001.0146
10 10  4-Series: PUF 2.7000.00052.01
6 +ZUM-HUB4: PUF 2.005.0056
11 11  VC-4: 2.7000.00047
12 12  )))
13 13  
... ... @@ -54,13 +54,10 @@
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 will automatically configure itself based on the LAN configuration, but it can optionally be configured manually:
58 -*** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox:
59 -**** Set routing to "Manual" with the start address and subnet size
60 -**** 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
61 -*** Using Text Console commands (example for a **100.64.0.0/20** subnet, with a processor IP address of **100.64.0.1**)
62 -**** Set CS IP: ##csrouterprefix **100.64.0.0/20**##
63 -**** Reboot the processor: ##reboot##
53 +** The Control Subnet can be configured manually in the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox
54 +*** Set routing to "Manual" with the start address and subnet size
55 +*** 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
56 +** 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**##
64 64  * If the job has multiple processors, then these steps must be repeated for all processors on the job
65 65  ** For jobs with Central Control, the IP addresses of the processors matters
66 66  ** 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
... ... @@ -69,7 +69,7 @@
69 69  === Program Load ===
70 70  
71 71  * Download the latest build of SHOWRUNNER™ from the[[ Chief Integrations Portal>>https://files.chiefintegrations.com/index.php/s/WHNzXrrZbB5jC3E]]
72 -* 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
65 +* 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.
73 73  ** While it is possible to load the program via USB, it is not recommended because the transfer speed is significantly slower than loading via Ethernet
74 74  * Double click the PUF to open the Package Update Tool and install SHOWRUNNER™ (works best with Toolbox closed)
75 75  ** The Package Update Tool will automatically open your Address Book and prompt you to select a device
... ... @@ -84,18 +84,17 @@
84 84  ** Run the command ##sr ver##
85 85  ** If the console returns with the newly installed version of SHOWRUNNER™, then the installation was successful
86 86  ** If the console returns with "Bad or Incomplete Command (sr)" then the installation was not successful
87 -*** Rename the downloaded .puf file to be a .zip file and open the archive
80 +*** Rename the .puf file to be a .zip file and open the archive
88 88  **** Some file archivers (such as 7-Zip) allow you to right click on the PUF file and open the archive without changing the filetype
89 89  *** Extract the "CI.Lighting.ShowRunner.cpz" file
90 -*** In Toolbox, connect to the processor via Text Console, click the lightning bolt icon, and select "SIMPL Program..."
91 -**** Alternatively, navigate to Functions>SIMPL Program...>SIMPL Program (Program01)...
92 -*** Under the "Send Program" section, browse your PC and select the extracted .cpz file
83 +*** In Toolbox, connect to the processor via Text Console and click the lightning bolt icon and select "SIMPL Program..."
84 +*** Under the "Send" section, browse your PC and select the extracted .cpz file
93 93  *** Click the "Send" button and click "Yes" to upload the program
94 94  *** Once it is done loading, you should be able to run the ##sr ver## command and see the currently installed version of SHOWRUNNER™
95 95  * 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.  
96 -** **3-Series processors require authentication enabled** (SSL self can be used but steps will need to be repeated)
97 -** If stuck on "Connecting to Processor" you will need to accept the certificate
98 -* For jobs with multiple processors, SHOWRUNNER™ will need to be loaded to each processor
88 +** **3-Series processors require authentication enabled** (SSL self can be used but steps will need to be repeated).
89 +** If stuck on "Connecting to Processor" you will need to accept the certificate.
90 +* For jobs with multiple processors, SHOWRUNNER™ will need to be loaded to each processor.
99 99  
100 100  === License and Configuration Deployment ===
101 101  
... ... @@ -120,7 +120,7 @@
120 120  ***** ##sradmin username "name" administrators password##
121 121  ***** The username and password should be one word each and are the credentials used to log in to the showrunnerHUB™
122 122  ***** The name can be multiple words as long as it is in quotes, and is simply a friendly name used to identify each user.
123 -*** Once logged in to the showrunnerHUB™ UI, you should be automatically redirected to the File Management page
115 +*** Once logged in to the showrunnerHUB™ UI, you should be automatically redirected to the File Management page.
124 124  **** If you are not automatically redirected, then you can navigate to this page by clicking "Setup" in the top right and then selecting "File Management" from the list on the left
125 125  **** [[image:1654807593390-193.png]]
126 126  **** Under “Upload New License File”