Free planning tool

Wi-Fi Network Planner

How many access points a building needs, and how many battery sensors one of them can really carry.

1 · Your site

Indoor coverage is decided by walls, not by metres. Get the wall count right and the rest follows.

5,000 m² · 500 sensors

2access points

Driven by coverage — the floor is larger than 2 cells can reach.

39.9m

Coverage radius

2

Needed for coverage

1

Needed for capacity

Network health

Red is the point past which the design stops working.

Concurrent sessions per AP5.5 / 100

Little's Law at peak: 500 sensors × 3.30 s session ÷ 15 min, ×3 for staggered reporting

Channel utilisation14.7% / 30%

Only 8% of a session is frames on air; the rest is waiting

Signal at the cell edge-70 dBm · SNR 24 dB

Noise floor -94 dBm in a 20 MHz channel. Above about 25 dB of SNR a client can use the fast modulation rates and gets off the air quickly.

Checks

2 access points fits inside the 3 non-overlapping channels on 2.4 GHz.
Peak 5.5 sensors mid-session against a limit of 100.
Channel utilisation 14.7%, limited by airtime.

How it lays out

2 cells over 5,000 m²

71 × 71 m · 2 access points · 39.9 m radius

Walls decide the range

2.4 GHz, office, light partitions, to -70 dBm.

one office wall costs about 4 dB at 2.4 GHz

A wall is worth more than distance. At 2.4 GHz one office wall costs about 4 dB — the same as moving the sensor 1.4× further away. Counting walls beats measuring metres.

2.4 or 5 GHz?

Reach against channels — the real trade.

2.4 GHz reaches roughly twice as far, so it needs fewer access points — but it has only 3 non-overlapping channels against 5 GHz's 19. Past three access points in earshot of each other, 2.4 GHz stops adding capacity and starts sharing it. Sparse sensor sites suit 2.4 GHz; dense ones need 5 GHz and more hardware.

How these numbers are calculated

Coverage — log-distance indoor path loss with wall attenuation counted explicitly, solved for the distance at which RSSI reaches your design target. Wi-Fi is planned to a target like −70 dBm rather than to the radio's sensitivity: a client will associate at −85 dBm and be useless. The table is anchored to the office case, where the published rule of thumb is 30–45 m at 2.4 GHz and 15–25 m at 5 GHz from a 20 dBm access point — this model returns 40 m and 17 m.

Capacity is about sessions, not bandwidth — a sensor fleet sends almost no data, but every reading costs a full connect sequence lasting seconds. The number of sensors mid-session at any instant is Little's Law: arrival rate × service time. That is what runs into an access point's concurrent-client limit, and it is why shortening the connect sequence raises capacity as sharply as it extends battery life.

Airtime — only about 8% of a session is actual frames on the channel; the rest is waiting for beacons, the DHCP server and the broker. That fraction is the figure worth measuring on your own site before quoting utilisation to anyone.

Channel reuse — 2.4 GHz has three non-overlapping channels and 5 GHz has nineteen. Co-channel neighbours share airtime rather than adding capacity, so an over-dense 2.4 GHz plan gets slower as you add access points.

A desk estimate on smooth assumptions. Real buildings have lift shafts, foil insulation and metal racking that no model predicts — confirm with a site survey before ordering hardware.

Got an IoT idea?

Let’s bring it to life!

flag image

WPC compliant · RoHS · a product engineer replies within one working day

Let‘s Make it Easy

Reach Out Now

Icon

Contact to Sales

Talk to our friendly team

chat@macnman.com
Icon

Call Us

24 X 7 Always On

+91 7972856163
Icon

Contact to Support

We are here to help

support@macnman.com
Icon

Visit Us

Visit our office HQ

View on Google Map

Socials

LoRaWAN

4G IoT

WiFi Ble IoT

Nb IoT

Customize

Maya

Documentation

Case Studies

Blogs

Use of this website and purchase of Macnman products are subject to our Terms and Conditions.