canopyrel10notes_issue1

Upload: flbcobra

Post on 04-Apr-2018

214 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/31/2019 CanopyRel10Notes_Issue1

    1/30

    Canopy

    Software Release 10.0For PMP 430 Series ONLY

    Release NotesIssue 1

    November 2009

  • 7/31/2019 CanopyRel10Notes_Issue1

    2/30

    Notices

    See important regulatory and legal notices in Section8on Page22.

    Trademarks, Product Names, and Service Names

    MOTOROLA, the stylized M Logo, Canopy, and all other trademarks indicated as such herein areregistered trademarks of Motorola, Inc. Reg. US Pat & Tm. Office. All other product or servicenames are the property of their respective owners.

    2009 Motorola, Inc. All rights reserved

    http://motorola.wirelessbroadbandsupport.com

  • 7/31/2019 CanopyRel10Notes_Issue1

    3/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page3

    Table of Contents

    1 Introduction ................................................................................................................. 51.1 Applicability ......................................................................................................... 51.2 Release Highlights .............................................................................................. 51.3 Network Management Highlights ........................................................................ 61.4 Future Upgrades ................................................................................................. 61.5 PMP 400/430 User Guide ................................................................................... 61.6 Abbreviations ...................................................................................................... 71.7 PMP 430 Series APs and SMs ........................................................................... 81.8 Document Change History .................................................................................. 81.9 Feedback on Documentation .............................................................................. 91.10 Technical Support ............................................................................................... 9

    2 Features and Enhancements ................................................................................... 102.1 Release 10.0 Enhancements (PMP 430 Series ONLY) .................................... 102.2 Performance Packets per Second ................................................................. 11

    3 Known Open Issues ................................................................................................. 124 Notes and Reference ................................................................................................ 13

    4.1 Notes ................................................................................................................. 134.2 PMP 430 Series DFS Operation Based on Region Code ................................. 16

    5 Canopy MIB ............................................................................................................... 176 Collocation ................................................................................................................ 18

    6.1 Collocation of 5.8 GHz OFDM with Standard 5.7 GHz Canopy FSK ................ 18 7 Performance Benchmarking Process ..................................................................... 198 Regulatory and Legal Notices ................................................................................. 22

    8.1 Important Note on Modifications ....................................................................... 228.2 National and Regional Regulatory Notices ....................................................... 228.3 RF Exposure Separation Distances .................................................................. 268.4 Legal Notices .................................................................................................... 288.5 Limit of Liability.................................................................................................. 30

  • 7/31/2019 CanopyRel10Notes_Issue1

    4/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page4

    List of Tables

    Table 1: Release 10.0 highlights ..................................................................................... 5Table 2: PMP 430 Series product names ....................................................................... 8Table 3: Release 10.0 enhancements .......................................................................... 10Table 4: Packet per Second (PPS) performance .......................................................... 11 Table 5: Release 10.0 known open issues ................................................................... 12Table 6: Release 10.0 Notes ......................................................................................... 13Table 7: Previous notes from Release 9.5 applicable to Release 10.0 ......................... 14Table 8: Release 10.0 operation based on Region Code ............................................. 16Table 9: PMP 430 Series US FCC IDs and Industry Canada Certification Numbers ... 23Table 10: China Disclosure table .................................................................................. 25Table 11: Exposure separation distances ..................................................................... 26Table 12: Calculated exposure distances and power compliance margins .................. 27

    List of Figures

    Figure 1: PMP 430 AP Region Code Set to United States ............................................. 6Figure 2: Benchmark test setup .................................................................................... 21

  • 7/31/2019 CanopyRel10Notes_Issue1

    5/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page5

    1 Introduction

    1.1 APPLICABILITY

    Release 10.0 is a product specific release for the PMP 430 Series (5.8-GHz) APs and SMs only.

    The PMP 430 Series AP and SM ship pre-loaded with Release 10.0; therefore is not available fordownload from the web since Release 10.0 is only for the PMP 430 Series.

    Not all PMP 430 products are available in all markets. Please check with your local reseller foravailability of the PMP 430 Series AP and SM.

    For additional information, see.

    Table 3: Release 10.0 Enhancements on Page10

    Table 5: Release 10.0 Known open issues on Page12

    1.2 RELEASE HIGHLIGHTS

    Release 10.0 is only for PMP 430 APs and SMs. This release contains all of the features ofRelease 9.5 along with the added hardware support for the PMP 430 Series APs and SMs.Highlights of Canopy Release 10.0 include

    Table 1: Release 10.0 highlights

    PMP 430 SeriesHighlights

    Brief Description

    Cyclic Prefix (AP and SM) Default cyclic prefix is 1/4, but is configurable on both the AP/SMto 1/8.

    Spectrum AnalyzerDifferences

    PMP 430 Series uses average detector rather than peak detectoralgorithm which results in ~10 dBm lower readings than PMP 400Series and FSK which use peak detectors.

    Region Code Frequencies

    5730 5845 are the center channel frequencies for the followingregions (United States, Canada, Brazil, Australia and Russia)

    5730 5870 are the center channel frequencies for Europe andOther.

    A PMP 430 AP with a Region Code set to United States will continue to be set to the UnitedStates Region Code and will not be configurable to another Region Code by installers or endusers. This is in response to FCC KDB 594280 and ensures that end users and professionalinstallers will not have access to settings which could allow a radio to be configured to operate ina manner other than that which was specified in the FCC equipment authorization grant.

    Within the United States and its territories the PMP 430 region code is pre-configured to UnitedStates and not selectable in the Configuration => General web page. Radios sold in regionsoutside of the United States and its territories are required to set the Region Code to the region inwhich it is used.

  • 7/31/2019 CanopyRel10Notes_Issue1

    6/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page6

    Figure 1: PMP 430 AP Region Code Set to United States

    1.3 NETWORK MANAGEMENT HIGHLIGHTS

    Motorola Prizm 3.2 with Patch 3 or One Point Wireless Manager 2.2 is recommended formanaging PMP 430 AP and SM modules with Release 10.0.

    Motorola Prizm 3.2 with Patch 3 and One Point Wireless Manager 2.2 is available for downloadfrom the Motorola support web site.http://motorola.wirelessbroadbandsupport.com/software/

    1.4 FUTURE UPGRADES

    CNUT 3.20.5 will be required for future Release 10.x upgrades. The PMP 430 Series APs and

    SMs ship pre-loaded with Release 10.0.

    1.5 PMP 400/430 USER GUIDE

    The PMP 400/430 User Guide Issue 4 is available for download from the Motorola support website.http://motorola.wirelessbroadbandsupport.com/software/

    http://motorola.wirelessbroadbandsupport.com/software/http://motorola.wirelessbroadbandsupport.com/software/http://motorola.wirelessbroadbandsupport.com/software/http://motorola.wirelessbroadbandsupport.com/software/http://motorola.wirelessbroadbandsupport.com/software/http://motorola.wirelessbroadbandsupport.com/software/http://motorola.wirelessbroadbandsupport.com/software/http://motorola.wirelessbroadbandsupport.com/software/
  • 7/31/2019 CanopyRel10Notes_Issue1

    7/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page7

    1.6 ABBREVIATIONS

    The following abbreviations may be used in these notes:

    AES

    AP

    CIR

    CNUT

    CMM

    CPE

    DES

    DFS

    DNS

    ETSI

    FCC

    FSK

    LAN

    MAC

    MIB

    MIR

    MOS

    NAT

    OFDM

    OID

    P10/P11

    PMP

    PTP

    RF

    SM

    SNMP

    VDC

    VLAN

    Advanced Encryption Standard

    Access Point Module

    Committed Information Rate

    Canopy Network Updater Tool

    Cluster Management Module

    Customer Premises Equipment

    Data Encryption Standard

    Dynamic Frequency Selection for radar avoidance

    Domain Name System

    European Telecommunications Standards Institute

    Federal Communications Commission (United States)

    Frequency Shift Keying

    Local Area Network

    Media Access Control (Ethernet address)

    Management Information Base

    Maximum Information Rate

    Mean Opinion Score

    Network Address Translation

    Orthogonal Frequency Division Multiplexing

    Object Identifier for an object in a MIB

    Shorthand for hardware series levels

    Point to Multi-Point

    Point to Point

    Radio Frequency

    Subscriber Module

    Simple Network Management Protocol

    Volts Direct Current

    Virtual LAN

  • 7/31/2019 CanopyRel10Notes_Issue1

    8/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page8

    1.7 PMP 430 SERIES APS AND SMS

    Table 2includes PMP 430 Series model numbers, product names SM/AP power and CMM4requirements.

    Table 2: PMP 430 Series product names

    CSM 58430ModelNumber

    5.8GHz OFDM SubscriberModule (SM) Description

    DESorAES

    Picture Power 29.5 VDC

    Supply Type

    5790SM4 5.8 GHz OFDM SM 4 Mbps DES

    5791SM4 5.8 GHz OFDM SM 4 Mbps AES

    5790SM10 5.8 GHz OFDM SM 10 Mbps DES

    5791SM10 5.8 GHz OFDM SM 10 Mbps AES

    5790SM20 5.8 GHz OFDM SM 20 Mbps DES

    5791SM20 5.8 GHz OFDM SM 20 Mbps AES5790SM40 5.8 GHz OFDM SM 40 Mbps DES

    5791SM40 5.8 GHz OFDM SM 40 Mbps AES

    CAP 58430ModelNumber

    5.8GHz OFDM Access Point(AP) Description

    DESorAES

    Picture CMM Type

    5780AP5.8 GHz OFDM ConnectorizedAP w/antenna

    DES Requires CMM4w/56 VDC supply

    5780APUS5.8 GHz OFDM ConnectorizedAP w/antenna - US Model

    DES Requires CMM4w/56 VDC supply

    5781AP5.8 GHz OFDM ConnectorizedAP w/antenna

    AES Requires CMM4w/56 VDC supply

    5781APUS5.8 GHz OFDM ConnectorizedAP w/antenna - US Model

    AES Requires CMM4w/56 VDC supply

    5780APC5.8 GHz OFDM ConnectorizedAP No antenna

    DESRequires CMM4w/56 VDC supply

    5781APC5.8 GHz OFDM ConnectorizedAP - No antenna

    AESRequires CMM4w/56 VDC supply

    Note: PMP 430 and CMM4 user guide documentation is available for download from the Motorolasupport web site. http://motorola.wirelessbroadbandsupport.com/software/

    1.8 DOCUMENT CHANGE HISTORY

    Issue 1 First Release

    http://motorola.wirelessbroadbandsupport.com/software/http://motorola.wirelessbroadbandsupport.com/software/http://motorola.wirelessbroadbandsupport.com/software/
  • 7/31/2019 CanopyRel10Notes_Issue1

    9/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page9

    1.9 FEEDBACK ON DOCUMENTATION

    Is this document accurate, complete, and clear? How can it be improved? Please send yourfeedback on Canopy documentation [email protected].

    1.10 TECHNICAL SUPPORT

    Tip! Do not clear the Event Log after you encounter issues. It may be useful toTechnical Support, if you need to escalate the issue.

    Here is the escalation path for resolution of a problem:

    1. Check documentation:

    this document

    Canopy System Release 8 Users Guide, available athttp://motorola.wirelessbroadbandsupport.com/software.

    2. Consider checking the Community Forum and Knowledge Base athttp://motorola.wirelessbroadbandsupport.com/support/community.

    3. Escalate the problem to your Canopy supplier or reseller.

    4. Escalate the problem to Canopy Technical Support or other designated Tier 3technical support:

    U.S. and Canada Email:[email protected]

    Latin and Central America Email:[email protected] 0800-666-2789Brazil 0800-891-4360Columbia 01-800-912-0557Mexico 001-800-942-7721Peru 0800-70-086All other countries +420 533 336 946

    Europe, Middle East, Email:[email protected] Africa Denmark 043682114

    France 0157323434Germany 06950070204Italy 0291483230Lithuania 880 030 828Netherlands 0202061404Norway 24159815Portugal 0217616160Spain 0912754787Russia 810 800 228 41044Saudi Arabia 800 844 5345

    South Africa 0800981900United Kingdom 0203 0277499

    Asia Pacific Email:[email protected]+6048503854 (9am - 5pm Malaysia Time)+420 533 336 946 (outside hours)

    When you send e-mail or call, please include, as appropriate, software release on each module,IP addresses, MAC addresses, and features enabled, like NAT, VLAN, high priority channel, orCIR. You may be asked to run the Support Tool on CNUT or Prizm to provide a complete networkpicture.

    mailto:[email protected]?subject=Release%204.0mailto:[email protected]?subject=Release%204.0mailto:[email protected]?subject=Release%204.0http://motorola.wirelessbroadbandsupport.com/softwarehttp://motorola.wirelessbroadbandsupport.com/softwarehttp://motorola.wirelessbroadbandsupport.com/support/communityhttp://motorola.wirelessbroadbandsupport.com/support/communitymailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]://motorola.wirelessbroadbandsupport.com/support/communityhttp://motorola.wirelessbroadbandsupport.com/softwaremailto:[email protected]?subject=Release%204.0
  • 7/31/2019 CanopyRel10Notes_Issue1

    10/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page10

    2 Features and EnhancementsThe following sections list enhancements for Release 10.0.

    2.1 RELEASE 10.0 ENHANCEMENTS (PMP 430 SERIES ONLY)Release 10.0 adds the enhancements listed inTable 3.

    Table 3: Release 10.0 enhancements

    Enhancement Description Summary

    Hardwaresupport forPMP 430 APsand SMs

    Hardware support for PMP430 Series APs and SMs

    Release 10.0 is NOT a general release. Release 10.0ships ONLY on PMP 430 Series APs and SMs andincludes all features supported in Release 9.5.

    Cyclic Prefix(AP and SM)

    PMP 430 Series APs andSMs support both 1/4 and

    1/8 cyclic prefix

    OFDM technology uses a cyclic prefix, where a portion ofthe end of a symbol (slot) is repeated at the beginning of

    the symbol (slot) to allow multi-pathing to settle beforereceiving the desired data. A 1/4 cyclic prefix means thatfor every 4 bits of throughput data transmitted, anadditional bit is used, A 1/8 cyclic prefix means that forevery 8 bit of throughput data transmitted, an additional bitis used.

    PMP 430 Series networks use a default cyclic prefix of 1/4that is configurable by the operator to 1/8. The CyclicPrefix is set on the Configuration => Radio page on theAP and SM. Changing the default from 1/4 to 1/8 canincrease throughput by ~2 Mbps (assuming 75% dutycycle) in installations with low multipath conditions. It isrecommended to test 1/8 cyclic prefix to determine actualperformance based on RF conditions.

    Region CodeFrequencies

    PMP 430 Series AP CenterChannel Frequencies

    Regulatory compliance mandates that they operator selectthe correct region code.

    Note: Users procuring equipment in the United States arerequired to purchase APs with model number 5780APUSfor DES encryption and 5781APUS for AES encryption.

    The valid center channel frequencies by region are:

    - 5730 5845 are the center channel frequenciesfor the following regions (United States, Canada,Brazil, Australia and Russia).

    - 5730 5870 are the center channel frequenciesfor the Europe and Other region code.

    Spectrum

    AnalyzerDifferences

    PMP 430 Series uses

    average detector rather thanpeak detector algorithm

    The PMP 430 series Spectrum Analyzer uses an average

    detector rather than the peak detector algorithm that isused by the Canopy FSK and PMP 400 series radios. Theaverage detector is closer to actual RF received powerwhile in session as opposed to the peak detector. Theaverage detector shows lower power readings by ~10dBm compared to the Canopy FSK and PMP 400 Serieswhich use peak detectors. In other words, the spectrumanalyzer in Release 10.0 more accurately displays theactual power readings.

  • 7/31/2019 CanopyRel10Notes_Issue1

    11/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page11

    2.2 PERFORMANCE PACKETS PER SECOND

    Packet per Second (PPS) performance for Release 10.0 that supports the PMP 430 series is thesame as the PMP 400 series with Release 9.5. Benchmark values are shown in Table 4.

    Table 4: Packet per Second (PPS) performance

    Product

    Hardware series

    P11 or P10

    PMP 58430 6800

    PMP 54400 6800

    Note: No significant difference between DES and AES

    Section7, Performance Benchmarking Process, on page19describes the benchmarking process

    used to measure packets per second and discusses the meaning and limitations of thebenchmark.

  • 7/31/2019 CanopyRel10Notes_Issue1

    12/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page12

    3 Known Open IssuesKnown open issues for Release 10.0 are listed inTable 5.

    Table 5: Release 10.0 known open issues

    Product Family Description Discussion and Recommendations

    All SM - DNS below aNATed SM

    Microsoft Vista and presumably Windows 7 will not route a169.254/16 subnet used as the default Canopy subnet sinceMicrosoft uses 169.254/16 subnet to talk between localmachines. This is not an issue if:

    - the PC is connected directly to the NATed SM.

    - the NAT/routing CPE underneath the NATed SMprovides DNS services.

    However; if a NAT/routing CPE that is not providing DNSservices (e.g. some home routers*) is placed between the SM

    and the users PC, a Microsoft Vista and Windows 7 machinewill not route to the default 169.254/16 SM IP address space toaccess DNS services.

    Workaround: Reconfigure the SMs NAT LAN address to aprivate IP address such as 192.168/16, 172.16/12, or 10/8.

    * Please refer to home router manufacturer documentation todetermine if the router provides DNS services.

    PMP 430 Degradation inVOIP capabilities(12038)

    Due to a packet scheduling issue, PMP 430 cannot handle thesame rate of VoIP traffic as PMP 400 (5.4-GHz OFDM).Whereas PMP 400 can handle 54 VoIP Calls, the PMP 430 withRelease 10.0 only supports approximately 45 VoIP calls beforethe MOS score becomes unacceptable.

  • 7/31/2019 CanopyRel10Notes_Issue1

    13/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page13

    4 Notes and Reference

    4.1 NOTES

    New notes for Release 10.0 are listed inTable 6and previous notes are listed inTable 7.

    Table 6: Release 10.0 Notes

    Ref # Description Discussion and Recommendations

    12257 PMP 430 SM MIRconfigured greaterthan max sustainedMIR data rate eitherby Prizm 3.2.

    For reference, themax SM MIR in kbps

    for each SM type is:4 Mbps SM = 4000

    10 Mbps SM = 10000

    20 Mbps SM = 20000

    40 Mbps SM = 50000

    Note: 40 Mbps SMdisplays Unlimited inthe Home => GeneralStatus web page.

    If the PMP 430 AP is set to Authentication Server or Authentication Server+ SM as configuration source in the Configuration => General web page,the PMP 430 SM will receive its MIR settings from the Prizm 3.2bandwidth authentication server. In this case, it is possible for Prizm 3.2 toset the PMP 430 SM MIR settings greater than the keyed bandwidth ofthe SM. For context, the PMP 430 SM is available keyed as 4, 10, 20 or40 Mbps.

    If the SM receives a MIR setting from Prizm 3.2 that is greater than the

    keyed bandwidth, the SM will cap the MIR using this formula.

    (desired uplink MIR * SM aggregate capped rate) / desired aggregate rate

    (desired downlink MIR * SM aggregate capped rate) / desired aggregate rate

    Note: Desired aggregate rate is the sum of the desired uplink rate and desireddownlink rate

    For example, if a PMP 430 4 Mbps SM with a max MIR cap of 4000receives a MIR setting from Prizm that is greater than 4000 kbps, it willcap the downlink MIR and the uplink MIR to equal a max of 4000 kbps.

    Below is a formula example with Prizm settings 10000 kbps uplink MIRand 7000 downlink MIR to a 4 Mbps SM that is capped at 4000 kbps maxMIR.

    Uplink formula: (10000 * 4000) / (7000 + 10000) = 2352 kbps

    Downlink formula: (7000 *4000) / (7000 + 10000) = 1648 kbpsThus the Uplink MIR of 2352 + Downlink MIR of 1648 = 4000 kbps

    In this example, the PMP 430 AP sessions page will display a SM uplinkand downlink MIR SMCAP as shown below.

  • 7/31/2019 CanopyRel10Notes_Issue1

    14/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page14

    Table 7: Previous notes from Release 9.5 applicable to Release 10.0

    Note: Release 10.0 includes all of the features documented in the Release 9.5 Release Notes.However; Release 10.0 includes support for PMP 430 hardware, spectrum analyzer differencesand cyclic prefix settings. SeeTable 1on page5for Release 10.0 highlights.

    ID Description Discussion and Recommendations

    11699 UpdatingCommunityStrings on theWeb GUI

    To flip-flop the read/write and read-only community string names, it isnecessary to change one community string to a temp name first beforeswitching community string names.

    10333 Link Status Page The AP or SM Tools => Link Status Page displays NA for Latest Remote LinkEfficiency Percentage. To update, either turn on web page auto update orpress F5 to refresh the web page.

    7427 AP Sync Input Remote AP receives sync from SM by setting SYNC Input to Timing Port.However; if this is incorrectly configured as SYNC input to Power port the

    remote AP will still correctly receive SYNC.

    10263 Disable TCP ACKprioritizing inbroadcast videoapplications

    When optimizing a system for broadcast video, on the APs Configuration =>General page configure Prioritized TCP ACK to Disabled.

    In a system being used for internet access or similar applications prioritizingTCP ACKs improves downloading of FTP files and other activities makingsignificant use of TCP ACKs under heavy load. However, in a system beingused for broadcast video or video surveillance, prioritizing TCP ACKs cancause sporadic choppy video in the uplink.

    8484 Procedures forsaving an XML fileof a spectrumgraph

    When the SpectrumAnalysis.xml button is clicked on the SMs Tools =>Spectrum Analyzer page or the APs Tools => Remote Spectrum Analyzerpage, the spectrum graph is redisplayed using XML and XSL if the browsersupports XSL. To save the underlying XML file, right click and select Save

    Target As on a Windows PC, or equivalent action for other operatingsystems.

    8172 SM scanfrequencies notcancelled bySNMP actions

    If you make frequency changes on the SM GUI, and then back them outusing SNMP, the Reboot Required message remains on the GUI.

    Workaround:

    If it says Reboot Required, go ahead and reboot, just to clear the message.

  • 7/31/2019 CanopyRel10Notes_Issue1

    15/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page15

    None Managing moduleaccounts andpasswords

    The best security practice is to be aware the unit starts withroot and adminaccounts, to plan your approach to accounts, and set passwords for allaccounts.

    A module that either is fresh from the factory or has been operator-reset tofactory defaults has two user accounts:root and admin, both with

    ADMINISTRATOR level permissions.

    To secure a module, access the Account => Change Users Password taband add a password to each of these accounts. Adding a password to onlyone account still leaves the other open. Furthermore, an account without apassword will accept any password potentially giving the impression the unitis protected when it isnt.

    Alternatively, an operators practices may be to delete theadmin account ordelete the root account and replace them with their own account(s). Bydefault Prizm 3.2, One Point Wireless Manager 2.2 and CNUT 3.20.5 use theroot account to manage the module, so if you deleteroot accounts onmodules you will need to make coordinated changes to Prizm 3.2, WirelessManager 2.2 and CNUT 3.20.5 to access them with your own accounts.

    7808 Use up to 16

    alphanumericcharacters in useraccount names,passwords, andCommunityStrings

    SNMP doesnt do data-entry checking, so more than 16 characters may be

    entered, but only 16 characters will be saved and displayed.

    You can set Community Strings that include characters like~`!@#$%^&;*()_+[]{}|;:,./? from the GUI, but SNMP only acceptsalphanumeric characters and SNMP get or set commands will return errors.

    7442 Timed SpectrumAnalyzer settingsanomaly

    Values of Timed Spectrum Analyzer duration and Spectrum Analysis onBoot get saved by clicking any button on the page, not just when clickingSave Changes or Start Time Spectrum Analysis (which is typical operationfor other pages).

    None Best Practice is toset SM to same

    Region Code asAP

    When an SM registers to an AP, it assumes the Region Code and associatedparameters of the AP, disregarding any Region code set in the SM by you.

    However, the best practice is still for you to set a Region Code in the SM sothat displayed options are consistent with the region.

    4831 Details on pingingCanopy modules

    A ping size larger than 1494 Bytes to a Canopy module times out and fails.However, a ping of this size or larger to a system that is behind a Canopymodule typically succeeds. It is generally advisable to ping such a system,since Canopy handles that ping with the same priority as is given all othertransport traffic. The results are unaffected by ping size and by the load onthe Canopy module that brokers this traffic.

    5298 AP may be listedtwice in APEvaluation tab

    To help during aiming, the Tools => AP Evaluation tab maintains AP entriesfor 15 minutes. If the frequency of an AP is changed, for 15 minutes the AP islisted twice in the AP Evaluation tab, once with the former frequency, andonce with the new.

    4844,2756

    When using LinkTest with MIR,need to set bothends

    To see the effects of MIR capping, you can run a link test with MIR enabled.To get meaningful results, set Link Test with MIR to Enabled on theTools => Link Capacity Test tab in boththe SM and the AP. When it isenabled on only one end, results are misleading.

    After you run perform a link test with MIR capping enabled, considerimmediately changing Link Test with MIR to Disabledin boththe SM andthe AP, to avoid mistakenly capping only one end of the link test.

  • 7/31/2019 CanopyRel10Notes_Issue1

    16/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page16

    5284 Click SpectrumAnalyzer Enablebutton twice

    After you click the Enable button in the Tools => Spectrum Analyzer tab, theresulting display may omit bars for some frequencies, especially in frequencybands that have a large number of center channels, such as the 5.4-GHzband. If you clicking Enable again, the display includes the entire spectrumbar graph.

    TIP: In the Configuration => General tab, set theWebpage Auto Updateparameter to a few seconds, to have the Spectrum Analyzer automaticallyfully displayed and refreshed. You can later reset theWebpage Auto Updatetime back to 0, to disable refresh.

    4706 Blank screen afterlogging in to SMthrough APSession Statustab

    In some instances, depending on network activity and network design, theinterface presents a blank screen to a user who logs in to an SM through theHome => Session Status tab in the AP. If you observe this, refresh yourbrowser window.

    7557 When connectingto a hub, use onlyhalf duplex

    Ethernet settings

    Ethernet connections set to 10 Base T Full Duplex or100 Base T Full Duplex will not connect to an SM through a hub, due to theway a hub works. Use half duplex settings when using a hub.

    4.2 PMP 430 SERIES DFS OPERATION BASED ON REGION CODE

    For reference, Table 8shows operation based on Region Code, by frequency band andmodule type.

    Table 8: Release 10.0 operation based on Region Code

    Region Code1

    PMP 430 Series - 5.8 GHz

    AP SM

    United States No effect No effect

    Canada No effect No effect

    Europe

    ETSI 5.8-GHzDFS indicatescompliance withETSI EN 302502 v1.2.1

    ETSI 5.8-GHzDFS indicatescompliance withETSI EN 302502 v1.2.1

    Brazil No effect No effect

    Australia No effect No effectRussia No effect No effect

    Other No effect No effect

  • 7/31/2019 CanopyRel10Notes_Issue1

    17/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page17

    5 Canopy MIBThe 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 theCanopy tab ofhttp://motorola.wirelessbroadbandsupport.com/software.

    Detailed information on the Canopy MIBs is available athttp://motorola.wirelessbroadbandsupport.com/support/online_tools.

    MIB files are used by Network Management Systems and Element Management Systems, suchas the Motorola Prizm 3.2 and One Point Wireless Manager 2.2 system, to support a host ofsurveillance, monitoring, control, and operational tasks.

    Information on the Motorola Prizm 3.2 element management system is available athttp://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-EN

    Information on the Motorola One Point Wireless Manager 2.2 management system is available athttp://www.onepointwireless.com/wirelessmanager/

    Prizm 3.2 and One Point Wireless Manager 2.2 documentation and installers are available fordownload from the Canopy tab ofhttp://motorola.wirelessbroadbandsupport.com/software.

    If you are using Prizm: Prizm 3.2 software includes the MIB information. You do not need toload MIB files.

    If you are using One Point Wireless Manager 2.2 or an SNMP network management system(NMS) or element management system (EMS) other than Prizm: Load the MIBs per theinstructions for One Point Wireless Manager 2.2 or your NMS or EMS.

    Important! When loading the Canopy MIB files

    1. First load the standard MIB files.

    2. Then load the Canopy MIB files.

    Some NMSs are not sensitive to order, but some require a specific loading order to build a MIBtree. Loading in the recommended order avoids any problems arising from loading sequence.

    http://motorola.wirelessbroadbandsupport.com/softwarehttp://motorola.wirelessbroadbandsupport.com/softwarehttp://motorola.wirelessbroadbandsupport.com/softwarehttp://motorola.wirelessbroadbandsupport.com/support/online_toolshttp://motorola.wirelessbroadbandsupport.com/support/online_toolshttp://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-ENhttp://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-ENhttp://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-ENhttp://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-ENhttp://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-ENhttp://www.onepointwireless.com/wirelessmanager/http://www.onepointwireless.com/wirelessmanager/http://motorola.wirelessbroadbandsupport.com/softwarehttp://motorola.wirelessbroadbandsupport.com/softwarehttp://motorola.wirelessbroadbandsupport.com/softwarehttp://motorola.wirelessbroadbandsupport.com/softwarehttp://www.onepointwireless.com/wirelessmanager/http://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-ENhttp://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-ENhttp://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-ENhttp://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Point-to-Multipoint+Networks/Unlicensed+Point-to-Multipoint+Solutions/Element_Management_PTMP_US-ENhttp://motorola.wirelessbroadbandsupport.com/support/online_toolshttp://motorola.wirelessbroadbandsupport.com/software
  • 7/31/2019 CanopyRel10Notes_Issue1

    18/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page18

    6 Collocation

    6.1 COLLOCATION OF 5.8 GHZ OFDM WITH STANDARD 5.7 GHZ

    CANOPY FSKWhen locating 5.8 GHz PMP 430 OFDM APs near 5.7 GHz standard Canopy FSK APs(especially on the same tower, but also in the same geographical area), the following practicesshould be followed to avoid interference between the two systems:

    Plan spacing between OFDM and FSK channels to provide 25 MHz center spacing,which gives a 10 MHz guard band between the 10 MHz OFDM channel and the 20MHz FSK channel.

    Coordinate Downlink Data %, Range, and Control Slot settings using both theOFDM and the FSK frame calculators

    The following paragraphs give more details on these recommended practices.

    6.1.1 Channel Spacing

    Center spacing of 25 MHz between collocated FSK and OFDM APs provides a 10 MHz guardband between the 20 MHz and 10 MHz channels, which has proven useful and needed in fieldtesting. Alternatively, in cases where channel planning is severely restricted and the 10 MHzguard band (25 MHz spacing) is not possible, using vertical separation of 5 feet or more betweenthe OFDM and FSK APs may allow collocation with no guard band (15 MHz spacing) in somedeployments.

    6.1.2 Frame Calculations and Configuration Settings

    Interference between collocated Canopy systems can be avoided by following two practices:

    1. Use a CMM. This synchronizes frame start, so that all collocated APs begin

    transmitting at the same time each 2.5 millisecond frame.2. Use the frame calculators in each module, OFDM and FSK (the frame calculators are

    different, as frame details are different) to select Downlink Data %, Range, andControl Slots for each system that produce Rec SEQ Start values that are within300 bit times. This ensures that all collocated APs end transmission each framebefore any collocated AP begins to receive.

    When collocating only Canopy OFDM APs together, or collocating only Canopy hardware-scheduled FSK APs together, the simple practice of setting the Downlink Data %, Range, andControl Slots the same on all APs ensures they wont interfere with each other. (Theseparameters are set on the Configuration => Radio page of the AP.) However, due to thedifferent physical layer between Canopy OFDM and Canopy FSK, this doesnt necessarily work

    when collocating OFDM and FSK together.

    You will need to use frame calculators on both the OFDM and FSK modules, as they are differentframe calculators. For the same Downlink Data %, Range, and Control Slots, the framecalculators give different results. Use of the frame calculators is similar to the previous use whencollocating software-scheduled and hardware-scheduled APs.

  • 7/31/2019 CanopyRel10Notes_Issue1

    19/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page19

    7 Performance Benchmarking Process

    7.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 interfaceof a module (SM or the AP). The specifications of the load includeboth packet size and packet rate.

    Carried Load Test equipment measures the load delivered at the Ethernet interfaceof a module. The load is calculated from packet size and number ofpackets. As resources are exhausted at any point in the system,packets may be dropped. The Carried Load equals the Offered Loadminus Dropped Packets.

    Downlink/Uplink Load Ratio The ratio of downlink Carried Load to uplink Carried Load.

    NOTE:Do notconfuse the Downlink/Uplink Load Ratio with the

    Downlink Data configuration parameter. The Downlink/Uplink LoadRatio is determined from the Carried Loads. The Downlink Data isset by the operator and determines the split of downlink and uplinkslots in the air frame.

    7.1.2 System Performance and System Constraints

    In the PMP 430 there are multiple performance constraints. Different combinations of systeminputs will result in different constraints limiting system performance.

    Larger Packets

    With larger packets (PMP 430 handles packets up to 1522 Bytes), the system constraint is airtime, which can also be stated as slots, or maximum bits per second. This can be calculated asfollows:

    For 1/4 Cyclic Prefix the calculation is64 Bytes/fragment x 3 fragments/slot x 33 slots/frame x 400 frames/sec x 8 bits/byte =20.2 Mbps

    For 1/8 Cyclic Prefix the calculation is64 Bytes/fragment x 3 fragments/slot x 37 slots/frame x 400 frames/sec x 8 bits/byte =22.6 Mbps

    This is an aggregate (uplink plus downlink) limit, as the PMP 430 system is an OFDM system.

    20 Mbps is a typical maximum aggregate throughput for larger packet sizes in a systemconfigured with 1/4 cyclic prefix. For 1/8 cyclic prefix systems 22.6 Mbps is a typical maximumaggregate throughput. Longer range settings can reduce the number of slots in a frame andpacket size (breakage on 64-byte boundaries) can affect packing efficiency (the percentage offragments fully packed with 64 bytes).

  • 7/31/2019 CanopyRel10Notes_Issue1

    20/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page20

    Smaller Packets

    With smaller packets, the system constraint is processing powerin any module handling thetraffic stream. Even though there may be airtime or slots available, the overall throughput islimited by packet handling ability.

    7.1.3 Benchmark Definition

    In a complex system, any measurement depends on system configuration, traffic mix, varioussettings, and measurement techniques, and so to have reproducible results a benchmark isdefined.

    System configuration

    The PMP benchmark system consists of 3 SMs and 1 Advantage AP, as shown in Figure 2 onpage21. Traffic generation and measurement equipment is connected to both SMs and the AP.Traffic is generated such that any one packet attempts to traverse an SM and then the AP, or theAP and then an SM. No SM-to-SM traffic is included in the benchmark. RF conditions aremaintained such that all links run at max rate (2X or 3X).

    Traffic mix/Packet sizeAll generated packets have a size of 64 Bytes. The packet format used is a valid Ethernet/IPpacket. The performance of interest is performance near a 50% Downlink/Uplink Load Ratio.

    PMP Settings

    Downlink Data: 50%

    Control Slots: 2

    Range: 2 miles

    Max rate (2X or 3X) Enabled

    Encryption: Enabled (DES modules)

    MIR: 20,000 kbits/sec sustained rate and 500,000 kbits burst allocation

    (defaults) CIR: 0 (default)

    NAT: Disabled (default)

    VLAN: Disabled (default)

    High Priority: Disabled (default)

    PTP Settings

    Downlink Data: 50%

    Max rate (2X or 3X) Enabled

    Encryption: Enabled (DES modules)

    Measurement technique

    1. Send a specific number of frames at a specific rate through SMs and AP (uplinks) and APand SM (downlink) simultaneously. This is the Offered Load. Count the frames that arereceived correctly at both sides. This is the Carried Load. Repeat this through the loadrates of interest. Review the results, noting where the packet loss (the difference betweenthe Offered Load and Carried Load) is essentially zero (

  • 7/31/2019 CanopyRel10Notes_Issue1

    21/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page21

    2. Confirm results by running longer tests at selected load rates.

    3. Confirm results by varying Downlink/Uplink Load Ratios to ensure no significant changesaround the 50% benchmark.

    SM2AP

    SM3

    Ixia T est Controll er

    and Load Modules

    All packets 64 Bytes

    x/2 pps

    x/2 pps

    x/6 pps

    x/6 pps

    x/6 pps

    x/6 pps

    x/6 pps

    x/6 pps

    xppsSM1

    Figure 2: Benchmark test setup

  • 7/31/2019 CanopyRel10Notes_Issue1

    22/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page22

    8 Regulatory and Legal Notices

    8.1 IMPORTANT NOTE ON MODIFICATIONS

    Intentional or unintentional changes or modifications to the equipment must not be made unless under theexpress consent of the party responsible for compliance. Any such modifications could void the usersauthority to operate the equipment and will void the manufacturers warranty.

    8.2 NATIONAL AND REGIONAL REGULATORY NOTICES

    8.2.1 U.S. Federal Communication Commission (FCC) Notification

    For 5.8-GHz devices:

    This device complies with Part 15 of the US FCC Rules and Regulations. Operation is subject to thefollowing two conditions: (1) This device may not cause harmful interference, and (2) This device mustaccept any interference received, including interference that may cause undesired operation.

    This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant toPart 15 of the US FCC Rules. These limits are designed to provide reasonable protection against harmfulinterference in a residential installation. This equipment generates, uses, and can radiate radio-frequencyenergy and, if not installed and used in accordance with these instructions, may cause harmful interferenceto radio communications. If this equipment does cause harmful interference to radio or televisionreception, which can be determined by turning the equipment on and off, the user is encouraged to correctthe interference by one or more of the following measures:

    Increase the separation between the affected equipment and the unit;

    Connect the affected equipment to a power outlet on a different circuit from that whichthe receiver is connected to;

    Consult the dealer and/or experienced radio/TV technician for help.

    FCC IDs and the specific configurations covered are listed inTable 9.

  • 7/31/2019 CanopyRel10Notes_Issue1

    23/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page23

    Table 9: PMP 430 Series US FCC IDs and Industry Canada Certification Numbers

    FCC ID IndustryCanada CertNumber

    Frequencies ModuleFamilies

    Antenna MaximumTx OutputPower

    ABZ89FT7634 --- 10 MHz channels,centered on 5730-5845 in 5 MHzincrements (within the5725-5850 MHz ISMband)

    5780APC 17 dBi connectorizedPCTEL Model8514724E01 antenna (60x 5-3 dB beam width)with 1 dB connector cableloss

    20 dBm

    ABZ89FT7635 --- 10 MHz channels,centered on 5730-5845 in 5 MHzincrements (within the5725-5850 MHz ISMband)

    5790SM 10 dBi (55x 55and 3 dBbeam width)

    19 dBm

    --- 109W-5780 10 MHz channels,

    centered on 5730-5845 in 5 MHzincrements (within the5725-5850 MHz ISMband)

    5780APC 17 dBi connectorized

    PCTEL Model8514724E01 antenna (60x 5-3 dB beam width)with 1 dB connector cableloss

    20 dBm

    --- 109W-5790 10 MHz channels,centered on 5730-5845 in 5 MHzincrements (within the5725-5850 MHz ISMband)

    5790SM 10 dBi (55x 55and 3 dBbeam width)

    19 dBm

    8.2.2 Industry Canada (IC) NotificationFor 5.8-GHz devices:

    This device complies with RSS-210 of Industry Canada. Operation is subject to the following two conditions:(1) This device may not cause harmful interference, and (2) This device must accept any interferencereceived, including interference that may cause undesired operation.

    This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant toRSS-210 of Industry Canada. These limits are designed to provide reasonable protection against harmfulinterference in a residential installation. This equipment generates, uses, and can radiate radio-frequencyenergy and, if not installed and used in accordance with these instructions, may cause harmful interferenceto radio communications. If this equipment does cause harmful interference to radio or televisionreception, which can be determined by turning the equipment on and off, the user is encouraged to correctthe interference by one or more of the following measures:

    Increase the separation between the affected equipment and the unit;

    Connect the affected equipment to a power outlet on a different circuit from that whichthe receiver is connected to;

    Consult the dealer and/or experienced radio/TV technician for help.

    To reduce potential radio interference to other users, the antenna type and its gain should be chosen so itsEquivalent Isotropic Radiated Power (EIRP) is not more than that permitted for successful communication.

    Industry Canada Certification Numbers and the specific configurations covered are listed inTable 9.

  • 7/31/2019 CanopyRel10Notes_Issue1

    24/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page24

    This device has been designed to operate with the antennas listed inTable 9and having a maximum gainas shown inTable 9. Antennas not included or having a gain greater than as shown inTable 9are strictlyprohibited from use with this device. Required antenna impedance is 50 ohms.

    8.2.3 European Union Notification for 5.8 GHz Product

    The 5.8 GHz connectorized product is a two-way radio transceiver suitable for use in Broadband WirelessAccess System (WAS), Radio Local Area Network (RLAN), or Fixed Wireless Access (FWA) systems. It is aClass 2 device and uses operating frequencies that are not harmonized throughout the EU member states.The operator is responsible for obtaining any national licenses required to operate this product and thesemust be obtained before using the product in any particular country.

    This equipment is marked to show compliance with the European R&TTE directive 1999/5/EC.

    The relevant Declaration of Conformity can be found athttp://motorola.wirelessbroadbandsupport.com/doc.php.

    8.2.4 Equipment Disposal

    Waste (Disposal)

    of Electronicand ElectricEquipment

    Please do not dispose of Electronic and Electric Equipment or Electronic and Electric Accessories with yourhousehold waste. In some countries or regions, collection systems have been set up to handle waste ofelectrical and electronic equipment. In European Union countries, please contact your local equipmentsupplier representative or service center for information about the waste collection system in your country.

    8.2.5 EU Declaration of Conformity for RoHS Compliance

    Motorola hereby, declares that these Motorola products are in compliance with the essential requirementsand other relevant provisions of Directive 2002/95/EC, Restriction of the use of certain HazardousSubstances (RoHS) in electrical and electronic equipment.

    The relevant Declaration of Conformity can be found athttp://motorola.wirelessbroadbandsupport.com/doc.php.

    8.2.6 UK Notification

    The 5.8 GHz connectorized product has been notified for operation in the UK, and when operated inaccordance with instructions for use it is compliant with UK Interface Requirement IR2007. For UK use,installations must conform to the requirements of IR2007 in terms of EIRP spectral density against elevationprofile above the local horizon in order to protect Fixed Satellite Services. The frequency range 5795-5815MHz is assigned to Road Transport & Traffic Telematics (RTTT) in the U.K. and shall not be used by FWAsystems in order to protect RTTT devices. UK licensing specifies that radiolocation services shall beprotected by a Dynamic Frequency Selection (DFS) mechanism to prevent co-channel operation in thepresence of radar signals.

    8.2.7 Norway NotificationUse of the frequency bands 5725-5795 / 5815-5850 MHz are authorized with maximum radiated power of 4W EIRP and maximum spectral power density of 200 mW/MHz. The radio equipment shall implementDynamic Frequency Selection (DFS) as defined in Annex 1 of ITU-R Recommendation M.1652 / EN301 893. Directional antennae with a gain up to 23 dBi may be used for fixed point-to-point links. The powerflux density at the border between Norway and neighboring states shall not exceed 122.5 dBW/m

    2

    measured with a reference bandwidth of 1 MHz.

    Canopy 5.8 GHz connectorized products have been notified for use in Norway and are compliant whenconfigured to meet the above National requirements. Users shall ensure that DFS functionality is enabled,

    http://motorola.wirelessbroadbandsupport.com/doc.phphttp://motorola.wirelessbroadbandsupport.com/doc.phphttp://motorola.wirelessbroadbandsupport.com/doc.phphttp://motorola.wirelessbroadbandsupport.com/doc.phphttp://motorola.wirelessbroadbandsupport.com/doc.phphttp://motorola.wirelessbroadbandsupport.com/doc.php
  • 7/31/2019 CanopyRel10Notes_Issue1

    25/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page25

    maximum EIRP respected for a 20 MHz channel, and that channel spacings comply with the allocatedfrequency band to protect Road Transport and Traffic Telematics services (for example, 5735, 5755, 5775 or5835 MHz are suitable carrier frequencies). Note that for directional fixed links, TPC is not required,conducted transmit power shall not exceed 30 dBm, and antenna gain is restricted to 23 dBi (maximum of40W from the Canopy 5.7 GHz connectorized products).

    8.2.8 Brazil Notification

    For compliant operation of an AP in the 5.8 GHz band, the Equivalent Isotropic Radiated Power from thebuilt-in patch antenna and any associated reflector dish or LENS shall not exceed 36 dBm (4 W). Whenusing the passive reflector (18 dB), transmitter output power must be configured no higher than 11 dBm.When using the LENS (10 dB at 5.8 GHz), transmitter output power must be configured no higher than 19dBm.

    Important Note:This equipment operates as a secondary application, so it has no rights against harmfulinterference, even if generated by similar equipment, and cannot cause harmful interference on systemsoperating as primary applications.

    8.2.9 Labeling and Disclosure Table for China

    The Peoples Republic of China requires that Motorolas products comply with China Management Methods(CMM) environmental regulations. (China Management Methods refers to the regulationManagementMethods for Controlling Pollution by Electronic Information Products.) Two items are used to demonstratecompliance; the label and the disclosure table.

    The label is placed in a customer visible position on the product.

    Logo 1 means that the product contains no substances in excess of the maximumconcentration value for materials identified in the China Management Methodsregulation.

    Logo 2 means that the product may contain substances in excess of the maximumconcentration value for materials identified in the China Management Methodsregulation, and has an Environmental Friendly Use Period (EFUP) in years, fifty yearsin the example shown.

    Logo 1 Logo 2

    The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic andHazardous Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutatecausing environmental pollution or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2label applies to a product and all its parts. Certain field-replaceable parts, such as battery modules, canhave a different EFUP and are marked separately.

    The Disclosure table is intended to communicate compliance with only China requirements; it is not intendedto communicate compliance with EU RoHS or any other environmental requirements.

    Table 10: China Disclosure table

    (Pb)

    (Hg)

    (Cd)

    (Cr6+

    )

    (PBB)

    (PBDE)

  • 7/31/2019 CanopyRel10Notes_Issue1

    26/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page26

    SJ/T11363-2006

    SJ/T11363-2006

    8.3 RF EXPOSURE SEPARATION DISTANCES

    To protect from overexposure to RF energy, install Canopy radios so as to provide and maintainthe minimum separation distances from all persons shown inTable 11.

    Table 11: Exposure separation distances

    Module Type Separation Distance from Persons

    Canopy SM Module (FSK or OFDM) At least 20 cm (approx 8 in)

    Canopy SM Module with Reflector Dish At least 1.5 m (approx 5 ft)

    Canopy SM Module with LENS At least 50 cm (approx 20 in)

    AP Antenna of connectorized module At least 80 cm (32 in)

    The following section and itsTable 12provide details and discussion of the associatedcalculations.

    8.3.1 Details of Exposure Separation Distances Calculations and Power Compliance

    Margins

    Limits and guidelines for RF exposure come from:

    US FCC limits for the general population. See the FCC web site athttp://www.fcc.gov, and the policies, guidelines, and requirements in Part 1 of

    Title 47 of the Code of Federal Regulations, as well as the guidelines andsuggestions for evaluating compliance in FCC OET Bulletin 65.

    Health Canada limits for the general population. See the Health Canada website athttp://www.hc-sc.gc.ca/rpband Safety Code 6.

    ICNIRP (International Commission on Non-Ionizing Radiation Protection)guidelines for the general public. See the ICNIRP web site athttp://www.icnirp.de/and Guidelines for Limiting Exposure to Time-VaryingElectric, Magnetic, and Electromagnetic Fields.

    http://www.fcc.gov/http://www.fcc.gov/http://www.hc-sc.gc.ca/rpbhttp://www.hc-sc.gc.ca/rpbhttp://www.hc-sc.gc.ca/rpbhttp://www.icnirp.de/http://www.icnirp.de/http://www.icnirp.de/http://www.hc-sc.gc.ca/rpbhttp://www.fcc.gov/
  • 7/31/2019 CanopyRel10Notes_Issue1

    27/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page27

    The applicable power density exposure limits from the documents referenced above are

    10 W/m2

    for RF energy in the 5.7/5.8-GHz frequency bands.

    Peak power density in the far field of a radio frequency point source is calculated as follows:

    S=P G

    4d2

    whereS= power density in W/m

    2

    P= RMS transmit power capability of the radio, in WG= total Tx gain as a factor, converted from dBd = distance from point source, in m

    Rearranging terms to solve for distance yieldsd=

    P G

    4S

    Table 12shows calculated minimum separation distances d, recommended distances and

    resulting power compliance margins for each frequency band and antenna combination.Table 12: Calculated exposure distances and power compliance margins

    Band Antenna

    Variable d

    (calcu-lated)

    Recom-mendedSeparationDistance

    PowerComplianceMarginP G S

    5.7 GHzFSK

    Integrated 0.2 W(23 dBm)

    5.0(7 dB)

    10W/m

    2

    9 cm 20 cm(8 in)

    5

    integrated plusreflector

    0.2 W(23 dBm)

    316(25 dB)

    10W/m

    2

    71 cm 1.5 m(5 ft)

    4.5

    Integrated plusLENS 0.2 W(23 dBm) 50(17 dB) 1W/m2 28 cm 50 cm(20 in) 3.13

    5.8 GHzOFDM

    Integrated SM 0.05 W(10 dBm)

    50(10 dB)

    10W/m

    2

    6 cm 20 cm(8 in)

    10

    Connectorized AP 0.063 W(17 dBm)

    40(16 dB)

    10W/m

    2

    14 cm 80 cm(32 in)

    10

    The Recommended Separation Distance is chosen to give significant compliance margin in allcases. It is also chosen so that a given item (bare module, reflector, or LENS) always has thesame distance, regardless of frequency band, to simplify remembering and following exposuredistances in the field.

    These are conservative distances:

    They are along the beam direction (the direction of greatest energy).Exposure to the sides and back of the module is significantly less.

    They meet sustained exposure limits for the general population (not justshort-term occupational exposure limits), with considerable margin.

    In the reflector cases, the calculated compliance distance dis greatlyoverestimated because the far-field equation models the reflector as a pointsource and neglects the physical dimension of the reflector.

  • 7/31/2019 CanopyRel10Notes_Issue1

    28/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page28

    8.4 LEGAL NOTICES

    8.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 YOUUSE THE SOFTWARE OR RELATED PRODUCT, YOU ACCEPT THE TERMS OF THIS LICENSEAGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT USE THE SOFTWARE ORRELATED PRODUCT; INSTEAD, RETURN THE SOFTWARE TO PLACE OF PURCHASE FOR A FULLREFUND. THE FOLLOWING AGREEMENT IS A LEGAL AGREEMENT BETWEEN YOU (EITHER ANINDIVIDUAL OR ENTITY), AND MOTOROLA, INC. (FOR ITSELF AND ITS LICENSORS). THE RIGHT TOUSE THIS PRODUCT IS LICENSED ONLY ON THE CONDITION THAT YOU AGREE TO THEFOLLOWING TERMS.

    Now, therefore, in consideration of the promises and mutual obligations contained herein, and for other goodand valuable consideration, the receipt and sufficiency of which are hereby mutually acknowledged, you andMotorola agree as follows:

    Grant of License. Subject to the following terms and conditions, Motorola, Inc., grants to you a personal,revocable, non-assignable, non-transferable, non-exclusive and limited license to use on a single piece of

    equipment only one copy of the software contained on this disk (which may have been pre-loaded on theequipment)(Software). You may make two copies of the Software, but only for backup, archival, or disasterrecovery purposes. On any copy you make of the Software, you must reproduce and include the copyrightand other proprietary rights notice contained on the copy we have furnished you of the Software.

    Ownership. Motorola (or its supplier) retains all title, ownership and intellectual property rights to theSoftware and any copies,

    including translations, compilations, derivative works (including images) partial copies and portions ofupdated works. The Software is Motorolas (or its supplier's) confidential proprietary information. ThisSoftware License Agreement does not convey to you any interest in or to the Software, but only a limitedright of use. You agree not to disclose it or make it available to anyone without Motorolas writtenauthorization. You will exercise no less than reasonable care to protect the Software from unauthorizeddisclosure. You agree not to disassemble, decompile or reverse engineer, or create derivative works of theSoftware, except and only to the extent that such activity is expressly permitted by applicable law.

    Termination. This License is effective until terminated. This License will terminate immediately withoutnotice from Motorola or judicial resolution if you fail to comply with any provision of this License. Upon suchtermination you must destroy the Software, all accompanying written materials and all copies thereof, andthe sections entitled Limited Warranty, Limitation of Remedies and Damages, and General will survive anytermination.

    Limited Warranty. Motorola warrants for a period of ninety (90) days from Motorolas or its customersshipment of the Software to you that (i) the disk(s) on which the Software is recorded will be free fromdefects in materials and workmanship under normal use and (ii) the Software, under normal use, willperform substantially in accordance with Motorolas published specifications for that release level of theSoftware. The written materials are provided "AS IS" and without warranty of any kind. Motorola's entireliability and your sole and exclusive remedy for any breach of the foregoing limited warranty will be, atMotorola's option, replacement of the disk(s), provision of downloadable patch or replacement code, orrefund of the unused portion of your bargained for contractual benefit up to the amount paid for this Software

    License.

    THIS LIMITED WARRANTY IS THE ONLY WARRANTY PROVIDED BY MOTOROLA, AND MOTOROLAAND ITS LICENSORS EXPRESSLY DISCLAIM ALL OTHER WARRANTIES, EITHER EXPRESS OFIMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. MOTOROLA DOES NOTWARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. NO ORAL OR WRITTENREPRESENTATIONS MADE BY MOTOROLA OR AN AGENT THEREOF SHALL CREATE A WARRANTYOR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY. MOTOROLA DOES NOT WARRANTANY SOFTWARE THAT HAS BEEN OPERATED IN EXCESS OF SPECIFICATIONS, DAMAGED,

  • 7/31/2019 CanopyRel10Notes_Issue1

    29/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    Issue 1, November 2009 Page29

    MISUSED, NEGLECTED, OR IMPROPERLY INSTALLED. BECAUSE SOME JURISDICTIONS DO NOTALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES, THE ABOVE LIMITATIONS MAYNOT APPLY TO YOU.

    Limitation of Remedies and Damages. Regardless of whether any remedy set forth herein fails of itsessential purpose, IN NO EVENT SHALL MOTOROLA OR ANY OF THE LICENSORS, DIRECTORS,OFFICERS, EMPLOYEES OR AFFILIATES OF THE FOREGOING BE LIABLE TO YOU FOR ANYCONSEQUENTIAL, INCIDENTAL, INDIRECT, SPECIAL OR SIMILAR DAMAGES WHATSOEVER(including, without limitation, damages for loss of business profits, business interruption, loss of businessinformation and the like), whether foreseeable or unforeseeable, arising out of the use or inability to use theSoftware or accompanying written materials, regardless of the basis of the claim and even if Motorola or aMotorola representative has been advised of the possibility of such damage. Motorola's liability to you fordirect damages for any cause whatsoever, regardless of the basis of the form of the action, will be limited tothe price paid for the Software that caused the damages. THIS LIMITATION WILL NOT APPLY IN CASEOF PERSONAL INJURY ONLY WHERE AND TO THE EXTENT THAT APPLICABLE LAW REQUIRESSUCH LIABILITY. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION ORLIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVELIMITATION MAY NOT APPLY TO YOU.

    Maintenance and Support. Motorola shall not be responsible for maintenance or support of the software.By accepting the license granted under this agreement, you agree that Motorola will be under no obligationto provide any support, maintenance or service in connection with the Software or any application developedby you. Any maintenance and support of the Related Product will be provided under the terms of theagreement for the Related Product.

    Transfer. In the case of software designed to operate on Motorola equipment, you may not transfer theSoftware to another party except: (1) if you are an end-user, when you are transferring the Software togetherwith the Motorola equipment on which it operates; or 2) if you are a Motorola licensed distributor, when youare transferring the Software either together with such Motorola equipment or are transferring the Softwareas a licensed duly paid for upgrade, update, patch, new release, enhancement or replacement of a priorversion of the Software. If you are a Motorola licensed distributor, when you are transferring the Software aspermitted herein, you agree to transfer the Software with a license agreement having terms and conditionsno less restrictive than those contained herein. You may transfer all other Software, not otherwise having anagreed restriction on transfer, to another party. However, all such transfers of Software are strictly subject tothe conditions precedent that the other party agrees to accept the terms and conditions of this License, andyou destroy any copy of the Software you do not transfer to that party. You may not sublicense or otherwisetransfer, rent or lease the Software without our written consent. You may not transfer the Software inviolation of any laws, regulations, export controls or economic sanctions imposed by the US Government.

    Right to Audit. Motorola shall have the right to audit annually, upon reasonable advance notice and duringnormal business hours, your records and accounts to determine compliance with the terms of thisAgreement.

    Export Controls. You specifically acknowledge that the software may be subject to United States and othercountry export control laws. You shall comply strictly with all requirements of all applicable export controllaws and regulations with respect to all such software and materials.

    US Government Users. If you are a US Government user, then the Software is provided with"RESTRICTED RIGHTS" as set forth in subparagraphs (c)(1) and (2) of the Commercial ComputerSoftware-Restricted Rights clause at FAR 52 227-19 or subparagraph (c)(1)(ii) of the Rights in TechnicalData and Computer Software clause at DFARS 252.227-7013, as applicable.

    Disputes.You and Motorola hereby agree that any dispute, controversy or claim, except for any dispute,controversy or claim involving intellectual property, prior to initiation of any formal legal process, will besubmitted for non-binding mediation, prior to initiation of any formal legal process. Cost of mediation will beshared equally. Nothing in this Section will prevent either party from resorting to judicial proceedings, if (i)good faith efforts to resolve the dispute under these procedures have been unsuccessful, (ii) the dispute,claim or controversy involves intellectual property, or (iii) interim relief from a court is necessary to preventserious and irreparable injury to that party or to others.

  • 7/31/2019 CanopyRel10Notes_Issue1

    30/30

    Release 10.0 (PMP 430 ONLY) Release Notes

    General. Illinois law governs this license. The terms of this license are supplemental to any writtenagreement executed by both parties regarding this subject and the Software Motorola is to license you underit, and supersedes all previous oral or written communications between us regarding the subject except forsuch executed agreement. It may not be modified or waived except in writing and signed by an officer orother authorized representative of each party. If any provision is held invalid, all other provisions shallremain valid, unless such invalidity would frustrate the purpose of our agreement. The failure of either partyto enforce any rights granted hereunder or to take action against the other party in the event of any breachhereunder shall not be deemed a waiver by that party as to subsequent enforcement of rights or subsequentaction in the event of future breaches.

    8.4.2 Hardware Warranty in US

    Motorola US offers a warranty covering a period of 1 year from the date of purchase by the customer. If aproduct is found defective during the warranty period, Motorola will repair or replace the product with thesame or a similar model, which may be a reconditioned unit, without charge for parts or labor.

    8.5 LIMIT OF LIABILITYIN NO EVENT SHALL MOTOROLA BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY DIRECT,INDIRECT, GENERAL, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR OTHER DAMAGE

    ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT (INCLUDING, WITHOUTLIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OFBUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS, OR FROM ANY BREACH OFWARRANTY, EVEN IF MOTOROLA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.(Some states do not allow the exclusion or limitation of incidental or consequential damages, so the aboveexclusion or limitation may not apply to you.) IN NO CASE SHALL MOTOROLAS LIABILITY EXCEED THEAMOUNT YOU PAID FOR THE PRODUCT.