Skip to Content

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
Change comment: There is no comment for this version
To version 44.1
edited by Alexander Mott
on 2023/05/23 17:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -31,6 +31,20 @@
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 +
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
... ... @@ -56,8 +56,8 @@
56 56  ** Connect to the processor via Text Console and run the command: ##startprogafterrouter on##
57 57  *** 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.
58 58  ** 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.
59 -** 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. 
60 -*** Lighting hardware can be connected via the LAN port, however for proper functionality you must run the command: ##securegateway default##
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 61  ** The Control Subnet will automatically configure itself based on the LAN configuration, but it can optionally be configured manually:
62 62  *** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox:
63 63  **** Set routing to "Manual" with the start address and subnet size