Wiki source code of *Starting Up Zūm Wired with SHOWRUNNER™
Version 6.1 by Alexander Mott on 2023/03/28 19:00
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | (% class="box errormessage" %) |
| 2 | ((( | ||
| 3 | n/a | ||
| 4 | ))) | ||
| |
2.1 | 5 | |
| |
1.1 | 6 | (% class="box warningmessage" %) |
| 7 | ((( | ||
| 8 | n/a | ||
| 9 | ))) | ||
| |
2.1 | 10 | |
| |
1.1 | 11 | {{box cssClass="floatinginfobox" title="**CONTENTS**"}} |
| 12 | {{toc/}} | ||
| 13 | {{/box}} | ||
| |
2.1 | 14 | |
| |
1.1 | 15 | (% class="row" %) |
| 16 | ((( | ||
| 17 | Lorem | ||
| 18 | See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details. | ||
| 19 | See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details. | ||
| |
2.1 | 20 | |
| 21 | = Start-Up Guide = | ||
| 22 | |||
| |
1.1 | 23 | Lorem |
| |
3.1 | 24 | |
| 25 | (% class="box warningmessage" %) | ||
| 26 | ((( | ||
| |
4.1 | 27 | cross reference/update to old [[zumnet startup>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUMNET-JBOX Setup.WebHome]]? |
| |
3.1 | 28 | |
| |
4.1 | 29 | basic steps: |
| |
5.1 | 30 | |
| |
3.1 | 31 | * configure your processor per chief's startup guide |
| 32 | * get all zumnet jbox online | ||
| 33 | ** use built in dhcp from processor control subnet | ||
| |
4.1 | 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**) | ||
| |
3.1 | 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 | * use chief tools tm tool to generate various zum wired load scripts | ||
| 38 | ** (need to determine exact process for this; will need to add IP-ID and new hostname to device summary somehow) | ||
| 39 | ** (will likely generate two versions of the loadscripts; one connecting by default hostname and one connecting by new hostname) | ||
| 40 | ** (intend to require SR license for zwired LS generator, if only to get the proc mac address) | ||
| 41 | * if firmware is old, run "zwms master/zum (def. hostname)" loadscript to make all ZUMNET JBOX primary and in app mode in order to enable discovery of devices on zumlink | ||
| 42 | ** devices will reboot | ||
| 43 | ** per crestron, 1.0006.00012 and newer ship in primary mode (**tbd if they will ship in app mode?**) | ||
| 44 | * connect to a few devices in device discovery tool to ensure that all zumlink devices were automatically readdressed and there are no conflicting cids | ||
| 45 | ** firmware 1.0001.00081 is new enough that this works correctly | ||
| 46 | * run "fw update (def. hostname)" loadscript to update the fw for all devices | ||
| 47 | ** will take up to several minutes per room, but will be able to do up to 10 rooms simultaneously | ||
| 48 | ** devices will reboot, possibly multiple times | ||
| 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) | ||
| |
6.1 | 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 | ||
| |
3.1 | 53 | * run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames |
| 54 | ** devices will reboot | ||
| 55 | ** devices will now have new hostnames, so any further loadscripts should use (new hostname) versions | ||
| |
6.1 | 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 | ||
| |
3.1 | 59 | * if using a processor without control subnet, run the "static ip config (new hostname)" script |
| 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 | ** (**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**) | ||
| |
5.1 | 62 | * once done, commission job essentially as normal showrunner job |
| 63 | ** (**sr commissioning guide is incomplete**) | ||
| |
6.1 | 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 | ||
| |
5.1 | 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. | ||
| |
6.1 | 72 | * once done, save and back up configuration file |
| |
1.1 | 73 | ))) |
| |
3.1 | 74 | ))) |