Skip to Content

Changes for page GLPAC Expansion Setup

Last modified by Alexander Mott on 2023/12/12 00:02
From version 27.1
edited by Alexander Mott
on 2023/05/16 18:09
Change comment: There is no comment for this version
To version 4.1
edited by Alexander Mott
on 2022/06/09 22:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome
1 +SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.WebHome
Content
... ... @@ -1,92 +1,55 @@
1 -{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 -{{toc/}}
3 -{{/box}}
1 +=== GLPACs in SHOWRUNNER™ ===
4 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.
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.
6 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.
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.
8 8  
9 -When a ShowRunnerCLC™ job with GLPACs is shipped, Chief integrations will provide several files:
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:
10 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)
9 +* Open the configuration file in VS Code, Notepad++, or another text editor of your choice
10 +* Press ctrl+h to open the "Find/Replace" menu
11 +** In the "Find" field, put the old GLPAC IP Address
12 +** In the "Replace" field, put the new GLPAC IP Address
13 +** Press the "Replace All" button
14 +* Repeat these steps for all GLPACs that have altered IP addresses
15 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.
16 +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:
17 17  
18 -**Using non-default GLPAC IP Addresses**
18 +* Open the GLPAC_LoadScript.txt file in a text editor of your choice
19 +* Press ctrl+h to open the "Find/Replace" menu
20 +** In the "Find" field, put the old GLPAC IP Address
21 +** In the "Replace" field, put the new GLPAC IP Address
22 +** Press the "Replace All" button
23 +* Repeat the previous step for all GLPACs that have altered IP addresses
24 +* Press ctrl+h to open the "Find/Replace" menu again
25 +** In the "Find" field, put the old processor IP Address
26 +** In the "Replace" field, put the new processor IP Address
27 +** Press the "Replace All" button
19 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:
29 +=== GLPAC IP Configuration ===
21 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
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.
28 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 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**(%%))
34 +* 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)
54 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**(%%)##
36 +** Set IP address: ##ipa 0 10.0.0.11##
37 +** Set IP subnet mask: ##ipm 0 255.255.255.0##
38 +** Set default gateway: ##defr 0 10.0.0.1##
39 +** Set hostname: ##host GLPAC-1##
59 59  ** Reboot the GLPAC: ##reboot##
60 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 61  
62 -= Loading the GLPAC Expansion Program =
43 +=== Loading the GLPAC Expansion Program ===
63 63  
64 -== Using Chief Integrations Provided Load Script ==
45 +==== Using Chief Integrations Provided Load Script ====
65 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
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.
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 +* Using Toolbox -> Script Manager, select the Scripting dropdown or right click and select “Load Script”.  Find the text file provided.
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™
51 +* Say yes to the dialog warning the hardware does not match (if prompted), and yes to overwrite the IP table (if prompted)
74 74  
75 -== Manually Loading the GLPAC Expansion ==
53 +==== Manually Loading the GLPAC Expansion ====
76 76  
77 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"
1654877108357-278.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -6.8 KB
Content
1654878734520-796.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -31.8 KB
Content
1654878970161-751.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -31.8 KB
Content