Changes for page Processor Setup
Last modified by Alexander Mott on 2024/12/02 19:04
From version 42.1
edited by Alexander Mott
on 2023/05/16 14:23
on 2023/05/16 14:23
Change comment:
There is no comment for this version
To version 43.1
edited by Alexander Mott
on 2023/05/19 17:21
on 2023/05/19 17:21
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -31,6 +31,21 @@ 31 31 32 32 [[https:~~/~~/www.youtube.com/watch?v=H8CLZ7bp0eI>>url:https://www.youtube.com/watch?v=H8CLZ7bp0eI]] 33 33 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 + 34 34 = IP Configuration = 35 35 36 36 * Connect to the processor via USB and set the processor’s IP Address per your network requirements