Wiki source code of GLPAC Expansion Setup

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

Navigation