Wiki source code of Cresnet Wiring Overview

Last modified by Alexander Mott on 2024/01/05 23:42
Show last authors
1 (% class="row" %)
2 (((
3 (% class="col-xs-12 col-sm-8" %)
4 (((
5 (% class="box warningmessage" %)
6 (((
7 Chief Integrations recommends against using lever-nuts (e.g. "WAGOs") for Cresnet due to reduced network performance: instead it is recommended to use twist-on wire nuts wherever necessary and always follow correct procedures with regards to the drain wire
8 )))
9
10 Communications between Crestron Cresnet devices occurs on the Cresnet bus. Cresnet is Crestron's proprietary 4-wire communications network that provides both 24V DC power and low-voltage, bidirectional communication adhering to to RS-485 standards.
11
12 Each job with Cresnet devices will have at least one Cresnet bus network. Every Cresnet bus network has a single //host// or //primary// device and one or more //client// or //secondary// devices (older materials may refer to hosts as //masters// and clients as //slaves//). Every Cresnet device on a Cresnet bus must be assigned a unique, one-byte hexadecimal Cresnet address. The range of available addresses is determined by the bus host:
13
14 (% class="table-condensed" %)
15 |=(% style="width: 171px;" %)Host|=(% style="width: 96px;" %)Available Addresses|=Start|=End|=Notes
16 |(% style="width:171px" %)3-Series or
17 4-Series processors|(% style="width:96px" %)252|03|FE|Chief Integrations has experienced significant communications slowdowns on systems with more than 100 devices, and recommends using DIN-CENCN-2(-POE) or additional processors to break up larger Cresnet bus networks
18 |(% style="width:171px" %)(((
19 DIN-CENCN-2 or
20 DIN-CENCN-2-POE
21 )))|(% style="width:96px" %)(((
22 25 per Net (50 total)
23 )))|03|1B|
24 |(% style="width:171px" %)ZUMNET-JBOX-16A-LV
25 or ZUMNET-JBOX-DALI|(% style="width:96px" %)32|03|22|(((
26 ZUMNET-JBOX local controller counts as a device; only 31 additional Zūm Link or Cresnet devices may be connected
27
28 Zūm Link and Cresnet can be intermingled; more details are available [[here>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Troubleshooting.Zūm Wired Wiring Overview.WebHome]]
29 )))
30
31 Power considerations also play a role in determining the number of Cresnet devices which can be supported on a Cresnet bus, however we will not cover them here due to the wide array of variables which impact power calculations and determining whether there is sufficient power for a given device.
32
33 = Cabling =
34
35 Cresnet cabling provides the physical infrastructure for communication between Crestron Cresnet devices and consists of a 4-wire, 2-pair cable:
36
37 (% class="table-condensed" %)
38 |=(% style="width: 307px;" %)Pair|=(% style="width: 287px;" %)Color|=(% style="width: 380px;" %)Purpose
39 |(% colspan="1" rowspan="2" style="width:307px" %)18 AWG pair|(% style="width:287px" %)Red|(% style="width:380px" %)24 V DC Power
40 |(% style="width:287px" %)Black|(% style="width:380px" %)Common
41 |(% colspan="1" rowspan="2" style="width:307px" %)22 AWG shielded twisted pair|(% style="width:287px" %)White|(% style="width:380px" %)Data +
42 |(% style="width:287px" %)Blue|(% style="width:380px" %)Data -
43
44 (% class="wikigeneratedid" %)
45 Cable is available directly from Crestron with either plenum or non-plenum rated jackets.
46
47 (% class="wikigeneratedid" %)
48 While Cresnet can be run in either a daisy-chain or a star topology, Chief Integrations strongly recommends only running in a daisy-chain pattern in order to simplify troubleshooting and increase system reliability. Per Crestron, the maximum run length is 3000', but we strongly recommend keeping runs as short as possible in order to avoid issues with EMF interference and voltage drop.
49
50 (% class="wikigeneratedid" %)
51 = Terminations =
52
53 Cresnet runs originate at the host device in a Crestron Processor Panel (CPP) or Cresnet Hub (HUB) panel and connect to Cresnet devices that are located either in the field or in Lighting Control Panels (LCP). Most Cresnet terminations are done with Phoenix connectors which can be easily connected and disconnected to the device. Phoenix connectors have "flags" on the plug so that the connector can only be plugged into the device in one orientation. With the flags pointing up, the wire colors from left to right should be red-white-blue-black, corresponding to 24-Y-Z-G.
54
55 Devices that do not use Phoenix connectors will have red, white, blue, and black leads corresponding to the 24, Y, Z, and G wires of the Cresnet cable. All four of the individual Cresnet wires should be connected to the corresponding wire at the device using twist-on wire nuts except for at GLPPs, where only the white (Y), blue (Z), and black (G) wires should be connected. The red wire coming from the GLPP is reserved for providing power to non-system devices and should be capped off if there are no devices connected to the GLPP.
56
57 When stripping wires, do not strip more than is necessary and avoid leaving any exposed copper at the termination. While it is possible to fit two wires into each terminal of a Phoenix connector, it is a tight fit and many ECs find it easier to make a pigtail so that only one of each 24/Y/Z/G wire needs to be terminated at the connector. If making a pigtail for this purpose, be sure to use twist-on wire nuts (not lever-nuts) and avoid excessively long pigtails.
58
59 == Drain Wire ==
60
61 It is important to pay attention to how the Cresnet drain wire (the bare wire that is part of the white/blue shielded twisted pair) is terminated, as failure to do so may result in communications issues that incur significant labor costs to correct. The drain wire provides a path to ground for electrical noise that may be caused by stray electromagnetic frequencies (EMF) acting on the Cresnet cabling.
62
63 The drain wire should be landed with the black ground wire at the CPP or HUB panel where the Cresnet run originates, spliced through at every device in the field, and capped off at the last device in the run. Think of the drain wire as an antenna that is only connected at one end (the CPP or HUB panel) and isolated everywhere else (at devices in the field). See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
64
65 //[[Figure 2>>WebHome||anchor="HFigure2"]]// includes detail on splicing the drain wire through in the field.
66
67 = Crestron Wiring Notes =
68
69 Crestron includes some general Cresnet wiring guidelines in their submittals. Many of these suggestions are covered above, but we have included them here for reference:
70
71 [[image:1704485841724-854.png]]
72 )))
73
74
75 (% class="col-xs-12 col-sm-4" %)
76 (((
77 {{box title="**Contents**"}}
78 {{toc/}}
79 {{/box}}
80
81 (% class="wikigeneratedid" id="HFigure1" %)
82 (((
83 [[image:1704494079517-977.png]]
84 [[image:1704494784105-233.png]]
85 //Figure 1: Cresnet terminations with Phoenix connectors. Drain wire left bare in top photo for illustration purposes only; actual installations should have the drain wire insulated as shown in the bottom photo.
86 Left: drain is terminated with ground (at run origin only), Right: drain wire is capped off (at end-of-line device only), Center: drain wire is spliced through (at all other devices)//
87 )))
88
89 (% class="wikigeneratedid" id="HFigure2" %)
90 (((
91 [[image:1704494146222-851.png]]
92 //Figure 2: Demonstration of correctly splicing the Cresnet drain wire
93 1: drain wire is separated from other wires, 2: drain wire is twisted together, 3: drain wire is wrapped around jacketed portion of cable, 4: drain wire is insulated with PVC electrical tape//
94 )))
95
96
97 )))
98 )))

Navigation