Soil-sensing path with reserve power

Connect reserve power while preserving the soil sensor path through a gateway to the cloud.

Physics Phoebe, your practice guide

Physics Phoebe
Predict which checkpoint will change, then test the connection.

IoT Ideator

Design Studio

Connect reserve power while preserving the soil sensor path through a gateway to the cloud.

Simulation — built in · No account

Version tested: aa0f6c2f299ef9404864df05928c6856471a9a98. Date: 2026-09-05.

Open the prepared mission; follow the guide and live checkpoints.

Open this design in the Design Studio (new tab)

Steps

Screens captured against IoT Ideator aa0f6c2f299ef9404864df05928c6856471a9a98 on 2026-09-05; the tool may have moved on — the text steps are the contract.

  1. Step 1

    Do
    In the Working View canvas, select Soil Moisture Sensor and inspect its analogue output and supply requirements.
    You will see
    The capacitive sensor appears connected to the ESP32. The model does not show a real soil-moisture measurement.
    Why it matters
    The chapter treats a datasheet as a promise with conditions. Output type and supply requirements are conditions to check before trusting the part.

  2. Step 2

    Do
    In the Working View canvas, select ESP32 and inspect its BLE connection to Protocol Translation Gateway.
    You will see
    The prepared gateway appears on the route from the sensor toward the cloud.
    Why it matters
    Start with the decision the reading must support. Tracing this route identifies where the reading travels, before considering whether its timing suits that decision.

  3. Step 3

    Do
    In the Power panel, add Li-Po Battery to the canvas.
    You will see
    The battery appears as a separate component. The connected-reserve checkpoint remains incomplete.
    Why it matters
    The chapter reads power needs alongside sensor performance. Adding a battery names a supply option but does not yet connect that option to the controller.

  4. Step 4

    Do
    In the canvas, link the Li-Po Battery power output to the ESP32 power input.
    You will see
    The connected-reserve checkpoint passes. It does not certify regulator choice or field runtime.
    Why it matters
    A supply claim needs its limit, unit, and test condition. The connection check cannot replace the electrical conditions recorded in the datasheet.

  5. Step 5

    Do
    In the Scenarios panel, read the connected-reserve, edge-to-cloud-route, and valid-link checkpoints.
    You will see
    All three checks pass, with the gateway connected to ThingsBoard.
    Why it matters
    Passing the design checks supports only the claims they inspect. The chapter still requires the full datasheet and field evidence for the installed sensor.

  6. Step 6

    Do
    In a browser tab, open the linked chapter knowledge check and identify which changed installation condition needs another test.
    You will see
    The question asks whether a bench result still applies outside the datasheet’s stated conditions.
    Why it matters
    The review record ties a claim to its test conditions. Naming the change that breaks those conditions tells the next reviewer when to test again.

Chapter checks

These questions refer to the chapter’s examples. Use the return links to review their answers.

  1. A sensor works in a quick bench demo, but the datasheet says the accuracy claim depends on a narrower temperature condition than the planned installation. What should the practitioner do?

    Return to the chapter’s knowledge check

  2. Why should a datasheet review include retest triggers after the sensor is selected?

    Return to the chapter’s knowledge check

Return to How to Read Sensor Datasheets · Browse Tutorials