Canopy Tech Training v3-2 Appendices Student Guide

Canopy Technical Training Course Student Guide - Appendices
Appendices
Canopy Technical Training Course
Version 3.2
Motorola: For General Business Use. CPYTTC Appendices Version 3.2

MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. Motorola, Inc. 2005.
Appendices
A. B. C. D. E. F. G. H. I. J.
IP and RF Review GPS Fundamentals Canopy Network Examples Canopy Auto-Sense Lightning Protection Grounding Canopy Antenna Patterns Useful Formulas RMA Procedures Canopy Specifications Software Upgrade Instructions
K. Authentication Feature Key Installation L. Enabling ISM M. Calibrating Canopy Modules N. Securing Canopy Modules O. Branding Changing the GUI Logo P. Path Planning Examples Q. Vendors and RF Resources R. Example IP Addressing Tables
Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Version 3.2
Appendix A: IP and RF Review

RF Review

Version 3.2
RF Considerations, page 1
Attenuation: Not a big issue, since Canopy operates in 900 MHz, 2.4 GHz and 5 GHz bands. Still needs to be considered, because signal strength decreases as range increases. Earth Curvature: Must be added to your LOS path calculations, especially over 10 miles (16 km) Fresnel Zone Clearance: For best performance, keep the Fresnel Zone clear. Minimum clearance: 60% LOS: Most Canopy products require line-of-sight for clear transmission.

RF Considerations, page 2
Reflection & Multi-path: RF signals bouncing off objects (man-made or natural) will arrive at destination at different times. Reduce reflection & multi-path for best performance. RF Power Most Canopy modules power output is no more than 1 watt. 900 MHz modules power output is 4 watts. 900 MHz, 2.4 GHz, 5.4 GHz and 5.7 GHz offer adjustable power modules. A reflector will increase the EIRP. C/I Ratio In general, Canopy provides 3dB or lower C/I. 20 Mbps Backhaul and Advantage equipment running at 2x operations provide 8 dB or lower C/I. Consult the Canopy website for complete specifications.
Version 3.2
RF & Canopy: Collocating Units
APs and 10 or 20 Mbps BH modules can be collocated on the same tower observing the following rules: APs and BH modules should be on different bands If APs and BH-master modules are in the same band, they must be vertically separated on the structure by a minimum of 30 meters (100 feet). If an RF shield were deployed between the APs and BH-master modules, then the vertical separation could be reduced. A match on the Uplink and Downlink data and control channels can also reduce the vertical separation requirements. All Canopy AP and BH modules, even those belonging to a competitor, must be synchronized by a CMM. APs or BH-Ms cannot be collocated with SMs or BH-Ss on single band operation.
RF & Canopy: Collocating Units
APs and the Canopy 45 Mbps Backhaul can be collocated on the same tower observing the following rules: The APs and 45 Mb BH units should be mounted at least 6 feet (1.8 m) apart vertically. When the AP and the 45 Mb BH are both using the 5.7 GHz band, separate the frequencies as much as possible.
For example, use 5735, 5755 and 5775 MHz for the Canopy AP modules. Select 5800, 5806, 5812, 5818, 5824, 5830, 5836 and 5842 for the Canopy 45 Mbps Backhaul modules. Ensure there is at least 25 MHz separation between adjacent AP and 45 Mbps BH frequencies. The 45 Mbps BH has additional guidelines on angular separation between multiple backhaul units.

Version 3.2
RF & Canopy: 900 MHz, 2.4, 5.2 & 5.4 GHz

906
Select three non-overlapping frequencies for Access Point clusters Assume 8 MHz channel separation for 900 MHz systems Assume 20 MHz channel separation for 2.4, 5.2 and 5.4 systems Note, the 5.4 GHz band offers 11 nonoverlapping channels; Canopy still recommends you use 3 per cluster. Each of these frequencies can be used twice in a cluster, as demonstrated here.
924
2.4150 2.4575 2.435
915 924 906
915
2.435 2.4575
2.4150 5.325 5.485 5.535 5. 510 5.485 5.510 5.535 5.300
5.275 5.300 5.325 5.275

RF & Canopy: 5.7 GHz Frequency

5.7 GHz provides six non-overlapping ISM/U-NII frequencies for configuring Access Points, assuming a channel separation of 20 MHz. Canopy recommends you use 3 per cluster.
5.735
5.755
5.775
5.795
5.815
5.835

10
Version 3.2
IP Review

11
Canopy and IP Considerations
Canopy modules are assigned IP addresses for network management purposes. Hosts, including Canopy modules, universally are assigned unique Ethernet (MAC layer 2) addresses. Canopy, in most cases, appears like a Layer 2 switch and is transparent to layer 2 protocols including DHCP, PPPoE, VPN, etc.

12
Version 3.2
Canopy Module IP Addressing
Needed to address Access Points, Backhaul modules and other network devices Used internally by each Access Point to address Subscriber Modules May be used to directly access Subscriber Modules from the AP side via IP routing Requires a network administrator to assign each IP address Can use private (not-routable) IP addresses (preferred, as security feature)

13
Canopy IP Addressing: Subnet Allocation
Each Canopy module requires one IP address on the network for management. Subscriber Modules may be configured to not take up IP address space (no public IP address). Canopy modules IP addresses should not be routable over the Internet. Canopy modules IP addresses should not share the same subnet as your users allocated IP address space. Canopy modules IP addresses are only used for module management by network operators.
14
Version 3.2
Canopy MAC Address Table
4096 MAC addresses can be stored by each AP and 4096 MAC addresses can be stored by each SM
Actually the table contains two MAC addresses of the same value with the first digit of one set to 0 and the other set to 1. The first MAC address 0x-xx-xx-xx-xx-xx represents the Ethernet interface. The second MAC address 1x-xx-xx-xx-xx represents the RF link (used internally) . The 4096 includes:
The AP address The SM address MAC addresses of SMs registered to an AP MAC addresses of all devices attached to SMs via MAC bridging
15
Canopy MAC Address Table
User gateways (i.e. Linksys Box) allow for large networks to be attached to each Subscriber Module (NAT, Firewalls, etc.). Canopys NAT (Network Address Translation) feature allows networks to be attached to each Subscriber Module and provides a firewall function, preventing devices attached to one Subscriber Module from seeing devices on another Subscriber Module. The Subscriber Module acts as a Traffic Director: The Subscriber Module will decide if traffic generated by a device attached to it is destined for another device on the same network.
If it is, it is directed to the destination device. If not, it is directed over the wireless link.
This prevents unnecessary traffic over the RF link.

16
Version 3.2
SM Bridging
IP Network
CMM
AP
Other traffic Network Traffic
This example shows that network traffic addressed to equipment behind SM #3 is delivered to that destination. Local traffic, generated from and addressed to devices on the same network behind SM-3, is delivered locally without being routed to the AP. Other traffic, not addressed to any equipment behind any of the SMs depicted here, is not routed to those modules.
SM-3 SM-1 SM-2

Router
Local traffic
17
Canopys Default IP Address
All Canopy modules (Subscriber Modules, Access Points and Backhauls) have the default IP address 169.254.1.1. For a computer to talk to Canopy, as it comes from the factory, either of the following conditions must be met:
If the computer is not configured for DHCP, then it has to have a static IP address on the 169.254 network (i.e. 169.254.1.5). If the computer is configured for DHCP, then it will automatically obtain an IP address on the 169.254 network after a minute or two, as long as it is not connected to the network.

18
Version 3.2
Appendix B: GPS Fundamentals

19
GPS Fundamentals

20
Version 3.2
10
GPS Fundamentals
NAVSTAR The NAVigation Satellite Timing and Ranging (NAVSTAR) GPS is an all weather, radio based, satellite navigation system that enables users to accurately determine 3-dimensional position, velocity, and time worldwide. The overall system consists of three major segments: the space segment, the ground control segment, and the user segment. Space Segment The space segment is a constellation of satellites operating in 12hour orbits at an altitude of 20,183 km (10,898 mi). The constellation is composed of 24 satellites in six orbital planes, each plane equally spaced about the equator and inclined at 55 degrees.
21
GPS Fundamentals
Ground Segment The ground control segment consists of a master control center and a number of widely separated monitoring stations. The ground control network tracks the satellites, precisely determines their orbits, and periodically uploads almanac ephemeris and other system data to all satellites for retransmission to the user segment. User Segment The user segment is the collection of all GPS user receivers (such as the Motorola Oncore GPS Receiver used in the CMM) and their support equipment.
22
Version 3.2
11
GPS Fundamentals
Navigation with the receiver is accomplished by passive multilateration. More simply, the GPS receivers position is determined by the geometric intersection of several simultaneously observed ranges (satellite to receiver distances) from satellites with known coordinates in space. The receiver measures the transmission time required for a satellite signal to reach the receiver. Transit time is determined using code correlation techniques. The actual measurement is a unique time shift for which the code sequence transmitted by the satellite correlates with an identical code generated in the tracking receiver. The receiver code is shifted until maximum correlation between the two codes is achieved.

23
GPS Fundamentals
This time shift multiplied by the speed of light is the receivers measure of the range to the satellite. This measurement includes various propagation delays, as well as satellite and receiver clock errors. Since the measurement is not a true geometric range, it is known as a pseudorange. The receiver processes these pseudorange measurements along with the received ephemeris data (satellite orbit data) to determine the users three-dimensional position. A minimum of four pseudorange observations are required to mathematically solve for four unknown receiver parameters (i.e., latitude, longitude, altitude, and clock offset). If one of these parameters is known (for example, altitude fixed) then only three satellite pseudorange observations are required and thus only three satellites need to be tracked.
24
Version 3.2
12
GPS Fundamentals
GPS NAVIGATION MESSAGE The GPS navigation message is the data supplied to the user from a satellite. The navigation message consists of a 50 bit per second data stream containing information enabling the receiver to perform the computations required for successful navigation. Each satellite has its own unique code that provides satellite identification for acquisition and tracking by the user.

25
Appendix C: Canopy Network Examples

26
Version 3.2
13
Canopy Network Examples

Potential New Fire House, Prior to the End of 2003 Could Connect to #8 Training Center to Hop Back to #6 HQs if #8 to #6 is Full Duplex and No Line of Sight is Available to #6 Tower or 68th & Dover Hill Tower
Two, Tsunami 10 Mbps Full Duplex Radios: B2 / B2 5.834 GHz Two, 2' Parabolic Antennas, Focused in an Offset, Opposing Direction.
FD
Four, Motorola; Canopy Radios, with a Cluster Management Module. Motorola Channel 4 is Optimized, Motorola Channel 1 has a 7 MHz spread with B1 Rx and Motorola Channel 3 has a 7 MHz Overlap with the 4' focused Proxim Tx Beam. Motorola Channel 2 Should NOT be used on this tower. Any overlap should occur on Proxim Tx
FD
Fire House #7 Zone #1 CH #4 Zone #2 CH #1
FD
FD
Fire House #5
High Bandwidth Applications
Fire House #3
Back Haul High Bandwidth Requirement
FD
Fire House #8 Training Center High Bandwidth Requirements Point-toPoint Proxim Tsunami 10 Mbps Full Duplex 5.8 GHz Vertical Position, No Motorola Present, Separated Channel from other Tsunami at #6
Tsunami 10 Mbps Full Duplex B1 Radio 5.772 GHz 2' Parabolic Antenna #8 Roof has Clear LOS to: #6 Taller Tower and 68th & Dover Hill Tower
Zone #3 CH #4
FD
Radio tower
FD
68th & Dover Hill Tower Zone #4 CH #3
Fire House #4
Tsunami 10 Mbps Full Duplex B1 Radio 5.772 GHz 4' Parabolic Antenna to Focus Beam as Low -on the tower- as possible with Clear LOS to #6's, 2' Parabolic High on Tower
Fire House #6 HQ Two Towers
FD
Fire House #2 No Line of Site to Hill Tower or #6 Tower
Point-to Point Proxim Tsunami 10 Mbps Full Duplex 5.8 GHz on a Separated Channel, in the Horizontal Position, Low on the Tower to Create as Much Frequency Separation, from The Motorola, as Possible
FD
Fire House #1
N W S E

27
Canopy Network Examples

28
Version 3.2
14
Appendix D: Canopy Auto-Sense

29
Canopy Auto-Sense
Auto-sense of CAT 5 cable capability on a Canopy module can be determined as follows: Check the circuit board revision: With the CAT 5 port pointing down, the board revision is located on the right side of the circuit board next to the metal shield. It typically looks like "ISS G 5.7 GHz" or "ISS B 5.2 GHz". There have only been 2 revisions of the 5.2 GHz boards, Revisions A and B.
30
Version 3.2
15
Canopy Auto-Sense
22 - 5.2 Rev B prototype boards were produced with ESN 0a003e001dc7 - 0a003e001ddc. 5.2 Rev B production units begin at ESN 0a003e0021c9. Everything prior to Rev B prototypes are Rev A and do not auto-sense. In Summary: 5.2 Rev A - no auto-sense. 5.2 Rev B - auto-sense.

31
Canopy Auto-Sense
In the 5.7 GHz platform there have been more releases of the circuit board (A - G). 18 - 5.7 GHz Rev F prototype modules were produced with ESN 0a003ef00f7a - 0a003ef00f8b. 5.7 GHz Rev G production modules begin at ESN 0a003ef00f8c. Everything prior to Rev E prototype modules do not autosense.

32
Version 3.2
16
Canopy Auto-Sense
Prototype modules should not be encountered in the field. In summary: 5.7 Rev A through Rev E - no auto-sense. 5.7 Rev F & G - auto-sense.

33
Appendix E: Lightning Protection - Grounding

34
Version 3.2
17
Lightning Protection - Grounding
Outdoor ground considerations: Masts, Towers Transmission lines Outdoor cabinets All cables entering or leaving a structure Indoor ground considerations: Equipment racks, other radio equipment

35
Lightning protection: Cables entering or leaving a building Data interface cables Masts, Towers Radios Transmission lines Canopy radios should be mounted .609 meters or 2 feet below the top of the tower or mounting structure Lightning rods must not be mounted directly to Canopy radios Lightning arrestors should be installed at intervals from the top of the mounting structure to the cable and power entrance of the building

36
Version 3.2
18
NOTES ON LIGHTNING PROTECTION A properly designed lightning protection system provides a path for lightning current to travel. The system neither attracts nor repels a lightning strike, but simply intercepts and guides the current harmlessly to ground. A lightning protection system is generally made up of several components. Air Terminals: (lightning rods etc.): Inconspicuous slender rods installed on a roof or tower as defined by industry standards. In some cases, these rods are placed on a tower leg opposite to the one on which the radio(s) is mounted. This is to direct the lightning strike away from the equipment.
37

Conductors: Aluminum or copper cables that interconnect the air terminals and the other system components such as copper grounding plates. Ground Terminations: Metal rods driven into the earth to guide the lightning current harmlessly to ground (usually steel with copper cladding). Surge Arrestors and Suppressors: Devices that are installed in conjunction with a lightning protection system to protect electrical wiring and electronic systems and equipment. These devices should be installed at intervals along the leg of a tower (or as designated by the tower owner), and at the point of entrance of the cable into a building.
38
Version 3.2
19
A lightning protection system is designed to control or redirect a lightning strike on a specified path. The system does not prevent a strike, but provides a path on which the electrical current can safely be directed to ground. A properly designed lightning protection system will not attract a bolt of lightning. Designing a grounding system prior to installing radios, antennas or other equipment on a roof or tower structure is critical to minimize the possibility of damage to equipment and serious injury to personnel.
39
When in doubt, consult local and national electrical codes or contact an electrician or professional trained in the design of grounding systems.

40
Version 3.2
20
Canopy SM Antenna Grounding Per NEC Specifications

Canopy SM SM Mounting Bracket 10 AWG Cu Grounding Conductors Per NEC 810-21
Canopy Surge Suppressor 300SS
CAT-5 Outdoor
Computer
Canopy 24 VDC Wall Mount
Power Service Panel
Power Service Ground Electrode or 8 foot ground rod

41
Appendix F: Canopy Antenna Patterns

42
Version 3.2
21
Canopy Antenna Patterns

Azimuth Constant Power Footprint

43
CANOPY 5250-5350 MHz Antenna Pattern/ ERP - Azimuth 30 dBm

120 60
20 dBm
150
10 dBm 0 dBm -10 dBm
30
180
210
330
240
300 270 44
Version 3.2
22
CANOPY 5250-5350 MHz Antenna Pattern/ ERP - Elevation 30 dBm

120
20 dBm 10 dBm
60
150
30
0 dBm -10 dBm
180
210
330
240 270
300 45
Appendix G: Useful Formulas

46
Version 3.2
23
Useful Formulas
Calculation For Antenna Down Tilt

47
Useful Formulas
Calculation For AP Coverage

48
Version 3.2
24
Useful Formulas
Fresnel Zone = 72.1 * SqrRoot (D1Mi * D2Mi / FreqGHz * DTMi) Where D1,D2 = miles DT=D1+D2 F=frequency GHz

49
Useful Formulas
See formula on next slide

50
Version 3.2
25
Useful Formulas
System Operating Margin (SOM)

Free Space Loss = 20Log10(F in MHz) + 20Log10(D in Miles)+36.6
Rx Signal Level = Tx Power - Tx Cable Loss + Tx Antenna Gain FSL + Rx Antenna GainRx Cable Loss System operating Margin (Fade Margin) = Rx Signal Level - Rx Sensitivity

51
Appendix H: RMA Procedures

52
Version 3.2
26
RMA Procedures
The Canopy RMA process consists several steps 1. End User, ACSP or ACR
determine that a problem exists if practical, field test unit to determine the source of the problem and correct if possible request an RA or RMA from a Canopy Distributor logs claim and tests unit to verify problem requests an RMA from Motorola Canopy returns defective product for repair or replacement
2. Distributor

53
RMA Procedures
End User, ACSP, ACR 1. Determine a problem exists
If the End User, ACSP or ACR has determined that a Canopy product has a problem, it is recommended that an attempt be made to diagnose and/or correct the fault using the procedures outlined in the Troubleshooting section of this course
2.
Request an RA or RMA from Canopy Distributor

Return Canopy unit to Distributor Note: If it is determined that Canopy defect was caused by improper installation or use unit warranty is void.

54
Version 3.2
27
RMA Procedures - Distributor

Distributor Receive defective Canopy unit from End User, ACSP or ASR Log claim and test Canopy unit to verify problem Request RMA from Canopy CBW group Return defective unit for repair or replacement

55

Fill out Motorola Canopy RMA Request form with the following required information: Distributor information Resellers information (if applicable) End Users information This information is needed in case Canopy staff needed to contact operator for specifics on problem that was observed with device. If information is not provided then distributor must have information on record and provide to Canopy if requested. Issue Code for each device Is it an out-of-box or in-service issue Issue description for each device
56
Version 3.2
28

Model number for each device Electronic Serial Number for each device OR Mechanical Serial Number for each device. If ESN is only given then distributor may have to contact Canopy to verify warranty status. Mechanical Serial Number of the replacement device Request RMA from Motorola Canopy by forwarding completed request form to warranty@canopywireless.com. RMA request will be denied if form is not completed in full. RMA number received is valid for 60 days. If the warranty claim is not received within 60 days the RMA will be cancelled. Ship warranty claims to Motorola Warranty Center

57

Receive replenishment equipment from Motorola Warranty Center. Replenishment equipment will be shipped to the ACD once a month based on the RMA requests received and approved up till one (1) business week before the replenishment shipment day. The replenishment shipments will be shipped on the 15th of the month or the first business day after the 15th in the case of a weekend or holiday. ACD may request out-of cycle replenishment shipment in situations where distributor stock is abnormally low or RMA requests are abnormally high. Requests should be made, in writing via email to the Canopy Warranty Coordinator.
58
Version 3.2
29
Appendix I: Canopy Specifications

59
Canopy Specifications
Up to date specifications for the entire Canopy family of products are maintained on the Canopy website. www.motorola.com/canopy Access the Product Info menu, then select Tech Specs.

60
Version 3.2
30
Appendix J: Upgrading Canopy Software

61
Recommended Upgrade Approach

Effective with Canopy Software Release 6.1, Canopy strongly recommends that operators use the Canopy Network Updater Tool (CNUT) for performing all Canopy upgrades. CNUT ensures that networks are upgraded in a logical sequence, especially in consideration of enabling the hardware scheduler feature. Download CNUT from the Canopy website, www.motorola.com/canopy, by accessing the Support menu, then Software Updates. Details on using CNUT can be found in the latest copy of the Canopy software Release Notes. Manual upgrade procedures are provided here as a reference, in situations where operators are upgrading to a software release earlier than release 6.1.
62
Version 3.2
31
Upgrading Canopy Software
Canopy software upgrades use FTP for file transfer and Telnet to process the upgrade files. Telnet and FTP should only be used for upgrading software or as indicated by Technical Support or in Canopy Technical Release Notes. Any other use of these utilities, not authorized by Canopy Technical Support, is not supported and may result in erratic module performance.

63
Software Upgrade Options

Standard Upgrade Procedures Canopy software upgrades are released periodically and can be downloaded from the Canopy web site at http:\www.motorola.com\canopy. Subscriber Modules can be updated automatically or manually (effective with software release 4.1). Access Point modules must be upgraded manually. Backhaul Modules must be upgraded manually. We will walk through the automatic upgrade process first, followed by the manual process.
64
Version 3.2
32
Automatic Upgrade Procedures: SMs
SMs must be running release 4.0.x to be auto-updated. SMs running release 3.x will not auto-update.
FTP the appropriate files into an AP (including the action list that comes with the software release). Use FTP to transfer the correct APboot.bin or APASboot.bin software to the AP. Also transfer FPGA and boot software (if required). Telnet to the AP module to issue commands to burn in the new software, then reboot. Use FTP to transfer the correct SMboot.bin to the AP, and FPGA (if required). Telnet to the AP to start the SM update function.
65
When an SM registers to that AP, the SM software version is checked. If the SM is not up to the current release, the SM is updated automatically. Leave auto-update running long enough to catch all SMs (including ones that are powered off overnight). Monitor the status of SMs and confirm all SMs on the AP have been updated. Start a second Telnet session to the AP to turn off updating (the first Telnet session is not directly interruptible at this point). NOTE: This procedure can take up to four minutes per SM to complete, so schedule the update for a time that is least likely to affect the end user.

66
Version 3.2
33
Important considerations: The action list and program files are stored in volatile memory in the AP. If the AP is rebooted before all SMs have upgraded, the action list and program files will be deleted. If this happens, those files must be reinstalled to complete the upgrade of all SMs. After the update command is given, the AP uses information from the action list to manage updates with up to four SMs at any one time, progressing through all registered SMs until all are updated. The update function continues to run on the AP, updating any new SMs that may register, until the update is turned off.
67
SM Auto-Update Example
The following example shows the command line prompts, inputs and responses while two SMs are updated from an AP. In this example, the AP has an address of 172.16.1.1. SMs are registered to the AP.
FTP SMboot.bin, FPGA, and action list to AP <Is 062403_D40.jbc APASboot.bin BH10boot.bin SMboot.bin 41actionlist.txt APboot.bin BH20boot.bin >ftp 172.16.1.1 Connected to 172.16.1.1. 220 FTP server ready Name (172.16.1.1:user): 331 Guest login ok Password: 230 Guest login ok, access restrictions apply. Remote system type is Type: ftp> binary 200 Type set to 1.

68
Version 3.2
34
SM Auto-Update Example, contd

ftp> put SMboot.bin local: SMboot.bin remote: SMboot.bin 500 EPSV: command not understood. 227 Entering Passive Mode (172,16,1,1,4,1) 150 Opening BINARY mode data connection for SMboot.bin 100% |*************************************| 712 KB 229.55 KB/s 00:00 ETA 226 Transfer complete. 729668 bytes sent in 00:03 (209.57 KB/s) ftp> put 062403_D40.jbc local: 062403_D40.jbc remote: 062403_D40.jbc 227 Entering Passive Mode (172,16,1,1,4,2) 150 Opening BINARY mode data connection for 062403_D40.jbc 100% |*************************************| 156 KB 219.48 KB/s 00:00 ETA

69

226 Transfer complete. 159859 bytes sent in 00:00 (156.18 KB/s) ftp> put 41actionlist local: 41actionlist remote: 41actionlist ftp: local: 41ctionlist: No such file or directory ftp> put 41actionlist.txt local: 41actionlist.txt remote: 41actionlist.txt 227 Entering Passive Mode (172,16,1,1,4,3) 150 Opening BINARY mode data connection for 41actionlist.txt 100% |*************************************| 53.58.81 KB/s 00:00 ETA 226 Transfer complete. 53 bytes sent in 00:00 (0.25 KB/s) ftp> exit 221 Goodbye.

70
Version 3.2
35

Telnet to the AP and start the SM update function > Telnet 172.16.1.1 Trying 172.16.1.1 Connected to 172.16.1.1. Escape character is ^]. /---------\ CANOPY Motorola Broadband Wireless Technology Center (Copyright 2001, 2002 Motorola Inc.) Telnet+> update 41actionlist.txt

71

Action List Contents: @BS SMboot.bin @BH 062403_D40.jbc @PR NOP @XX NOP The information from the AP is read: 12.49.13 UT : 11/10/03: AutoUpdate currently active using 41actionlist.txt Software Version: CANOPY4.1 Nov 04 2003 10:38:27 FPGA Version: 06240308 SNMP Site Name: No Site Name SNMP Site Location: No Site Location

72
Version 3.2
36

Update of the first SM begins. Current information is read from the AP, and the SM is told to manage its update. During the update the SM continues to handle traffic, until it is booted at the end of the process. Access to the modules user interface pages may terminate, because they have lower priority than traffic. The SM is still active: 12:49:17 UT : 11/10/03 : Started update of 0a-00-3e-00-29-56 Software Version : CANOPY4.0 May 28 2003 13:15:22 Software Boot Version : Indeterminate FPGA Version : 04290308 SNMP Site Name : No Site Name SNMP Site Location : No Site Location SM powers up in alignment mode

73

Start a second Telnet session to the AP to turn off updating after you have confirmed the desired SMs are updated. Open a separate Telnet session to the AP: > telnet 172.16.1.1 Trying 172.16.1.1 Connected to 172.16.1.1. Escape character is ^]. /---------\ CANOPY Motorola Broadband Wireless Technology Center (Copyright 2001, 2002 Motorola Inc.) Telnet+> updateoff 41actionlist.txt Back on the original Telnet session: 13:15:40 UT : 11/10/03 : AutoUpdate currently Disabled. Telnet +>
This completes the automatic upgrade instructions and example.

74
Version 3.2
37
Manual Upgrade Procedures
Download the upgrade procedures and files from the Canopy web site. Unzip the files from the download to find the release notes as well as a number of individual files specific to each Canopy module. Place these module-specific files in a directory that is easily accessible by FTP for file transfer. Updates can be performed via the wireless link no need to physically access each unit. (No truck rolls!)

75
Manual Upgrade Operations
File Transfer Protocol (FTP) and Telnet are the two programs used for the upgrade process. Software is uploaded to each module via FTP. The upgrade is completed via a Telnet session on the module.

76
Version 3.2
38
Canopy Software and Processors
The two processors in a Canopy module each run their own software. Release 4.0 marks the first time the main processors boot software has changed. The modules Status page now lists the software boot version. Module types and activated features are not changed during an upgrade. You cant change an AP into an APAS (an AP whose Authentication Mode has been turned on using a purchased Feature Activation Key). By attempting to apply the APAS software, you will receive an error message and the software wont be applied. Similarly, you cannot change an APAS into an AP or a BH20 into a BH10, or a BH10 into a BH20.

77
Upgrade each point-to-point link in the network. A point-to-point link is made up of one Backhaul Timing Master and one Backhaul Timing Slave. Choose an Access Point cluster to upgrade. Upgrade all Access Point modules in that cluster (1-6 modules). Next, systematically upgrade each of the Subscriber Modules registered with the newly upgraded cluster. When all Subscriber Modules have been upgraded, move on to the next Access Point cluster.

78
Version 3.2
39
Accessing Subscriber Modules on the Network Subscriber Modules can be set to use either local or public IP addresses on their Configuration page. Subscriber Modules set to use public IP addresses can be directly accessed by an Access Point. Subscriber Modules set to use local IP addresses require the following procedures to upgrade them over the air from an Access Point module. The Access Point module must be upgraded before the Subscriber Module upgrade begins.
Check the Private IP address on the Access Point module using the Configuration page of the web-based interface. (The default is 192.168.101.1) From a command line on a computer attached to the same network as the Access Point module, change directories to the directory where the upgrade files are located. FTP the files to the Access Point module via its LAN IP address. Telnet to the Access Point module. At the prompt type in the command ftp nnn.nnn.nnn.<LUID> (where nnn.nnn.nnn is the first 3 octets of the Private IP address for the Access Point).

79
This starts an FTP session from the Access Point module to the Subscriber Module whose LUID is the number that you placed in the last octet of the private IP address in the FTP command. For example, if a Subscriber Module is registered to the Access Point and receives an LUID 8, then the SM IP address is 192.168.101.8.

80
Version 3.2
40
Manual Upgrade Example

Using the file transfer protocol (ftp), copy the appropriate boot.bin file and, if necessary, xxxxxx.jbc file for the FPGA, to the Canopy module. IP address 169.254.1.1 is the default address of all Canopy modules; your IP address may be different. A sample FTP session follows:
> ftp 169.254.1.1 Connected to 169.254.1.1 220 FTP server ready Name (169.254.1.1:none): <enter> 331 Guest login ok Password: <enter> 230 Guest login ok, access restrictions apply. ftp> binary 200 Type set to I ftp> put <XX>boot.bin (where XX is the prefix of the file, e.g., SMboot.bin) ftp> put block.bin ftp> put xxxxxx_Dxx.jbc (e.g., 062403_D40.jbc) ftp> quit 221 Goodbye

81
Manual Upgrade Example
Using the Telnet protocol, connect to the Canopy module. The default IP address of Canopy modules is 169.254.1.1; your IP address may be different. The results of a typical Telnet session follow:
> telnet 169.254.1.1 Trying 169.254.1.1 Connected to 169.254.1.1 Escape character is ^]. /---------\ C A N O P Y Motorola Broadband Wireless Technology Center Telnet> burnfile Updating Boot Block with file: block.bin Programming Boot Block Success Burn Boot from file: Validating Boot File
82
Version 3.2
41
Manual Upgrade Example, contd

File Checksum OK 047621D6 Updating Boot Block ALT_BOOT_ADR to 000A0000 Updating Alt Boot Burn Alt File Burn OK Lock Alt OK Validating Alt Boot Erasing Boot Copying Alt Boot to Boot File Burn OK Locking Alt Boot Telnet> reset
83
Manual Upgrade Example, contd

If it becomes necessary to upgrade the FPGA software then repeat the previous Telnet step, executing the xxxxxx.jbc file to the Canopy module as demonstrated below.
Telnet> jbi aprogram xxxxxx_Dxx.jbc (example: 062403_D40.jbc) Jam STAPL Byte-Code Player Version 2.1 Copyright 1998-2000 Altera Corporation Device #1 Silicon ID is A98(01) Erasing EPC device(s) Programming EPC device(s) Verifying EPC device(s) DONE Exit code = 0 Success Telnet+> fpga_conf (Connection closed by foreign host)
This message may or may not appear on your screen. Refer to the network connection in your systray. The module is now successfully upgraded.
84
Version 3.2
42
Appendix K: Authentication Feature Key Installation

85
Authentication Feature Key Installation
Access Points that are to be managed by the Bandwidth Authentication Manager program must be initially enabled with an optional feature key that is keyed to each APs ESN. To obtain these keys, contact your local Canopy distributor and request an APAS form. Fill in the required information and return to your distributor with the appropriate fees. Upon receipt from your distributor, Motorola Canopy Division will generate a special key for each AP requested and will email the keys directly to you. Upon receipt of your keys, upgrade the APs using the procedure outlined on the following slides.
86
Version 3.2
43
Save the key files on the network where they will have IP connectivity to the APs. Double click on the key file identified by the last five characters of the ESN of the AP to be upgraded. The key file will auto-execute to IP address of 169.254.1.1 and modify the module. A browser window will pop up showing the conversion on the Status screen. The device type will now be listed as APAS. Reboot the module. When the module comes up it will display several extra radio buttons on the Configuration page for authentication.
87
The last four digits of the modules MAC address is embedded in the key file name. For example: KEYAPAS005D70 If your AP modules are not set to the factory default IP address 169.254.1.1, then right click on the file name and go to the properties section. You can modify the IP address the key file will seek out by changing the IP address located in the URL file section.

88
Version 3.2
44
Appendix L: Enabling ISM

89
Enabling ISM
Prior to software release 4.0, Canopy modules operating in the 5.7 GHz band only used channels in the U-NII band. Software release 4.0 added additional channels in the ISM band. As a consequence, Canopy modules that were not shipped with software release 4.0 do not have the ISM channels enabled by default. To enable ISM channels on 5.7 GHz Canopy modules, access the ISM web page on the module using the following URL: http://169.254.1.1/ism.html (using whatever IP address applies to the module). Read the notice on the screen. Check the box Enable ISM Frequencies. contd

90
Version 3.2
45
Enabling ISM
Click Save Changes. Click Reboot. The module will reboot and the ISM frequencies will now be available on the Configuration screen. Obtain the appropriate FCC compliance stickers from Canopy Technical Support. Apply the FCC compliance stickers over the FCC ID label found above the module MAC address, illustrated in the following slide.

91
Enabling ISM FCC ID Sticker Replacement
FCC ID

92
Version 3.2
46
Appendix M: Calibrating Canopy Modules

93
Calibrating Canopy Modules
Software release 4.0 offers more improvement in RSSI stability and offers the ability to read the power level in dBm on a Canopy module. Module calibration improves reported measurement of RSSI and allows reporting of the power level in dBm, but does not affect or improve module operation or performance. Modules shipped from the factory with release 4.0 installed will be calibrated. Currently deployed modules can be calibrated using data that was recorded at the factory during manufacture and is available for you to enter in the modules. Following are the steps to enter calibration data into the modules.

94
Version 3.2
47
Calibrating Canopy Modules

Make a list of the MAC addresses (Electronic Serial Numbers) of the Access Points, Subscriber Modules and Backhaul Modules you want to calibrate. Go to http://www.canopywireless.com/calibrate.php and enter the MAC addresses previously recorded, along with the specified contact information, including email address. An email containing the factory calibration data, three values per MAC address, will be sent to you automatically. Prior to calibration, the modules must be upgraded to Release 4.0. You must upgrade first before you enter calibration data. When entering calibration data into an AP, BH or SM, go to the modules Calibration web page, which is http://ip-address/mac.html, where ipaddress is the IP address assigned to the module. Enter the three calibration values: Measured RSSI, Radio Slicing Value, and Power Level. The Power Level is entered with a minus sign. Click Store Calibration Settings to Flash, then click Reboot.
95

Calibrating Canopy Modules Notes
It is not possible to change the MAC address and Tx Calibration Constant. These were set and locked at the factory. The calibration settings can be changed, if you have entered them incorrectly. On calibrated modules, the RSSI value on the Status page will be displayed in black instead of red, indicating it is now a calibrated value. Also, next to the RSSI value, the power level in dBm will be displayed. Additionally, the temperature of the module can now be read through SNMP, or by going to the Extended Stats page and then selecting the Status page. The temperature displayed is the internal temperature of the module.

96
Version 3.2
48
Appendix N: Securing Canopy Modules

97
Securing Canopy Modules

Canopy software release 4.0 supports a new feature that allows Canopy modules to be locked to prohibit access to the management functions of the module. Locking the modules requires a truck roll (driving to the site), inserting a Canopy default plug and then enabling this feature. Disabling the feature requires another truck roll, inserting a Canopy default plug and disabling this feature. Once the module is locked, it will pass traffic but cannot be managed, monitored or upgraded!

98
Version 3.2
49
Securing Canopy Modules
Carefully read the message on the screen. Check the box Lock System Configuration. Click Save Changes. Click Reboot. Remove the Canopy default plug. The module will reboot and the module will be locked.

99
Appendix O: Branding Changing the GUI Logo

100
Version 3.2
50
BRANDING (Changing the GUI Logo)

On each Canopy module, the web-based interface screens have a Canopy logo that can be replaced with an operators company logo. The Canopy logo file is called canopy.jpg and the replacement file must also be called canopy.jpg. The new file is transferred via FTP to the module and then added to a special filesystem through a telnet session. The following commands can be used during a telnet session: addwebfile add a custom logo file to the file system clearwebfile clear the customer logo file from the file system lsweb list the custom logo file and display the storage space available on the file system

101

Copy your custom logo file to the name canopy.jpg on your system. Use an FTP session to transfer the new canopy.jpg file to the module. Example session shown here: > ftp ModuleIPAddress Connected to ModuleIPAddress 220 FTP server ready Name (ModuleIPAddress:none): root 331 Guest login ok Password: <password-if-configured> 230 Guest login ok, access restrictions apply. ftp> binary 200 Type set to I ftp> put canopy.jpg ftp> quit 221 Goodbye
Distinctive fonts indicate: Literal user input Variable user input Literal system response Variable system response

102
Version 3.2
51
Use a telnet session to add the new canopy.jpg file to the file system. Example shown here:
>telnet ModuleIPAddress /---------\ C A N O P Y Motorola Broadband Wireless Technology Center (Copyright 2001, 2002 Motorola Inc.) Login: root Password: <password-if-configured> Telnet+> lsweb Flash Web files /canopy.jpg 7867 free directory entries: 31 free file space 56468

103
Telnet+> clearwebfile Telnet+> lsweb Flash Web files free directory entries: 32 free file space: 64336 bytes Telnet +> addwebfile canopy.jpg Telnet+> lsweb Flash Web files /canopy.jpg 7867 free directory entries: free file space: 55331 Telnet +> exit
31

104
Version 3.2
52
BRANDING (Configure a Hyperlinked Logo)

Starting with Canopy system release 4.2, you can add a URL hotlink to the logo that displays at the top of the Canopy screens. This can be a link to your own support page, a test page, or whatever other URL makes sense for your situation. The following pages outline the steps required to implement this change.

105
Browse to http://ModuleIPAddress/top.html. Select View as source in your web browser and save a copy of the file locally. In the html editor of your choice, open the file top.html. Find the expression <a href=http://www.canopywireless.com and change the address to the destination URL that is desired. Change the canopy.jpg reference within the file to your logos file name. Save the file as top.html. Use FTP and Telnet sessions to transfer the top.html file and your logo file to the Canopy module, as shown on the following pages.

106
Version 3.2
53

Example FTP session to transfer updated files to the Canopy module (using sample file name logo.jpg: > ftp ModuleIPAddress Connected to ModuleIPAddress 220 FTP server ready Name (ModuleIPAddress:none): root 331 Guest login ok Password: <password-if-configured> 230 Guest login ok, access restrictions apply. ftp> binary 200 Type set to I ftp> put logo.jpg ftp> put top.html ftp> quit 221 Goodbye

107
Use a telnet session to add the new logo file to the modules file system. Example shown here, using file name logo.jpg:
>telnet ModuleIPAddress /---------\ C A N O P Y Motorola Broadband Wireless Technology Center (Copyright 2001, 2002 Motorola Inc.) Login: root Password: <password-if-configured> Telnet+> Telnet+> Telnet+> Telnet+> clearwebfile addwebfile logo.jpg addwebfile top.html lsweb

108
Version 3.2
54
Flash Web files /logo.jpg 7867 /top.html 313 free directory entries: 32 free file space: 64336 bytes Telnet +> exit

109
Appendix P: Path Planning Examples

110
Version 3.2
55
Verify Line of Sight
There are a number of ways to verify line of sight between objects:
Drive the path Fly the path Measure height of suspect obstructions Use terrain database software or mapping software Refer to topographical maps Topographical software Aeronautical charts
Following are several examples of tools available for line of sight verification.

111
Street Maps
Easy to use but provides limited information for RF planning
Determine the locations of each site Draw a line between the two locations Measure the distance with a scale
Step 4

112
Version 3.2
56
Topographic Maps
Step 4
Provides information derived from different datum

NAD27 WGS84 NAD83
Provides Magnetic offset from true North Contour lines provide details about terrain Topographic maps provide more accurate scale
113
Aeronautical Charts
Step 4
Also called Sectionals Updated frequently Useful for locating tall buildings and towers Details airspace around airports Must account for magnetic offset Subtract for East Add for West
114
Version 3.2
57
Web-Based Maps
Step 4
Some Web-based map programs allow entry of GPS coordinates for the location in question Some Web-based map programs provide GPS coordinates of the location in question

115
Path Planning Software
Step 4
Path Planning Software often uses a satellite based terrain database Popular Path Planning Software Programs EDX Micropath Pathloss RadioMobile Numerous other programs are available ranging in price from hundreds to thousands of dollars

116
Version 3.2
58
Map Software
Step 4
Microsoft Streets and Trips DeLorme Street Atlas Other computer based map software

117
DeLorme Topo Tools
Step 4

118
Version 3.2
59
Use Visual Confirmation
Step 4

119
Determining the Elevation and Height of Obstacles

Use Inclinometer to determine height
Step 4
Use GPS altimeter
Count the number of floors in a building. Each floor is approximately 3.6-4.5 m or 12 15 feet in height
120
Version 3.2
60
Using an Inclinometer
Step 4

121
Appendix Q: Vendors and RF Resources

122
Version 3.2
61
Vendors and RF Resources
Maps, Charts and Misc. Stuff Delorme (3D mapping), TOPO USA, TOPO TOOLS http://www.delorme.com Microsoft (Mapping software), Streets & Trips 2001 NOAA (Aeronautical Sectional Charts) http://www.sportys.com Topografix (Waypoint Management for GPS), Panterra http://www.topografix.com

123
Maps, Charts and Misc. Stuff USGS (Topo Maps), Timely Discount Topos Inc:
http://www.usgstopomaps.com
Earthviewer:
http://www.earthviewer.com/index.html
Digital Globe, Satellite Images:

http://www.digitalglobe.com

124
Version 3.2
62

Programs and Miscellaneous Software Red Hat Linux http://www.redhat.com Microsoft (Network Diagram Software), Visio 2000 MySQL http://www.mysql.org MIBs Standard MIB Files http://www.simpleweb.org/ietf/mibs/ SNMP Browsers and related software http://www.adventnet.com Go to the products section and locate SNMP Tools http://net-snmp.sourceforge.net
125
Broadband Performance Enhancement Software and Reference Information DSL Reports: http://www.dslreports.com DRTCP TCP Windows Tuning Utility: http://www2.kansas.net/drtcp.asp NetIQ Chariot QCheck http://www.netiq.com Mikrotik http://www.mikrotik.com/download.html#Bandwidth_tester Hagel Technologies DU Meter http://www.dumeter.com

126
Version 3.2
63
Management Software HP Openview:

http://www.openview.hp.com/products/index.html
Tivoli:
http://www-306.ibm.com/software/tivoli/
SNMP Server:
SNMPc: http://www.castlerock.com
MRTG:
http://www.mrtg.org

127
Vendors and RF Resources (continued)
Path Profile Programs Contract Telecommunications Engineering (Pathloss) www.pathloss.com EDX http://www.edx.com Micropath (Microwave Path Analysis Software), Micropath 2001, http://www.micropath.com RadioMobile www.cplus.org/

128
Version 3.2
64
Instruments Garmin (GPS) http://www.tvnav.com Magellan (GPS) http://www.magellingps.com Brunton (Compass), Eclipse Compass http://www.rei.com Avcom (Spectrum Analyzers) http://www.avcomofva.com

129
Cable and Connectors Andew (Coax Cable, Connectors, Antennas):

http://www.andrew.com
Belden (CAT5 Cable)

http://www.belden.com
BestTronics (CAT5 Cable, GPS Cable):

http://www.best-tronics.com/motorola.htm
Times Microwave (Coaxial Cable, Connectors):

http://www.timesmicrowave.com

130
Version 3.2
65
Cable and Connectors BestTronics (CAT5 Cable, GPS Cable, Connectors):

Shielded RJ-45 Connectors P/N: MC-0542 Shielded RJ-11 Connectors P/N: MC-0643 Amp-Tyco (Connectors):
http://catalog.tycoelectronics.com/TE/bin/TE.Menu?M=Main
Shielded RJ-45 Connectors P/N: 5-569550-3 Shielded RJ-11 Connectors P/N: 5-555175-3

131
Miscellaneous Positioning Tone Cable and Headset: Canopy Distributor BestTronics (CAT5 Cable, GPS Cable):
Positioning Tone Audio Amplifier Radio Shack PN. 277-1008

132
Version 3.2
66
Appendix R: Example IP Addressing Tables

133
IP Addresses in Canopy (NAT)

SM AP & Network CPE NAT Public DMZ DHCP Server subnet subnet-A subnet-B subnet-A subnet-B configuration DHCP server @ SM DHCP client @ SM manual manual template A.A.A.X B.B.B.X A.A.A.DMZ B.B.B.X RF Public RF Private NAT Private RF Public RF Private subnet subnet-C subnet-D subnet-A subnet-C subnet-D configuration manual or default (for local) automatic manual manual default (or manual) template C.C.C.X D.D.D.X A.A.A.1 C.C.C.Y D.D.D.1
IP Network
Canopy's Network Management

134
Version 3.2
67
IP Addresses in Canopy ( no NAT)
IP Network
Canopy's Network Management
CPE subnet subnet-A configuration DHCP server @ network template A.A.A.X RF Public subnet subnet-C configuration manual or default (for local) template C.C.C.X
SM NAT Public RF Private subnet-D automatic D.D.D.X
AP & Network DMZ DHCP Server subnet-A manual A.A.A.Y NAT Private RF Public RF Private subnet-C subnet-D manual default (or manual) C.C.C.Y D.D.D.1

135
Version 3.2
68

Canopy Tech Training v3-2 Appendices Student Guide

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Canopy Tech Training v3-2 Appendices Student Guide

Загружено:

Авторское право:

Доступные форматы

Canopy Technical Training Course Student Guide - Appendices

Motorola: For General Business Use. CPYTTC Appendices Version 3.2

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

Appendix A: IP and RF Review

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

RF & Canopy: Collocating Units

RF & Canopy: Collocating Units

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

RF & Canopy: 900 MHz, 2.4, 5.2 & 5.4 GHz

915 924 906

2.4150 5.325 5.485 5.535 5. 510 5.485 5.510 5.535 5.300

5.275 5.300 5.325 5.275

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

RF & Canopy: 5.7 GHz Frequency

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy and IP Considerations

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

Canopy Module IP Addressing

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy IP Addressing: Subnet Allocation

Canopy Technical Training Course Student Guide - Appendices

Canopy MAC Address Table

Canopy MAC Address Table

This prevents unnecessary traffic over the RF link.

Canopy Technical Training Course Student Guide - Appendices

Other traffic Network Traffic

SM-3 SM-1 SM-2

Canopys Default IP Address

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

Appendix B: GPS Fundamentals

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

Canopy Technical Training Course Student Guide - Appendices

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Appendix C: Canopy Network Examples

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

Canopy Network Examples

Fire House #7 Zone #1 CH #4 Zone #2 CH #1

High Bandwidth Applications

68th & Dover Hill Tower Zone #4 CH #3

Fire House #6 HQ Two Towers

Fire House #2 No Line of Site to Hill Tower or #6 Tower

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Network Examples

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices

Appendix D: Canopy Auto-Sense

Motorola: For General Business Use. CPYTTC Appendices, Version 3.2

Canopy Technical Training Course Student Guide - Appendices