Changes for page Processor Setup

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.alexander\.mott@chiefintegrations\.com
	1	+XWiki.scott\.kohlmann@chiefintegrations\.com

Content

...	...	@@ -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
...	...	@@ -70,8 +70,8 @@
70	70	** Connect to the processor via Text Console and run the command: ##startprogafterrouter on##
71	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.
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
	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##
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
...	...	@@ -130,16 +130,14 @@
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	135	** 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 add user **username **"**name**" Administrators **password**##
	126	+***** ##sradmin username "name" administrators password##
141	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
	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.
143	143	*** 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]]
...	...	@@ -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 to restart, possibly longer depending on the size and complexity of the configuration
162		-***** 4-Series processors will restart considerably faster
	147	+***** 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
...	...	@@ -183,3 +183,4 @@
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	+)))