Skip to Content

Changes for page Processor Setup

Last modified by Alexander Mott on 2026/03/04 22:06
From version 56.1
edited by Alexander Mott
on 2024/12/02 19:04
Change comment: There is no comment for this version
To version 58.1
edited by Alexander Mott
on 2026/03/04 20:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -69,7 +69,13 @@
69 69  *** Once the processor is assigned an IP address, connect to it via Text Console at the assigned IP address
70 70  *** Run the above commands to disable DHCP and assign a static IP address to the processor
71 71  * For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4), there are some additional considerations and setup that must be performed: 
72 -** Never connect an external router to the Control Subnet, as doing so will cause the internal DHCP server to shut down.
72 +** **Never **connect an external router to the Control Subnet, as doing so will cause the internal DHCP server to shut down.
73 +** **Never **set the LAN IP address to an address that is in the range of the Control Subnet
74 +*** e.g. for a processor with the default 172.22.0.0/20 Control Subnet configuration, the LAN IP address must be below 172.22.0.0 or above 172.22.15.255
75 +** **Always** set devices on the Control Subnet to DHCP so that their IP addresses are managed by the built-in DHCP server. Only set static IP addresses on the Control Subnet if you really know what you are doing.
76 +*** If setting static IP addresses on the Control Subnet for any reason: **always** assign an address within the Control Subnet range, but **never** use the first two or the last address in the range
77 +*** e.g. for a processor with the default 172.22.0.0/20 Control Subnet configuration, IP addresses must be in the range 172.22.0.3 through 172.22.15.254
78 +**** 172.22.0.0 is not a valid address, 172.22.0.1 is taken by the processor, 172.22.0.2 is taken by the DHCP server (default gateway), and 172.22.15.255 is the broadcast address for the Control Subnet
73 73  ** Connect to the processor via Text Console and run the command: ##startprogafterrouter on##
74 74  *** 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.
75 75  *** ShowRunnerCLC™ .puf versions 3.042 and newer automatically run this command when the "Configure Processor with Router" option is selected.
... ... @@ -89,8 +89,11 @@
89 89  ** For jobs with Central Control, the IP addresses of the processors matters
90 90  ** 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
91 91  ** 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
92 -* 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]]
93 93  
99 += Firmware Update =
100 +
101 +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||anchor="HNetworkDevices"]]
102 +
94 94  = Program Load =
95 95  
96 96  * Download the latest build of ShowRunnerCLC™ from the[[ Chief Integrations Portal>>https://files.chiefintegrations.com/index.php/s/WHNzXrrZbB5jC3E]]