Look, I'm not going to pretend I got it right the first time. Or the second. I've been handling RF equipment orders for about six years now, and I've personally made—and documented—a few significant mistakes that cost my employer a total of roughly $12,000 in wasted budget and rework. The biggest category of error? Picking the wrong RFS leaky feeder cable for the job.
There's no single "best" RFS leaky feeder cable. It depends entirely on your environment: tunnel length, frequency band, interference risk, and budget constraints. I learned this the hard way.
So here's what I've learned after three specific screw-ups involving RFS equipment. I'll break it down by scenario so you can figure out which one matches your project.
Scenario A: The Short Tunnel (Up to 500 meters, single band)
This is the scenario I thought was a no-brainer. Turned out I was wrong.
The job: We were deploying coverage in a 200-meter pedestrian underpass. Single operator, 700 MHz band. I ordered a standard RFS leaky feeder cable, one of their standard variants. Looked fine on paper.
The mistake: I chose a cable with a coupling loss spec that was technically within range, but I completely ignored the installation environment. The tunnel had metal conduit running the entire length. The cable I chose had a narrower vertical radiation pattern. Result? Signal nulls every 20 meters. Coverage was patchy.
That error cost $890 in redo plus a 1-week delay. I only believed in checking the installation environment after ignoring that advice and getting burned.
What I'd tell you now: For short tunnels with a single band, you don't need the most expensive RFS leaky feeder cable. But do not skip looking at the environment. If there's metal infrastructure, choose a cable with a wider radiation angle. I'd go for a variant like the RFS DURA-FLEX series for these cases—it's not the cheapest, but it handles interference better in tight spaces.
Also, get a site survey. I know it sounds obvious, but I skipped it because the tunnel was "short." That was dumb.
Scenario B: The Long Haul (Multi-kilometer tunnel, multi-band, high reliability requirement)
This one hurt more. It was September 2022, a major rail tunnel project. We needed multi-band support (700 MHz, 1800 MHz, and 2.6 GHz) over 3.2 kilometers. Order RFS equipment for the whole thing.
The mistake: I was cost-conscious. I found an RFS leaky feeder cable that met all frequency specs at a lower price point. I pushed for it. We ordered 3.2 km of it.
Installation was done. Then we did the drive test. The higher band (2.6 GHz) had attenuation that was 30% worse than expected. The cheap cable just didn't support that frequency well over distance. We had to install amplifiers mid-tunnel. That raised the total cost by about $4,200.
My lesson: In a long-haul, multi-band scenario, the RFS cable's attenuation spec at the highest frequency is not negotiable. Pay for the cable that guarantees flat performance across all your bands. The RFS CFS series, for instance, is built for this—it's engineered for multi-band consistency.
Even after choosing the more expensive cable on the redo, I kept second-guessing. What if the specs were just marketing fluff? The two weeks until we got the new samples tested were stressful. Didn't relax until the test results matched the spec sheet.
What I'd tell you now: For long tunnels, budget for the premium RFS equipment. The time certainty of getting it right the first time is worth the extra cost. In March 2024, we paid $400 extra for a rush delivery on the correct cable. The alternative was missing a $15,000 event. Honest to god, you can't afford the cheap option here.
Scenario C: The Budget-Sensitive Project (Short life span, low traffic, single band)
This is the one scenario where I think you can be more relaxed. Sometimes the project is temporary—a construction site tunnel, a one-time event, a short-term emergency.
What I learned: For these, a standard RFS leaky feeder cable is fine. You don't need the expensive, high-spec stuff. The risk of failure is low, and the consequence of failure (replacement within a short time) is manageable.
I made this mistake in reverse—I once specified a premium RFS cable for a 3-month construction site project. The project manager was not happy. The cable cost 50% more than necessary. The DURA-FLEX standard variant would have worked perfectly. That error cost about $1,200 in wasted budget.
My advice: If the project life is under a year and you're running a single band, go with the standard product. Just verify the basics: coupling loss, cable length, and connector type. Don't over-engineer it.
How Do You Know Which Scenario You're In?
Here's the practical litmus test I now use before any RFS equipment order. Ask yourself these three questions:
1. How long is the leaky feeder run?
Under 500 meters? It could be Scenario A or C. Over 1 km? You're in Scenario B territory.
2. Are you supporting multiple frequency bands?
If yes, especially if one is above 2 GHz, you're likely in Scenario B. Don't cut corners.
3. What's the project lifespan and criticality?
Critical? Long-term? You need the premium spec. Temporary? Low traffic? You can save money.
There's no universal answer. But once you know your scenario, picking the right RFS leaky feeder cable becomes a lot clearer. Trust me—I learned by making the wrong choices first. You don't have to.
