Changes for page DIN-CENCN-2 Setup
Last modified by Alexander Mott on 2024/02/09 01:01
From version 8.1
edited by Alexander Mott
on 2022/09/17 00:25
on 2022/09/17 00:25
Change comment:
There is no comment for this version
To version 1.1
edited by Alexander Mott
on 2022/06/13 21:08
on 2022/06/13 21:08
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,1 @@ 1 -SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide. SHOWRUNNER™ Installation and Network Setup.WebHome1 +SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.WebHome - Content
-
... ... @@ -1,14 +1,10 @@ 1 -{{box title="**CONTENTS**"}} 2 -{{toc/}} 3 -{{/box}} 1 +=== DIN-CENCN-2s in SHOWRUNNER™ === 4 4 5 -= DIN-CENCN-2s in SHOWRUNNER™ = 6 - 7 7 DIN-CENCN-2s are Cresnet-to-Ethernet bridges which convert data over the Cresnet bus into high-speed Ethernet traffic. This helps avoid issues with bandwidth over the Cresnet bus for jobs which have a large number of Cresnet devices, as well as allowing for additional power supplies to provide power Cresnet devices. 8 8 9 -For SHOWRUNNER™ installations, the IP address of the DIN-CENCN-2 does not matter as long as it is in the same range as the processor and does not conflict with any other devices on the network. Instead, DIN-CENCN-2s are identified to the processor via their IP-ID. Note that which Cresnet devices are landed at each Net of each DIN-CENCN-2 matters, and if devices are moved between Nets or between DIN-CENCN-2s then the configuration will need to be updated (see below). Chief Integrations typicallyprovidesan SRTakeoff.xlsx spreadsheet with an IP Table tab that lists all the DIN-CENCN-2 IP-IDs in the program.If no takeoff is provided, then the processor's IP table 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.5 +For SHOWRUNNER™ installations, the IP address of the DIN-CENCN-2 does not matter as long as it is in the same range as the processor and does not conflict with any other devices on the network. Instead, DIN-CENCN-2s are identified to the processor via their IP-ID. Note that which Cresnet devices are landed at each Net of each DIN-CENCN-2 matters, and if devices are moved between Nets or between DIN-CENCN-2s then the configuration will need to be updated (see below). Chief Integrations will provide an SRTakeoff.xlsx spreadsheet with an IP Table tab that lists all the DIN-CENCN-2 IP-IDs in the program. 10 10 11 -= IP Configuration = 7 +=== IP Configuration === 12 12 13 13 Typically, each DIN-CENCN-2 will need to be initially configured via USB, unless their MAC addresses are already known and the lighting network has a DHCP server (either by running DHCP server software on your computer, or if the processor has a control subnet or is running the [[SHOWRUNNER™ DHCP Server>>doc:SHOWRUNNER™ User Guide & Wiki.Troubleshooting.DHCP Server.WebHome]]). 14 14 ... ... @@ -16,7 +16,7 @@ 16 16 17 17 * Open Text Console in Toolbox and connect to the DIN-CENCN-2 18 18 * Run the following commands to configure the DIN-CENCN-2's IP settings (example is for a **10.0.0.0(% style="color:darkgoldenrod" %)/24(%%)** subnet, with a CENCN-2 IP address of (% style="color:blue" %)**10.0.0.12**(%%), a CENCN-2 IP-ID of (% style="color:olive" %)**D1**(%%), a processor IP address of (% style="color:orange" %)**10.0.0.10**(%%), and a hostname of (% style="color:purple" %)**CENCN-L1**(%%)) 19 -** Disable DHCP: ##dhcp off## 15 +** Disable DHCP: ##dhcp 0 off## 20 20 ** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.12**(%%)## 21 21 ** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)## 22 22 ** Set default gateway: ##defr 0 **10.0.0.1**## ... ... @@ -25,7 +25,7 @@ 25 25 ** Reboot the DIN-CENCN-2: ##reboot## 26 26 * Repeat for all DIN-CENCN-2s on the job 27 27 28 -= Moving Cresnet Devices = 24 +=== Moving Cresnet Devices === 29 29 30 30 In SHOWRUNNER™, which Net each Cresnet cable is landed on is important. Each DIN-CENCN-2 is firmware limited to a maximum of 25 Cresnet devices per Net, and which CENCN-2/Net each device is on is tracked in the configuration file. If devices are moved between DIN-CENCN-2s or moved between Nets on the same DIN-CENCN-2, then the configuration file must be updated. Every device in the configuration has a ##"DeviceHostId"## (the host DIN-CENCN-2's IP-ID) and a ##"DeviceHostBranch"## (the Net of the DIN-CENCN-2) associated with it. 31 31