Skip to Content

Changes for page Processor Setup

Last modified by Alexander Mott on 2024/12/02 19:04
From version 41.1
edited by Alexander Mott
on 2023/05/15 21:07
Change comment: There is no comment for this version
To version 52.1
edited by Alexander Mott
on 2024/03/27 15:23
Change comment: There is no comment for this version

Summary

Details

Page properties
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.0146
11 -* 4-Series: PUF 2.7000.00052.01
12 -* VC-4: 2.7000.00047
10 +* 3-Series: PUF 1.8001.0214
11 +* 4-Series: PUF 2.8003.00037.01
12 +* VC-4: 4.0003.00016
13 13  
14 14  **Notes:**
15 15  
... ... @@ -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,20 @@
33 33  
34 34  [[https:~~/~~/www.youtube.com/watch?v=H8CLZ7bp0eI>>url:https://www.youtube.com/watch?v=H8CLZ7bp0eI]]
35 35  
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 +
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
... ... @@ -54,13 +54,17 @@
54 54  *** Configure your DHCP server software to assign IP addresses in the desired range
55 55  *** Once the processor is assigned an IP address, connect to it via Text Console at the assigned IP address
56 56  *** Run the above commands to disable DHCP and assign a static IP address to the processor
57 -* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4), additional setup is required
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.
58 58  ** Connect to the processor via Text Console and run the command: ##startprogafterrouter on##
59 59  *** 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 automatically run this command when the "Configure Processor with Router" option is selected.
60 60  ** 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.
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:
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:
64 64  *** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox:
65 65  **** Set routing to "Manual" with the start address and subnet size
66 66  **** 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
... ... @@ -71,6 +71,7 @@
71 71  ** For jobs with Central Control, the IP addresses of the processors matters
72 72  ** 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
73 73  ** 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]]
74 74  
75 75  = Program Load =
76 76  
... ... @@ -148,6 +148,8 @@
148 148  **** Wait for the processor to finish restarting and then reload the page.
149 149  ***** 3-Series processors will take 45 to 90 seconds to restart, possibly longer depending on the size and complexity of the configuration
150 150  ***** 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]]
151 151  
152 152  = Set System Time =
153 153  
... ... @@ -171,4 +171,3 @@
171 171  ** Navigate to Setup>System Settings>Location and System Clock
172 172  ** Adjust the time, timezone, and location as necessary
173 173  ** Click Apply to save the changes
174 -)))