Skip to Content

Wiki source code of GLPAC Expansion Setup

Version 23.1 by Alexander Mott on 2022/09/19 16:07
Show last authors
1 {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 {{toc/}}
3 {{/box}}
4
5 (% class="row" %)
6 (((
7
8 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.
9
10 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.
11
12 When a SHOWRUNNER™ job with GLPACs is shipped, Chief integrations will provide several files:
13
14 * The GLPAC expansion program (A folder called "GLPAC" containing CI.Lighting.ShowRunner_GLPAC-Expansion.spz)
15 * A Load Script to streamline loading the program to the GLPACs (GLPAC_LoadScript.txt)
16 * The main SHOWRUNNER™ configuration file (SrConfig.json or CiLightingConfig.json)
17 * The job hardware takeoff (SRTakeoff.xlsx)
18
19 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 typically recorded in the provided hardware takeoff, or can be checked by running the ##ipt -t ##command from the processor after the configuration is loaded. DIN-CENCN-2's will typically have IP-IDs in the "##Dx##" range.. 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.
20
21 **Using non-default GLPAC IP Addresses**
22
23 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:
24
25 1. Open the configuration .json in a text editor (Notepad++ or VS Code recommended)
26 1. Press ctrl+h to open the "Find/Replace" menu
27 1. In the "Find" field, put the old GLPAC IP address
28 1. In the "Replace" field, put the new GLPAC IP address
29 1. Press the replace all button
30 1. Repeat steps 2-5 for all GLPACs that have different IP addresses
31
32 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:
33
34 1. Open the load scrip in a text editor (Notepad++ or VS Code recommended)
35 1. Press ctrl+h to open the "Find/Replace" menu
36 1. In the "Find" field, put the old GLPAC IP address
37 1. In the "Replace" field, put the new GLPAC IP address
38 1. Press the replace all button
39 1. Repeat steps 2-5 for all GLPACs that have different IP addresses
40
41 **Using non-default processor IP Address**
42
43 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:
44
45 1. Open the load scrip in a text editor (Notepad++ or VS Code recommended)
46 1. Press ctrl+h to open the "Find/Replace" menu
47 1. In the "Find" field, put the old processor IP address
48 1. In the "Replace" field, put the new processor IP address
49 1. Press the replace all button
50
51 = IP Configuration =
52
53 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 that has a control subnet or is 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.
54
55 * Connect to the GLPAC via USB
56 * Open Text Console and run the following commands to configure the GLPACs IP settings (example is for a GLPAC at (% style="color:blue" %)**10.0.0.11**(%%) on a **10.0.0.0(% style="color:darkgoldenrod" %)/24(%%)** subnet with hostname (% style="color:purple" %)**GLPAC-1**(%%))
57 ** Disable DHCP: ##dhcp off##
58 ** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.11**(%%)##
59 ** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)##
60 ** Set default gateway: ##defr 0 **10.0.0.1**##
61 ** Set hostname: ##host (% style="color:purple" %)**GLPAC-1**(%%)##
62 ** Reboot the GLPAC: ##reboot##
63 * All GLPACs on the job will need to be configured in this way, but if the network is not up (i.e., if it is not yet possible to plug in at one location and communicate via Ethernet to all GLPACs on the job) then it is more time efficient to proceed and load the program over USB before moving on to the next GLPAC
64
65 = Loading the GLPAC Expansion Program =
66
67 == Using Chief Integrations Provided Load Script ==
68
69 * Chief Integrations typically provides a Load Script
70 * 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
71 ** 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
72 ** The load script must be in the same folder as a folder called "GLPAC" with the GLPAC Expansion program in it:
73 [[image:1654877108357-278.png]]
74 * Using the Script Manager tool in toolbox, select the Scripting dropdown or right click and select “Load Script”
75 * 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
76 * If prompted, select "Yes" to overwrite the existing IP Table and "Yes" to proceed even though the device model is different
77
78 == Manually Loading the GLPAC Expansion ==
79
80 * Connect to the GLPAC via Text Console
81 * Click the lighting bolt and select "SIMPL Program..."
82 ** Alternatively, press alt+p to open this menu directly
83 * Under "Send Program", browse for and select the CI.Lighting.ShowRunner_GLPAC-Expansion.spz file
84 * If you have the corresponding .sig file, you can check "Send SIG File"
85 * Click "Send" to begin loading the program to the GLPAC
86 ** If prompted, click "Yes" to overwrite the device's IP Table
87 ** If prompted, click "Yes" to ignore that the program specifies a different model
88 * Wait for the GLPAC to finish rebooting and then connect via Text Console
89 * In Text Console, send the following commands (example is for a processor at (% style="color:orange" %)**10.0.0.10**(%%) and a GLPAC with IP-ID (% style="color:olive" %)**B1**(%%)):
90 ** Remove current IP Table entry: ##rems E0 10.44.5.55##
91 ** Update IP Table entry: ##adds (% style="color:olive" %)**B1**(%%) (% style="color:orange" %)**10.0.0.10**(%%) E0##
92 ** Reboot the GLPAC: ##reboot##
93 * Wait for the GLPAC to finish rebooting
94 * Connect to the processor via Text Console and run the command: ##ipt##
95 * 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"
96 )))