Got it — when a developer asks for *work requirements*, they basically want the **functional specification**: what exactly the software must do, how the ESP32 pins are mapped, which features are mandatory, and what counts as "done." Here’s a **clean Work Requirement Document (WRD)** you can hand over directly. It includes pin mapping, software features, deliverables, and acceptance criteria. --- # **Work Requirement Document (WRD)** **Project:** Custom Visual Programming IDE for ESP32 DevModule with CH340C **Client:** MY STEAM LAB **Developer:** \[Name/Company] **Date:** \[Insert Date] --- ## **1. Hardware Specification** * **Microcontroller:** ESP32 DevModule (with CH340C USB-serial chip) * **Peripherals & Sensors:** * LDR (Light Dependent Resistor) → IO34 * IR Sensor → IO35 * Temperature Sensor (Data) → IO32 * Ultrasonic Sensor: * Trigger → IO33 * Echo → IO32 (shared pin with Temp data – must be handled in software) * Touch Sensor → IO12 * OLED Display (I2C, 4-pin) → SCL=IO15, SDA=IO13 * Motors: * M1 → IO19, IO18 * M2 → IO5, IO17 * M3 → IO23, IO22 * M4 → IO21, IO16 * Joysticks: * J1: V-axis IO4, H-axis IO2 * J2: V-axis IO26, H-axis IO25 * Servo Motor (standard PWM output, pin assignable) --- ## **2. Software Requirements** ### **2.1 Core Features** 1. **Block-based Workspace** * Scratch/Blockly style drag-and-drop blocks. * Predefined blocks for: * Digital read/write * Analog read * PWM motor control (M1–M4) * Servo motor control * OLED text/image display * Ultrasonic distance read * Touch sensor read * IR sensor read * LDR sensor read * Joystick input read * Loops, conditionals, math, variables, functions 2. **Code Generation** * Convert blocks into **Python (MicroPython)** code. * Convert blocks into **C/C++ (Arduino or ESP-IDF)** code. * Generated code must include all required libraries, setup, and loop logic. * Output must be clean, beginner-friendly, and directly compilable. 3. **Compiler & Uploader** * Integrate compiler (PlatformIO or Arduino CLI recommended). * Upload firmware to ESP32 over CH340C USB-serial automatically. * Show progress, errors, and success messages. 4. **Serial Terminal** * Built-in terminal window to show ESP32 outputs (Serial Monitor). * Configurable baud rate (default 115200). * Option to send input commands (for REPL if Python). 5. **Project Management** * Save/load block projects. * Export generated code to local files. * Compile & upload directly from software. --- ### **2.2 Deliverables** * Desktop application (Windows mandatory, macOS optional). * Source code (well-structured, documented). * Required ESP32 libraries and drivers packaged. * Example projects for each sensor/actuator (at least one demo per component). * User documentation (how to use blocks, generate, compile, and upload code). * Developer documentation (how to add new blocks/libraries). --- ### **2.3 Acceptance Criteria** * All pin mappings implemented exactly as specified. * Blocks must successfully generate both Python & C/C++ code. * Code compiles and runs on ESP32 without user modification. * Upload works via CH340C on Windows. * Terminal displays ESP32 logs/output in real-time. * At least **5 example projects** must be provided (e.g., LDR-controlled motor, joystick-controlled servo, ultrasonic distance display on OLED). * Final delivery includes source code, installer, libraries, and test results. --- ## **3. Milestones (linked to contract)** 1. Prototype editor with one working block (e.g., LDR read). 2. Core editor + Python/C++ code generation. 3. Compiler & uploader + working terminal. 4. Full hardware integration (all sensors/motors tested). 5. Documentation, final source code, and installer handover. --- ## **4. Developer Responsibilities** * Deliver code under **work-for-hire** terms (IP belongs to Client). * Ensure stability and compatibility with ESP32 DevModule (CH340C). * Provide basic support for 30–90 days after delivery for bug fixes. --- This WRD + the NDA + Milestone Contract together form your **complete package** to give to the developer.