Last modified by Alexander Mott on 2023/12/19 00:37
From version 13.1
edited by Alexander Mott
on 2023/12/18 21:39
Change comment: There is no comment for this version
To version 17.2
edited by Alexander Mott
on 2023/12/18 23:32
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -4,6 +4,11 @@
4 4  
5 5  Introduction
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
11 +
7 7  = Network Device Tree View =
8 8  
9 9  (% class="box warningmessage" %)
... ... @@ -12,8 +12,27 @@
12 12  Check the currently installed version of Toolbox by navigating to Help > About Crestron Toolbox... and upgrade or downgrade your installation as necessary, or use an alternate method of addressing devices
13 13  )))
14 14  
20 +Network Device Tree View is the most user-friendly way of manually addressing devices for Crestron systems. Below is information specific to using the Network Device Tree View tool to address devices; see our [[Toolbox Basics page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HNetworkDeviceTreeView"]] page for more general information on using and configuring the tool.
21 +
22 +Below are some tips and things to keep in mind when using the Network Device Tree View tool to address devices for a ShowRunnerCLC™ deployment:
23 +
24 +* **It is generally recommended to right-click and ensure that "Show by Device Connection" is checked.** While "Show by Category" can be useful in some situations, it is not recommended when addressing devices as it gives no indication which Net a device is connected to and may lead to accidentally misaddressing devices. "Show by Device Connection" will group devices by their connection to the host device (e.g., Cresnet devices on a DIN-CENCN-2 will be sorted by the Net that they are connected to, Zūm Wireless devices will be sorted by the ZUM-NETBRIDGE they are connected to, etc.).
25 +** In the below screenshot, all devices have already been addressed so all devices appear with the yellow circle indicating "Status: OK"
26 +[[image:ndtv_by connection.png||height="508" width="401"]]
27 +** A new system where all devices are online but have not been re-addressed may look more like the following example, with a red exclamation point indicating duplicate Network IDs (all devices ship from the factory with the same Network ID, which inevitably leads to duplicate IDs on an uncommissioned system)
28 +[[image:ndtv_all loops.png||height="503" width="404"]]
29 +** Other types of status indicator may include a black circle for "Invalid Network ID" or "Invalid/duplicate TSID or Serial Number"
30 +* To address an individual device:
31 +** Select the device so that it is highlighted and press the F2 key (you may need to hold down the "Fn" button on your laptop)
32 +** Right-click on an individual device and select "Change Network ID..."
33 +* Type the new hexadecimal Network ID for the device into the "New Value" field and click "OK"
34 +[[image:ndtv_change nid.png]]
35 +* After a few moments, the device should update its ID and diks
36 +
15 15  = Text Console =
16 16  
39 +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.
40 +
17 17  Command for processor/no nets
18 18  
19 19  Command for devices with nets (DIN-CENCN-2/ZUMNET)
... ... @@ -22,8 +22,10 @@
22 22  
23 23  = Troubleshooting Tips and Tools =
24 24  
25 -== General Tips ==
49 +When addressing devices, there are a number of issues that can occur. The causes of these issues can
26 26  
51 +== General Troubleshooting Tips ==
52 +
27 27  Verify correct connection point
28 28  
29 29  Isolate cables
ndtv_all loops.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +61.4 KB
Content
ndtv_by connection.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +332.0 KB
Content
ndtv_change nid.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +19.9 KB
Content