Skip to Content

Changes for page Processor Setup

Last modified by Alexander Mott on 2024/12/02 19:04
From version 50.1
edited by Alexander Mott
on 2024/03/27 15:22
Change comment: There is no comment for this version
To version 38.1
edited by Scott Kohlmann
on 2023/04/20 22:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
1 +XWiki.scott\.kohlmann@chiefintegrations\.com
Content
... ... @@ -7,9 +7,9 @@
7 7  (((
8 8  ShowRunnerCLC™™ is tested against current Crestron firmware releases. **Please use at least the recommended firmware builds.**
9 9  
10 -* 3-Series: PUF 1.8001.0214
11 -* 4-Series: PUF 2.8003.00037.01
12 -* VC-4: 4.0003.00016
10 +* 3-Series: PUF 1.8001.0146
11 +* 4-Series: PUF 2.7000.00052.01
12 +* VC-4: 2.7000.00047
13 13  
14 14  **Notes:**
15 15  
... ... @@ -21,6 +21,8 @@
21 21  {{toc/}}
22 22  {{/box}}
23 23  
24 +(% class="row" %)
25 +(((
24 24  **ShowRunnerCLC™ Installation Tutorial:**
25 25  
26 26  [[https:~~/~~/www.youtube.com/watch?v=xuJ94cMCCa8>>url:https://www.youtube.com/watch?v=xuJ94cMCCa8]]
... ... @@ -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,17 +66,13 @@
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), there are some additional considerations and setup that must be performed: 
70 -** Never connect an external router to the Control Subnet, as doing so will cause the internal DHCP server to shut down.
57 +* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4), additional setup is required
71 71  ** Connect to the processor via Text Console and run the command: ##startprogafterrouter on##
72 72  *** 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.
73 -*** ShowRunnerCLC™ .puf versions 3.042 and newer include this command in the "Configure Processor with Router" option.
74 74  ** 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.
75 -** Lighting control hardware (e.g. TSWs, DIN-CENCN-2s, etc.) should be left in DHCP mode and connected to the Control Subnet port.
76 -*** The processor acts as a DHCP server on the Control Subnet, with addresses that are determined automatically based on the LAN configuration.
77 -*** If lighting hardware is to be connected via the LAN anyway, then you must run the command: ##securegateway default##
78 -*** 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
79 -** The Control Subnet will automatically configure itself based on the LAN configuration, but it should be configured manually if the processor is to be connected to building LAN as the default scheme may cause networking issues:
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:
80 80  *** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox:
81 81  **** Set routing to "Manual" with the start address and subnet size
82 82  **** 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
... ... @@ -87,7 +87,6 @@
87 87  ** For jobs with Central Control, the IP addresses of the processors matters
88 88  ** 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
89 89  ** 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
90 -* At this point, it is a good idea to [[update the device firmware>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Updating Firmware.WebHome]]
91 91  
92 92  = Program Load =
93 93  
... ... @@ -135,16 +135,14 @@
135 135  *** Right-click on the right-hand side and select "Copy File(s) From..." and select the downloaded SrConfig.json file
136 136  **** Alternatively, drag and drop the file from your computer to the File Management tool
137 137  **** If you downloaded a CiLightingConfig.json file, it must be renamed to "SrConfig.json"
138 -*** Note: when loading the license and configuration through Toolbox, the "License.lic" file and "SrConfig.json" file must have exact filenames
139 -**** 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
140 140  ** Using the ShowRunnerHUB™ UI:
141 141  *** Using Chrome or Firefox, navigate to the processor's IP address
142 142  *** When prompted, input your credentials and log in
143 143  **** 4-Series processor or 3-Series processor with authentication enabled: Log in using the same admin credentials used to connect to the processor
144 144  **** 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.
145 -***** ##sradmin add user **username **"**name**" Administrators **password**##
126 +***** ##sradmin username "name" administrators password##
146 146  ***** The username and password should be one word each and are the credentials used to log in to the ShowRunnerHUB™
147 -***** The name can be multiple words as long as it is in quotes, and is simply a friendly name used to identify each user
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.
148 148  *** Once logged in to the ShowRunnerHUB™ UI, you should be automatically redirected to the File Management page
149 149  **** 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
150 150  **** [[image:1654807593390-193.png]]
... ... @@ -163,10 +163,8 @@
163 163  ****** Enter the secret used to create the backup. ShowRunner will upload the file and verify the secret.
164 164  **** Once both the license and either a configuration file or backup have been loaded, click "Restart"
165 165  **** Wait for the processor to finish restarting and then reload the page.
166 -***** 3-Series processors will take 45 to 90 seconds to restart, possibly longer depending on the size and complexity of the configuration
167 -***** 4-Series processors will restart considerably faster
168 -**** If licensed for SR-BNI, you will need to generate a [[free Crestron BACnet License>>https://www.crestron.com/Support/Tools/Licensing-Registration/Bacnet-License-Registration]]
169 -**** If licensed for SR-BNI50, you will need to generate a [[paid Crestron 50+ BACnet Point License>>https://www.crestron.com/Support/Tools/Licensing-Registration/Bacnet-License-Registration]]
147 +***** 3-Series processors will take 45 to 90 restart
148 +***** 4-Series processors should restart considerably faster
170 170  
171 171  = Set System Time =
172 172  
... ... @@ -190,3 +190,4 @@
190 190  ** Navigate to Setup>System Settings>Location and System Clock
191 191  ** Adjust the time, timezone, and location as necessary
192 192  ** Click Apply to save the changes
172 +)))