Fifteen days sounds like plenty of time, right up until day 12, when you're still deciding which sensor array to buy and your robot is a pile of parts on the desk. That's not bad luck — it's the default outcome of treating "prepare for a competition" as one task instead of six sequential ones.

This isn't a parts list. It's a day-by-day sequence: what to do, in what order, and why the order matters — because a line follower punishes skipped steps in a very specific way. Calibrate before you tune and the tune is garbage. Tune before your firmware is stable and you're chasing a bug that isn't real. Skip practice runs and your first attempt at an actual track happens in front of judges.

Follow this and by day 15 you'll be standing at the start line with a robot that's been tested, not just built.

The 15-Day Plan at a Glance

Days 15–13: Learn Before You Touch a Screwdriver

Before you buy anything, get three concepts straight: how the sensor sees the line, how the motors respond to a correction, and what PID is actually doing when your robot hugs a curve instead of overshooting it.

You don't need to derive the math. You need to know that a line follower repeatedly asks "am I centered, and by how much?" — and that answer comes from an infrared sensor array reading contrast between a dark line and a light floor, thousands of times a second.

If you're unsure which robot to even buy, Techgeeks' Mark 1 vs Mark 2 vs Mark-X breaks down which one matches your track — and its own conclusion is blunt: if you can't decide, start with Mark 1 regardless. Every builder fast on the advanced bots got there by tuning something simpler first.

Every mistake in the phases below traces back to skipping this one. You can't debug a robot you don't conceptually understand.

Days 12–10: Decide, Order, and Stop Deliberating

Fifteen days doesn't leave room for a long comparison spiral. For a first competition, the Mark 1 Line Follower Robot Kit is the standard starting point — a real 8-channel ARC8 sensor array and a proper PID loop, not the fixed 3-sensor comparator setups that teach you nothing about tuning.

Two decisions to make here:

• DIY kit (₹4,499) vs. pre-assembled & tuned (₹4,999). The pre-tuned version saves you the wiring and soldering, but "pre-tuned" means tuned on their bench, not your track — you'll still calibrate and sanity-check the PID values yourself in phase 5. Never soldered before, on a 15-day clock? Pay the extra ₹500. Every hour matters more than the money.

• The basic chassis is enough. Skip the suction chassis and downforce hardware for now. Techgeeks' own chassis guide is direct about this: a chassis upgrade should solve a measured problem, and on your first build, you don't have measurements yet.

Order today, not day 10. Shipping is free above ₹1,999, and the kit alone clears that.

Days 9–7: Build — Chassis, Motors, Sensor, Board

This is the only phase that's genuinely hands-on. Mount the motors and wheels to the chassis, seat the Blueprint 01 controller board — the board running the motor driver, voltage regulation, and sensor inputs — and attach the ARC8 sensor array low at the front, where it can read the line without dragging.

Three checks before you close anything up:

• Wheels spin freely with no chassis rub.

• Sensor arm sits level and parallel to the floor.

• Battery connector polarity is correct — reversed LiPo leads are the single most common first-build mistake.

While you're wiring, it's worth understanding what your motor driver can and can't handle under sustained load. Motor driver heat and current basics covers why small drivers overheat during long practice sessions — exactly the kind of failure that shows up on day 14, not day 8.

Build fully before you power anything on. A half-wired robot that "sort of moves" wastes more time than a fully-wired one that doesn't move yet.

Days 6–5: Flash Firmware and Confirm It Moves

Upload the base firmware and — before touching a single PID value — confirm the fundamentals: both motors spin the correct direction, both wheels respond to the same command with the same speed, and the sensor array returns readings when you wave it over a printed line.

This is a wiring test, not a tuning test. If a motor spins backward, that's a wiring or firmware direction flag issue, not a PID problem. Chasing it with Kp adjustments burns a day you don't have.

Days 4–3: Calibrate, Then Tune — In That Order

Run the calibration routine first: rotate the robot across the line so it records the sensor's minimum and maximum readings on your actual track surface, under your actual lighting. Skip this and every PID value you tune afterward is tuned against wrong data.

Once calibrated, tune in the order that actually works: isolate Kp alone with Ki and Kd at zero, increase it until the robot wobbles on a straight line, then back off to roughly 70% of that value. Add Kd next to kill the overshoot. Most line followers never need Ki at all.

Techgeeks' PID guide goes deep on why each term does what it does — worth the read if day 4 still feels theoretical. The short version is enough for now: P reacts to now, D reacts to how fast you're closing the gap, and copying someone else's Kp/Kd numbers almost never works, because your chassis weight and motor torque aren't theirs.

Day 2: Practice Like the Judges Are Watching

Desk testing and track testing are different problems. Run full laps at the speed you intend to race at, not a cautious crawl — PID behavior changes with speed, so a smooth slow-speed run can fall apart at competition pace.

Time each lap. Deliberately nudge the robot off-line mid-run and watch whether it recovers. A robot that only works when it never makes a mistake will lose to one that recovers well from small ones.

Day 1: Freeze the Firmware

Today you stop changing things. Techgeeks' race-day firmware checklist puts it plainly: competition firmware should be boring, and the fewer decisions you make at the table, the more attention you have for the track.

Before you pack up:

• Save your working PID values as a labeled, known-safe profile — don't leave them scattered across test edits.

• Turn off any debug serial output; it can slow the control loop when performance actually matters.

• Pack one spare battery, one spare upload cable, and a spare pair of N20 wheels (₹349) — cracked wheels under competition stress are common and cheap insurance.

No "just one more tweak." Every late change is untested by definition.

Race Day: Recalibrate On-Site, Then Trust the Work

Tracks look different under competition lighting than they did in your room. Recalibrate the sensor array on the actual competition surface before your run — non-negotiable, even if the robot "worked perfectly" the night before.

Confirm motor direction one more time after the final upload, run your known-safe profile, and resist the urge to touch Kp in the pit five minutes before your run. If something's genuinely broken, fix wiring, not tuning — bad tuning under pressure has ended more runs than bad hardware ever has.

Mistakes First-Timers Make in Their Last 5 Days

• Still comparing sensor options on day 10, with no build time left.

• Tuning PID before running calibration on the actual track surface.

• Changing more than one PID term at a time, under pressure, on race morning.

• Skipping full-speed practice and only ever testing at a crawl.

• Making "just one more" firmware change the night before.

Conclusion

Fifteen days is tight, but it's enough — if it's spent in this order: learn, decide, build, verify, calibrate, tune, practice, freeze. Most first-timers don't lose time because the robot is hard to build. They lose it by building and tuning out of sequence and ending up debugging three problems at once on day 14.

Start with the Mark 1 Line Follower Robot Kit if you haven't already, and treat this like the checklist it is, not a suggestion.

What day are you starting on — day 15, or are you already behind? Tell us in the Techgeeks community, and we'll help you figure out where to compress.