Changes for page GLPAC Expansion Setup
Last modified by Alexander Mott on 2023/12/12 00:02
From version 8.1
edited by Alexander Mott
on 2022/06/10 21:02
on 2022/06/10 21:02
Change comment:
There is no comment for this version
To version 7.1
edited by Alexander Mott
on 2022/06/10 16:36
on 2022/06/10 16:36
Change comment:
Uploaded new attachment "1654878970161-751.png", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,54 +1,37 @@ 1 1 === GLPACs in SHOWRUNNER™ === 2 2 3 - GLPACs are anall-in-one,processor plus 0-10V load controller producedby Crestron.They are available in 4-channel(GLPAC-DIMFLV4)and 8-channel(GLPAC-DIMFLV8) varieties.GLPACscanbeusedintand-aloneconfigurationsusing eitherthebuilt-inpaceBuilder program or ChiefIntegrations'own CI-GLPACprogram.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. 4 4 5 - MostSHOWRUNNER™ jobs usingGLPACs arenotusingtheminastandaloneconfiguration,however.SHOWRUNNER™ jobswithnetworkedGLPACsusethe 3-Series or 4-Series processor to run the program logic, andtreatthe GLPACsas load controllersratherthanasseparate processors. Each GLPACmusthave its IP settingsconfigured, be loaded with a GLPAC-Expansionprogram, and then haveits IP tableupdated.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. 6 6 7 - Whena SHOWRUNNER™job with GLPACs is shipped,Chiefintegrationswill 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: 8 8 9 -* The GLPAC expansion program (A folder called "GLPAC" containing CI.Lighting.ShowRunner_GLPAC-Expansion.spz) 10 -* A Load Script to streamline loading the program to the GLPACs (GLPAC_LoadScript.txt) 11 -* The main SHOWRUNNER™ configuration file (SrConfig.json or CiLightingConfig.json) 12 -* 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 13 13 14 - TheIP address and IP-ID of each GLPACis importanttoproper functionality. Unlesstherwiserequested, ChiefIntegrations will assign default IP addressesto all GLPACs onthejob. These IP addressesare recordedin theprovidedhardware takeoff.If network requirementsonthe jobsite requirechanging theIP address of any GLPAC orthe processor, thenboththeprovided configuration file and load script will need to be updatedwith 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: 15 15 16 -**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 17 17 18 - IfGLPACsneed to be configured with differentIPaddresses than are given in the hardware takeoff, thenthe showrunner configurationfile must be updated:29 +=== GLPAC IP Configuration === 19 19 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 26 - 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: 28 - 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 - 36 -**Using non-default processor IP Address** 37 - 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: 39 - 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 45 - 46 -=== IP Configuration === 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 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 50 50 * Connect to the GLPAC via USB 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")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) 52 52 ** Disable DHCP: ##dhcp off## 53 53 ** Set IP address: ##ipa 0 10.0.0.11## 54 54 ** Set IP subnet mask: ##ipm 0 255.255.255.0## ... ... @@ -61,30 +61,12 @@ 61 61 62 62 ==== Using Chief Integrations Provided Load Script ==== 63 63 64 -* Chief Integrations typically provides a Load Script 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 67 -** The load script must be in the same folder as a folder called "GLPAC" with the GLPAC Expansion program in it: 68 -[[image:1654877108357-278.png]] 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 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) 72 72 73 73 ==== Manually Loading the GLPAC Expansion ==== 74 74 75 75 * 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"