Canopy SW Release 8.4.3 is posted on the Canopy Software Update web site at http://motorola.canopywireless.com/support/software/
Canopy SW R8.4.3 (OFDM)
* Motorola PMP 400 Series OFDM APs and SMs.
* Motorola PTP 200 Series OFDM BHs.
* Release 8.4.3 provides the same general features that are in Release 8.2.7 for classic Canopy FSK radios.
R8.4.3 Highlights
* Adds support for Backhauls (BHs – Motorola PTP 200 Series).
* Adds support for AES modules (APs, SMs, and BHs).
* PMP 400 Series OFDM APs and SMs should be upgraded to this release.
* PTP 200 Series OFDM BHs ship with this release.
* Release 8.2.x runs on classic Canopy FSK radios. Release 8.4.x does not.
* Release 8.4.x runs on Canopy OFDM radios. Release 8.2.x does not.
* Release 8.3 is not used for release numbering.
R8.4.x Features
* Higher maximum throughput and capacity. Includes a 3X option (in addition to 1X and 2X options) that provides up to 21 Mbps of throughput or capacity.
* Longer range Supports longer range than Canopy 5.4 GHz FSK systems or nonreflector-equipped Canopy 5.7 GHz FSK systems.
* NLOS performance The use of OFDM gives additional NLOS performance under many conditions.
* Standard Canopy Features. RF (Radio Frequency) and IP (Internet Protocol) features in standard Canopy FSK up through Release 8.2.7.
Support for BHs. Release 8.4.3 supports new Canopy OFDM BHs (Motorola PTP 200 Series).
* Support for AES radios. Release 8.4.3 supports new Canopy OFDM AES radios (APs and SMs – PMP 400 Series, and BHs – PTP 200 Series).
* Support for 1/8 Cyclic Prefix on BHs. Release 8.4.3 offers the option of 1/8 cyclic prefix on BHs, which provides about a 10% increase in maximum throughput or capacity over cyclic prefix.
R8.4.3 Issues Resolved
* Broadcast traffic limited under high traffic conditions. Under heavy downlink unicast traffic, downlink broadcast/multicast traffic on a link is limited (or drops) to about 100 kbps.
* Very high broadcast traffic from AP reduces broadcast throughput . At very high (5 Mbps) downlink broadcast traffic, the carried throughput drops. (At 5 Mbps offered load, Broadcast Repeat Count set to 0, throughput is 4 Mbps, at 5.8 Mbps offered load, throughput is 1 Mbps). Such high broadcast traffic is not normal operation and would usually be indicative of a broadcast storm condition.
* Very high broadcast traffic from AP can force SMs into scanning mode. At very high (5 Mbps) downlink broadcast traffic, SMs can drop their link and go into scanning mode. The SMs then reconnect normally to the AP. Such high broadcast traffic is not normal operation and would usually be indicative of a broadcast storm condition.
* Anomalous behavior under some scenarios when DHCP Client is enabled on an SM with NAT enabled. Requests from the DHCP client are not backing off correctly. When the DHCP client does not receive an ACK to a REQUEST it sent, it should cease sending the REQUEST, except at one-half of the remaining lease time, but it doesn’t.
See R8.4.3 “Known Open Issuesâ€