Changes for page GLPAC Expansion Setup

Summary

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

Details

Page properties

Content

...	...	@@ -1,9 +1,35 @@
1	1	=== GLPACs in SHOWRUNNER™ ===
2	2
3		-On SHOWRUNNER™ jobs which have GLPACs, all GLPACs must have their IP settings configured and then the CI.Lighting.ShowRunner_GLPAC-Expansion.spz program must be loaded to each GLPAC.
	3	+GLPACs are an all-in-one, processor plus 0-10V load controller produced by Crestron. They are available in 4-channel (GLPAC-DIMFLV4) and 8-channel (GLPAC-DIMFLV8) varieties. GLPACs can be used in stand-alone configurations using either the built-in SpaceBuilder program or Chief Integrations' own CI-GLPAC program.
4	4
5		-Since GLPACs are 2-Series processors, the expansion program must be loaded to make them obey commands from the 3-Series or 4-Series processor that is running the main SHOWRUNNER™ program and configuration file.
	5	+Most SHOWRUNNER™ jobs using GLPACs are not using them in a standalone configuration, however. SHOWRUNNER™ jobs with networked GLPACs use the 3-Series or 4-Series processor to run the program logic, and treat the GLPACs as load controllers rather than as separate processors. Each GLPAC must have its IP settings configured, be loaded with a GLPAC-Expansion program, and then have its IP table updated.
6	6
	7	+When a SHOWRUNNER™ job with GLPACs is shipped, Chief integrations will provide several files:
	8	+
	9	+* The GLPAC expansion program (A folder called "GLPAC" containing CI.Lighting.ShowRunner_GLPAC-Expansion.spz)
	10	+* A Load Script to streamline loading the program to the GLPACs (GLPAC_LoadScript.txt)
	11	+* The main SHOWRUNNER™ configuration file (SrConfig.json or CiLightingConfig.json)
	12	+* The job hardware takeoff (SRTakeoff.xlsx)
	13	+
	14	+The IP address and IP-ID of each GLPAC is important to proper functionality. Unless otherwise requested, Chief Integrations will assign default IP addresses to all GLPACs on the job. These IP addresses are recorded in the provided hardware takeoff. If network requirements on the jobsite require changing the IP address of any GLPAC or the processor, then both the provided configuration file and load script will need to be updated with the new IP information.
	15	+
	16	+**Using non-default GLPAC IP Addresses**
	17	+
	18	+If GLPACs need to be configured with different IP addresses than are given in the hardware takeoff, then the showrunner configuration file must be updated:
	19	+
	20	+* Open the configuration .json in a text editor (Notepad++ or VS Code recommended)
	21	+* Press ctrl+h to open the "Find/Replace" menu
	22	+* In the "Find" field, put the old GLPAC IP address
	23	+* In the "Replace" field, put the new GLPAC IP address
	24	+* Press the replace all button
	25	+
	26	+The
	27	+
	28	+**Using non-default processor IP Address**
	29	+
	30	+The SHOWRUNNER™ configuration file
	31	+
	32	+
7	7	For jobs with GLPACs, Chief Integrations will provide a load script to streamline the GLPAC configuration process. The IP addresses for each GLPAC are set to Chief Integrations default addresses unless otherwise requested. These IP addresses are provided in the IP Table section of the SRTakeoff.xlsx spreadsheet. If these IP addresses need to be changed to meet the job's network requirements, then SHOWRUNNER™ configuration file will need to be updated:
8	8
9	9	* Open the configuration file in VS Code, Notepad++, or another text editor of your choice
...	...	@@ -26,7 +26,7 @@
26	26	** In the "Replace" field, put the new processor IP Address
27	27	** Press the "Replace All" button
28	28
29		-=== GLPAC IP Configuration ===
	55	+=== IP Configuration ===
30	30
31	31	Theoretically, GLPACs should be able to be configured over Ethernet using a computer that is running a DHCP server (or if they are on a network with a processor running the [[SHOWRUNNER™ DHCP Server>>doc:SHOWRUNNER™ User Guide & Wiki.Troubleshooting.DHCP Server.WebHome]]). In practice, however, GLPACs will oftentimes fail to take an IP address from a DHCP server and still require manual configuration via USB.
32	32
...	...	@@ -44,7 +44,11 @@
44	44
45	45	==== Using Chief Integrations Provided Load Script ====
46	46
47		-* When GLPACs are deployed Chief Integrations will provide a load script that loads and configures the GLPAC hardware. The script includes Chief Integrations chosen IP addresses unless otherwise requested.
	73	+* Chief Integrations typically provides a Load Script
	74	+* The load script
	75	+** The script is set up using the Chief Integrations chosen IP addresses unless otherwise requested. If the GLPACs or processor are at different IP addresses, then the script will need to be edited as described above
	76	+** The load script must be in the same folder as a folder called "GLPAC" with the GLPAC Expansion program in it:
	77	+[[image:1654877108357-278.png]]
48	48	* Set the IP addresses on all GLPACs per your network requirements.  The script will need to be updated if IP Addresses are changed from Chief Integrations chosen IP Addresses.
49	49	* Using Toolbox -> Script Manager, select the Scripting dropdown or right click and select “Load Script”.  Find the text file provided.
50	50	* Provided the given IPs can be seen on the network, double or right clicking an entry will load the program and link the IP table, enabling control through showrunner™