Open the editorEditor
Parts

Finding a part

Three ways in: the search box in the editor's part panel, the bench at /parts, and each part's own page.

Open the editorAll the docs

Mokxi teamParts

In the editor

The part panel's search box is the fastest way. It matches the part's name, its type string, its one-line description, and a list of extra words filed against it: pot, knob, dial and volume all find the potentiometer.

It is forgiving in a few useful ways:

  • Plurals and typos. leds finds the LED, and a word one letter off still finds its part when nothing matches exactly.
  • Part numbers. irlz44 finds the MOSFET set to an IRLZ44N, and lm741 finds the
    1. Punctuation does not matter: ky035 and KY-035 are the same.
  • A value with the part. resistor 220, resistor 4k7 or 330 ohm resistor places a resistor already set to that value.
  • Other languages. A few common words in Hindi and Urdu (in Latin letters), Indonesian, Filipino, Vietnamese, Arabic, French, Portuguese, Spanish, Thai, German and Turkish map to the part: saklar finds a switch, lampu a lamp.
  • Things that are not parts. Search for wire and the panel tells you to drag from one pin to another instead. Search for a part Mokxi does not simulate and it suggests the nearest one it does.

Beside the search box is a category rail for browsing: Basics, Boards, Inputs, Sensors, Outputs, Displays, Logic, Timers and analog, Clocks and links, and Power and wiring. See the part families for what is in each, and placing parts for dragging one onto the canvas.

The bench

/parts is every part in the catalog, each drawn live by the editor's own code rather than photographed, with one line saying what it does. A count at the top says how many parts are on the bench, and every part is free on every plan.

The page is grouped by the same ten families as the part panel, each with a line about the family and how many parts are in it. On a phone each family shows eight parts at a time, with a Show more button that says how many are left.

The list is generated from the catalog itself. A part added to the engine appears here on the next build, with the same name it has in the editor.

A part's own page

Click a tile and you get /parts/<type>. It has:

  • the drawing, with its pin count, its number of settings and how many projects use it;
  • a short summary of the part, and its pin table;
  • for the parts people search for most, a how-to section with a working example, common errors and questions;
  • what the model gets right and what it leaves out;
  • See the <part> in a project: every built-in project whose circuit actually places that part. That row is computed from the projects, so it never points at a project that no longer uses the part;
  • the lessons, boards and Arduino libraries it turns up with.

The glossary

/glossary is the other way in: plain definitions, for when you know what you want the circuit to do but not what the thing is called.

If you cannot find it

  • Try another word. Search by what the part does (distance, temperature, motor driver) rather than its exact model number.
  • Check the family. Browse the rail; a breakout board is usually under the thing it senses or drives.
  • It may not be simulated. If the search offers a stand-in, that is the closest part Mokxi has, and the note under it says what differs.