Skip to Content

Changes for page Processor Setup

Last modified by Alexander Mott on 2024/12/02 19:04
From version 44.1
edited by Alexander Mott
on 2023/05/23 17:11
Change comment: There is no comment for this version
To version 48.1
edited by Alexander Mott
on 2024/03/27 15:14
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  
... ... @@ -66,13 +66,16 @@
66 66  *** Configure your DHCP server software to assign IP addresses in the desired range
67 67  *** Once the processor is assigned an IP address, connect to it via Text Console at the assigned IP address
68 68  *** Run the above commands to disable DHCP and assign a static IP address to the processor
69 -* 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 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 +*** ShowRunnerCLC™ version 3.042 and newer .puf files have a "Configure Processor with Router" section which runs this command automatically.
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 +** Lighting control hardware (e.g. TSWs, DIN-CENCN-2s, etc.) should be left in DHCP mode and connected to the Control Subnet port.
75 +*** The processor acts as a DHCP server on the Control Subnet, with addresses that are determined automatically based on the LAN configuration.
76 +*** If lighting hardware is to be connected via the LAN anyway, then you must run the command: ##securegateway default##
74 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
75 -** The Control Subnet will automatically configure itself based on the LAN configuration, but it can optionally be configured manually:
78 +** 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:
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
78 78  **** 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
... ... @@ -83,6 +83,7 @@
83 83  ** For jobs with Central Control, the IP addresses of the processors matters
84 84  ** 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
85 85  ** 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
89 +* 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]]
86 86  
87 87  = Program Load =
88 88  
... ... @@ -160,6 +160,8 @@
160 160  **** Wait for the processor to finish restarting and then reload the page.
161 161  ***** 3-Series processors will take 45 to 90 seconds to restart, possibly longer depending on the size and complexity of the configuration
162 162  ***** 4-Series processors will restart considerably faster
167 +**** 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]]
168 +**** 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]]
163 163  
164 164  = Set System Time =
165 165