Canopy® Software Release 9.
Notices See important regulatory and legal notices in Section 10 on Page 58. Trademarks, Product Names, and Service Names MOTOROLA, the stylized M Logo, Canopy, and all other trademarks indicated as such herein are registered trademarks of Motorola, Inc. ® Reg. US Pat & Tm. Office. All other product or service names are the property of their respective owners. © 2009 Motorola, Inc. All rights reserved http://motorola.wirelessbroadbandsupport.
Release 9.5 Release Notes Table of Contents 1 2 Introduction................................................................................................................. 6 1.1 Applicability ......................................................................................................... 6 1.2 Release Highlights .............................................................................................. 7 1.3 Abbreviations ...............................................................
Release 9.5 Release Notes 4 Known Open Issues ................................................................................................. 38 5 Notes and Reference ................................................................................................ 39 5.1 Notes ................................................................................................................. 39 5.2 Operation Based on Region Code and Frequency Band .................................. 43 6 Canopy MIB .
Release 9.5 Release Notes Table 10: Release 9.5 operation based on Region Code and frequency band ............ 43 Table 11: Radios upgradeable to Release 9.5 .............................................................. 46 Table 12: 5.4- and 5.2-GHz interfering frequencies ...................................................... 52 Table 13: US FCC IDs and Industry Canada Certification Numbers and covered configurations .......................................................................................
Release 9.5 Release Notes 1 Introduction 1.1 APPLICABILITY Release 9.5 is a general release applicable to Radio Type PMP (Point-to-MultiPoint) PTP (Point-To-Point) FSK * PMP 100 Series PTP 100 Series 4.9-GHz OFDM PMP 49400 PTP 49200 5.4-GHz OFDM PMP 54400 PTP 54200 * FSK frequencies: 900 MHz, 2.4, 5.1, 5.2, 5.4, 5.7, 5.9, 6.050 MHz Within the United States and its territories the following radios require this release: PMP 100 Series FSK Access Points (APs) in the 5.2-, 5.4-, and 5.
Release 9.5 1.2 Release Notes RELEASE HIGHLIGHTS Highlights of Canopy Release 9.5 include Table 1: Release 9.5 highlights Highlight Changes for US Region Code and TDWR radar band to support compliance with US FCC guidance Brief Description A 5.2-, 5.4-, or 5.7-GHz P10 or higher AP or BH with a Region Code set to United States and upgraded to Release 9.5 will no longer be configurable to another Region Code by installers or end users. 5.
Release 9.5 1.
Release 9.5 1.4 Release Notes NAMES Table 2 maps product names to previous names, older names, and example model numbers.
Release 9.5 1.5 Release Notes IDENTIFYING HARDWARE SERIES (P7, P8, P9, P10, P11) The following methods can be used to identify the hardware series of a module: For modules that are running Release 8 or Release 9, look on the Home => General Status tab, under Board Type as shown in Figure 1. Figure 1: Board Type on modules running Release 8. For modules that are running Release 7.3.6, view the Configuration web page.
Release 9.5 1.7 Release Notes FEEDBACK ON DOCUMENTATION Is this document accurate, complete, and clear? How can it be improved? Please send your feedback on Canopy documentation to technical-documentation@canopywireless.com. 1.8 TECHNICAL SUPPORT Tip! Do not clear the Event Log after you encounter issues. It may be useful to Technical Support, if you need to escalate the issue. Here is the escalation path for resolution of a problem: 1.
Release 9.5 Release Notes 2 Features and Enhancements The following sections list features and enhancements for Release 9.5. 2.1 RELEASE 9.5 ENHANCEMENTS Release 9.5 adds the enhancements listed in Table 3. Table 3: Release 9.5 enhancements Enhancement Type / Section Enhancement Summary Regulatory 2.3 Changes for 5-GHz Radios set to United States Region Code A 5.2-, 5.4-, or 5.7-GHz P10 or higher AP or BH with a Region Code set to United States and upgraded to Release 9.
Release 9.5 Release Notes Enhancement Type / Section Enhancement Summary Network Redundancy 2.11 Color Code Priority on SM SMs have a total of ten configurable color codes which can be tagged as Primary, Secondary or Tertiary. In earlier releases, there was one primary color code. Usability 2.12 GPS Coordinates Stored in AP, SM and BH AP, SM or BH contain input fields for Latitude, Longitude and Height in the Configuration => General web page. Usability 2.
Release 9.5 Release Notes Hardware series Product P11 or P10 P9 PMP 54400 6800 — PTP 54200 4800 — PMP 49400 6300 — PMP 49400 with VLAN 5300 — Note: No significant difference between DES and AES 1: Links with a P9 module on one end and a P10 or P11 module on the other perform between 3200 and 3500 pps Section 9, Performance Benchmarking Process, on page 55 describes the benchmarking process used to measure packets per second and discusses the meaning and limitations of the benchmark. 2.
Release 9.5 2.3.1 Release Notes US Region Code for US 5.x‐GHz APs A 5.2-, 5.4-, or 5.7-GHz P10 or higher AP or BH with a Region Code set to United States and upgraded to Release 9.5 will continue to be set to the United States Region Code and will not be configurable to another Region Code by installers or end users. As discussed in section 2.
Release 9.5 2.3.2 Release Notes US 5.4‐GHz Radios and the TDWR Band To prevent co-channel operation with Terminal Doppler Weather Radar (TDWR) systems, P10 and P11 5.4-GHz APs and BHMs configured with a Region Code of United States running Release 9.5 will not use or allow configuration of the center channel frequencies shown in table 5.
Release 9.5 2.4 Release Notes AP ‐ DHCP RELAY/OPTION 82 The AP can now act as a DHCP relay for SMs and CPEs underneath it. The AP will make use of the DHCP Option 82 (DHCP Relay Agent Information) from RFC 3046 when performing relay functions. In this RFC, there are two sub options defined for DHCP Relay Agents to use to pass useful information along to the DHCP server to identify from where the DHCP request is coming.
Release 9.5 Release Notes Figure 6: Enable Large VC data Q via Configuration => Radio on SM, BHM and BHS. If an operator is experiencing packet loss in the uplink due to bursting IP traffic and the overall traffic rate is less than or equal to the uplink capacity of the radio system, then the large VC data Q should be enabled. For example, a PTP 20 Mbps BH has a video camera connected to the BH Slave (BHS) uplink.
Release 9.5 2.6 Release Notes SNMP UPDATES FOR SM REGISTRATION FAILURES A new register trap was added for when an SM receives a registration grant failure. The OID is .1.3.6.1.4.1.161.19.3.1.5.1.3 (whispRegFailure). This trap is contained in the existing wispApsRegEvent group in the AP MIBs. As with the existing events in this group, this event can be enabled and disabled by the existing OID .1.3.6.1.4.1.161.19.3.1.1.28 (regTrap).
Release 9.5 Release Notes In addition to the above changes, a new status was added. This is .1.3.6.1.4.1.161.19.3.1.7.32 (regFailureCount), which is the number of Registration Failures that have occurred at the AP/BHM. This is a type of Counter32. This statistic was also added to Failure SM List Page. 2.7 AP/SM PRE‐SHARED KEY AUTHENTICATION Previously, in a PMP system, the only option for authenticating SMs was through the use of the BAM Authentication function of Prizm. Now, in Release 9.
Release 9.5 Release Notes Figure 8: AP Pre-shared Key option on AP’s Configuration => Security tab Here you can see the new option in the drop-down box and the two new configuration options. When AP PreShared Key is selected, all five Authentication Server boxes will be grayed out. Similarly, when Authentication Server is selected, then Authentication Key and Select Key options all be grayed out. When Disabled is selected, all of the sub options will be grayed out.
Release 9.5 2.8 Release Notes ABILITY TO HIDE SITE INFO FROM GUEST USERS ON SM Operators can enable or disable site information from appearing when a user is in GUEST account mode. Configuration can be done via the GUI or via an OID. Figure 9: Configure Hide Site Information via Configuration => SMNP on SM. The following table shows the Site Information Viewable OID’s. Note: Prior to release 9.5 the site information appeared in GUEST account mode. 2.
Release 9.5 Release Notes Figure 10: Configure up to 5 Prizm Authentication Servers via Configuration =>Security on AP. This table shows the two additional authentication server OIDs. 2.10 PPPOE CHAP AUTHENTICATION SUPPORT The PPPoE authentication type selection has been changed from PAP only to CHAP/PAP on the Configuration => PPPoE web page on the SM.
Release 9.5 2.11 Release Notes COLOR CODE PRIORITY ON SM SMs may now be configured with up to 10 color codes. These color codes can be tagged as “Primary”, Secondary”, or “Tertiary”. When the SM is scanning for APs, it will first attempt to register to an AP that matches one of the SM’s Primary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SM’s Secondary color codes.
Release 9.5 Release Notes Color Codes 2 through 10 are placed in the SM MIB. The current first color code exists in the box MIB as it is used for both the AP and SM. The SM MIB updates are as follows: In addition, two timers can be configured on the AP by the operator. The timers’ configurations are sent down to the SM during registration negotiations. These timers are only used when the SM is registered to an AP with a non-Primary Color Code.
Release 9.5 Release Notes Figure 12: Configure SM Color Code Rescan and Wait Period via Configuration => Radio on AP.
Release 9.5 2.12 Release Notes GPS COORDINATES STORED IN AP, SM AND BH GPS coordinates can be manually entered into each AP, SM and BH. Figure 13: Enter GPS Coordinates via Configuration => General on AP, SM and BH. This table shows the three GPS coordinate OIDs. 2.13 CONFIGURATION TO HIDE IDLE SUBSCRIBERS ON AP Idle subscribers can be quickly hidden (without a reboot) from the Home => Session Status list on the AP by selecting Enabled.
Release 9.5 2.14 Release Notes QUICK LOGIN ON AP, SM AND BH The login “Username” and “Password” fields are now located on the lower left hand side of the Home => General Status page. Figure 15: Quick login via Home => General Status on AP, SM and BH. 2.15 OBSOLETE UNUSED OIDS This table shows the six OIDs that are no longer used and have been removed from the MIBs.
Release 9.5 Release Notes 2.16 ONLY ALLOWING AP TO REGISTER SMS THAT ARE ON AT LEAST RELEASE 9.5 For feature compatibility, an operator can enforce that all SMs in a sector are running 9.5 software or above. If an SM that is running pre-9.5 software tries to register to an AP with this option enabled, it will be rejected and an SM registration failure trap will be sent indicating why the SM was not allowed to register. To allow only SMs that are running release 9.
Release 9.5 2.17 Release Notes CLEAR STATISTICS ON AP, SM AND BH Prior to Release 9.5, the only way to clear statistics on the AP, SM or BH was to reboot the radio. In Release 9.5, the AP, SM and BH Statistics pages can be cleared one tab at a time without requiring a reboot of the radio. Upon clicking the “Clear Statistics” button the statistics zero out and begin to increment. Figure 17: Clear Statistics button via Statistics on AP, SM and BH.
Release 9.5 2.18 Release Notes POP‐UP TOOL TIPS The following list of web pages contains tool tip pop-ups to explain specific radio features.
Release 9.5 2.20 Release Notes SUPPORT FOR P11 HARDWARE 5.2-GHz and 5.4-GHz P11 modules require, at a minimum, Release 9.4.x. These modules should be upgraded to Release 9.5 before being deployed. 5.7-GHz P11 modules require, at a minimum, Release 9.3. These modules should be upgraded to Release 9.5 before being deployed. P11 modules exhibit performance similar to P10, as shown in Table 4 on page 13. 2.20.1 Mixing Hardware Vintages P11 APs and SMs can be mixed with other hardware vintages in a sector.
Release 9.5 Release Notes 3 Resolved Issues Issues resolved in Release 9.5 are listed in Table 6. Table 6: Issues resolved in Release 9.5 Ref # Description Explanation 11590 PMP 400 and PTP 200 OFDM potential radio communication failure Due to an issue in previous releases, PMP 400 and PTP 200 OFDM modules have a potential to drop the radio communication link (appear to fail) as they age. NTP Event Log Beginning with Release 9.
Release 9.5 Release Notes Ref # Description Explanation 10300 Added OIDs for High Priority Channel Stats OIDs were added to the whispLinkTable for the High Priority Channel statistics. If there is no high priority channel enabled, the entries will all return values of 0. OIDs added for P9, P10 and P11 hardware: OID to check if high priority channel is enabled.
Release 9.5 Release Notes Ref # Description Explanation 10595 & 10596 Added OIDs for Scheduler and Bridge Control Block Stats OIDs were added to match the already-available-via-GUI Scheduler stats. Also, OIDs have been added for the first three sections of the Bridge Control Block page.
Release 9.5 Release Notes Ref # Description Explanation 10053 Translation Bridge Table Access via SNMP When Translation Bridge is enabled, every SM maintains a translation bridge table. The entries of this table are now also accessible via SNMP (Read only access). The entries in this table are dynamically added/deleted based upon the devices are under the SM. The max number of entries for this table is 128. Translation Bridge Table OIDs 10094 DNS Proxy/Relay for NAT SMs In 9.
Release 9.5 Release Notes Ref # Description Explanation 10213, 10234 & 10237 Improvements to SNMP Mibs SNMP Mibs now import the “Unsigned32” type from the SNMP v2 standard; therefore, the following OIDs have been changed from “INTEGER” to… …Unsigned32 OIDs … Gauge32 OIDs The below OIDs were mislabeled as INTEGER instead of a counter. They were changed to the appropriate “Counter32” type.
Release 9.5 Release Notes 4 Known Open Issues Known open issues for Release 9.5 are listed in Table 7. Table 7: Known open issues Product Family Description Discussion and Recommendations All SM - DNS below a NATed SM (R9.5) Microsoft Vista and presumably Windows 7 will not route a 169.254/16 subnet used as the default Canopy subnet since Microsoft uses 169.254/16 subnet to talk between local machines. This is not an issue if: - the PC is connected directly to the NATed SM.
Release 9.5 Release Notes 5 Notes and Reference 5.1 NOTES New notes for Release 9.5 are listed in Table 8 and previous notes are listed in Table 9. Table 8: Notes Ref # Description Discussion and Recommendations 11383 SNMP Set of Region Code fails in some cases Consistent with the changes described above for Release 9.5, attempting an SNMP Set of the Region Code of a US 5.2-, 5.4-, or 5.7-GHz AP or BHM that was upgraded to Release 9.5 will return a “failed” response.
Release 9.5 Release Notes Table 9: Previous notes ID Description Discussion and Recommendations - Changes to boxTemperature OIDs Starting with Release 9.4 the boxTemperature (1.3.6.1.4.1.161.19.3.3.1.5) OID (which returned an octet string value) is no longer valid. Two new OIDS which return integer values are added: boxTemperatureC Object ID: 1.3.6.1.4.1.161.19.3.3.1.35 Syntax: INTEGER Access: read-only Status: current Radio temperature in Celsius. boxTemperatureF Object ID: 1.3.6.1.4.1.161.19.3.3.1.
Release 9.5 Release Notes ID Description Discussion and Recommendations 8241 Avoid power cycling modules during upgrading Power cycling a module while it is upgrading can cause anomalous events, such as rebooting every time you try to access the GUI. Managing module accounts and passwords The best security practice is to be aware the unit starts with root and admin accounts, to plan your approach to accounts, and set passwords for all accounts.
Release 9.5 Release Notes ID Description Discussion and Recommendations 4789 Lowest settable Transmitter Output Power varies The low end of the Transmitter Output Power can vary from radio to radio due to manufacturing tolerances. If you set this parameter to lower than the range capable on a radio, the value is automatically reset to the lowest capable. NOTE: The high end of the range of settable Transmitter Output Power does not vary from radio to radio.
Release 9.5 5.2 Release Notes OPERATION BASED ON REGION CODE AND FREQUENCY BAND For reference, Table 10 shows operation based on Region Code, by frequency band and module type. Changes for Release 9.5 are highlighted in Bold. Table 10: Release 9.5 operation based on Region Code and frequency band Region Code1 United States Canada 900 MHz 2.4 GHz 4.9 GHz 5.1 GHz AP/SM AP/SM /BH AP/SM /BH AP/SM/ BH No effect No effect No effect No effect No effect No effect 5.
Release 9.5 Region Code1 Release Notes 900 MHz 2.4 GHz 4.9 GHz 5.1 GHz AP/SM AP/SM /BH AP/SM /BH AP/SM/ BH Display Community options No effect No effect NA NA No effect No effect No effect No effect No effect No effect No effect No effect No effect Russia NA NA No effect Other No effect No effect No effect 1. 2. 3. 5.2 GHz AP/ BHM 5.4 GHz SM/ BHS AP/ BHM 5.
Release 9.5 Release Notes 6 Canopy MIB The Canopy Enterprise MIB (Management Information Base), consisting of 5 MIB definition files, supports SNMP access to Canopy modules. The MIB files are available for download from the Canopy tab of http://motorola.wirelessbroadbandsupport.com/software. Detailed information on the Canopy MIBs is available at http://motorola.wirelessbroadbandsupport.com/support/online_tools.
Release 9.5 Release Notes 7 Upgrading to Release 9.5 7.1 BEFORE YOU UPGRADE 7.1.1 Applicability Table 11 shows the product series, hardware series, and radio types that are upgradeable to Release 9.5. Yes in larger bold font identifies radios that, if they are in the US, should be upgraded to Release 9.5 to ensure that systems are compliant with FCC guidance. Table 11: Radios upgradeable to Release 9.
Release 9.5 Release Notes Release 9.5 is not applicable to 7.1.2 PMP 500 Series modules (Canopy 3.5 GHz OFDM APs and SMs) PTP 300 Series Bridges PTP 400 Series Bridges (formerly 30-/60-Mbps backhaul modules) PTP 500 Series Bridges PTP 600 Series Bridges (formerly 150-/300-Mbps backhaul modules) CMMs (Cluster Management Modules) Powerline MU Gateway and Modem Supported Upgrade Path Upgrade paths for operating sectors are shown in Figure 21.
Release 9.5 Release Notes CNUT CNUT (Canopy Network Updater Tool) is a free tool for upgrading Canopy modules. For information and details on installing CNUT on a PC or Linux machine, download the CNUT software and help file from the Canopy tab of http://motorola.wirelessbroadbandsupport.com/software. If you need to upgrade from a previous CNUT release, ensure you back up your network file before upgrading CNUT. CNUT 3.
Release 9.5 Release Notes Network Updater Tool Release 3.20 for Windows or Network Updater Tool Release 3.20 for Linux Network Updater Tool Release 3.20 Release Notes 2. Install CNUT Release 3.20 on Windows or Linux using the CNUT release notes. 3. If you do not have a previously stored network archive file within CNUT, add your Canopy infrastructure elements (APs, BHs, and CMMs) to the network root and Move and Modify the elements until you have captured your network.
Release 9.5 5. 7.4 Release Notes In the email sent to you, click on the desired link or links. RESULT: The appropriate.pkg3 package or packages will download to your computer. PERFORMING THE UPGRADE VIA CNUT OR PRIZM Upgrade using the following steps. For additional details on using CNUT, see the CNUT help file or click on the Help menu in the CNUT application. For additional details on using Prizm, see the Prizm user guide.
Release 9.5 Release Notes 13. Initiate the Update operation. 14. Monitor the update progress through the Network Tree. 15. Allow the update to run, leaving CNUT/Prizm active, until all involved SMs are upgraded. An AP enabled for Auto-update a. updates all registered or registering P7/8/9 SMs that require an upgrade. b. waits for 20 minutes of no upgrade or new P7/8/9 registration activity. c. updates all registered or registering P10 SMs that require an upgrade. d.
Release 9.5 Release Notes 8 Collocation 8.1 COLLOCATING 5.2‐GHz AND 5.4‐GHz MODULES 5.4-GHz radios that are set to a center channel frequency of 5595 MHz or lower produce a signal that is 280 MHz below their center channel. This signal can interfere with 5.2-GHz channels as shown In Table 12. Because of this, care needs to be taken in choosing 5.4-GHz channels where 5.4 GHz systems are collocated with 5.2-GHz systems. Choosing 5.
Release 9.5 8.2 Release Notes COLLOCATING 5.4‐GHz AND 5.7‐GHz MODULES For collocation design, the 5.4-GHz and 5.7-GHz frequency bands are essentially one continuous band. When collocating 5.4-GHz and 5.7-GHz modules, use the guidelines for collocating modules within a band listed under Collocating Same-Frequency Band Modules on Page 53. Alternatively, either provide 100 ft (30 m) of vertical separation between the 5.4-GHz and 5.7GHz radios.
Release 9.5 Release Notes − Set identical range, downlink data %, and slot settings − Use the Frame Calculator (see Using the Frame Calculator below) to ensure compatible receive start times. This ensures that at any one instant the collocated modules are either all receiving or all transmitting. This avoids, for example, the issue of one AP attempting to receive a signal from a distant SM, while a nearby AP is transmitting and overpowering the signal from the distant SM. 8.3.
Release 9.5 Release Notes 9 Performance Benchmarking Process 9.1.1 Definitions The following terms are used where these release notes discuss packet processing: Aggregate Throughput Sum of uplink plus downlink traffic. Offered Load Test equipment generates a specified load to the Ethernet interface of a module (SM or the AP). The specifications of the load include both packet size and packet rate. Carried Load Test equipment measures the load delivered at the Ethernet interface of a module.
Release 9.5 9.1.3 Release Notes Benchmark Definition In a complex system, any measurement depends on system configuration, traffic mix, various settings, and measurement techniques, and so to have reproducible results a “benchmark” is defined. System configuration The PMP benchmark system consists of 3 SMs and 1 Advantage AP, as shown in Figure 22 on page 57. Traffic generation and measurement equipment is connected to both SMs and the AP.
Release 9.5 3. Release Notes Confirm results by varying Downlink/Uplink Load Ratios to ensure no significant changes around the 50% benchmark.
Release 9.5 Release Notes 10 Regulatory and Legal Notices 10.1 IMPORTANT NOTE ON MODIFICATIONS Intentional or unintentional changes or modifications to the equipment must not be made unless under the express consent of the party responsible for compliance. Any such modifications could void the user’s authority to operate the equipment and will void the manufacturer’s warranty. 10.2 NATIONAL AND REGIONAL REGULATORY NOTICES 10.2.1 U.S. Federal Communication Commission (FCC) Notification For 900-MHz, 2.
Release 9.5 Release Notes Table 13: US FCC IDs and Industry Canada Certification Numbers and covered configurations FCC ID Industry Canada Cert Number ABZ89FC5809 109W-9000 Frequencies Module Families 8 MHz channels, centered on 906-924 MHz in 1 MHz increments (within the 902-928 MHz ISM band) ABZ89FC3789 ABZ89FC5807 for P7/8/9 ABZ89FC3789 for P10/11 109W-2400 109W-5200 109W-5210 for P78/9 109W-5200 for P10/11 Issue 2, October 2009 20 MHz channels, centered on 24152457.5 MHz in 2.
Release 9.
Release 9.5 ABZ89FT7631 Release Notes 109W-4940 10 MHz channels, centered on 49454985 in 5 MHz increments (within the 4940-4990 MHz public safety licensed band) 5440 SM 5440 BH 17 dBi integrated antenna (15° x 15° -3 dB beam width) 10 dBm 4940 AP 18 dBi connectorized PCTEL Model AP 85010066001 antenna (60° x 5° -3 dB beam width) with 1 dB cable loss 18 dBm 4940 SM 4940 BH 17 dBi integrated antenna (15.5° x 17.
Release 9.5 Release Notes For 4.9-GHz devices: The 4.9-GHz band is a licensed band allocated to public safety services. Government entities that provide public safety services are eligible to apply for 4.9 GHz licenses. For additional information, refer to Industry Canada regulations. 10.2.3 Regulatory Requirements for CEPT Member States (www.cept.org) When operated in accordance with the instructions for use, Motorola Canopy Wireless equipment operating in the 2.4 and 5.
Release 9.5 Release Notes with the European Radio & Telecommunications Terminal Equipment (R&TTE) directive 1999/5/EC. The relevant Declaration of Conformity can be found at http://motorola.wirelessbroadbandsupport.com/doc.php. A European Commission decision, implemented by Member States on 31 October 2005, makes the frequency band 5470-5725 MHz available in all EU Member States for wireless access systems. Under this decision, the designation of Canopy 5.
Release 9.5 Release Notes EIRP must be lower then 100 mW For crossing the public domain over a distance >300m the user must have the authorization of the BIPT. No duplex working 10.2.9 Luxembourg Notification For the 2.4 GHz band, point-to-point or point-to-multipoint operation is only allowed on campus areas. 5.4GHz products can only be used for mobile services. 10.2.10 Czech Republic Notification 2.4 GHz products can be operated in accordance with the Czech General License No. GL-12/R/2000.
Release 9.5 Release Notes 10.2.13 Australia Notification 900 MHz modules must be set to transmit and receive only on center channels of 920, 922, or 923 MHz so as to stay within the ACMA approved band of 915 MHz to 928 MHz for the class license and not interfere with other approved users. After taking into account antenna gain (in dBi), 900 MHz modules’ transmitter output power (in dBm) must be set to stay within the legal regulatory limit of 30 dBm (1 W) EIRP for this 900 MHz frequency band. 10.2.
Release 9.5 ×： 10.3 Release Notes 表示该有毒有害物质至少在该部件的某一均质材料中的含量超出SJ/T11363-2006 标准规定的限量要求。 RF EXPOSURE SEPARATION DISTANCES To protect from overexposure to RF energy, install Canopy radios so as to provide and maintain the minimum separation distances from all persons shown in Table 15. Table 15: Exposure separation distances Module Type Separation Distance from Persons Canopy Module (FSK or OFDM) At least 20 cm (approx 8 in) Canopy Module with Reflector Dish At least 1.
Release 9.5 Release Notes P G S 4 d2 where S = power density in W/m2 P = RMS transmit power capability of the radio, in W G = total Tx gain as a factor, converted from dB d = distance from point source, in m PG 4 S d Rearranging terms to solve for distance yields Table 16 shows calculated minimum separation distances d, recommended distances and resulting power compliance margins for each frequency band and antenna combination.
Release 9.5 Release Notes Variable Band Antenna 5.7 GHz 5.4 GHz OFDM 4.9 GHz OFDM d (calculated) Recommended Separation Distance Power Compliance Margin P G S integrated 0.2 W (23 dBm) 5.0 (7 dB) 10 W/m2 9 cm 20 cm (8 in) 5 integrated plus reflector 0.2 W (23 dBm) 316 (25 dB) 10 W/m2 71 cm 1.5 m (5 ft) 4.5 Integrated plus LENS 0.2 W (23 dBm) 50 (17 dB) 1 W/m2 28 cm 50 cm (12 in) 3.13 Integrated, 17 dBi 0.
Release 9.5 10.4 Release Notes LEGAL NOTICES 10.4.1 Software License Terms and Conditions ONLY OPEN THE PACKAGE, OR USE THE SOFTWARE AND RELATED PRODUCT IF YOU ACCEPT THE TERMS OF THIS LICENSE. BY BREAKING THE SEAL ON THIS DISK KIT / CDROM, OR IF YOU USE THE SOFTWARE OR RELATED PRODUCT, YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT USE THE SOFTWARE OR RELATED PRODUCT; INSTEAD, RETURN THE SOFTWARE TO PLACE OF PURCHASE FOR A FULL REFUND.
Release 9.5 Release Notes MISUSED, NEGLECTED, OR IMPROPERLY INSTALLED. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES, THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. Limitation of Remedies and Damages.
Release 9.5 Release Notes General. Illinois law governs this license. The terms of this license are supplemental to any written agreement executed by both parties regarding this subject and the Software Motorola is to license you under it, and supersedes all previous oral or written communications between us regarding the subject except for such executed agreement. It may not be modified or waived except in writing and signed by an officer or other authorized representative of each party.
