Changes for page Processor Setup

Summary

• Page properties (1 modified, 0 added, 0 removed)

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
...	...	@@ -81,11 +81,12 @@
81	81	** Run the command ##sr ver##
82	82	** If the console returns with the newly installed version of SHOWRUNNER™, then the installation was successful
83	83	** If the console returns with "Bad or Incomplete Command (sr)" then the installation was not successful
84		-*** Rename the .puf file to be a .zip file and open the archive
	87	+*** Rename the downloaded .puf file to be a .zip file and open the archive
85	85	**** Some file archivers (such as 7-Zip) allow you to right click on the PUF file and open the archive without changing the filetype
86	86	*** Extract the "CI.Lighting.ShowRunner.cpz" file
87		-*** In Toolbox, connect to the processor via Text Console and click the lightning bolt icon and select "SIMPL Program..."
88		-*** Under the "Send" section, browse your PC and select the extracted .cpz file
	90	+*** In Toolbox, connect to the processor via Text Console, click the lightning bolt icon, and select "SIMPL Program..."
	91	+**** Alternatively, navigate to Functions>SIMPL Program...>SIMPL Program (Program01)...
	92	+*** Under the "Send Program" section, browse your PC and select the extracted .cpz file
89	89	*** Click the "Send" button and click "Yes" to upload the program
90	90	*** Once it is done loading, you should be able to run the ##sr ver## command and see the currently installed version of SHOWRUNNER™
91	91	* Once SHOWRUNNER™ is loaded, you can connect to the UI by navigating to the processor’s IP. A license and configuration file are still required.