Changes for page **Starting Up Zūm Wired with SHOWRUNNER™
Last modified by Alexander Mott on 2023/12/13 19:15
From version 6.1
edited by Alexander Mott
on 2023/03/28 19:00
on 2023/03/28 19:00
Change comment:
There is no comment for this version
To version 3.1
edited by Alexander Mott
on 2023/03/28 15:08
on 2023/03/28 15:08
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Hidden
-
... ... @@ -1,1 +1,1 @@ 1 - true1 +false - Content
-
... ... @@ -24,15 +24,12 @@ 24 24 25 25 (% class="box warningmessage" %) 26 26 ((( 27 - cross reference/update to old [[zumnetstartup>>doc:SHOWRUNNER™Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUMNET-JBOX Setup.WebHome]]?27 +Basic steps: 28 28 29 -basic steps: 30 - 31 31 * configure your processor per chief's startup guide 32 32 * get all zumnet jbox online 33 33 ** use built in dhcp from processor control subnet 34 -** if using proc without control subnet, use showrunner [[dhcp>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]] 35 -** (**will probably need a lot of extra steps + alterations to how we make configs since static IPs require a lot more information as well as corresponding modifications to SrConfig.json**) 32 +** if using proc without control subnet, use showrunner [[dhcp>>https://wiki.chiefintegrations.com/SHOWRUNNER%E2%84%A2%20Setup%20Guide/Troubleshooting%20Guide/Advanced%20Tools/DHCP%20Server/]] 36 36 * use crestron toolbox device discovery to create a [[Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HExporttoDeviceSummary"]] 37 37 * use chief tools tm tool to generate various zum wired load scripts 38 38 ** (need to determine exact process for this; will need to add IP-ID and new hostname to device summary somehow) ... ... @@ -47,28 +47,11 @@ 47 47 ** will take up to several minutes per room, but will be able to do up to 10 rooms simultaneously 48 48 ** devices will reboot, possibly multiple times 49 49 ** check loadscript manager for any failures and re-run script for those devices if necessary (a rebooting zumnet box will temporarily disrupt online status for downstream zumnet jboxs and potentially interrupt the firmware update) 50 -* run device discovery again to confirm that all zumnet boxes were updated 51 -** zumnet boxes update last, so if a zumnet jbox is updated then this means that all of the zumlink devices that were online have also been updated 52 -* if app mode backup is desired, configure the boxes using the app now 53 53 * run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames 54 54 ** devices will reboot 55 55 ** devices will now have new hostnames, so any further loadscripts should use (new hostname) versions 56 -* run "cnet mode (def. hostname)" loadscript to put devices into CNET mode 57 -** if app mode backup is desired, also run "autoswitch enable (def. hostname)" loadscript 58 -** devices will reboot 59 59 * if using a processor without control subnet, run the "static ip config (new hostname)" script 60 60 ** this loadscript is necessary, as the showrunner DHCP server is only intended for commissioning. It must always be manually started after program restart and should not be used in production 61 61 ** (**will probably need a lot of extra steps + alterations to how we make configs since static IPs require a lot more information as well as corresponding modifications to SrConfig.json**) 62 -* once done, commission job essentially as normal showrunner job 63 -** (**sr commissioning guide is incomplete**) 64 -** connect to each zumnet jbox and address zumlink devices per the takeoff 65 -*** if devices are not online, then troubleshoot why and update firmware through device tree view once they are online 66 -** occ timeouts can be adjusted through UI; other settings (ie reach) should be adjusted through app 67 -** photocells etc are set up through UI 68 -** loads teseted and verified through UI; can be moved around between controllers as necessary 69 -*** loads don't need to be in the same room as the zumnet that controls them 70 -** keypads can use standard SR types or be fully customized 71 -** set up schedule, etc. 72 -* once done, save and back up configuration file 73 73 ))) 74 74 )))