PCBGrade

For educators

How much grading time does a measured lab return?

Students design the board. The server grades the published rules. You see who finished, how the scores spread, and which rules the class misses. The requirements they read are the requirements that are scored.

01

Create a class

Name the class. The workspace gives you a join code you can turn on or off.

02

Assign a problem

Pick from the same twenty challenges. A due date is optional. The score is the server grade.

03

Students join

A student redeems the code, opens the lesson, and designs in the editor.

04

Read the cohort

The class page shows who passed, the score bands, and the rules that failed most often.

Class pageEmpty, before the first assignment

Students

0

Roster count

Assignments

0

Problems you assign

Passed seats

—

Passed / enrolled

Assignments

No problems assigned. Scores show up after a student submits in Learn.

Score bands

90–100, 70–89, submitted and not passed, not submitted.

Common errors

Failed rules from the server report, with the share of submissions. Nothing is counted until a student submits.

What the class page shows

  • Roster. Each student, with pass or not-yet and the best server score.
  • Assignments. Passed seats over enrolled seats, and an optional due date. A pass after the deadline is marked late. The number is still the server grade.
  • Common errors. Failed rules grouped from the submissions the class actually made.
  • Score bands. 90–100, 70–89, submitted and not passed, and not submitted.

Can a student game the grader?

The score is connectivity, width, clearance, length, current, and the other published properties, computed from the design. Many layouts pass. A screenshot of one solution does not. A challenge number is a limit for that problem, written in the requirements before they submit. Shorts and unfinished nets cap the score where the problem says so.

The curriculum you would assign

  1. Problems 1–5

    Foundations

    Afterward: Route and check a simple board

  2. Problems 6–10

    Core PCB Engineering

    Afterward: Place power parts in the order the current and the fault require

  3. Problems 11–15

    Intermediate PCB Design

    Afterward: Keep a pair on its reference and sample a signal without cutting the ground

  4. Problems 16–18

    Advanced PCB Design

    Afterward: Repair spacing, heat, and build defects without breaking the circuit

  5. Problem 19

    Engineering Judgment

    Afterward: Repair a faulty board from evidence, then recheck the copper

  6. Problem 20

    Capstone

    Afterward: Finish a four-layer data-acquisition design and read the measured result

Read the curriculum introduction

What a student needs

  • A desktop browser. The editor is built for a laptop, not a phone.
  • An account. Drafts and scores stay with that account.
  • The lesson before the challenge, if they are new to the topic. Advanced students can open the editor directly.
  • No local EDA install for the twenty challenges. Analyze, if you use it, accepts a KiCad board, an Altium Designer PCB (.PcbDoc), or an IPC-2581 export.

Start a class

Create an account, open Profile, and redeem the instructor access code for your course. From there you create a class, share a join code, and assign problems from the same twenty challenges.