Changes for page Toolbox Basics
Last modified by Alexander Mott on 2024/03/19 21:00
From version 64.1
edited by Alexander Mott
on 2023/12/14 21:29
on 2023/12/14 21:29
Change comment:
Uploaded new attachment "1702589379487-339.png", version {1}
To version 77.1
edited by Alexander Mott
on 2023/12/18 16:49
on 2023/12/18 16:49
Change comment:
Uploaded new attachment "fm2.png", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 6 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -36,7 +36,7 @@ 36 36 37 37 These elements have various functions: 38 38 39 -1. Address Book Menu - Used to view and edit the current address book, or to change the active Address Book to a different Address Book 39 +1. Address Book Menu - Used to view and edit the current address book, or to change the active Address Book to a different Address Book. See [[Troubleshooting a Failed Connection>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HExporttoAddressBook"]] below for information about creating an Address Book 40 40 1. Known Device Dropdown - This drop down menu can also be used to connect to devices in the current Address Book. If the currently connected device is in the Address Book, it's name in the Address Book will be displayed here 41 41 1. Manual Connection Menu - This menu is used to manually connect to a device that is not in the current Address Book. It can be used regardless of the connection type or device being connected to: 42 42 1*. [[image:1663625644870-585.png]] ... ... @@ -169,7 +169,7 @@ 169 169 170 170 === Export to Address Book === 171 171 172 -Address Books provide a convenient way to easily connect to different devices without memorizing all the different IP addresses and credentials for devices on your network. When an Address Book has been created for a job, you are able to connect to specific devices using the dropdown menu on the lower left of the tool instead of manually inputting the IP address or hostname using the Pencil menu. Note that when exporting devices to the Address Book, it is possible to add devices by either Hostname or by IP Address, and if the device settings are modified then it may be necessary to update your Address Book or create a new one. 172 +Address Books [[image:1702589379487-339.png]] provide a convenient way to easily connect to different devices without memorizing all the different IP addresses and credentials for devices on your network. When an Address Book has been created for a job, you are able to connect to specific devices using the dropdown menu on the lower left of the tool instead of manually inputting the IP address or hostname using the Pencil menu. Note that when exporting devices to the Address Book, it is possible to add devices by either Hostname or by IP Address, and if the device settings are modified then it may be necessary to update your Address Book or create a new one. 173 173 174 174 To create an Address Book in Toolbox: 175 175 ... ... @@ -234,30 +234,68 @@ 234 234 * DeviceSummary.csv: 235 235 [[image:https://wiki.chiefintegrations.com/download/SHOWRUNNER%E2%84%A2%20Setup%20Guide/SHOWRUNNER%E2%84%A2%20Installation%20Guide/SHOWRUNNER%E2%84%A2%20Installation%20and%20Network%20Setup/ZUMNET-JBOX%20Setup/WebHome/1655487132138-904.png?rev=1.1||alt="1655487132138-904.png" height="289" width="752"]] 236 236 237 +== Text Console == 238 + 239 + 237 237 (% class="box warningmessage" %) 238 238 ((( 239 239 This section is under construction: please check back at a later date for more information 240 240 ))) 241 241 242 -== Text Console == 243 - 244 244 Text Console [[image:1663622220065-810.png]] is one of the most important tools in the Crestron Toolbox. Whenever the Chief Integrations' ShowRunnerCLC™ Startup Guide mentions "sending console commands," the Text Console is the tool that is required. 245 245 247 +- help commands 248 + 249 +- sr commands 250 + 251 +- link to other pages 252 + 246 246 == File Manager == 247 247 255 +(% class="box warningmessage" %) 256 +((( 257 +This section is under construction: please check back at a later date for more information 258 +))) 259 + 248 248 File Manager [[image:1663622340028-319.png]] is an essential tool for transferring files to and from the processor. While the ShowRunnerCLC™ license and configuration files can be loaded through the ShowRunnerHUB™ Web UI, it is still sometimes necessary to use the File Manager tool in certain circumstances (e.g., an Ethernet connection to the device cannot be established or for transferring files that aren't supported through the Web UI, such as custom ShowRunner™ extensions). 249 249 250 250 == Network Device Tree View == 251 251 252 -Network Device Tree View [[image:1663622313939-259.png]] is a useful tool for [[device addressing>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Addressing Devices from Toolbox.WebHome||anchor="HNetworkDeviceTreeView"]]. 264 +(% class="box warningmessage" %) 265 +((( 266 +This section is under construction: please check back at a later date for more information 267 +))) 253 253 269 +Network Device Tree View [[image:1663622313939-259.png]] is a useful tool for addressing devices and resolving certain issues with networked hardware. 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. 270 + 254 254 == Script Manager == 255 255 256 -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 theScript Manager tool[[image:1663622272369-417.png]]is whereLoadScriptscanbe opened andexecuted.273 +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. 257 257 275 +To use a Load Script with the Load Script Manager: 276 + 277 +* Open the Load Script Manager in Toolbox 278 +* Right-click anywhere in the Load Script Manager, select "Load Script...", and locate your Load Script .txt file 279 +* The window will populate with all of the different command sets defined in the Load Script 280 +** Ensure that you are connected to your devices by the method required based on the connection type listed in the "Connection" column 281 +** This example script is expecting to connect to devices over Ethernet using their hostname 282 +[[image:sm1.png||height="218" width="954"]] 283 +* Select the command sets you would like to execute by ctrl+clicking or shift+clicking them and then right-click and "Start Selected" to begin executing the commands 284 +** If no commands are currently running, the "Start All" option will also be available. Note that the number of concurrent command sections may be limited by the load script, so even if "Start All" is selected there may only be e.g. 10 command sets that actually start 285 +** If commands are currently running, you can cancel them using this right-click menu as well 286 +[[image:sm2.png]] 287 +* While commands are running, their current status and progress are displayed under the various columns displayed in the Script Manager 288 +[[image:sm3.png||height="189" width="835"]] 289 +* Once a command section has executed all commands, it will display the success or failure of the commands 290 +** In this example, all of the commands failed for different reasons: 291 +** ZUMNET-JBOX-16A-LV-F2D94E commands failed due to the firmware file specified by the script not being in the correct location 292 +** The commands which failed due to an "unknown error" failed because they weren't reachable at the specified connection address due to some quirks with this specific LAN configuration 293 +** The remaining command sections were manually cancelled before they could complete 294 +[[image:sm4.png||height="205" width="904"]] 295 + 258 258 == Package Update Tool == 259 259 260 -The Package Update Tool is a very convenient way of [[performing firmware updates>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Updating Firmware.WebHome||anchor="HPackageUpdateTool28.puf29"]] for networked devices and [[loading the ShowRunnerCLC™ program>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Processor Setup.WebHome||anchor="HProgramLoad"]] to processors. 298 +The Package Update Tool [[image:1663622297411-164.png]] is a very convenient way of [[performing firmware updates>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Updating Firmware.WebHome||anchor="HPackageUpdateTool28.puf29"]] for networked devices and [[loading the ShowRunnerCLC™ program>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Processor Setup.WebHome||anchor="HProgramLoad"]] to processors. 261 261 262 262 While the Package Update Tool can be opened from within Toolbox, Chief Integrations does not recommend it as doing so will lock Toolbox until the .puf is finished loading to the device. Instead, we recommend to closing Toolbox (or at least closing any Toolbox connections to devices that you intend to update) and double-clicking the .puf file to open the Package Update Tool in a separate window. This allows you to open multiple instances of the Package Update Tool and load .puf files to multiple devices at once. **Exercise caution when updating firmware for multiple devices simultaneously,** as some devices will reboot as part of the update process which may disrupt connection to downstream devices. 263 263
- fm1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,0 +1,1 @@ 1 +10.2 KB - Content
- fm2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.4 KB - Content
- sm1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,0 +1,1 @@ 1 +26.6 KB - Content
- sm2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,0 +1,1 @@ 1 +8.3 KB - Content
- sm3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,0 +1,1 @@ 1 +30.5 KB - Content
- sm4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,0 +1,1 @@ 1 +35.7 KB - Content