docs: switch to ESP32-S3 and add logging server
- Update HARDWARE.md to recommend ESP32-S3 over RP2040 to support Wi-Fi logging capabilities and better GPIO availability. - Initialize a Node.js Express server to receive and store test results from the hardware device. - Add a web-based dashboard to visualize HDMI pin status history, including basic pass/fail logic for voltage drops.
This commit is contained in:
10
HARDWARE.md
10
HARDWARE.md
@@ -9,10 +9,10 @@ This project aims to create a handheld HDMI tester for console repair technician
|
||||
|
||||
To measure diode mode (voltage drop across a diode junction), we need a microcontroller with an ADC and the ability to source a small constant current or use a pull-up resistor.
|
||||
|
||||
### 1. Microcontroller: ESP32 or Raspberry Pi Pico
|
||||
- **ESP32**: Integrated Wi-Fi/BT (good for future logging), multiple ADCs.
|
||||
- **RP2040 (Pico)**: Great documentation, dual-core, very affordable, stable ADCs.
|
||||
- **Recommendation**: **Raspberry Pi Pico** for its simplicity and 3.3V logic which is safer for HDMI lines.
|
||||
### 1. Microcontroller: ESP32 (S3 or DevKitV1)
|
||||
- **ESP32**: Integrated Wi-Fi/BT is essential for the server-side logging feature. It has multiple ADCs and enough GPIOs to drive the multiplexers.
|
||||
- **RP2040 (Pico W)**: Also an option, but ESP32 has better community support for async HTTP clients.
|
||||
- **Recommendation**: **ESP32-S3** for its high number of GPIOs and built-in Wi-Fi.
|
||||
|
||||
### 2. Multiplexers (Mux)
|
||||
Since the Pico doesn't have 19 ADC pins, we need multiplexers to switch between the HDMI pins.
|
||||
@@ -39,5 +39,5 @@ Since the Pico doesn't have 19 ADC pins, we need multiplexers to switch between
|
||||
|
||||
## Next Steps
|
||||
1. Define the Pinout mapping.
|
||||
2. Create the software structure (C++ or MicroPython).
|
||||
2. Create the software structure (C++ / Arduino with ESP32 WiFi libraries).
|
||||
3. Implement the measurement logic.
|
||||
|
||||
Reference in New Issue
Block a user