Wireless telemetry and microwave links: where they fit in modern CCTV projects

Wireless telemetry and microwave links: where they fit in modern CCTV projects

Wireless telemetry and microwave links: where they fit in modern CCTV projects

The decision framework you can use on every quote

Here’s a simple way to decide what fits, without making it complicated.

Step 1: Is the thing you’re sending video or events?

  • Video (IP streams) → you’re in PtP / microwave / wireless bridge territory

  • Events (open/closed, alarm, trigger) → you’re in telemetry territory

  • Both → treat them separately (and don’t assume 1 solves the other)

Step 2: What’s the tolerance for downtime?

Be honest here. A remote farm gate camera might be “nice to have”. A high-risk industrial site with monitored response might be “cannot fail”.

If downtime is unacceptable:

  • build headroom (throughput, signal strength, proper mounting)

  • protect power properly (surge, UPS where appropriate)

  • consider dual paths (wireless + wired where possible, or 2 radios)

  • log and monitor link health

Step 3: What’s the environment really like?

This is where wireless installs succeed or fail.

Ask yourself:

  • Is there a clean line-of-sight?

  • Are there trees that will leaf up in spring?

  • Is there metal cladding that will reflect and mess with the signal?

  • Is it a high-interference area (industrial estate, dense housing)?

  • Are poles stable, or do they sway?

If you can’t answer these, you’re guessing — and wireless punishes guessing.

Step 4: How will you power it?

Wireless gear is often easy until you get to power.

Typical routes:

  • PoE from a cabinet

  • local AC spur into a small enclosure

  • existing lighting circuits (with proper regulation/protection)

Don’t forget the basics: decent Power Supplies and tidy accessories make a huge difference to reliability over time.

Step 5: Can you maintain it easily?

If you’re sending someone out every time the client says “camera is buffering”, your margin disappears.

Think maintenance upfront:

  • label everything

  • leave service loops

  • use proper glands and enclosures

  • document alignment points

  • set passwords and configs professionally

This is also why bundling properly matters — FVS has a good install-minded approach in pieces like Bundling CCTV Equipment, because a system is only as strong as its weakest component.

The “gotchas” that catch installers out (and how to avoid them)

Line-of-sight isn’t just “I can see it”

Wireless links care about the Fresnel zone (the “fat tube” around the direct path). You can have visual line-of-sight and still have performance issues if trees, roofs, or signage sit in that zone.

If you’re doing longer hops, mount higher than you think you need to.

Don’t spec throughput too tight

A common mistake is building a link that’s fine at commissioning and then struggles later when:

  • the client adds more cameras

  • bitrates increase (higher res, better quality settings)

  • more users view streams remotely

  • weather/interference reduces usable throughput

Give yourself breathing room.

Weatherproofing and surge protection matter

Outdoor wireless means outdoor risk:

  • water ingress

  • UV damage

  • lightning/surge events

  • cable wicking

Choose a kit with protection where you can, and keep your network side stable. Even a basic unmanaged surveillance switch with surge protection can help in the right place.

Security: treat wireless like a network device (because it is)

You’re extending a LAN. That means you need:

  • strong credentials

  • encryption where supported

  • no default passwords

  • sensible IP scheme and documentation

If the client is security-conscious, this is where you win trust.

A few real-world “this is where it works” examples

Example 1: Industrial unit + yard cameras (no trenching)

You mount cameras to cover the yard, run them into a local PoE point, then backhaul to the office rack using a PtP link. Record centrally using your chosen NVR platform (start with FV-PRO 4K POE H.265 NVRs if you’re building a typical IP system), and don’t forget storage like surveillance hard drives sized for retention.

Example 2: Farm entrance gate + automation trigger

You need a camera at the gate and a trigger when it opens. Use PtP for the camera stream, and telemetry (or I/O over the correct hardware) for the open/close status. That way, even if the video stream is busy, the event data still gets through reliably.

Cost reality: how to talk about it on a quote (in £)

Clients often assume wireless is expensive. Sometimes it is — but trenching, ducting, resurfacing, and making good can spiral fast.

A simple way to frame it:

  • Wireless link cost: usually a predictable equipment + labour line item

  • Civils cost: can be the “unknown unknowns” (and the part that causes delays)

If you position wireless as:

  • faster delivery

  • less disruption

  • cleaner outcome

  • easier to extend later

What to spec (without overthinking it)

If you want a simple, repeatable spec approach:

  1. Pick cameras based on the job

  1. Choose recording that matches channel count + growth

  1. Build the network properly (don’t “wing it”)

  1. Add the wireless layer where it solves a real problem

  1. Finish the job with the unglamorous bits that prevent call-backs

Those “boring” items are usually what separates a system that runs for years from a system that generates support tickets.

Want help speccing a wireless CCTV link for your next job?

If you’ve got a site plan, rough distances, and a few photos of the mounting points, FVS CCTV can help you choose the right approach — whether that’s a clean PtP bridge, telemetry triggers, or a full IP package built to suit the project.

Browse the wireless options in Wireless IP Transceivers or get in touch with the team via the main site at FVS CCTV to talk through your quote and avoid expensive surprises.