Skip to Content

Changes for page DIN-CENCN-2 Setup

Last modified by Alexander Mott on 2024/02/09 01:01
From version 5.4
edited by Alexander Mott
on 2022/06/17 19:42
Change comment: Update document after refactoring.
To version 7.1
edited by Alexander Mott
on 2022/09/16 20:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,16 @@
1 -=== DIN-CENCN-2s in SHOWRUNNER™ ===
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
5 +(% class="row" %)
6 +(((
7 += DIN-CENCN-2s in SHOWRUNNER™ =
8 +
3 3  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.
4 4  
5 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 typically provides an 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.
6 6  
7 -=== IP Configuration ===
13 += IP Configuration =
8 8  
9 9  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]]).
10 10  
... ... @@ -21,7 +21,7 @@
21 21  ** Reboot the DIN-CENCN-2: ##reboot##
22 22  * Repeat for all DIN-CENCN-2s on the job
23 23  
24 -=== Moving Cresnet Devices ===
30 += Moving Cresnet Devices =
25 25  
26 26  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.
27 27  
... ... @@ -31,3 +31,4 @@
31 31  1. Cresnet IDs must be in the hexadecimal range 03 to 1B
32 32  1. Any children devices (such as NS occ sensors, photocells, GLPPA-KP keypads, etc.) must also be moved. If the parent Cresnet ID is changed then the children IDs must also be updated
33 33  1. If devices are moved from a DIN-CENCN-2 to be landed directly on a processor (or landed on a DIN-HUB on a processor), then the device host ID should be ##null## and the host branch should be ##0##
40 +)))