Changes for page Processor Setup
Last modified by Alexander Mott on 2024/12/02 19:04
From version 36.1
edited by Alexander Mott
on 2022/10/04 22:08
on 2022/10/04 22:08
Change comment:
There is no comment for this version
To version 37.1
edited by Alexander Mott
on 2022/10/19 18:04
on 2022/10/19 18:04
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -54,11 +54,12 @@ 54 54 *** Configure your DHCP server software to assign IP addresses in the desired range 55 55 *** Once the processor is assigned an IP address, connect to it via Text Console at the assigned IP address 56 56 *** Run the above commands to disable DHCP and assign a static IP address to the processor 57 -* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4 /ZUM-HUB4), additional setup is required57 +* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4), additional setup is required 58 58 ** Connect to the processor via Text Console and run the command: ##startprogafterrouter on## 59 59 *** This will force the processor to wait until the router has started before attempting to load the showrunner™ program, avoiding potential license validation issues if the processor boots up before the router. 60 60 ** The previously listed "ipa," "ipm," etc. commands will configure settings for the processor's LAN port, which should be connected to the building LAN or third party network. 61 -** Lighting control hardware (e.g. TSWs, DIN-CENCN-2s, etc.) should be connected to the Control Subnet port. The processor acts as a DHCP server on the Control Subnet, with addresses that are determined automatically based on the LAN configuration. 61 +** Lighting control hardware (e.g. TSWs, DIN-CENCN-2s, etc.) should be connected to the Control Subnet port. The processor acts as a DHCP server on the Control Subnet, with addresses that are determined automatically based on the LAN configuration. 62 +*** Lighting hardware can be connected via the LAN port, however for proper functionality you must run the command: ##securegateway default## 62 62 ** The Control Subnet will automatically configure itself based on the LAN configuration, but it can optionally be configured manually: 63 63 *** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox: 64 64 **** Set routing to "Manual" with the start address and subnet size