Skip to Content

Changes for page Processor Setup

Last modified by Alexander Mott on 2025/04/30 15:55
From version 54.1
edited by Alexander Mott
on 2024/12/02 18:59
Change comment: There is no comment for this version
To version 57.1
edited by Alexander Mott
on 2025/04/30 15:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,12 @@
1 -(% class="box errormessage" %)
2 -(((
1 +{{info}}
3 3  This page is for typical processor setup; for ZUM-HUB4 deployments, see our [[dedicated ZUM-HUB4 page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUM-HUB4 Processor Setup.WebHome]].
3 +{{/info}}
4 4  
5 +{{error}}
5 5  All 4-Series processors require authentication to be configured when first connecting: **the Crestron Agent or Field Tech are responsible for recording these credentials. Chief Integrations cannot provide assistance unless the credentials are known. The only way to connect to a device for which the credentials have been lost is to factory reset the device, which may require redoing the start-up from scratch if the latest configuration was not saved and backed up. **
6 -)))
7 +{{/error}}
7 7  
8 -(% class="box warningmessage" %)
9 -(((
9 +{{warning}}
10 10  ShowRunnerCLC™™ is tested against current Crestron firmware releases. **Please use at least the recommended firmware builds.**
11 11  
12 12  * 3-Series: PUF 1.8001.0214
... ... @@ -17,7 +17,7 @@
17 17  
18 18  * Static IP or properly setup DHCP/DNS implementation required.
19 19  * Auto-Assigned/Link-Local IP address range of 169.254.x.x not supported (Crestron xPanel issue)
20 -)))
20 +{{/warning}}
21 21  
22 22  {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
23 23  {{toc/}}
... ... @@ -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.