35 Stationary WSN Fundamentals

iot

wireless-sensor-networks

mobility-sensing

35.1 Start With the Field Story

This section: Start With the Field Story — A wireless sensor network (WSN) joins sensors that share readings over wireless links.

A wireless sensor network (WSN) joins sensors that share readings over wireless links. A stationary WSN keeps its nodes in fixed places. The nodes do not move, but their environment still changes. Start with the sensing claim. Then check coverage, the data collection point, relay work, maintenance access, and reasons to test again.

Cartoon panel 1 illustrates this step: Fixed field sensors share readings over radio links. — A fixed sensor network is reviewed as its field conditions change.

Cartoon panel 2 illustrates this step: The nodes stay still, but weather, batteries, and paths still change. — A fixed sensor network is reviewed as its field conditions change.

35.2 In 60 Seconds

This section: In 60 Seconds — A stationary network fixes sensors, data collection points, gateways, relays, and antennas in known places.

A stationary network fixes sensors, data collection points, gateways, relays, and antennas in known places. A gateway is a device that passes data to another network. Fixed places make coverage, routes, maintenance, and sensor checks easier to plan. They also make placement mistakes last. A missed area, weak link, busy relay, blocked case, or unreachable node remains a problem until someone changes the site.

Stationary WSN review is a check of fixed places. Record what the sensors must prove and where each node sits. Record coverage, links, collection points, relay work, and power assumptions. Also record visible failures, the maintenance route, a fallback action, and reasons to test again. The design is acceptable only when this evidence matches the installed setting.

Antenna Far-Field Distance and Mounting Evidence

The mathematical gist. For a 5.00 cm leaf antenna at 2.4 GHz, $2D^2/\lambda$ gives 4.00 cm; for a 30.0 cm gateway antenna at 900 MHz, it gives 0.540 m. These are illustrative calculation results, not guaranteed far-field boundaries for installed antennas. A 20 cm metal offset cannot be judged by subtracting it from the calculated $2D^2/\lambda$ distance; follow the antenna maker’s mounting guidance and verify the installed match, radiation pattern, and link margin before relying on catalog gain. Because $R_{ff}=2D^2/\lambda$ , physical size enters twice.

35.3 Learning Objectives

This section: Learning Objectives

By the end of this chapter, you will be able to:

Explain when a stationary WSN is a good fit and when movement should be considered.
Review fixed node placement for sensing meaning, coverage, links, energy, and maintenance.
Identify energy holes, busy relays, coverage holes, and broken-network risks without brittle number shortcuts.
Build a stationary WSN record with accepted limits, fallback actions, an owner, and reasons to test again.
Connect stationary design to mobile WSN, energy, routing, and coverage lessons.

35.4 Stationary WSN Fundamentals

This section: Stationary WSN Fundamentals

35.5 Prerequisites

This section: Prerequisites — Start with WSN Introduction and WSN Communication Patterns.

Start with WSN Introduction and WSN Communication Patterns. For moving designs, use Mobile WSN Fundamentals Review and MWSN Nodes, Sinks, and Data MULEs Review. The design checks also use WSN Energy Management, WSN Routing Introduction, and WSN Coverage Fundamentals.

Review those chapters first if the learner cannot describe sensing claims, node roles, gateway boundaries, coverage, routes, and relay work. They should also understand radio sleep schedules, stored data, and maintenance ownership.

35.6 Stationary Review Scope

This section: Stationary Review Scope — Stationary WSN review starts with the reason nodes should stay fixed.

Stationary WSN review starts with the reason nodes should stay fixed. Fixed placement is useful when the monitored condition is tied to known locations, but every placement assumption must be verified.

Sensing claim State what physical condition must be measured, where it is valid, how fresh it must be, and what decision uses the result.

Placement evidence Record node location, mounting, sensor exposure, enclosure, antenna orientation, calibration state, and environmental constraints.

Coverage evidence Show which areas, assets, or route segments are covered, uncertain, redundant, or outside the claim.

Connectivity evidence Record link quality, relay paths, sink reachability, reverse-link behavior, retries, and what happens when a path fails.

Relay and power evidence Review relay burden, wake schedules, battery or power source, replacement access, and hotspots near sinks or gateways.

Operations loop Name the owner, monitoring signal, fallback action, uncertainty rule, replacement rule, and retest trigger.

35.7 Fixed Placement Evidence Map

This section: Fixed Placement Evidence Map — Use the visual in Figure 35.1 to test Fixed Placement Evidence Map.

Use the visual in Figure 35.1 to test Fixed Placement Evidence Map. Its Sensing claim and decision labels anchor the structure behind Fixed Placement Evidence Map in named system parts.

Figure 35.1: Stationary WSN fixed-placement evidence map connecting sensing claim, fixed node placement, coverage evidence, connectivity evidence, sink placement, relay burden, power evidence, failure visibility, maintenance access, fallback action, accepted limits, and retest trigger.

Read Figure 35.1 through three markers. Sensing claim states what the network must prove. Fixed node records where a sensor supports that claim. The path checks coverage, links, the collection point, relay work, and power. It then records visible failures, maintenance access, a fallback, accepted limits, and reasons to test again. The final decision says whether the fixed design supports the claim.

The map prevents a common mistake: treating stationary placement as finished once the nodes are installed. Fixed topology makes evidence easier to collect, but it also makes failures persistent. If a relay hotspot, coverage hole, obstructed sensor, or inaccessible battery is not visible in the record, the deployment can look stable while its data quality is drifting.

Figure Figure 35.2 adds measured signal variation to the fixed placement review.

Stationary-source RSSI heatmap with a fixed source node, signal-strength samples, weak and strong signal legend, and coverage assessment labels. — Figure 35.2: Stationary-source RSSI heatmap showing signal-strength variation around a fixed source node and a coverage assessment boundary.

The heatmap marks a stationary source and signal samples across positions in a vehicle interior. Its axes locate weak and strong readings, and the legend and coverage assessment summarize the measured area. This helps the team find weak positions. Yet RSSI alone does not prove packet delivery or a safe reverse path. The section’s fixed-placement record also needs gateway reach, relay burden, power, failure visibility, and maintenance access. A node may stay in the same place while enclosure exposure, obstruction, traffic, or gateway position changes its usable link, so later field measurements can reopen acceptance.

The fixed map is an index into evidence, not the evidence itself. A node position may stay correct for years while link quality, enclosure exposure, crop canopy, traffic mix, or maintenance access changes after one season, one equipment move, or one gateway relocation.

35.8 Stationary Design Proof Limits

This section: Stationary Design Proof Limits

Predictable topology Fixed nodes can make routes easier to inspect. They do not prove reliability unless link quality, reverse paths, retry behavior, and route repair are recorded.

Repeatable sensing A fixed sensor can compare the same place over time. It still needs mounting, exposure, calibration, drift, and physical access evidence.

Coverage planning Planned placement can reduce blind spots. It cannot prove coverage unless the review ties sensing range, obstacles, redundancy, and uncertain areas to the claim.

Energy planning Stable routes can make energy review easier. They can also concentrate relay work near sinks, gateways, or chokepoints.

Maintenance planning Known locations can simplify replacement. They can also create hard-to-service nodes if access, safety, and ownership are not reviewed.

Baseline comparison Stationary design gives a stable baseline for mobile alternatives. It does not prove that mobility is unnecessary unless fixed design risks are accepted.

35.9 Evidence Record

This section: Evidence Record — The practical question in evidence record is where sense, place, hands responsibility to freshness.

The practical question in evidence record is where sense, place, hands responsibility to freshness. Use Figure 35.3 to inspect that hand-off before carrying the design forward.

Figure 35.3: Stationary WSN evidence record from requirement and placement assumptions through coverage evidence, connectivity evidence, relay burden, decision, accepted limits, fallback, monitoring owner, and retest trigger.

In Figure 35.3, sense, place names the field reading and its location. Freshness sets how old that reading may be. Placement fixes the area each node can support. The path then checks coverage, links, relay work, limits, and the decision. It ends with a fallback, monitoring owner, and reasons to test again.

Requirement: Record the sensed condition, location meaning, freshness need, tolerated gaps, and decision that uses the reading.

Placement assumptions: Record node positions, mounting, sensor exposure, antenna orientation, sink placement, gateway boundary, and access constraints.

Observations: Record coverage checks, link evidence, route traces, relay burden, power state, sensor calibration, failure signals, and maintenance access.

Decision: Accept, revise, or reject the fixed deployment for this monitoring claim and operating environment.

Operations: Name owner, monitoring signal, fallback action, uncertainty rule, replacement rule, and retest trigger.

35.10 Reviewing Placement and Coverage

This section: Reviewing Placement and Coverage — Fixed placement is not just a map.

Fixed placement is not just a map. It is a claim about what each sensor can observe from a specific physical position.

Location meaning Record whether the reading describes a point, surface, zone, asset, route segment, volume, or inferred area.

Sensor exposure Review airflow, vibration, moisture, light, contact pressure, line of sight, enclosure effects, and interference from nearby equipment.

Coverage boundary Mark covered, redundant, uncertain, and uncovered areas. Do not let a placement diagram imply coverage that was not checked.

Retest condition New equipment, walls, crops, weather exposure, antenna position, gateway movement, or mounting changes can invalidate coverage evidence.

35.11 Reviewing Connectivity and Relay Burden

This section: Reviewing Connectivity and Relay Burden — Stationary WSNs often use fixed multi-hop paths or stable neighbor sets.

Stationary WSNs often use fixed multi-hop paths or stable neighbor sets. That stability can make operations easier, but it can also hide relay pressure.

Reusable stationary evidence and retest triggers.
Property	Evidence made reusable by fixed topology	Retest trigger
Routing	Parent choices, route traces, reverse paths, and retry patterns can be checked against known node positions.	Node failure, gateway move, new obstruction, channel change, or repeated route repair.
Scheduling	Wake windows and TDMA-style slots can be planned around a stable neighbor set and known traffic pattern.	Added node, removed node, changed sampling period, relay overload, or unexpected collisions.
Localization	Surveyed positions, mounting height, orientation, and sensor exposure can be reused for later reviews.	Remounting, enclosure change, calibration drift, crop growth, equipment move, or access change.
Coverage	Covered, redundant, uncertain, and uncovered areas can be marked against a fixed physical layout.	Obstacle, environment, asset layout, sensing radius, or data-quality change.

The strongest records separate planned topology from observed topology. Planned topology says where nodes, relays, sinks, and gateways should be. Observed topology says which neighbors were actually heard, which parent paths were selected, which nodes forwarded for others, which readings arrived stale or missing, and which physical areas stayed uncertain. The acceptance decision should cite the observed topology.

Link evidence Record delivery, reverse-link behavior, retries, channel state, antenna placement, enclosure effects, and link-quality trend.

Route evidence Record route traces, parent choices, failover path, route repair behavior, and whether data meaning changes through aggregation.

Relay burden Identify nodes that forward for others, especially near sinks, gateways, chokepoints, and narrow route corridors.

Energy-hole risk Energy-hole review is about role and evidence, not a fixed multiplier. Inspect wake time, receive windows, retransmissions, and replacement access.

Partition risk Record which node, relay, gateway, antenna, or power source failure would isolate readings or make an area uncertain.

Fallback path Record whether fallback is route repair, extra relay, alternate gateway, mobile collection, manual collection, or uncertainty marking.

35.12 Reviewing Maintenance and Operations

This section: Reviewing Maintenance and Operations — Stationary deployments fail quietly when maintenance assumptions are absent.

Stationary deployments fail quietly when maintenance assumptions are absent.

Access and safety Record how a node is reached, who can replace it, what tools are needed, and whether access changes by season or operating state.

Health signals Monitor battery or power state, link trend, stale readings, missed samples, repeated reboot, sensor fault, and gateway ingestion status.

Replacement rule Define what triggers service, replacement, recalibration, route change, gateway move, or downgrade to uncertain data.

Mobility comparison If fixed maintenance is risky, compare a mobile sink, Data MULE, carried reader, or temporary gateway instead of forcing a fixed design.

35.13 Worked Review: Bridge Vibration Nodes

This section: Worked Review: Bridge Vibration Nodes — Scenario: Fixed vibration nodes are mounted along a bridge to monitor structural trends and alert maintenance when readings become abnormal.

Scenario: Fixed vibration nodes are mounted along a bridge to monitor structural trends and alert maintenance when readings become abnormal.

Requirement: Repeatable vibration readings tied to specific bridge locations, missing-node visibility, and enough freshness for maintenance review.

Placement assumptions: Nodes are mounted at reviewed locations, enclosures preserve vibration transfer, gateway placement supports link quality, and maintenance access is safe.

Evidence: Mounting photos, calibration record, baseline readings, route trace, link trend, power state, stale-data signal, and service access notes.

Decision: Accept only if each installed location supports the sensing claim and relay burden does not hide failures near the gateway.

Fallback: Add a relay, move a gateway, service a node, flag a span uncertain, or schedule manual inspection.

35.14 Worked Review: Greenhouse Climate Grid

This section: Worked Review: Greenhouse Climate Grid — Scenario: A greenhouse uses fixed temperature and humidity nodes across aisles to guide ventilation and irrigation review.

Scenario: A greenhouse uses fixed temperature and humidity nodes across aisles to guide ventilation and irrigation review.

Requirement: Zone-level climate trends, missing-zone visibility, and enough freshness for daily operations.

Placement assumptions: Nodes are placed where airflow and crop canopy do not distort the claim, and gateway coverage reaches each aisle.

Evidence: Placement map, airflow check, calibration record, link evidence, route trace, relay burden, power state, and missing-zone alert.

Decision: Accept only if fixed locations represent the intended zones and operations can detect stale readings before decisions rely on them.

Fallback: Add a fixed relay, add a mobile service-cart collection path, move a sensor, adjust sampling, or mark an aisle uncertain.

35.15 Common Mistakes

This section: Common Mistakes

Map-first acceptance A placement map is not proof of sensing, coverage, connectivity, power, or maintenance readiness.

Ignoring gateway-side burden Nodes close to a sink or gateway may become relay chokepoints even when their own sensing workload is small.

Assuming fixed means reliable Stable topology can hide stale readings, weak reverse links, inaccessible batteries, and persistent coverage holes.

Overclaiming coverage Sensor range, radio range, and meaningful measurement range are different. The review must preserve those boundaries.

No maintenance owner Fixed nodes still need replacement, calibration, enclosure inspection, gateway repair, and uncertainty marking.

No mobility comparison If fixed access, gateway placement, or relay burden is weak, a mobile collection path may be the better evidence choice.

35.16 Review Checklist

This section: Review Checklist

Before accepting a stationary WSN design, verify these parts of the record:

The sensing claim, location meaning, freshness need, tolerated gaps, and decision owner.
Node placement, mounting, sensor exposure, antenna direction, enclosure, sensor checks, and access evidence.
A coverage map with covered, repeated, uncertain, and uncovered areas tied to the claim.
Link evidence, route traces, return-link behavior, retries, grouped-data meaning, and gateway intake evidence.
Relay work, energy-hole risk, power source, health signs, replacement rule, and service access.
A fallback action, uncertainty rule, monitoring owner, mobile comparison, and reason to test again.

35.17 Knowledge Check: Fixed Placement

This section: Knowledge Check: Fixed Placement

35.18 Knowledge Check: Energy-Hole Risk

This section: Knowledge Check: Energy-Hole Risk

35.19 Knowledge Check: Stationary Tradeoff

This section: Knowledge Check: Stationary Tradeoff

35.20 Match Stationary Claims to Evidence

This section: Match Stationary Claims to Evidence

35.21 Order a Stationary WSN Review

This section: Order a Stationary WSN Review

35.22 Summary

This section: Summary — Stationary WSNs are fixed-placement sensing systems.

Stationary WSNs are fixed-placement sensing systems. Their strength is repeatable location-specific measurement, predictable topology, and planned maintenance. Their risk is that bad placement, weak links, overloaded relays, inaccessible nodes, and stale readings can persist unnoticed.

The accepted record must prove the sensing claim, placement, coverage, links, relay work, power state, and maintenance route. It also names the owner, fallback action, and reasons to test again. A fixed design is a good fit when it gives stronger monitoring evidence than a moving design.

35.23 Key Takeaway

This section: Key Takeaway — Compare fixed nodes with moving nodes and collection points.

Compare fixed nodes with moving nodes and collection points. Use coverage, delay, stored-data pressure, route cost, energy, and field evidence.

35.24 Concept Relationships

This section: Concept Relationships

Mobile WSN fundamentals Provides the comparison point when fixed placement, access, relay burden, or coverage assumptions are weak.

MWSN components Explains mobile sinks, Data MULEs, rendezvous points, and service routes that can supplement or replace fixed collection.

Routing and energy Connect fixed placement to relay burden, wake schedules, route repair, retries, and power evidence.

Coverage fundamentals Connects node placement to sensing radius, redundancy, uncertainty, gaps, and coverage maintenance.

35.25 What’s Next?

This section: What’s Next? — Continue with Mobile WSN Fundamentals Review to compare fixed and moving designs.

Continue with Mobile WSN Fundamentals Review to compare fixed and moving designs. Use MWSN Nodes, Sinks, and Data MULEs Review for mobile roles. Use MWSN Types and Mobile Entities for types of movement. Use WSN Coverage Fundamentals when sensing coverage is the main risk.

Find help

Search reviewed answers

3 reviewed answers.

Where should I start in a module?

Open the module page from the sidebar to see its chapters in order. Use the module map to return to a topic you need.

Modules and paths

Reviewed 2026-10-16

What can I try when a project does not work?

Check the symptom, then work through the diagnostic steps. Keep the error message and the smallest example that reproduces it.

When you are stuck

Reviewed 2026-10-16

How do interactive examples work?

Use the interactive guide to check how examples and simulations work before changing your project.

Interactive examples guide

Reviewed 2026-10-16