Skip to Content

Changes for page Processor Setup

Last modified by Alexander Mott on 2024/12/02 19:04
From version 24.1
edited by Alexander Mott
on 2022/06/30 16:53
Change comment: There is no comment for this version
To version 25.1
edited by Alexander Mott
on 2022/06/30 17:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -54,10 +54,13 @@
54 54  *** This will force the processor to wait until the router has started before attempting to load the showrunner™ program, avoiding potential license validation issues if the processor boots up before the router.
55 55  ** 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.
56 56  ** 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.
57 -** The Control Subnet can be configured manually in the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox
58 -*** Set routing to "Manual" with the start address and subnet size
59 -*** E.g., a setting of "10.0.0.0/24" will have the processor at 10.0.0.1 with an IP mask of 255.255.255.0 and a default gateway and DNS server at 10.0.0.2
60 -** The Control Subnet can also be configured to e.g. **10.0.0.0/24** using Text Console command: ##csrouterprefix **10.0.0.0/24**##
57 +** The Control Subnet will automatically configure itself based on the LAN configuration, but it can optionally be configured manually:
58 +*** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox:
59 +**** Set routing to "Manual" with the start address and subnet size
60 +**** 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
61 +*** Using Text Console commands (example for a **100.64.0.0/20** subnet, with a processor IP address of **100.64.0.1**)
62 +**** Set CS IP: ##csrouterprefix **100.64.0.0/20**##
63 +**** Reboot the processor: ##reboot##
61 61  * If the job has multiple processors, then these steps must be repeated for all processors on the job
62 62  ** For jobs with Central Control, the IP addresses of the processors matters
63 63  ** 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