Brain Turbocharger

For centuries, humans have searched for ways to think faster, focus harder, and unlock hidden mental potential. Monks meditated. Scientists studied the brain. Silicon Valley invented productivity apps. I built the Brain Turbocharger, a wearable that measures your brainwaves and activates cooling fans when you're concentrating.

What if concentrating really did make your brain work harder?

At the heart of the project is a heavily modified Star Wars Force Trainer, a toy originally designed to measure changes in attention and relaxation using a basic EEG headset. In the original game, players use "the Force" to levitate a ball inside a clear tube. In this version, the Force Trainer has been repurposed into something far more important: powering an absurd number of cooling fans.

When the wearer focuses, the Force Trainer detects the change in brain activity and sends a signal to an Arduino microcontroller, which interprets that signal activates a network of fans embedded in a helmet. The harder the concentration, the more dramatic the airflow becomes. The result is a completely scientific* feedback loop in which intense thinking causes the helmet to sound increasingly like a small aircraft preparing for takeoff.

Along the way, the project evolved into a surprisingly complex engineering challenge. What began as a simple weekend experiment eventually required custom electronics, modified power systems, relay-controlled startup sequences, signal conditioning, and more troubleshooting than any reasonable person would voluntarily undertake.

Most importantly, it answers a question nobody was asking:

If thinking harder generated horsepower, what would that look like?

* Science may have been stretched slightly in the pursuit of entertainment. 🦕

Supplies

Star Wars Force Trainer toy (or any EEG type toy that you can tap a motor signal from)
Decoy Board
45W battery (20000mAh)
2x UBEC Step-down module
2x MOSFET triggers
Arduino
30x 40mm fans
5V relay
Step up power converter
DC bench top variable power supply (for testing)
Hole saw
Plastic hardhat

Code

I needed a micro controller to help me keep the components talking to each other and getting signal from the noise the Force Trainer base sends out. This is where the Arduino comes in.

Here's the Big Idea: Force Trainer headset signal → Force Trainer base activate → Arduino reads activation → opens fan relay

The Arduino is able to handle the Big Idea of opening the fan relay, but it does a few other things. Since we're using a single power supply everything want to turn on at once, but the Force Trainer base needs to be on before the headset, so the Arduino handles small delay in powering on the headset. There is also a lot of noise coming from reading the Arduino receives from the Force Trainer base, so it smooths out this signal and allows a cleaner reading from the motor. Lastly, the Arduino also throttles the fan duration so it's not directly tied to the base fan, staying on for a few seconds longer after the signal decays, this allows the fans to continue to spin while the base fan may start or stop. If a new fan threshold is reached the timer resets for the fans.

// ====================================================================

// PROJECT: Brain Turbocharger

// AUTHOR: Mike Warren / Dinomike 🦕

// DATE: May 2026

//

// DESCRIPTION:

// Hacked Star Wars Force Trainer system. Reads analog brainwave

// signals via A0 and uses an Arduino Uno to trigger a dual-battery fan

// cooling array. Both isolated MOSFETs are triggered simultaneously

// via Pin 9, while maintaining delayed headset power on Pin 8.

//

// LICENSE: Creative Commons BY-NC-SA 4.0

// (Attribution-NonCommercial-ShareAlike)

// You are free to share and adapt this code, provided

// credit is given, changes are noted, and it is NOT

// used for commercial purposes.

// ====================================================================

int fanPin = 9; // Triggers BOTH MOSFET modules simultaneously

int relayPin = 8; // Headset Boot Sequencer

float val = 0;

// --- Calibration Thresholds ---

// Adjusted for the resistor circuit layout where readings rest high and dip on focus.

const int FOCUS_THRESHOLD = 940;

// Timing & Ramp Variables

unsigned long fanOffTime = 0;

const unsigned long holdDuration = 7000; // Sustained 7-second fan hold time

int currentPWM = 0; // Tracks the actual speed of the fans

const int targetPWM = 220; // Maximum safe high power for the fans

void setup() {

Serial.begin(9600);

pinMode(fanPin, OUTPUT);

pinMode(relayPin, OUTPUT);

// Ensure fans start dead silent

analogWrite(fanPin, 0);

// 1. Safe Headset Startup Sequence

digitalWrite(relayPin, LOW); // Ensure headset is OFF initially

delay(2000); // Wait 2 seconds for base unit to boot up

digitalWrite(relayPin, HIGH); // CLICK! Turn headset power ON to initiate pairing

// 2. Adjust PWM frequency to ~31Hz for the MOSFET module

TCCR1B = (TCCR1B & 0b11111000) | 0x05;

}

void loop() {

int raw = analogRead(A0);

// Heavy smoothing math for a clean analog envelope

val = (val * 0.9) + (raw * 0.1);

// Trigger fans when focus pulls the voltage signal BELOW the threshold

if (val < FOCUS_THRESHOLD) {

fanOffTime = millis() + holdDuration;

}

// --- SMOOTH RAMP LOGIC (Controls Both MOSFETs at once) ---

if (millis() < fanOffTime) {

if (currentPWM < targetPWM) {

currentPWM += 4; // Ramps both banks from 0 to 220 in about 1.6 seconds

if (currentPWM > targetPWM) currentPWM = targetPWM;

}

} else {

currentPWM = 0;

}

analogWrite(fanPin, currentPWM);

// Output formatting optimized for clear tracking in Serial Plotter

Serial.print("Smoothed_Signal:");

Serial.print(val);

Serial.print(",");

Serial.print("Threshold:");

Serial.print(FOCUS_THRESHOLD);

Serial.print(",");

Serial.print("Fan_Output_PWM:");

Serial.println(currentPWM);

delay(30); // Runs the loop ~33 times a second

}

// stay awesome 🦕

Wiring

After some trial and error I managed to find a setup that woks for this project.

A large 45W battery is used to supply power. This was chosen because there is a large power draw when all the fans activate, and not all battery packs can handle a rush load like that. Most battery packs are also voltage and current limited, meaning thay can't deliver more than 5V and 2A. To get around this I used a decoy board which tricks the battery into giving us as much power as I need. Using the DIP switches on the decoy board I wanted 12V, which gives me almost 4A (45W = 12v * 3.75A). This is plenty of power to run everything this project needs.

This power is then divided into 2 UBEC's which drop this voltage down to 5V while keeping the amps. One UBC goes to power 2 fan arrays which are controlled by relays, which are activated by the Arduino.

The other UBEC goes to power the headset, fan base, and Arduino. The headset and Arduino both run on 5V, but the base requires more power to a step-up power converter is used. There's a dial on the converter to set the power needed for the base. This then powers the base.

Here's an interactive link for the wiring:

https://app.cirkitdesigner.com/project/f917d6b6-a099-4b5b-8e73-3e02cbc2843f

Tapping Into the Motor

The battery power was wired into the headset and base battery compartment terminals (instead of the AA batteries it used originally), and the Arduino was powered through the USB A jack.

The only other bit of electronics that was needed were 2x 100k Ω resistors placed on the power contacts for the Force Trainer base motor. This was used to help reduce the noise the motor signal created for the Arduino.

Testing & Validating

Before committing everything with solder there was plenty of testing to make sure I had things working correctly. It was a mess of wires, but worth it to troubleshoot while everything was laid out.

With the headset on and Arduino IDE open with the visual plotter, I could see the baseline readings (left graph), and then when the motor activates the top line crosses the threshold and activates the fan array. The bottom line represents the fans powering up. I spent some time here dialing in the readings the Arduino was getting and smoothing out the signal, and the threshold activation window.

Map Fan Array on Helmet

With the electronics figure out, I could move on the the helmet. I figured a plastic construction hardhat was a good choice as it's already designed to be worn on your head, it's plastic so I can easily drill into it, and there's a gap inside the hardhat between where the webbing rests on your head and the outer shell, creating an air gap for air to flow through. Perfect!

Inside the hardhat there are a few places where the head webbing is connected to the shell, so I couldn't drill or modify these areas. I used blue tape to cover the exterior of the hardhat to help me place the fans, carefully marking the webbing connection from the inside on the outside so that I didn't modify the helmet in these areas.

I placed a 40mm fan on the helmet and traced around it, then continued tracing around fan placements until I had covered the helmet with as many fans as I could fit.

Drilling Helmet

I used a hole saw that was the same diameter as the fan blades (not the fan housing) and drilled into the hardhat at the areas marked. I then used a small drill bit to make openings where the fan mounting holes were located. This didn't have to be perfect as the machine screws can bite into the plastic hardhat easily enough if they are a bit off.

The edges were deburred to make them nice and smooth.

Add Fans

Fans were installed over every opening and held in place with 2-3 machine screws. The screw holes in the helmet are slightly undersized so that the screw threads bite into the plastic, so there is no need for nuts on the other side.

I oriented the fans so that the wire tails all went towards the back of the helmet. I would figure out the wiring arrangement/fan grouping later, it was more important to get them all installed. Make sure the fans are pointing with the airflow going into the helmet, that way you can feel the fans blowing on your sweaty scalp when you're in extreme thinking mode.

Stuff It All in a Helmet

A construction helmet is not only a good choice for a chassis for fan mounting, the webbing inside that cradles your head also creates ample space to put some of the smaller electronics, like the relay, step-up power converter, and even the EEG headset, allowing the legs of the headset to poke down below the inside brim of the helmet and onto the connection points of your head (one on the forehead and two behind the ears).

To mount the Force Trainer base I removed most of the housing and kept the signal receiver, operation buttons and LEDs, and the original fan. These were all mounted onto the side of the helmet. I could have removed most of this, but having an extra fan from the original Force Trainer works well for my intention, and the flashing LEDs on the base are actually a visual signal to the operator to let them know what the intensity setting of the Force Trainer is at.

Power Pack

To power everything I needed a large 20000 mAh battery back to ensure I had lots of juice to run everything for a sustained period of time. Wile the size was important, of equal importance is the 45W, which means I can draw a large current at once. The external fan array draws 32 × 0.15A = 4.8A total. With this much draw this branch had it's own dedicated UBEC.

The power pack was mounted on the back of the helmet, on a spot with no fans. The holder for the battery also offered some places to mount the rest of the electronics that didn't fit anywhere else.

Troubleshooting

There was lots. Nothing wanted to cooperate. I found the easiest way to navigate this was isolating as much as possible and hunting down the problem, which was usually a loose wire or an attempt to draw too much power at once. A multimeter and patience was all that was needed in the end.

Turbo Your Brain

Projects like this are a reminder that innovation doesn't always begin with a practical problem. Sometimes it begins with a ridiculous idea and the willingness to see where it leads. Along the way I learned more about electronics, power systems, and troubleshooting than I ever expected. More importantly, it reminded me that some of the most rewarding projects are the ones that exist simply because you're curious enough to build them.

Does it make me smarter? Probably not.

Does it make me look smarter? Also probably not.

But it does provide immediate, wind-powered feedback whenever I concentrate, and that's more than most productivity tools can claim.

Thanks for following along, and if you build one of your own, I'd love to see it. 🦕