website@flyteccomputers.com

DFS on 5 GHz Links in LATAM: Why the PBE-5AC-Gen2-US Is a Practical Option

Published by Juan David Ramirez on 1st Jul 2026

Hi there, it’s Juan David again, your Lead Tech Support specialist at Flytec Computers. DFS can sound confusing if you are planning a 5 GHz wireless link for the first time. Some customers see a DFS warning or hear that certain channels require radar detection, and they immediately wonder if the link will disconnect, stop working, or become difficult to support. 

That concern is understandable, but DFS does not mean the radio is defective or unusable. It is a normal protection feature built into many 5 GHz deployments. When a radio detects radar activity on a DFS channel, it follows the required behavior for that band and avoids interfering with protected systems. 

For installers using the PBE-5AC-Gen2-US, the key is planning the link correctly. In Chile, Mexico, and other LATAM markets where 5 GHz ranges are similar or heavily overlapping with the US profile, the radio can be very practical. DFS simply needs to be understood as part of normal 5 GHz channel planning. 

What Is DFS? 

DFS stands for Dynamic Frequency Selection. In simple terms, DFS is a radar protection feature used on certain 5 GHz channels. Some 5 GHz frequencies are shared with radar systems, such as weather radar, airport radar, maritime radar, or government systems. If a wireless radio is using one of those DFS channels and detects radar activity, it must avoid that channel. 

That is why DFS is sometimes described as a radar detection requirement. The radio checks the channel, monitors for radar signals, and reacts if radar is detected. 

For installers, the important point is this: DFS does not mean the PBE-5AC-Gen2-US cannot be used. It means the radio follows the required behavior on channels where DFS applies. 

Also, DFS does not affect every location the same way. A customer near an airport, weather radar site, coast, military area, or other radar source may be more likely to see DFS activity. A rural site with no nearby radar activity may never experience a DFS event, even when using a DFS channel. That is why checking the local RF environment is important. 

Why DFS Matters in LATAM 

Many countries in Latin America and the Caribbean use 5 GHz ranges that are similar or heavily overlapping with the US profile. Chile and Mexico are good examples, but they should not be described in exactly the same way. 

The PBE-5AC-Gen2-US supports these main US/CA 5 GHz ranges:

  • 5150 to 5250 MHz
  • 5250 to 5350 MHz
  • 5470 to 5725 MHz
  • 5725 to 5850 MHz 

In simple terms, not every 5 GHz range has the same DFS behavior. Some ranges are normally treated as non-DFS, while other ranges may require DFS radar detection depending on the country, channel, and local rules. 

For the US/CA profile, installers commonly look at the ranges this way: 

  • 5150 to 5250 MHz: generally non-DFS, often used for lower 5 GHz channels
  • 5250 to 5350 MHz: DFS range
  • 5470 to 5725 MHz: DFS range
  • 5725 to 5850 MHz: generally non-DFS, often used for upper 5 GHz channels where permitted 

This is important because if an installer chooses a non-DFS range, DFS radar detection is generally not part of that link’s operation. If the installer chooses a DFS range, the radio may need to check for radar activity and may need to move channels if radar is detected. 

Chile uses the same main 5 GHz blocks: 

  • 5150 to 5250 MHz
  • 5250 to 5350 MHz
  • 5470 to 5725 MHz
  • 5725 to 5850 MHz 

That makes the US version especially practical for many 5 GHz deployments in Chile because the main 5 GHz blocks line up very closely with the US/CA profile. Installers should confirm local rules for power, EIRP, DFS, indoor or outdoor use, and certification. 

Mexico is also very similar, but its 5 GHz rules split part of the DFS range: 

  • 5150 to 5250 MHz
  • 5250 to 5350 MHz
  • 5470 to 5600 MHz
  • 5650 to 5725 MHz
  • 5725 to 5850 MHz 

For Mexico, the overlap is strong, but installers should pay close attention to the split between 5600 and 5650 MHz. Instead of assuming the entire 5470 to 5725 MHz range is one continuous block, installers should choose channels that fit the local Mexican rules. 

DFS becomes part of the conversation because some of these 5 GHz ranges may require radar detection behavior. That does not mean those channels are bad. It simply means the installer should understand when DFS applies and plan the link accordingly. 

What Happens If DFS Is Triggered? 

If DFS is triggered, the radio is doing what it is supposed to do. It is protecting the channel and avoiding interference with radar or other protected systems. 

Depending on the configuration and environment, the link may need to change channels. In some cases, the radio may pause briefly while it checks channel availability or moves to a different channel. 

That can sound concerning, but it does not make the radio unusable. It simply means installers should plan the link properly. 

In real deployments, DFS only becomes an issue when radar activity is actually detected on the channel being used. If there is no radar activity in that area, a DFS channel may operate normally. This is why two customers can have different experiences with the same equipment: one site may be close to radar activity, while another site may be in a clean rural area. 

For many WISP, rural, and building to building links, DFS channels can be very usable when the spectrum is clean and the installation is planned correctly. 

In PtMP, the AP Controls the DFS Decision 

One important point for WISP deployments is that in a typical airMAX point to multipoint sector, the AP is the channel master. That means the AP is the radio that controls the channel for the whole sector. 

A simple way to explain it is this: 

The AP is like the leader of the group. The subscriber radios, or client radios, do not each pick their own channel while connected to that AP. They follow the AP’s channel. 

So, if the AP is using a non-DFS channel, DFS is generally not part of that sector’s operation. The clients will stay on the AP’s non-DFS channel, and a client being DFS capable does not make it independently search for radar or force the whole sector to move. 

If the AP is using a DFS channel, then the AP is the radio responsible for managing DFS behavior for that sector. The AP checks the channel, monitors for radar activity, and decides whether the sector needs to move. If the AP detects a DFS event and changes channels, the connected client radios follow the AP to the new channel. 

In practical terms: 

  • The AP chooses the operating channel for the sector
  • The client radios follow the AP’s channel
  • Clients do not independently move the sector to another channel
  • If the AP is on a non-DFS channel, DFS behavior is generally not part of that sector
  • If the AP is on a DFS channel and radar is detected, the AP manages the move
  • The connected client radios reconnect or follow according to the AP’s channel behavior 

This is important for installers because it makes the behavior more predictable. Instead of every client making separate channel decisions, the sector follows the AP. That helps WISPs plan around DFS with cleaner channel selection, better sector control, and more predictable customer behavior. 

For LATAM markets, this can be a strong selling point. If the installer selects a clean, permitted non-DFS channel on the AP, the sector can avoid DFS-related channel changes. If the installer chooses a DFS channel because it is cleaner or has better spectrum availability, the AP controls the process for the whole sector. 

In other words, if the AP does not have the DFS feature, like an International version RP-5AC-Gen2, then even if the clients are US version like the PBE-5AC-Gen2-US, which have the DFS feature, the channels will never change because the AP will never trigger the DFS feature because it doesn’t even exist in the AP. 

 

DFS Is Not a Problem With the Radio 

It is important to explain this clearly to customers: DFS behavior is not a failure of the PBE-5AC-Gen2-US. 

If the radio detects radar on a DFS channel and reacts, that means it is following the required rules for that band. This is normal behavior for 5 GHz equipment that operates in DFS ranges. 

The PBE-5AC-Gen2-US remains a strong option because it gives installers several usable 5 GHz ranges and multiple channel width options. For point to point links, the radio can support channel widths such as 10, 20, 30, 40, 50, 60, and 80 MHz. For point to multipoint deployments, common options include 10, 20, 30, and 40 MHz. 

That flexibility helps installers adjust the link for speed, stability, and interference conditions. 

How Installers Can Plan Around DFS 

DFS is easier to manage when the link is designed properly from the beginning. 

Before installing the PBE-5AC-Gen2-US, installers should: 

  • Scan the local spectrum
  • Check for clean available channels
  • Use a stable channel width
  • Avoid using the widest channel in noisy areas
  • Confirm line of sight and Fresnel clearance
  • Mount the radio securely
  • Use outdoor rated cable
  • Add proper grounding and surge protection
  • Follow local power and EIRP requirements 

For many links, 20 or 40 MHz is a good starting point because it balances throughput and stability. Wider channels such as 60 or 80 MHz may work well in clean point to point environments, but they require cleaner spectrum and better conditions. 

The goal is not just maximum speed. The goal is a stable link that performs consistently. If a clean non-DFS channel is available and permitted, it may be the simpler choice. If a DFS channel is cleaner and allowed, it can be a good option, but the installer should understand that radar detection may apply in some locations. 

Why the PBE-5AC-Gen2-US Makes Sense 

The PBE-5AC-Gen2-US is designed for up to 450+ Mbps real TCP/IP throughput under ideal conditions. It includes a 25 dBi integrated dish antenna, Gigabit Ethernet, passive 24V PoE, airMAX AC performance, and a dedicated management WiFi radio. 

Its focused dish design helps concentrate the signal toward the other side of the link. That makes it useful for rural links, tower to customer deployments, camera backhaul, and building to building bridges where directionality and noise isolation matter. 

For Chilean deployments, the US version is especially practical because the main 5 GHz frequency ranges align closely with the US/CA profile. For Mexican deployments, the overlap is also strong, but installers should be careful with channel selection because Mexico separates part of the 5470 to 5725 MHz range into 5470 to 5600 MHz and 5650 to 5725 MHz. In both cases, installers should always confirm local rules before deployment. 

Final Thoughts 

DFS is a normal part of many 5 GHz wireless deployments. It does not mean the PBE-5AC-Gen2-US is blocked, defective, or unusable. It means the radio follows the required behavior when operating on channels where radar protection applies. 

The important point is that DFS does not affect every channel or every location the same way. Non-DFS channels are usually simpler when they are available and permitted. DFS channels can work well, but they may require radar detection behavior, especially in areas near radar activity. 

For point to multipoint WISP sectors, the AP-controlled DFS behavior is especially important. The AP manages the channel decision, and the subscriber radios follow the AP. This gives installers more predictable sector behavior and makes it easier to plan around DFS in LATAM deployments. 

With the right channel planning, clean line of sight, proper mounting, and local compliance, the PBE-5AC-Gen2-US can be a strong option for WISPs, camera backhaul, rural links, and building to building bridges. In Chile, the main 5 GHz ranges are very similar to the US/CA profile. In Mexico, the main ranges also overlap strongly, but installers should account for the 5600 to 5650 MHz split when selecting channels. 

For help planning a 5 GHz link in Chile, Mexico, or nearby LATAM markets, contact Flytec through live chat, call 305-471-5142, or email website@flyteccomputers.com with the link distance, mounting height, line of sight conditions, and expected bandwidth so the right channel width and deployment approach can be recommended.