Last modified by Alexander Mott on 2023/12/19 00:37
From version 17.10
edited by Alexander Mott
on 2023/12/19 00:07
Change comment: (Autosaved)
To version 18.1
edited by Alexander Mott
on 2023/12/19 00:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -*Addressing Devices from Toolbox
1 +Addressing Devices from Toolbox
Hidden
... ... @@ -1,1 +1,1 @@
1 -true
1 +false
Content
... ... @@ -2,13 +2,16 @@
2 2  {{toc/}}
3 3  {{/box}}
4 4  
5 -Introduction
5 +In ShowRunnerCLC™, all hardware on the job is defined in the configuration so that it can be registered with the processor when the program starts. Once the program has been installed and all hardware is reporting online, the program still will not work unless the hardware has been addressed according to the config.
6 6  
7 -* In ShowRunnerCLC™, the method by which a device is connected to the control processor is recorded in the configuration file and is relevant to whether or not the system will work. Relevant details include:
8 -** Specific host device (i.e. connected to the processor, connected to a specific DIN-CENCN-2, connected to a specific CEN-GWEXER, etc.)
9 -** Specific net of the host device (i.e. Net 1 or Net 2 of the DIN-CENCN-2)
10 -** Specific Connection ID or Network ID of the device
7 +The hardware definitions in the configuration (which are reflected in the SRTakeoff) are based on the approved submittals provided by the Crestron Agent. If the as-built conditions do not match the submittals, then it is generally preferable to modify the installation (i.e. move Cresnet cables around, reconnect devices, etc.) so that the as-built conditions match the design as given in the submittals. If this cannot be accomplished, then the configuration may be modified to match the as-built conditions, though some restrictions still apply (e.g. the limit of 25 devices per Net on a DIN-CENCN-2 is a hard limit built into the hardware and there is no software workaround).
11 11  
9 +Some the following is a non-exhaustive list of some of the details which require configuration changes to implement:
10 +
11 +* Specific host device (e.g. the specific DIN-CENCN-2, CEN-GWEXER, or processor that a device is connected to)
12 +* Specific net of the host device (e.g. whether a device is landed at Net 1 or Net 2 of a DIN-CENCN-2)
13 +* Specific Connection ID or Network ID of the device
14 +
12 12  = Network Device Tree View =
13 13  
14 14  (% class="box warningmessage" %)
... ... @@ -38,26 +38,46 @@
38 38  
39 39  = Text Console =
40 40  
41 -With the correct preparation, the Text Console can be a much faster way of addressing devices when compared to Network Device Tree View since you are able to rapidly address multiple devices instead of being restricted to addressing one device at a time.
44 +With the correct preparation, the Text Console can be a much faster way of addressing devices as compared to Network Device Tree View since it is possible to rapidly address multiple devices near-simultaneously instead of being restricted to addressing one device at a time. Some caveats for addressing through Text Console are:
42 42  
43 -Command for processor/no nets
46 +* You must know the TSID of the device to be addressed
47 +** This can be obtained through Network Device Tree View or by using the ##ppndiscover## command (this command returns all online devices listed with their model, Network ID, and TSID)
48 +** Devices which have a 1:1 correlation of serial number to TSID can also be converted using an Excel plugin or with the "Utility > Serial/TSID Conversion..." menu in Toolbox
49 +* Using Excel's CONCAT() function can be useful for automatically constructing the necessary console commands provided the Takeoff has been kept up-to-date with the TSID and required Network ID for each device
44 44  
45 -Command for devices with nets (DIN-CENCN-2/ZUMNET)
51 +The command required for addressing a device varies by the host device you are connected to:
46 46  
47 -Command for RFID
53 +* For Cresnet devices without Nets (such as processors and GLPACs): 
54 +** ##setcresnetidbyppn [CID] [TSID]##
55 +** [CID] is the network ID for the device as dictated in the Takeoff/configuration (hexadecimal value as low as 03 with a variable maximum value determined by host device)
56 +** [TSID] is the touch-settable ID of the device
57 +* For Cresnet/ZUMLINK devices with Nets (such as DIN-CENCN-2s and ZUMNET-JBOXs):
58 +** ##setcresnetidbyppn [NET] [CID] [TSID]##
59 +** [NET] is the net that the device is landed on (for DIN-CENCN-2s, this is either "1" or "2"; for ZUMNET-JBOXs this is always 1)
60 +** [CID] is the network ID for the device as dictated in the Takeoff/configuration (hexadecimal value as low as 03 with a variable maximum value determined by host device)
61 +** [TSID] is the touch-settable ID of the device
62 +* For RFID devices (such as CEN-GWEXERs): 
63 +** ##setrfidbytsid [CID] [TSID]##
64 +** [CID] is the network ID for the device as dictated in the Takeoff/configuration
65 +** [TSID] is the touch-settable ID of the device
48 48  
49 49  = Troubleshooting Tips and Tools =
50 50  
51 -When addressing devices, there are a number of issues that can occur. The causes of these issues can
69 +When addressing devices, there are a number of issues that can occur. The causes of these issues can vary wildly and troubleshooting them requires taking a methodical approach to narrowing potential causes of the issue. Below are some general tips for troubleshooting Cresnet, but is by no means exhaustive and learning to troubleshoot low-voltage data is a skill that can only really be developed through experience.
52 52  
53 53  == General Troubleshooting Tips ==
54 54  
55 -Verify correct connection point
73 +* Verify cables are landed at the correct ports
74 +** As mentioned above, the specific Net is relevant for the program to function correctly
75 +** There are limits to the amount of power available, and arbitrarily moving where cables are landed may inadvertently result in overdrawing power on some of the ports and lead to issues
76 +* Isolate cables (plug in one at a time) to verify that only the expected devices are online
77 +* When isolating cables, it also becomes possible to check for loops in the Cresnet cabling by verifying that each Cresnet cable has unique devices online (i.e., that there are no devices that report online from two different cables) and that there are no cables which have 24V DC across the red and black wires when they are unplugged
56 56  
57 -Isolate cables
79 +== DIN-CENCN-2 Specific Tips ==
58 58  
59 -Check for cabling loops
81 +There are some unique console commands and features available on DIN-CENCN-2s that provide additional information about potential Cresnet wiring issues:
60 60  
61 -== Network Analyzer Tool ==
83 +* The ##cnettest## console command will provide information such as power fault, shorts between two of the 24/Y/Z/G wires, communication issues at specific devices, among others
84 +* Navigating to the DIN-CENCN-2 IP address in a web browser will bring up the web UI (default credentials are "admin" for both username and password), where you can view the power draw broken down by Net
62 62  
63 -== DIN-CENCN-2 Specific Tips ==
86 +Combining these additional diagnostic tools with the basic troubleshooting technique of isolating cables can provide additional insight into potential wiring issues.