Back to start

Parking sensor: Simulate → Debug → Save

Six repeatable software checks, fault recovery, and a saved project. No controller needed.

This is a read-only preview of the built-in guide. Steps below describe what you will do after starting your own project; no project has been created. Expected observations are software checks, not physical test evidence.

FluxBench is in private beta, by invitation only. An invited account is required to run, compile and save. Signing in does not grant an invitation.

Invited? Sign in to continue with this guide
  1. 1. Your own parking-sensor project

    This is your separate saved copy of the parking template. Its virtual ESP32, distance sensor, divider, three LEDs and piezo are already wired. You will check distance responses, diagnose a missing echo, compile the sketch, and reopen your work. No physical controller or PCB is needed.

    Guide position saves with the project. The verification badges describe the reference template; your edits need fresh checks. The time shown is an estimate, not a measured beginner result.

  2. 2. Trace the ECHO divider

    Follow the blue wire from ECHO to the 2.2 kΩ resistor. The junction with the 3.3 kΩ resistor goes to GPIO18; the other end of 3.3 kΩ goes to ground. This reduces a nominal 5 V echo to 3.0 V. TRIG goes to GPIO5. Each LED has its own 330 Ω resistor.

    Use Trace net or the named probe terminals in 2D/3D to follow the path. The divider matters because the ESP32 input is not 5 V tolerant. Physical assembly remains deferred.

  3. 3. Understand the schematic

    Pins with the same net label are electrically connected even without one long drawn wire. ECHO_5V and ECHO_3V are different nets separated by R4; R5 returns the 3 V side to GND. LEDG, LEDY and LEDR connect the matching GPIOs and LEDs. Use Show wires to make named connections visible.

    This pilot is a breadboard build. It does not include a fabrication-ready PCB or verified board footprint.

  4. 4. Run four distance checks

    Press Run code and click the HC-SR04 to change distance: 130 cm gives green/CLEAR; 70 cm green + yellow/APPROACHING; 25 cm all three/CLOSE; 10 cm red/STOP. Use Open parking checks below, choose Add parking checks if needed, and run the four named distances plus Parking exact boundaries. Each reports expected GPIO levels and completed Serial lines.

    Listen separately: silence, slow beeps, fast beeps, then continuous tone. Exactly 100/40/15 cm means APPROACHING/CLOSE/STOP. The saved checks use a teaching interpreter, not compiled ESP32 firmware or acoustic timing.

  5. 5. Check a missing sensor response

    Run Parking lost ECHO and recovery. It disconnects the ECHO jumper in an isolated replay, expects SENSOR FAULT and blinking red, then reconnects at 1000 ms and expects APPROACHING at 70 cm. Your live wires stay in place. To practice diagnosis, stop Run code, remove the GPIO18 jumper, and rerun a distance check. Expand Investigate on the failed expectation to locate the relevant circuit in 3D. Undo the removal and rerun.

    Restore the wire and get passing checks before saving. A missing echo is a fault, never proof of a clear space. This educational project is not a vehicle safety system.

  6. 6. Understand compilation

    Check that ESP32 is selected. You may compile now to see the separate toolchain result, then compile again after reopening for the final checkpoint. A successful compile proves the toolchain accepted this sketch; it does not prove that the circuit or sensor works. If you edited the code or circuit, repeat the distance and fault checks.

  7. 7. Save the software checkpoint

    Save your project with its current sketch, circuit, six scenario definitions and guide position. Record any changes and observations in the description. Scenario results are temporary: saving a passing run does not certify later edits. After reopening, this saved step returns; use the final compile step once you have checked the loaded project.

    Physical uploads, controller testing and PCB work are deferred. You can complete this software guide without any of them.

  8. 8. Reopen and repeat

    After the Save dialog confirms success, open saved projects and select this project. Selecting it reloads the saved copy and replaces any unsaved edits in the current workspace. The saved guide returns to the Save step; you do not need to save again. Confirm the circuit, sketch and six scenario definitions returned, rerun checks for fresh results, then choose the final compile step.

    If Save failed, resolve that first. Hardware remains untested. If checks fail after an edit, fix the circuit or code; do not widen an expectation just to get a pass.

  9. 9. Compile the reopened sketch

    Compile the sketch in the reopened project and inspect the result. The ESP32 Teaching interpreter executes supported behavior from the current sketch with a fixed sensor/circuit model; arbitrary edits may be inconclusive. This separate compile checks whether the actual source is accepted by the ESP32 toolchain. Neither result verifies physical timing, wiring or a controller upload. Record the compile outcome, then finish the guide.

    Finish only closes this guide. The pilot observer records success from the reopened project, passing fresh checks and compile result.

Support profiles and limits
FluxBench.AI