This is an old revision of the document!


ARGB PC Fan Controller with Wireless Remote

1. Introduction

The project represents an intelligent and independent system for controlling the cooling and lighting (ARGB) inside a PC case. It is based on a two-node architecture that communicates wirelessly via Wi-Fi protocol, eliminating the need for long cables and bloatware software installed on the operating system.

Project Objectives:

  • Monitoring internal PC temperature.
  • Automatic/manual RPM (PWM) control.
  • Managing ARGB visual effects.
  • Remote control interface.

2. Project Description (What it does)

The system is divided into two main units working together:

A. Central Unit (The Controller)

It is the heart of the system, implemented on a T-HMI (ESP32-S3) module with an integrated LCD display.

  • DHT22 Sensor: Constantly reads the case temperature.
  • ARGB Control: Manages the colors and modes of the Thermalright fan.
  • Real-time Display: Projects the RPM, temperature, and current mode on the screen.

B. The Remote (Control Unit)

Built on an ATmega328P Xplained Mini board connected to an ESP-01S module.

  • Features an expansion board with 5 buttons.
  • Allows changing operating modes and speed remotely.
  • Externally powered for total portability.

3. Operating Modes

  • Auto Mode (Default):
    • The system automatically adjusts the fan speed using a temperature curve.
    • For every 5°C threshold reached, the fan speed progressively increases or decreases to maintain the balance between cooling and noise.
  • Manual Mode:
    • The user takes full control via the remote.
    • Dedicated buttons can be used to increase or decrease the speed regardless of the read temperature.

4. Project Purpose and Motivation

What is its purpose?

The primary purpose is to provide a user-friendly hardware interface that allows users to easily monitor and control fan speeds and ARGB lighting. While connecting a fan directly to the motherboard provides basic cooling, this project focuses on delivering accessible, real-time control without relying on proprietary software. It essentially protects the user from the risk of losing manufacturer support (abandonware), or turning into resource-heavy bloatware over time.

Origin of the Idea

The idea stemmed from the frustration caused by software dependency and forced firmware updates of commercial products, which often break functionality or add unnecessary background processes. I wanted a hardware-level “Plug & Play” device that guarantees longevity and provides clear information on a physical display, completely independent of the PC's software ecosystem.

Usefulness for users

  • For me: It gives me precise, physical control and immediate visual monitoring over my PC's thermal state and aesthetics without tabbing out of applications or games.
  • For others: The same as above, but also Future-Proof & No Obsolescence: Since it doesn't require a dedicated app, it will never lose functionality due to lack of software support from a manufacturer.
    • OS Independence: Works on Windows, Linux, or macOS seamlessly, without requiring any drivers.
    • Zero Resource Consumption: Does not load the PC's processor or RAM (crucial for gamers or heavy-duty tasks).
    • Customization: While the interface is simple, it ofers all the customization a normal user needs.

5. Hardware Components Used

  • Microcontrollers: ESP32-S3 (Central unit) and ATmega328P Xplained Mini (Remote).
  • Remote Communication: ESP8266 ESP-01S Wi-Fi module.
  • Sensor: AM2302 (DHT22) for temperature and humidity.
  • Actuator: Thermalright C12CW-S ARGB Fan.
  • Interface: LCD Display (integrated on T-HMI) and a 5-button module.
  • Power Management:
    • Remote: External battery and an AMS1117-3.3V voltage regulator (to step down voltage for the Wi-Fi module).
    • Controller: Laptop USB-C connection (5V for the ESP32 logic and ARGB LEDs), a 12V 1A Wall Adapter, and a DC Screw Terminal (for the fan motor).

Block Schema

Hardware Design

Schema electrica controller: Schema electrica telecomanda

Software Design

Descrierea codului aplicaţiei (firmware):

  • mediu de dezvoltare (if any) (e.g. AVR Studio, CodeVisionAVR)
  • librării şi surse 3rd-party (e.g. Procyon AVRlib)
  • algoritmi şi structuri pe care plănuiţi să le implementaţi
  • (etapa 3) surse şi funcţii implementate

Rezultate Obţinute

Care au fost rezultatele obţinute în urma realizării proiectului vostru.

Concluzii

Download

O arhivă (sau mai multe dacă este cazul) cu fişierele obţinute în urma realizării proiectului: surse, scheme, etc. Un fişier README, un ChangeLog, un script de compilare şi copiere automată pe uC crează întotdeauna o impresie bună ;-).

Fişierele se încarcă pe wiki folosind facilitatea Add Images or other files. Namespace-ul în care se încarcă fişierele este de tipul :pm:prj20??:c? sau :pm:prj20??:c?:nume_student (dacă este cazul). Exemplu: Dumitru Alin, 331CC → :pm:prj2009:cc:dumitru_alin.

Jurnal

Puteți avea și o secțiune de jurnal în care să poată urmări asistentul de proiect progresul proiectului.

Bibliografie/Resurse

Listă cu documente, datasheet-uri, resurse Internet folosite, eventual grupate pe Resurse Software şi Resurse Hardware.

Export to PDF

pm/prj2026/jan.vaduva/gabriel.eftimie.1779114546.txt.gz · Last modified: 2026/05/18 17:29 by gabriel.eftimie
CC Attribution-Share Alike 3.0 Unported
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0