Add More CrewCom Devices

When adding an RT, any advanced system configuration and customization of radio bands and hopping patterns must be done via the in CrewWare. These settings are part of the CrewCom Configuration File, but they are not adjustable in "Live" mode.

• Radio Band – All radios on a CrewCom system of the same frequency must be set to the same Radio Band. The default Radio Band is selected automatically by choosing the widest Radio Band setting for that frequency range. The Radio Band you use should follow the rules governing radio use in your country. You can change the system Radio Band selection from the Control Unit or CrewWare, choosing either Full, High, Low, or Mixed. The Mixed Band allows for the simultaneous use of both the Low and the High bands on the same CrewNet-based system. Using this mode allows Radio Packs to roam from Low Band to High Band and vice-versa. This is especially useful when coordinating hopping patterns and bands on more than one collocated and synced CrewCom or X-System/CrewCom system.

  Radio Band Options
  	900MHz Radio Bands	2.4GHz Radio Bands
  Full	902–928 Mhz	2400–2483.5 Mhz
  High	915–928 Mhz*	2445–2483.5 Mhz
  Low	902–915 Mhz	2400–2444 Mhz
  Mixed	902–915 Mhz / 915–928 Mhz	2400–2444 Mhz / 2445–2483.5 Mhz

  *The -900AN device models use only the High 900MHz radio band.

  Note: Changes to the Radio Band setting will require all Radio Packs to be re-paired. See Pair Radio Packs for more information about that process.

• Hopping Pattern – The RT’s Hopping Pattern is selected automatically by CrewCom when comparing all the existing RTs and assigning the next compatible number (within the same frequency range) available on CrewNet. You can either leave the Hopping Pattern that the system selects or edit the Hopping Pattern to your preference. If you select a Hopping Pattern that is not compatible with the Control Unit’s setting, a warning will display prompting you to confirm your preferred settings.

Every CCF must contain one primary CU. By default, the first Control Unit (CU) added to the CCF is automatically assigned as the primary CU. Any additional CUs will need to be added through CrewWare and CCF loaded to CUs or auto configured on the non-primary CU. Up to 3 non-primary CUs can be added to a system. See diagrams below steps and System Diagram Tab for more information on building system diagrams in CrewWare.

1. Restore Factory Defaults on the non-primary CU. See Restore Factory Defaults for more information.

   Caution: Loading or having a previously loaded CCF on any CU other than the primary CU will cause a configuration malfunction. You may also Delete System Configuration from the External USB Drive menu; see Delete Configuration File (CCF)

2. Once the non-primary CU has powered on, select Use as Non-primary CU.

   

   CU LCD Use as Non-primary CU

3. Connect the non-primary CU to a configured system. Make sure to connect the non-primary CU exactly as drawn in the system's configuration file.

   

   CU LCD Connect to Configured System

4. Once connected, the CU will automatically begin loading the CCF.

   

   CU LCD Loading CCF

5. The CU will show a blank home screen when the CCF loading is complete.

   

   CU LCD Home Screen

CrewNet supports up to 4 CUs. These additional CUs can be connected to the network via an available CrewNet port on another CU or a CrewCom Hub. No CU additions can be made via an RT's CrewNet or Loop ports. Multiple Control Units may only be connected together (i.e., daisy-chained) when they are connected directly from the primary CU. A single CU may be connected from a CrewCom Hub; this configuration is not considered to be daisy-chaining the CUs. See the images below for examples of acceptable and unacceptable multi-CU system diagrams. See System Diagram Tab for more information on building system diagrams in CrewWare.