Changes for page GLPAC Expansion Setup

Summary

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

Details

Page properties

Content

...	...	@@ -17,47 +17,38 @@
17	17
18	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	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
	20	+1. Open the configuration .json in a text editor (Notepad++ or VS Code recommended)
	21	+1. Press ctrl+h to open the "Find/Replace" menu
	22	+1. In the "Find" field, put the old GLPAC IP address
	23	+1. In the "Replace" field, put the new GLPAC IP address
	24	+1. Press the replace all button
	25	+1. Repeat steps 2-5 for all GLPACs that have different IP addresses
25	25
26		-The
	27	+If you intend to use the load script to load the GLPAC program, then the load script must also be updated with the new GLPAC IP addresses:
27	27
	29	+1. Open the load scrip in a text editor (Notepad++ or VS Code recommended)
	30	+1. Press ctrl+h to open the "Find/Replace" menu
	31	+1. In the "Find" field, put the old GLPAC IP address
	32	+1. In the "Replace" field, put the new GLPAC IP address
	33	+1. Press the replace all button
	34	+1. Repeat steps 2-5 for all GLPACs that have different IP addresses
	35	+
28	28	**Using non-default processor IP Address**
29	29
30		-The SHOWRUNNER™ configuration file
	38	+If you intend to use the load script to load the GLPAC program but the processor has a different IP address than is indicated in the hardware takeoff, then the load script must be updated with the new processor IP address:
31	31
	40	+1. Open the load scrip in a text editor (Notepad++ or VS Code recommended)
	41	+1. Press ctrl+h to open the "Find/Replace" menu
	42	+1. In the "Find" field, put the old processor IP address
	43	+1. In the "Replace" field, put the new processor IP address
	44	+1. Press the replace all button
32	32
33		-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:
34		-
35		-* Open the configuration file in VS Code, Notepad++, or another text editor of your choice
36		-* Press ctrl+h to open the "Find/Replace" menu
37		-** In the "Find" field, put the old GLPAC IP Address
38		-** In the "Replace" field, put the new GLPAC IP Address
39		-** Press the "Replace All" button
40		-* Repeat these steps for all GLPACs that have altered IP addresses
41		-
42		-If either the GLPAC or the processor's IP address needs to be changed to meet the job's network requirements, then the load script will also need to be updated:
43		-
44		-* Open the GLPAC_LoadScript.txt file in a text editor of your choice
45		-* Press ctrl+h to open the "Find/Replace" menu
46		-** In the "Find" field, put the old GLPAC IP Address
47		-** In the "Replace" field, put the new GLPAC IP Address
48		-** Press the "Replace All" button
49		-* Repeat the previous step for all GLPACs that have altered IP addresses
50		-* Press ctrl+h to open the "Find/Replace" menu again
51		-** In the "Find" field, put the old processor IP Address
52		-** In the "Replace" field, put the new processor IP Address
53		-** Press the "Replace All" button
54		-
55	55	=== IP Configuration ===
56	56
57	57	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.
58	58
59	59	* Connect to the GLPAC via USB
60		-* Open Text Console and run the following commands to configure the GLPACs IP settings (example is for a GLPAC at 10.0.0.11 on a 10.0.0.0/24 subnet)
	51	+* Open Text Console and run the following commands to configure the GLPACs IP settings (example is for a GLPAC at 10.0.0.11 on a 10.0.0.0/24 subnet with hostname "GLPAC-1")
61	61	** Disable DHCP: ##dhcp off##
62	62	** Set IP address: ##ipa 0 10.0.0.11##
63	63	** Set IP subnet mask: ##ipm 0 255.255.255.0##
...	...	@@ -71,15 +71,29 @@
71	71	==== Using Chief Integrations Provided Load Script ====
72	72
73	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
	65	+* The Load Script connects to each GLPAC via it's IP address and will automatically load the expansion program and update the GPLACs IP table
	66	+** The script is set up using the Chief Integrations chosen IP addresses unless otherwise requested. If either the GLPAC or processor are at different IP addresses, then the script will need to be edited as described above
76	76	** The load script must be in the same folder as a folder called "GLPAC" with the GLPAC Expansion program in it:
77	77	[[image:1654877108357-278.png]]
78		-* 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.
79		-* Using Toolbox -> Script Manager, select the Scripting dropdown or right click and select “Load Script”.  Find the text file provided.
80		-* 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™
81		-* Say yes to the dialog warning the hardware does not match (if prompted), and yes to overwrite the IP table (if prompted)
	69	+* Using the Script Manager tool in toolbox, select the Scripting dropdown or right click and select “Load Script”
	70	+* Provided the given IP addresses can be seen on the network, double clicking or right clicking an entry will run the script, loading the program and configuring the IP table for the selected GLPAC
	71	+* If prompted, select "Yes" to overwrite the existing IP Table and "Yes" to proceed even though the device model is different
82	82
83	83	==== Manually Loading the GLPAC Expansion ====
84	84
85	85	* Connect to the GLPAC via Text Console
	76	+* Click the lighting bolt and select "SIMPL Program..."
	77	+** Alternatively, press alt+p to open this menu directly
	78	+* Under "Send Program", browse for and select the CI.Lighting.ShowRunner_GLPAC-Expansion.spz file
	79	+* If you have the corresponding .sig file, you can check "Send SIG File"
	80	+* Click "Send" to begin loading the program to the GLPAC
	81	+** If prompted, click "Yes" to overwrite the device's IP Table
	82	+** If prompted, click "Yes" to ignore that the program specifies a different model
	83	+* Wait for the GLPAC to finish rebooting and then connect via Text Console
	84	+* In Text Console, send the following commands (example is for a processor at 10.0.0.10 and a GLPAC with IP-ID B1):
	85	+** Remove current IP Table entry: ##rems E0 10.44.5.55##
	86	+** Update IP Table entry: ##adds B1 10.0.0.10 E0##
	87	+** Reboot the GLPAC: ##reboot##
	88	+* Wait for the GLPAC to finish rebooting
	89	+* Connect to the processor via Text Console and run the command: ##ipt##
	90	+* The console should print the processor's IP table. If the GLPAC has been configured correctly, it's corresponding entry in the IP table (with the IP-ID and IP address for the GLPAC) should read "Status: ONLINE"