Last modified by Alexander Mott on 2023/12/13 19:15
From version 5.1
edited by Alexander Mott
on 2023/03/28 17:50
Change comment: There is no comment for this version
To version 1.1
edited by Alexander Mott
on 2023/03/27 21:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Hidden
... ... @@ -1,1 +1,1 @@
1 -true
1 +false
Content
... ... @@ -2,64 +2,35 @@
2 2  (((
3 3  n/a
4 4  )))
5 -
6 6  (% class="box warningmessage" %)
7 7  (((
8 8  n/a
9 9  )))
10 -
11 11  {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
12 12  {{toc/}}
13 13  {{/box}}
14 -
15 15  (% class="row" %)
16 16  (((
17 17  Lorem
18 18  See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
19 19  See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details.
20 -
21 -= Start-Up Guide =
22 -
17 += The SHOWRUNNER™ Advantage =
23 23  Lorem
24 -
25 -(% class="box warningmessage" %)
26 -(((
27 -cross reference/update to old [[zumnet startup>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUMNET-JBOX Setup.WebHome]]?
28 -
29 -basic steps:
30 -
31 -* configure your processor per chief's startup guide
32 -* get all zumnet jbox online
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**)
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)
50 -* run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames
51 -** devices will reboot
52 -** devices will now have new hostnames, so any further loadscripts should use (new hostname) versions
53 -* if using a processor without control subnet, run the "static ip config (new hostname)" script
54 -** 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
55 -** (**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**)
56 -* once done, commission job essentially as normal showrunner job
57 -** (**sr commissioning guide is incomplete**)
58 -** occ timeouts can be adjusted through UI; other settings (ie reach) should be adjusted through app
59 -** photocells etc are set up through UI
60 -** loads teseted and verified through UI; can be moved around between controllers as necessary
61 -*** loads don't need to be in the same room as the zumnet that controls them
62 -** keypads can use standard SR types or be fully customized
63 -** set up schedule, etc.
19 +== Ease of Start-Up ==
20 +Lorem
21 +== Exclusive Features ==
22 +Lorem
23 +== Suitable for a Range of Applications ==
24 +Lorem
25 +== Support and Continued Development ==
26 +Lorem
27 += Best Practices for Zūm Wired with SHOWRUNNER™ =
28 +Though it is possible to design a Zūm Wired system to use the standard ZUM-HUB4 program and then import rooms from SHOWRUNNER™, it is not recommended as it adds the expense of a custom program without taking advantage of any of the added functionality that SHOWRUNNER™ has to offer.
29 +Instead, to take full advantage of everything that SHOWRUNNER™ has to offer, follow these best practices:
30 +* Design the system to use SHOWRUNNER™ as the main program
31 +* Set ZUMNET-JBOX-* devices in CNET mode after any App-specific configurations have been made
32 +Zūm
33 +SHOWRUNNER™
34 += Feature Comparison Table =
35 +Lorem
64 64  )))
65 -)))