Changes for page Toolbox Basics
Last modified by Alexander Mott on 2024/03/19 21:00
From version 44.1
edited by Alexander Mott
on 2023/12/08 19:18
on 2023/12/08 19:18
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 6 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,7 +2,7 @@ 2 2 {{toc/}} 3 3 {{/box}} 4 4 5 -[[Crestron's Toolbox>>url:https://www.crestron.com/Products/Control-Hardware-Software/Software/Development-Software/SW-TB]] software is vital to being able to startup any Crestron lighting control job. The intent of this article is to familiarize a new lighting control tech with the very basics of the various Tools available within the Crestron Toolbox software ; detailed information can be access anytime from within Toolbox by pressing the F1 function key to open the Crestron Toolbox Help Menu.If a tool window is the active window, pressing F1 will open the Crestron Toolbox Help Menu to the specific page for that tool.5 +[[Crestron's Toolbox>>url:https://www.crestron.com/Products/Control-Hardware-Software/Software/Development-Software/SW-TB]] software is vital to being able to startup any Crestron lighting control job. The intent of this article is to familiarize a new lighting control tech with the very basics of the various Tools available within the Crestron Toolbox software. 6 6 7 7 = Initial Toolbox Configuration = 8 8 ... ... @@ -28,204 +28,36 @@ 28 28 29 29 = Connecting to Devices = 30 30 31 -In order to connect to any lighting devices, your computer must be physically connected to the lighting device or the lighting network. Typically, this is achieved via TCP(i.e. Ethernetor WiFi) or USB (usuallyaUSB-A to USB-B cable), though someolder devicesmay requireanRS-232serialconnection.31 +In order to connect to any lighting devices, your computer must be physically connected to the lighting device or the lighting network. Typically, this is achieved with either a USB-A to USB-B cable or an Ethernet cable, though some devices use different types of USB or have wireless adapters. 32 32 33 -Any Toolbox tool which requires connecting to a device has several buttons and fields at the lower left which relate to device connection: 33 +(% class="box infomessage" %) 34 +((( 35 +Note: It is not recommended to use Toolbox with multiple types of connections simultaneously as Toolbox may behave unexpectedly. If changing the connection method (e.g. switching to an Ethernet connection after using a USB connection), then you should unplug the first cable before plugging in the second one. 36 +))) 34 34 35 -[[image:Untitled.png]] 36 - 37 -These elements have various functions: 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 40 -1. Current Connected Device - If the currently connected device is in the Address Book, it's name in the Address Book will be displayed here. This drop down menu can also be used to connect to a different device within the current Address Book 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 -1*. [[image:1663625644870-585.png]] 43 -1. Quick Function Menu (keyboard shortcut: ALT+F) - menu containing a few useful functions 44 -1*. Firmware (keyboard shortcut: ALT+O) - menu for loading firmware 45 -1*. SIMPL Program (keyboard shortcut: ALT+P) - menu for loading a SIMPL or SIMPL# Program 46 -1*. Project (keyboard shortcut: ALT+T) - menu for loading an XPanel UI 47 -1. Current connection status ("Connecting", "Connected", "Disconnected", or "Unknown") 48 -1. Current connection type and address (e.g. "usb" or "ssh 10.44.5.71") 49 - 50 50 == USB Connection == 51 51 52 - Connectingto a device via USBisonlyrecommended duringinitial configuration of thedevice's IP settingsorfthereisan issuewith connecting via Ethernet/TCP. The data transfer rateoverUSB is verylowrelativetoEthernet,andso any activities that requiredata transfer (suchas updating firmware, updatingshowrunner™,or loadinga UI) willtake muchlongerthan necessary. Additionally,when connectingvia USB, only the device you areplugged in to will beconnectablein Toolbox, rather than being able to connect to anydeviceonthe lighting networkaswouldbepossiblewhen connected by Ethernet.40 +To connect via USB, simply plug the appropriate USB cable into your computer and the device and then open the desired tool. When connected via USB, only the device you are connected to will appear: 53 53 54 -To connect via USB: 55 55 56 -1. Determine the necessary USB cable 57 -1*. Most devices (DIN-AP3, DIN-AP4, DIN-CENCN-2, etc.) will require a USB-B connection, but some devices may require a Mini USB-B or Micro USB-B connection 58 -1. Plug the USB cable in to both the device and your computer 59 -1. Open Toolbox and then open the desired tool 60 -1. Connect to the device 61 -1*. If you are using the Default Address Book, there is already an entry for "Local-USB" 62 -1*. If you are not using an Address Book, then you should click the Pencil Icon to open the Manual Connection Menu: 63 -1*1. Change the connection type from "TCP" to "USB" 64 -1*1. Leave Model, Hostname, and Serial fields blank 65 -1*1. If the device has authentication enabled, expand the Advanced options and input the username and password 66 -1*1. Click "OK" 67 -1. The current connection status field should change from "Unknown" to "Connecting" 68 -1. After a brief period, the connection status field should change from "Connecting" to "Connected" 69 -1*. Some devices may take longer than others to connect 70 -1*. If the device has just recently powered up, it may take a few minutes to completely wake up before it can be connected to 71 -1*. If you have issues connecting, see [[Troubleshooting a Failed Connection>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HTroubleshootingaFailedConnection"]] below 72 - 73 73 == Ethernet Connection == 74 74 75 - Pluggingin to thelighting network and connecting to devicesvia Ethernet isthe most useful way toconnect to lighting control hardware. Whenyourlaptop is connected to thelightingnetwork, youare able to connect to anydevicethat is on the network, as well as connect to multipledevices simultaneously. Unlike with a USB connection, connecting to adevice via Ethernet doesnot require physicalproximity tothe device. Wireless connection to the lighting networkis possible if the lighting network has properly configured a wireless router on it.45 +== Device Discovery Tool and Address Book == 76 76 77 -To connect to a device via Ethernet, your laptop must first be connected to the lighting network. 78 - 79 -To connect to the lighting network: 80 - 81 -1. Identify an open where you are able to plug in to the lighting network 82 -1*. Many Crestron processor and HUB panels will have one or more CEN-SW-POE-5 or CEN-SWPOE-16 ethernet switches. Any open port on these Ethernet switches should be able to be used to connect a laptop to the network. 83 -1*. Laptops do not require power over Ethernet, so it is acceptable to use the "Uplink" port if necessary. 84 -1*. If the lighting network is on the building LAN, then you may need to reach out to the building's IT department for instructions on how to access the lighting network or VLAN. 85 -1. Use a Cat 5a or Cat 6 cable to connect your laptop to the lighting network at an open port 86 -1*. Most newer laptops will require some sort of adapter in order to connect to a Cat 5a/6 cable 87 -1. Configure your laptop's network settings to be compatible with the lighting network: 88 -11. Navigate to Control Panel>Network and Internet>Network Connections 89 -11. Locate the network adapter that is connected to the lighting network 90 -11. Right click the network adapter and click "Properties" 91 -11. In the Networking tab of the adapter Properties menu, select "Internet Protocol Version 4 (TCP/IPv4)" from the list 92 -11. Click the "Properties" button 93 -11*. If the lighting network uses static IP addresses: 94 -11*1. Click "Use the following IP address:" 95 -11*1. For the IP Address, give your laptop an address that is in the range of the lighting devices but that does not conflict with any addresses on the network 96 -11*1. For the Subnet mask, give your laptop the same subnet mask as the lighting devices 97 -11*1. The Default gateway can be left blank 98 -11*1. Once all settings have been configured, press "OK" to close the IP configuration dialog 99 -11*1*. E.g., if there is a lighting network with a processor at 10.0.0.10, a DIN-CENCN-2 at 10.0.0.11, and a TSW at 10.0.0.12 and all devices have a subnet mask of 255.255.255.0, then your laptop can have any address in the range 10.0.0.2 through 10.0.0.9 or 10.0.0.13 through 10.0.0.254, since these addresses are all in the subnetwork range and are not being used by other devices. 100 -11*1. Press "OK" again to close the Ethernet Properties dialog 101 -11*. If the lighting network has a DHCP server (such as a CP4N control subnet): 102 -11*1. Use the "Obtain an IP address automatically" option 103 -11*1. Press "OK" to close the IP Configuration dialog 104 -11*1. Press "OK" again to close the Ethernet Properties dialog 105 -11*1. Your laptop will automatically be assigned an IP address in the correct range by the DHCP server on the network. 106 -11*1*. You can verify this by opening the Windows Command Line tool and running "ipconfig" command to view your current adapter settings 107 -1. Open Toolbox and then open the desired tool 108 -1. Connect to the device: 109 -1*. If you have created an address book, then select the device from the drop down menu 110 -1*. If you have not created an address book, then you should click the Pencil Icon to open the Manual Connection Menu: 111 -1*1. Leave the connection type as "TCP" 112 -1*1. Type in the IP address of the device you wish to connect to 113 -1*1. Generally, the "Auto Detect" box should be left at "Auto Detect", though if you know what type of connection you need then you can manually change it 114 -1*1. Leave Model, Hostname, and Serial fields blank 115 -1*1. If the device has authentication enabled, expand the Advanced options and input the username and password 116 -1*1. Click "OK" 117 -1. The current connection status field should change from "Unknown" to "Connecting" 118 -1. After a brief period, the connection status field should change from "Connecting" to "Connected" 119 -1*. Some devices may take longer than others to connect 120 -1*. If the device has just recently powered up, it may take a few minutes to completely wake up before it can be connected to 121 -1*. If you have issues connecting, see [[Troubleshooting a Failed Connection>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HTroubleshootingaFailedConnection"]] below 122 - 123 -== Device Discovery Tool == 124 - 125 -Crestron's Device Discovery Tool is used to "discover" any Crestron devices which are connected to your laptop. The most useful feature of the Device Discovery Tool is the ability to export all discovered devices to either a "Device Summary" text file or an Address Book. Discovered devices are listed in a scrollable list on the left side of the menu, and double clicking a discovered device will bring up additional configuration options on the right side. Below is an overview of the Device Discovery Tool UI: 126 - 127 -[[image:device discovery tool numbered.png]] 128 - 129 -1. Device Model - gives the specific model of the device type 130 -1. Device Type - gives an idea of what function the device serves ("Control System", "AV", "Lighting", etc.) 131 -1. Connection and Firmware Information 132 -1*. Ethernet connected devices give their hostname, IP address, and firmware version 133 -1*. USB connected devices give their hostname, serial number, and firmware version 134 -1. Discovery Summary - gives a summary of how long it took to discover devices and how many devices were discovered at each connection type 135 -1. Discover Devices button - press this to restart the discovery process 136 -1. Export... button - use this button to export discovered devices to either a Device Summary or Address Book (covered in more detail below) 137 - 138 -=== Export to Device Summary === 139 - 140 -The Device Summary is an important documentation tool provided by Crestron. It is a .txt file containing a comma-separated-values of all networked devices, and is useful to capture which devices are online, what their current IP and hostname settings are, what version of firmware they are on, and their MAC address and serial number. 141 - 142 -To generate a Device Summary in Toolbox: 143 - 144 -1. Connect to the lighting network and open Device Discovery Tool in Toolbox 145 -1. The Device Discovery tool will automatically report how many Ethernet devices have been discovered 146 -1. Verify that the expected number of Ethernet devices have been discovered, including any TSWs, GLPACs, DIN-CENCN-2s, etc. 147 -1*. Note that only Crestron devices will appear in Device Discovery; non-Crestron devices (such as Pharos or Enttec DMX controllers) will not appear in Device Discovery Tool 148 -1*. If no devices are discovered, verify that your computer is connected to the network and your IP address is compatible with the network 149 -1*. If some devices are missing, there may be an issue with your DHCP server settings or the network wiring 150 -1. Click the "Export..." button below the list of discovered devices 151 -1*. If this button says "Address Book", then Toolbox needs to be updated 152 -1. Click the Write Device Summary button and save the Device Summary to your computer 153 -1*. Though saved as a text file, the Device Summary is actually a table of comma separated values 154 -1*. Renaming DeviceSummary.txt to DeviceSummary.csv will allow it to be opened and manipulated in common spreadsheet software such as Microsoft Excel or LibreOffice Calc 155 -1**. Note that this .csv will have whitespace, so it may be beneficial to "clean" it using Excel's "=TRIM()" function 156 - 157 -Below is an example of a Device Summary for a fully-configured Zūm Wired job: 158 - 159 -* DeviceSummary.txt: 160 -[[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/1655487020590-542.png?rev=1.1||alt="1655487020590-542.png"]] 161 -* DeviceSummary.csv: 162 -[[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"]] 163 - 164 -=== Export to Address Book === 165 - 166 -(% class="box warningmessage" %) 167 -((( 168 -This section is under construction: please check back at a later date for more information on using the Address Book 169 -))) 170 - 171 -Address Books are useful ways of managing multiple jobs that each have many devices. 172 - 173 -Note that when exporting devices to the Address Book, it is possible to add devices by either Hostname or by IP Address. On systems with a DHCP server, it is recommended to add devices by Hostname, but only after the final hostnames have been set for all devices. 174 - 175 -== Troubleshooting a Failed Connection == 176 - 177 -"Device refused to identify" 178 - 179 -* This message typically means that the device is not online or could not be connected to 180 -* This message may also occur when a device has blocked your username or IP address due to making too many incorrect login attempts 181 -** IP addresses are blocked for 24 hours by default, but you can attempt to circumvent this block by changing your IP address and trying again 182 -** Users are blocked for 30 minutes by default, and it is only possible to circumvent this if another user has already been created, otherwise you must wait for the block to expire before connecting again 183 -** The below commands are useful if you are able to connect to the processor through some other means (specific commands may vary depending on the device): 184 -*** ##listblockedip## and ##remblockedip## commands can be used to view/unblock an IP address 185 -*** ##listlockeduser## and ##remlockeduser## commands can be used to view/unblock specific users 186 -*** ##setloginattempts## and ##setlockouttime## commands can be used to modify how many login attempts are allowed before blocking an IP address and how long an address will be blocked 187 -*** ##setuserloginattempts## and ##setuserlockouttime## commands are used to modify how many login attempts are allowed before blocking a user and how long that user will be blocked 188 -*** ##setlogoffidletime## command can be used to modify how long you can be inactive before the processor automatically logs you out 189 - 190 -"Device not found in database" 191 - 192 -* This message typically means that the version of your device database is out of date and the device being connected to is not in it. Use Crestron's MasterInstaller tool to ensure that Toolbox and all installed Crestron components are up-to-date 193 - 194 194 = Basic Tool Usage = 195 195 196 -(% class="box warningmessage" %) 197 -((( 198 -This section is under construction: please check back at alater date for more information on using tools in Toolbox 199 -))) 200 - 201 201 == Text Console == 202 202 203 -== File Manager == 204 - 205 -== Script Manager == 206 - 207 207 == Network Device Tree View == 208 208 209 -= Miscellaneous =53 += Toolbox Quirks = 210 210 55 +Toolbox has some unique quirks that can sometimes cause issues. 56 + 211 211 == VPT COM Server == 212 212 213 - WheneverToolbox is open, Toolboxalso startsa separate process called theCrestronToolbox VPT COM server.This process appears inthesystem tray with the following icon whenactive:[[image:1663630447432-699.png]]59 +== Text Console Alternatives == 214 214 215 - Occasionally, somethinggoes wrongwith theVPT COM Server process which will preventToolbox from functioning correctly. To solve this problem, takethe following steps:61 +== File Management Alternatives == 216 216 217 -1. Close Crestron Toolbox 218 -1. Press CTRL+SHIFT+ESC to open Windows Task Manager 219 -1. Click the "More Details" button to see all processes 220 -1. Sort processes alphabetically and look for "VptCOMServer Module (32 bit)" under the "Background Processes" section 221 -1*. If you do not see the VptCOMServer process in Task Manager and the icon is not in the system tray, then it is not running 222 -1*. If the VptCOMServer process is still running after Toolbox has closed, select it in Task Manager and press End Process to stop it 223 -1. Once VptCOMServer is stopped, open Toolbox and see if your issues have been resolved 224 - 225 -== Alternatives to Specific Toolbox Tools == 226 - 227 -Sometimes it is necessary to connect to a Crestron device for troubleshooting using a computer that either does not or cannot have Toolbox installed on it. In these instances, third-party software can be used to replace some of the Tools in Toolbox in order to allow immediate troubleshooting of the lighting control system. 228 - 229 -The Text Console tool can be substituted with [[PuTTY>>https://www.putty.org/]], a free and open-source Telnet and SSH client/terminal emulator. [[SecureCRT>>https://www.vandyke.com/products/securecrt/]] is another option with some more capability than PuTTY, but note that it is a paid software which requires a license to use. The File Management tool can be substituted with [[WinSCP>>https://winscp.net/eng/index.php]], [[FileZilla>>https://filezilla-project.org/]], or [[CyberDuck>>https://cyberduck.io/]]. These are all free FTP/SFTP clients that do not require any license to use. 230 - 231 -Note that any Text Console or File Management alternatives are only suitable when connecting to Crestron devices over TCP/IP (Ethernet). When connecting to a Crestron device using these third-party programs, use port 22. Connecting to Crestron devices over USB is only possible using Toolbox because these devices do not use a standard communications protocol for USB communications. 63 +== Package Update Tool Alternatives ==
- 1663624626576-209.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.6 KB - Content
- 1663625594527-742.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,1 +1,0 @@ 1 -7.4 KB - Content
- 1663625644870-585.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,1 +1,0 @@ 1 -7.4 KB - Content
- 1663630447432-699.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,1 +1,0 @@ 1 -349 bytes - Content
- Untitled.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,1 +1,0 @@ 1 -2.7 KB - Content
- device discovery tool numbered.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,1 +1,0 @@ 1 -190.2 KB - Content