KNOWLEDGE BASE.
// Frequently asked questions regarding hardware limitations, safety loops, and firmware architecture.
What is the maximum throughput of the telemetry websocket?
The ESP32 firmware is hardcoded to publish a telemetry frame every 500ms. Attempting to push the HiveMQ broker faster than 100ms per frame will result in buffer overflows on the ESP32's limited SRAM, triggering an automatic watchdog reset. For the dashboard, 2 frames per second provides completely fluid UI updates without saturating the IoT bandwidth.
How does the hardware-level E-Stop function?
The E-Stop is not a software gimmick. It relies on a 10K NTC thermistor mechanically bonded to the XL4016 heatsink. If the thermistor analog read exceeds the calibrated 55°C threshold, Core 0 instantly pulls the 5V relay logic pins LOW, physically disconnecting the load from the power rails. The dashboard will reflect a 'STATE_THERMAL_LOCKOUT' error, and it requires a physical button press on the hardware to clear.
Why use MCP4131 Digital Potentiometers instead of PWM?
Traditional Arduino-based power supplies use smoothed PWM to drive a control transistor. This introduces significant voltage ripple and instability under heavy loads. By using the SPI-driven MCP4131 digital potentiometer, we physically alter the resistance in the XL4016's analog feedback loop. This maintains the clean, ripple-free characteristics of an analog supply while offering microsecond-accurate digital control.
Is the platform isolated from the main PC?
Yes. The entire BenchCore architecture communicates entirely over WiFi via MQTT to a cloud broker (HiveMQ). There is zero physical connection (USB/Serial) required between the high-power bench supply and your expensive development laptop, protecting your primary workstation from accidental ground loops or voltage spikes.
Can I flash the firmware over-the-air (OTA)?
Yes. The ESP32 firmware includes standard OTA routines. However, for safety reasons, OTA updates are completely locked out while any of the power rails are engaged (Relay HIGH). The system must be in STATE_STANDBY before it will accept a new binary payload.
Why is the AI reasoning feature necessary?
While raw numbers (Volts, Amps, Temp) are useful, complex failures often require context. The integrated AI system analyzes the telemetry stream (e.g., a slow thermal creep coupled with a steady current draw) to predict component stress or short-circuits *before* the hardware E-Stop is forced to trigger.
Need further clarification?
// System architects are available during the STEM Exhibition floor hours. Please refer to the primary technical manual (SYS.DOCS) before escalating hardware-level inquiries.