Changes for page Toolbox Basics

Last modified by Alexander Mott on 2024/03/19 21:00
From version 91.8
edited by Alexander Mott
on 2023/12/18 23:02
Change comment: (Autosaved)
To version 93.1
edited by Alexander Mott
on 2024/01/05 18:52
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -253,7 +253,7 @@
253 253  ** These help lists can be further refined by typing out more of the specific command you want to learn about, e.g. ##sr devmgr ?## will show commands related to the ShowRunnerCLC™ device manager
254 254  * Use ##err sys## command to show the error log (up to the last 500 entries), and use the ##clear err## command to clear the log (useful if you are about to restart the program to diagnose errors and don't want to need to sort through which errors are new and which are from the previous startup)
255 255  * Many commands can be shortened by typing just enough letters to make the command unique, e.g. ##sr show loads## can be shortened to ##sr sh lo## and ##setlogoffidletime## can be shortened to ##setl##
256 -* See our [[frequently used commands page>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.Crestron Command Line.WebHome]] and our [[debug program logic page>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Troubleshooting.Debug Program Logic.WebHome]] for some more useful information on using Text Console with ShowRunnerCLC™
256 +* See our [[frequently used commands page>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.Crestron Command Line.WebHome]] and our [[debug program logic page>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Hardware and Installation.Debug Program Logic.WebHome]] for some more useful information on using Text Console with ShowRunnerCLC™
257 257  
258 258  == File Manager ==
259 259  
... ... @@ -281,15 +281,8 @@
281 281  
282 282  == Network Device Tree View ==
283 283  
284 -(% class="box warningmessage" %)
285 -(((
286 -This section is under construction: please check back at a later date for more information
287 -)))
284 +Network Device Tree View [[image:1663622313939-259.png]] is a useful tool for addressing devices and resolving certain issues with networked hardware. Below are just some general tips for using the tool; see our [[device addressing>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Addressing Devices from Toolbox.WebHome||anchor="HNetworkDeviceTreeView"]] page for specific instructions on how to use the Network Device Tree View for device addressing. The below are some general tips and recommended settings for Network Device Tree View:
288 288  
289 -Network Device Tree View [[image:1663622313939-259.png]] is a useful tool for addressing devices and resolving certain issues with networked hardware. Below are just some general tips for using the tool; see our [[device addressing>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Addressing Devices from Toolbox.WebHome||anchor="HNetworkDeviceTreeView"]] page for specific instructions on how to use the Network Device Tree View for device addressing.
290 -
291 -Initial configuration:
292 -
293 293  * When connecting to a device for the first time in Network Device Tree View, we recommend making certain changes to the type of information displayed by right-clicking and selecting the "Show Configuration Dialog" option:
294 294  ** Displaying the Serial Number and TSID is useful for easily identifying devices and determining whether specific devices are online or not
295 295  ** Displaying the Network ID is useful for easily identifying whether devices have been addressed or not
... ... @@ -298,11 +298,30 @@
298 298  [[image:ndtv_settings.png||height="317" width="565"]]
299 299  * In addition to the above settings, **it is generally recommended to right-click and ensure that "Show by Device Connection" is checked**
300 300  ** "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.)
301 -** "Show by Category" can be useful in some situations, particularly when looking at devices on a processor where all of the devices are necessarily on the same net, but it can be confusing since you are not able to tell at a glance how a device is connected (i.e. whether it is on Net 1 or Net 2 of a DIN-CENCN-2) and may result in accidentally misaddressing devices
294 +[[image:ndtv_by connection.png||height="436" width="344"]]
295 +** "Show by Category" can be useful in some situations, particularly when looking at devices on a processor where all of the devices are necessarily on the same net, but it can be confusing since you are not able to tell at a glance how a device is connected (i.e. whether it is on Net 1 or Net 2 of a DIN-CENCN-2) and may result in accidentally misaddressing devices; notice how in the below example there appear to be duplicate network IDs (e.g. a keypad and a GLXP-DIMFLV8 both at ID: 04) that aren't being flagged as duplicates because the devices are actually on different Nets, a detail that is only visible when "Show by Device Connection" is enabled as shown above.
296 +[[image:ndtv_by category.png||height="442" width="349"]]
302 302  * These configuration changes are saved per device type, so once they are made they will not need to be made again unless you are connecting to a new type of device for the first time (e.g. changes made while connected to a DIN-AP4 will apply to all DIN-AP4s, but will not apply to any DIN-CENCN-2s you may connect to later)
298 +* If Network Device Tree View has been configured as recommended above, then the interface will look similar to the below for a fully-addressed system with no issues:
299 +** Since all of the devices have been addressed and there are no issues, the Network Device Tree View shows a yellow circle next to each device indicating an "OK" status
300 +[[image:ndtv_by connection.png||height="436" width="344"]]
301 +** 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
302 +[[image:ndtv_all loops.png||height="423" width="339"]]
303 +** Other types of status indicator may include a black circle for "Invalid Network ID" or "Invalid/duplicate TSID or Serial Number"
304 +* Right-clicking on an individual device will give many options to resolve common issues, as well as allow for identifying a specific device:
305 +** "Refresh All" use to refresh the list of actively connected devices, necessary e.g. if a Cresnet cable has been connected/disconnected from the device
306 +*** F5 is the keyboard shortcut for this function, though in both cases it may be more reliable to completely close and reopen Network Device Tree View to ensure all devices are refreshed
307 +** "Change Network ID..." use to change the Network ID (CID) of a specific device (see our [[device addressing page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Addressing Devices from Toolbox.WebHome||anchor="HNetworkDeviceTreeView"]] for more information)
308 +*** F2 is the keyboard shortcut for this function
309 +** "Identify This Device..." will put a specific device into "Identify" mode, the specific behavior for which depends on the individual device:
310 +*** Note that entering identify mode may stop the ShowRunnerCLC™ program and restart it when exiting identify mode: **to avoid losing progress and placing strain on the processor**, it is recommended to either identify and address all hardware prior to loading the ShowRunnerCLC™ program, or temporarily suspend the program with the console command ##stopprog -p:01## and then resume the program once done identifying all devices with the command ##progreset##
311 +*** Some devices will flash an LED (Cresnet keypads, GLS-SIMs, et al.)
312 +*** Some devices will flash an LED and make a noise (Cresnet occupancy sensors, most room controllers, et al.)
313 +*** Load controllers will typically flash all connected loads
314 +** "Change Serial Number..." is used to change the device's Serial Number (and thus its TSID); this is rarely required and is only necessary in cases where a device reports an invalid or duplicate SN/TSID, or where the reported SN does not match the SN physically printed on the device
315 +** "Open Text Console..." will open a Text Console window directly to the specific selected Cresnet/RFID device (//not// to the host device you are connected to in Network Device Tree View); only recommended for advanced users
316 +[[image:ndtv_rc on device.png]]
303 303  
304 -If the
305 -
306 306  == Script Manager ==
307 307  
308 308  The Script Manager [[image:1663622272369-417.png]] is where Load Scripts can be opened and specific sets of commands executed. Load Scripts are .txt files that allow you to automate certain tasks by connecting to a device and executing a predetermined sequence of commands, and are a powerful tool to save time on-site when you need to run the same or similar set of commands on many devices.