← All tools

PID Error Analyzer

Paste a run logged from the robot and get the numbers that describe it: overshoot, rise time, settling time and steady-state error. Tuning with evidence instead of by feel.

Inputs

Fill from a robot log (CSV)

A CSV the robot saved to its SD card, or any spreadsheet saved as CSV. It’s read on this device and isn’t uploaded anywhere.

One sample per line, time, value. Seconds and whatever unit you are controlling. A bare list of values also works, in which case the sample interval below is used.

The setpoint the run was aiming for.

%

How close counts as settled. 2% is a common choice.

sec

Only used when your data has no time column.

Results

Overshoot

—%

Peak value

—

Rise time

—sec

10% to 90% of target.

Settling time

—sec

Last entry into the band.

Steady-state error

—

Mean of the final 10%.

Tracking RMS error

—

From the moment it first reaches target. The number to compare tunings on.

RMS error, whole run

—

Includes the opening ramp.

Samples read

—

Direction changes

—

Across the whole run.

Play the run back

Play the run back
100%

Your logged run, value against time. The straight line across is the target and the band either side is the settling band you set. The marks are the two points rise time is measured between, the peak, and the moment it last entered the band for good. Scrub through and read the error at any moment: a run that crosses the target several times before it stays there is one with too much of something.

How this is calculated

Every number here is measured from your data. None of it depends on knowing your gains, which is the point: the response tells you what the gains are doing more reliably than the gains themselves do.

The measurements

  • Overshoot is how far past the target the peak went, as a percentage of the target. Some overshoot buys speed. A lot means P is too high or D too low.
  • Rise time is 10% to 90% of target, the standard definition. It measures how aggressively the loop attacks the error.
  • Settling time is the last moment the signal entered your band and stayed. Taken from the last crossing rather than the first, so a run that wanders back out is not credited with settling early.
  • Steady-state error is the average of the final tenth of the run. A stubborn offset here is the classic sign that I is missing or too small.
  • Tracking RMS error is measured from the moment the run first reaches target, so it describes how well the loop holds position. This is the number to compare two tunings on.
  • RMS error over the whole run includes the opening ramp, which is mostly a measure of how far the start was from the target. Use it to compare runs of the same move, not different ones.
  • Direction changes counts reversals across the whole run. Repeated reversals that are not shrinking mean the loop is oscillating rather than converging.

Reading them together

The pattern matters more than any single figure. Large overshoot with fast rise is too much P. Slow rise with no overshoot is too little. Overshoot that decays over several cycles wants more D. An offset that never closes wants I. A run that oscillates without settling is not tuned yet, and no amount of D will rescue a P that is far too high.

One run proves nothing

Log the same move several times before believing any of this. Robots are not repeatable enough for a single trial, and a tuning that looks better once often turns out to be the same tuning with a luckier start. Compare RMS error across several runs of each candidate.

Sources & assumptions

No VEX data is used. These are standard step-response measurements applied to numbers you supply, so nothing here goes stale between seasons.

Assumes a single step toward one target, sampled often enough to catch the peak. Sampling too slowly hides overshoot: if your log interval is close to the rise time, the reported peak is meaningless. Rise time is interpolated between samples; the other times are reported at sample boundaries.

    Every source the site uses, and when it was checked

    Save this run, and compare

    Keeps what is on screen so you can change something and see both sides of the change. Saved in this browser only, never uploaded.

    Make a notebook page

    Turns this calculation into a dated engineering notebook page: the setup, data, results, figures, working and sources, numbered and cited. You add the goal, the decision and the reflection in your own words, plus photos and sketches. Print it, paste it into Google Docs, or download a Word file or slides.

    My notebook

    Notebook page

    More
    Open My notebook

      This page

      Our own layouts

      A layout remembers how a page is set up: its type, its system, which parts print and which of your tables it uses. It never remembers a word, a number or a photo.

      Your team kept on this device
      Add someone to the team list
      Your words never written for you

      These are the parts a judge or teacher reads to see your thinking, so the page leaves them to you. Leave a box empty to get lined space for writing by hand. Start lines with "- " for a list. The notes under each box only count and point things out; they never change what you wrote.

      Rough notes

      Rough notes

      Rough notes

      Rough notes

      Rough notes

      Rough notes

      Rough notes

      Rough notes

      Rough notes

      The word counts can be measured against a target your team sets on My notebook. The reading level is Flesch-Kincaid grade level = 0.39 × (words ÷ sentences) + 11.8 × (syllables ÷ words) − 15.59. Syllables are counted by vowel groups, so the grade is an estimate of the school year the writing reads at. It says nothing about whether the writing is any good.

      One part at a time, with a clock. At the end of practice, while you remember it.
      How you tested your details

      Fill in what applies. These print as a small table under the method.

      Before and after

      Compare this calculation with a run you saved earlier on this tool (under “Saved runs”). The page shows what changed and by how much.

      A line through the data from your recorded table

      Pick two measured columns from the same table. The page plots them and draws the least-squares line, only across the range you measured.

      Robot log a CSV from the robot's SD card

      Load a CSV your robot saved. Pick the time column and up to three columns to plot, and type their units. Only those columns go on the page; the file stays on this device.

      Two versions' trials your data, compared

      Pick a column of recorded trials for each version, from this page or another saved page. The page shows both averages and a 95% range for the difference. The numbers are copied in when you pick them, so later changes to the other page don't change this one.

      Options compared your scores

      Score each option 1 to 5 on each criterion, and weight each criterion 1 to 5 by how much it matters. The page only multiplies and adds.

      Photos and sketches stay on this device

      Up to 4. Paste a screenshot with Ctrl+V, drop pictures here, or pick them. Photos are shrunk before they’re kept, and an unsaved page keeps them in its draft. Use Mark up to draw arrows, labels, dimensions and numbered callouts on a photo. Mark one photo Before and one After to print them side by side.

        Test plan written before testing

        Write this before you test: the question, what you expect with a number, and what result would make you drop the idea.

          Build steps our build

          One row per step, in order, so someone could rebuild from this page.

            Parts used our parts list

            Lengths in holes are also shown in inches between the end holes. Weights are only added up where you type them.

              Plan the cuts: packs every piece of one part (sizes in holes, or inches on the hole grid) onto whole sticks of the stock length you type.

              Ways it could fail our scores

              List the ways this could fail. Score how likely (1 to 5) and how bad (1 to 5); the page multiplies them and puts the biggest risks first.

                Designed against built our measurements

                What the CAD or the plan said, and what you measured on the robot. The tolerance is yours.

                  Changes from the last version our changes

                  What changed since the last version, why, and which result it was meant to move.

                    That page’s settings, results and first photo are copied in and set beside this page’s. The result each change should move is looked up on both pages.

                    Tasks our plan

                    What needs doing, who, and by when. Open tasks carry to the next meeting page until someone ticks them done.

                      The pages behind this idea our evidence

                      The pages in this notebook that show the idea being tried, measured or changed. A judge reading the claim can turn straight to them.

                        Time spent our hours

                        Who worked on this and for how long.

                          Session log what we did, as we did it

                          Notes taken during a session. The time comes from the clock when the note was taken; every word is yours.

                            Size limit does it fit?

                            Type the starting size limit from the current game manual, and the robot's size as designed or measured, in inches. The site doesn't store the limit, because it changes with the game.

                            What broke from your breakage log

                            The breakage log is on My notebook. Copy it onto this page as a table, as it stands now; later entries don't change this page.

                            CAD model which version this page is about

                            Paste a link to the model (Onshape, Fusion or anything else) and the name you use for this version. For Onshape, the page reads from the link whether it points at a saved version or a workspace that keeps changing. Nothing is fetched.

                            Your code
                            Comments notes for the team, not the page

                            A teammate or coach can leave a note here. Comments stay beside the page, travel with it in exports and links, and don't print unless you tick them under Include.

                              Sources you used besides this tool

                              Videos, other teams, manuals, people. The tool’s own sources are cited for you.

                                Sign-off
                                Include

                                Press a ? to see what an option is for, or read them all on How the notebook tools work.

                                What “The calculator’s figures” is for

                                The calculator’s own diagrams and charts, numbered as figures and drawn from your numbers. Judges look for pictures that explain a design.

                                What “How it was calculated” is for

                                The formulas and steps the calculator used, so a reader can check the arithmetic for themselves.

                                What “The calculator’s warnings” is for

                                Things the calculator flagged, such as a motor near stall. They’re quoted and credited to the calculator, so they never read as your conclusion.

                                What “The calculator’s notes” is for

                                The calculator’s plain-language notes on the result. Off at first, because they read like conclusions, and the conclusions on a page should be yours.

                                What “Lined space” is for

                                Ruled lines under any part you haven’t written yet, so a printed page can be finished by hand.

                                What “Writing space as” is for

                                The blank space for handwriting as ruled lines, a dot grid or quarter-inch squares. Dots and squares suit sketches and hand-drawn graphs.

                                What “A summary under recorded data” is for

                                The number of readings, the average, the spread, the lowest and the highest under each table you recorded, worked out from your numbers. It shows every run counted, not just the best one.

                                What “Words used” is for

                                A small box with the site’s one-line definitions of glossary terms the calculator used, for readers who don’t know them. It never looks at your own writing.

                                What “Robot at the time” is for

                                The Robot Profile as it was when the page was first saved, so weeks later you can tell which version of the robot a test was run on.

                                What “Long tables in full” is for

                                Long calculated tables printed complete on an extra page, instead of every few rows on the page itself.

                                What “Fit on one sheet” is for

                                Smaller type and shorter tables, aiming for one printed sheet. Use it when every entry in your notebook should be a single page.

                                What “Wider left margin” is for

                                A wider left edge, so the page can be hole-punched or bound without losing any words.

                                What “Larger type, for reading aloud” is for

                                Bigger print with more room between lines, for the team member who reads the page to a judge. It overrides Fit on one sheet.

                                What “Our rubric scores” is for

                                Your own scores against the rubric, on a sheet of their own, for checking a page before a judge does.

                                What “When this page was first saved” is for

                                The day the page was first saved, printed beside its date. It shows the notebook was kept while the work happened.

                                What “Teammates’ comments” is for

                                Prints the comments teammates left on this page at the end, marked as not part of the page. Off at first, because comments are notes for the team, not for judges.

                                What “Show every table and block” is for

                                Shows every table and block in the editor, not only the ones this type of page usually uses. It changes the editor, not the printed page.

                                Rubric check

                                  This checks what is on the page, not how good it is. Clear, specific writing in your own words is what earns the top marks.

                                  Preview, letter size

                                  Write it now

                                  Where this goes next

                                  Explore further on the full map

                                  Where the answers on this page can be used, and which tools could have given you the numbers it asks for.

                                  Comes after

                                  Feedforward Characterizationgives you your trial resultsPID Comparisongives you your trial resultsPID Simulatorgives you your PID gainsOdometry Ticks per InchGravity Feedforward

                                  You are here

                                  PID Error Analyzer

                                  Where your answer goes

                                  PID Comparisonrun old and new gains several times to prove the change really helpeduses your trial results againFeedforward Characterizationsee if feedforward removes the error that PID keeps chasinguses your trial results againAutonomous Time Estimatoradd the settling wait to each move and see if the routine still fitsOdometry Calibration Calculatorcheck the robot really ended up where the sensors say it settleduses your position error again

                                  a number carries across the next question it raises

                                  Keyboard shortcuts

                                  Anywhere

                                  Ctrl K or /
                                  Search
                                  T
                                  Switch color theme
                                  B
                                  Bigger text, for a projector
                                  F
                                  Readable font, on or off
                                  ?
                                  This list

                                  On a tool

                                  S
                                  Star or unstar it
                                  C
                                  Copy the results
                                  L
                                  Copy a link to these exact numbers
                                  P
                                  Print or save as PDF

                                  Letter keys do nothing while you're typing in a box.