Skip to Content

Changes for page GLPAC Expansion Setup

Last modified by Alexander Mott on 2023/12/12 00:02
From version 19.1
edited by Alexander Mott
on 2022/06/17 19:40
Change comment: Renamed from xwiki:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.GLPAC Setup.WebHome
To version 20.1
edited by Alexander Mott
on 2022/09/16 20:57
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.WebHome
1 +SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome
Content
... ... @@ -1,5 +1,11 @@
1 -=== GLPACs in SHOWRUNNER™ ===
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
5 +(% class="row" %)
6 +(((
7 += GLPACs in SHOWRUNNER™ =
8 +
3 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 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.
... ... @@ -43,7 +43,7 @@
43 43  1. In the "Replace" field, put the new processor IP address
44 44  1. Press the replace all button
45 45  
46 -=== IP Configuration ===
52 += IP Configuration =
47 47  
48 48  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.
49 49  
... ... @@ -57,9 +57,9 @@
57 57  ** Reboot the GLPAC: ##reboot##
58 58  * 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
59 59  
60 -=== Loading the GLPAC Expansion Program ===
66 += Loading the GLPAC Expansion Program =
61 61  
62 -==== Using Chief Integrations Provided Load Script ====
68 +== Using Chief Integrations Provided Load Script ==
63 63  
64 64  * Chief Integrations typically provides a Load Script
65 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
... ... @@ -70,7 +70,7 @@
70 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 71  * If prompted, select "Yes" to overwrite the existing IP Table and "Yes" to proceed even though the device model is different
72 72  
73 -==== Manually Loading the GLPAC Expansion ====
79 +== Manually Loading the GLPAC Expansion ==
74 74  
75 75  * Connect to the GLPAC via Text Console
76 76  * Click the lighting bolt and select "SIMPL Program..."
... ... @@ -88,3 +88,4 @@
88 88  * Wait for the GLPAC to finish rebooting
89 89  * Connect to the processor via Text Console and run the command: ##ipt##
90 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"
97 +)))