Changes for page Processor Setup

Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -21,8 +21,6 @@
21	21	{{toc/}}
22	22	{{/box}}
23	23
24		-(% class="row" %)
25		-(((
26	26	**ShowRunnerCLC™ Installation Tutorial:**
27	27
28	28	[[https:~~/~~/www.youtube.com/watch?v=xuJ94cMCCa8>>url:https://www.youtube.com/watch?v=xuJ94cMCCa8]]
...	...	@@ -33,6 +33,21 @@
33	33
34	34	[[https:~~/~~/www.youtube.com/watch?v=H8CLZ7bp0eI>>url:https://www.youtube.com/watch?v=H8CLZ7bp0eI]]
35	35
	34	+(% class="wikigeneratedid" %)
	35	+= Error Broadcasting =
	36	+
	37	+The first thing that should be done after connecting to a processor is to open the Text Console and run the command: ##broadcast on##
	38	+
	39	+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:
	40	+
	41	+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.
	42	+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.
	43	+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)
	44	+
	45	+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.
	46	+
	47	+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.
	48	+
36	36	= IP Configuration =
37	37
38	38	* Connect to the processor via USB and set the processor’s IP Address per your network requirements
...	...	@@ -118,14 +118,16 @@
118	118	*** Right-click on the right-hand side and select "Copy File(s) From..." and select the downloaded SrConfig.json file
119	119	**** Alternatively, drag and drop the file from your computer to the File Management tool
120	120	**** If you downloaded a CiLightingConfig.json file, it must be renamed to "SrConfig.json"
	134	+*** Note: when loading the license and configuration through Toolbox, the "License.lic" file and "SrConfig.json" file must have exact filenames
	135	+**** 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
121	121	** Using the ShowRunnerHUB™ UI:
122	122	*** Using Chrome or Firefox, navigate to the processor's IP address
123	123	*** When prompted, input your credentials and log in
124	124	**** 4-Series processor or 3-Series processor with authentication enabled: Log in using the same admin credentials used to connect to the processor
125	125	**** 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.
126		-***** ##sradmin username "name" administrators password##
	141	+***** ##sradmin add user **username **"**name**" Administrators **password**##
127	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.
	143	+***** 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	129	*** Once logged in to the ShowRunnerHUB™ UI, you should be automatically redirected to the File Management page
130	130	**** 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
131	131	**** [[image:1654807593390-193.png]]
...	...	@@ -144,8 +144,8 @@
144	144	****** Enter the secret used to create the backup. ShowRunner will upload the file and verify the secret.
145	145	**** Once both the license and either a configuration file or backup have been loaded, click "Restart"
146	146	**** Wait for the processor to finish restarting and then reload the page.
147		-***** 3-Series processors will take 45 to 90 restart
148		-***** 4-Series processors should restart considerably faster
	162	+***** 3-Series processors will take 45 to 90 seconds to restart, possibly longer depending on the size and complexity of the configuration
	163	+***** 4-Series processors will restart considerably faster
149	149
150	150	= Set System Time =
151	151
...	...	@@ -169,4 +169,3 @@
169	169	** Navigate to Setup>System Settings>Location and System Clock
170	170	** Adjust the time, timezone, and location as necessary
171	171	** Click Apply to save the changes
172		-)))