Changes for page Processor Setup
Last modified by Alexander Mott on 2024/12/02 19:04
From version 44.1
edited by Alexander Mott
on 2023/05/23 17:11
on 2023/05/23 17:11
Change comment:
There is no comment for this version
To version 30.1
edited by Alexander Mott
on 2022/09/16 20:47
on 2022/09/16 20:47
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -5,23 +5,26 @@ 5 5 6 6 (% class="box warningmessage" %) 7 7 ((( 8 -ShowRunnerCLC™™ 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 +3-Series: PUF 1.8001.0146 10 +4-Series: PUF 2.7000.00052.01 11 +VC-4: 2.7000.00047 12 +))) 9 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) 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) 18 18 ))) 19 19 20 -{{box cssClass="floatinginfobox"title="**CONTENTS**"}}21 +{{box title="**Contents**"}} 21 21 {{toc/}} 22 22 {{/box}} 23 23 24 -**ShowRunnerCLC™ Installation Tutorial:** 25 +(% class="row" %) 26 +((( 27 +**ShowRunner Installation Tutorial:** 25 25 26 26 [[https:~~/~~/www.youtube.com/watch?v=xuJ94cMCCa8>>url:https://www.youtube.com/watch?v=xuJ94cMCCa8]] 27 27 ... ... @@ -31,20 +31,6 @@ 31 31 32 32 [[https:~~/~~/www.youtube.com/watch?v=H8CLZ7bp0eI>>url:https://www.youtube.com/watch?v=H8CLZ7bp0eI]] 33 33 34 -= Error Broadcasting = 35 - 36 -The first thing that should be done after connecting to a processor is to open the Text Console and run the command: ##broadcast on## 37 - 38 -Running the ##broadcast on## command tells the processor to begin logging useful messages to the text console and error log. These messages typically begin with an indication of their severity: 39 - 40 -1. Error: Most errors indicate a major issue that should be investigated and remedied. Some errors will prevent the ShowRunner™ program from starting up or functioning as expected, and may be the result of a configuration issue (e.g. errors registering devices), a network issue (e.g. errors connecting to other devices), or authentication issues (e.g. errors related to connection attempts from clients not providing correct username/password information), among other possible causes. 41 -1. Warning: Warnings indicate issues that are less severe than errors and do not usually prevent the ShowRunner™ program from running, but may result in some unexpected behaviors. 42 -1. Notice: Notices are not a problem, and just give useful information during program startup (e.g. devices registered) and while the program is running (e.g. the times at which scheduled events are triggered) 43 - 44 -Running the ##err sys## command will print the most recent 500 messages to the console. Running the ##clear err## command will clear the log, which is sometimes useful to run before doing a ##progreset## in order to troubleshoot configuration issues on startup. 45 - 46 -To view more than the last 500 messages, connect to the processor with the File Manager tool and navigate to the "Internal Storage > logs" folder. Logs since the last time the processor rebooted are stored in the "CurrentBoot" folder, with a new log started every time the current log reaches ~~1 MB in size. When the processor reboots, the logs in the "PreviousBoot" folder are zipped and moved to the "ZippedLogs" folder, logs in the "CurrentBoot" folder are moved to the "PreviousBoot" folder, and a new log is started in the "CurrentBoot" folder. 47 - 48 48 = IP Configuration = 49 49 50 50 * Connect to the processor via USB and set the processor’s IP Address per your network requirements ... ... @@ -66,12 +66,11 @@ 66 66 *** Configure your DHCP server software to assign IP addresses in the desired range 67 67 *** Once the processor is assigned an IP address, connect to it via Text Console at the assigned IP address 68 68 *** Run the above commands to disable DHCP and assign a static IP address to the processor 69 -* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4), additional setup is required 58 +* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4/ZUM-HUB4), additional setup is required 70 70 ** Connect to the processor via Text Console and run the command: ##startprogafterrouter on## 71 -*** This will force the processor to wait until the router has started before attempting to load the ShowRunnerCLC™ program, avoiding potential license validation issues if the processor boots up before the router.60 +*** 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. 72 72 ** 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. 73 -** 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. If lighting hardware is to be connected via the LAN anyway, run the command: ##securegateway default## 74 -*** Note: this setting enables unsecure connections to the processor from the LAN. This is necessary if ZUMNET-JBOXs or other non-secure Crestron devices (such as 3-Series EISC) will be connected via the LAN port of the processor 62 +** 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. 75 75 ** The Control Subnet will automatically configure itself based on the LAN configuration, but it can optionally be configured manually: 76 76 *** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox: 77 77 **** Set routing to "Manual" with the start address and subnet size ... ... @@ -86,10 +86,10 @@ 86 86 87 87 = Program Load = 88 88 89 -* Download the latest build of S howRunnerCLC™ from the[[ Chief Integrations Portal>>https://files.chiefintegrations.com/index.php/s/WHNzXrrZbB5jC3E]]77 +* Download the latest build of SHOWRUNNER™ from the[[ Chief Integrations Portal>>https://files.chiefintegrations.com/index.php/s/WHNzXrrZbB5jC3E]] 90 90 * 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 91 91 ** 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 92 -* Double click the PUF to open the Package Update Tool and install S howRunnerCLC™ (works best with Toolbox closed)80 +* Double click the PUF to open the Package Update Tool and install SHOWRUNNER™ (works best with Toolbox closed) 93 93 ** The Package Update Tool will automatically open your Address Book and prompt you to select a device 94 94 *** If you have not created an Address Book for this job, close the Address Book window and press the pencil icon 95 95 *** Type in the IP address of your processor and click "OK" ... ... @@ -96,11 +96,11 @@ 96 96 ** Double check that the correct PUF file is listed under the "Package Info" section and that the correct IP address is listed under "Target" 97 97 ** Press the "Recheck" button 98 98 ** Make sure that all three tasks are selected ("Load ShowRunner Program", "Update Crestron App", and "Update XPanel") 99 -** Press the "Update" button to begin loading S howRunnerCLC™87 +** Press the "Update" button to begin loading SHOWRUNNER™ 100 100 * Sometimes the PUF tool will falsely report a failure to load the program 101 101 ** Connect to the processor via Text Console 102 102 ** Run the command ##sr ver## 103 -** If the console returns with the newly installed version of S howRunnerCLC™, then the installation was successful91 +** If the console returns with the newly installed version of SHOWRUNNER™, then the installation was successful 104 104 ** If the console returns with "Bad or Incomplete Command (sr)" then the installation was not successful 105 105 *** Rename the downloaded .puf file to be a .zip file and open the archive 106 106 **** Some file archivers (such as 7-Zip) allow you to right click on the PUF file and open the archive without changing the filetype ... ... @@ -109,11 +109,11 @@ 109 109 **** Alternatively, navigate to Functions>SIMPL Program...>SIMPL Program (Program01)... 110 110 *** Under the "Send Program" section, browse your PC and select the extracted .cpz file 111 111 *** Click the "Send" button and click "Yes" to upload the program 112 -*** Once it is done loading, you should be able to run the ##sr ver## command and see the currently installed version of S howRunnerCLC™113 -* Once S howRunnerCLC™ is loaded, you can connect to the UI by navigating to the processor’s IP. A license and configuration file are still required.114 -** **3-Series processors require authentication enabled** ( "##sslself##"commandfollowedby a rebootcan beused but steps will need to be repeated)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 +* 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** (SSL self can be used but steps will need to be repeated) 115 115 ** If stuck on "Connecting to Processor" you will need to accept the certificate 116 -* For jobs with multiple processors, S howRunnerCLC™ will need to be loaded to each processor104 +* For jobs with multiple processors, SHOWRUNNER™ will need to be loaded to each processor 117 117 118 118 = License and Configuration Deployment = 119 119 ... ... @@ -120,7 +120,7 @@ 120 120 * Download the SrConfig.json or CiLightingConfig.json configuration file from the link provided by Chief Integrations 121 121 * Obtain and download the license from [[https:~~/~~/portal.chiefintegrations.com>>url:https://portal.chiefintegrations.com]] 122 122 ** Processors with a Control Subnet should use the LAN MAC address, **not** the Control Subnet MAC address 123 -* The license and configuration can be loaded with Toolbox using Text Console and File Management, or through the ShowRunnerHUB™ web interface111 +* The license and configuration can be loaded with Toolbox using Text Console and File Management, or through the showrunnerHUB™ web interface 124 124 ** Using Toolbox: 125 125 *** Connect to the processor via Text Console and via File Management 126 126 *** In File management, navigate to the "NVRAM>sr" folder from the left-hand menu ... ... @@ -130,17 +130,15 @@ 130 130 *** Right-click on the right-hand side and select "Copy File(s) From..." and select the downloaded SrConfig.json file 131 131 **** Alternatively, drag and drop the file from your computer to the File Management tool 132 132 **** If you downloaded a CiLightingConfig.json file, it must be renamed to "SrConfig.json" 133 -*** Note: when loading the license and configuration through Toolbox, the "License.lic" file and "SrConfig.json" file must have exact filenames 134 -**** If the files were automatically numbered during download (e.g. by adding a "(1)" or "(2)" to the end of the filename), the files must be renamed before loading them to the processor 135 -** Using the ShowRunnerHUB™ UI: 121 +** Using the showrunnerHUB™ UI: 136 136 *** Using Chrome or Firefox, navigate to the processor's IP address 137 137 *** When prompted, input your credentials and log in 138 138 **** 4-Series processor or 3-Series processor with authentication enabled: Log in using the same admin credentials used to connect to the processor 139 139 **** 3-Series processor without authentication enabled: Connect to the processor via Text Console and run the following command, replacing the "username", "name" and "password" with your desired credentials. 140 -***** ##sradmin adduser**username**"**name**"Administrators**password**##141 -***** The username and password should be one word each and are the credentials used to log in to the ShowRunnerHUB™142 -***** The name can be multiple words as long as it is in quotes, and is simply a friendly name used to identify each user 143 -*** Once logged in to the ShowRunnerHUB™ UI, you should be automatically redirected to the File Management page126 +***** ##sradmin username "name" administrators password## 127 +***** The username and password should be one word each and are the credentials used to log in to the showrunnerHUB™ 128 +***** The name can be multiple words as long as it is in quotes, and is simply a friendly name used to identify each user. 129 +*** Once logged in to the showrunnerHUB™ UI, you should be automatically redirected to the File Management page 144 144 **** 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 145 145 **** [[image:1654807593390-193.png]] 146 146 **** Under “Upload New License File” ... ... @@ -158,8 +158,8 @@ 158 158 ****** Enter the secret used to create the backup. ShowRunner will upload the file and verify the secret. 159 159 **** Once both the license and either a configuration file or backup have been loaded, click "Restart" 160 160 **** Wait for the processor to finish restarting and then reload the page. 161 -***** 3-Series processors will take 45 to 90 seconds torestart, possibly longer depending on the size and complexity of the configuration162 -***** 4-Series processors willrestart considerably faster147 +***** 3-Series processors will take 45 to 90 restart 148 +***** 4-Series processors should restart considerably faster 163 163 164 164 = Set System Time = 165 165 ... ... @@ -172,14 +172,15 @@ 172 172 ** If your PC is in the incorrect Timezone or the time did not synchronize properly, then manually adjust the Time, Date, and Timezone 173 173 * Press the Apply button 174 174 175 -Note that the Location given in the System Clock... menu of Toolbox is not used by S howRunnerCLC™. Instead, the location used for sunrise/sunset calculations is stored in the configuration and will typically be set by Chief Integrations prior to delivery of the configuration. Both the location and time can be viewed and edited using the ShowRunnerCLC™ UI161 +Note that the Location given in the System Clock... menu of Toolbox is not used by SHOWRUNNER™. Instead, the location used for sunrise/sunset calculations is stored in the configuration and will typically be set by Chief Integrations prior to delivery of the configuration. Both the location and time can be viewed and edited using the SHOWRUNNER™ UI 176 176 177 -* S howRunnerCLC™ XPanel UI:163 +* SHOWRUNNER™ XPanel UI: 178 178 ** Navigate to Settings>Location and System Clock 179 179 ** Press the Lock icon to enable editing 180 180 ** Adjust the time, timezone, and location as necessary 181 181 ** Press Set System Clock to save the changes 182 -* ShowRunnerHUB™ Web UI:168 +* showrunnerHUB™ Web UI: 183 183 ** Navigate to Setup>System Settings>Location and System Clock 184 184 ** Adjust the time, timezone, and location as necessary 185 185 ** Click Apply to save the changes 172 +)))