Changes for page DIN-CENCN-2 Setup

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -2,6 +2,8 @@
2	2	{{toc/}}
3	3	{{/box}}
4	4
	5	+(% class="row" %)
	6	+(((
5	5	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.
6	6
7	7	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.
...	...	@@ -8,7 +8,7 @@
8	8
9	9	= IP Configuration =
10	10
11		-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™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]).
	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™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]).
12	12
13	13	Whether connected to the DIN-CENCN-2 via USB or Ethernet, the process to configure the static IP addresses is the same:
14	14
...	...	@@ -23,14 +23,6 @@
23	23	** Reboot the DIN-CENCN-2: ##reboot##
24	24	* Repeat for all DIN-CENCN-2s on the job
25	25
26		-(% class="wikigeneratedid" %)
27		-= Useful Commands =
28		-
29		-Below is a list of useful commands that can be used with DIN-CENCN-2 to help with troubleshooting Cresnet issues.
30		-
31		-* ##ppndiscover## - this command scans each of the DIN-CENCN-2's Nets and prints out a list of connected Cresnet devices identified by their connection ID and their TSID
32		-* ##cnettest## - this command scans each Net and prints a summary of the number of devices on each net as well as any Cresnet issues found (e.g., "Y short to Z" or "Power Fault")
33		-
34	34	= Moving Cresnet Devices =
35	35
36	36	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.
...	...	@@ -41,3 +41,4 @@
41	41	1. Cresnet IDs must be in the hexadecimal range 03 to 1B
42	42	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
43	43	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##
	38	+)))