Personal workbench

A compact PrometheOS system for personal projects.

A personal workbench runs the same local environment with a smaller set of compatible sensors, controls, and outputs for independent use.

Reference projects Curriculum sequence
A personal invention moving from a first question to a working idea
A saved project can be reopened on compatible PrometheOS hardware.

Project continuity

Projects can move between shared and personal systems.

Save a project from a shared lab, open it on a compatible personal setup, reconnect the required hardware, and continue the work.

  1. 01

    Shared system

    Create on shared equipment

    Use a lab hub, assigned station, shared equipment, and educator guidance to create and test the first version.

  2. 02

    Project file

    Export the project

    Preserve configuration, behavior, hardware requirements, and notes in a project that can be reopened later.

  3. 03

    Personal system

    Reconnect compatible hardware

    Open the project on a smaller PrometheOS workbench and map the required inputs and outputs to available components.

  4. 04

    Project record

    Document revisions

    Keep diagrams, configuration, test results, failures, and design changes with the project.

Compact personal PrometheOS workbench with a sensor, control, and light
A compact configuration for compatible low-voltage inputs and outputs.

Personal hardware configuration

A smaller set of compatible equipment.

A personal system can use a subset of the equipment from a shared lab. Projects remain portable when their required hardware is available or mapped to compatible components.

  • Open a project from the shared lab.
  • Reconnect a smaller set of safe sensors and controls.
  • Change one thing and watch the idea evolve.
  • Save the next version so it stays with you.

Personal projects still require appropriate supervision, safe wiring, correct power supplies, and responsible testing.

Personal software use included

Personal, non-commercial software use is included.

Your PrometheOS product includes personal, non-commercial software use. Commercial use requires a paid license.

Project documentation

Record the system, tests, revisions, and results.

Documentation makes a project reproducible and shows how its design changed in response to tests and observed system behavior.

  • Diagram How components and systems connect
  • Choices What you wanted the project to do
  • Test Expected behavior and observed results
  • Surprise What did not work the way you expected
  • Revision What changed and why
  • Reflection What the next version still needs

Increasing project depth

Move from a single behavior to a complete system.

Projects can begin with one input and output, then add sensing, interfaces, automation, multiple devices, and custom behavior.

  1. StartOne input, one rule, and one output
  2. ConnectAdditional sensors, controls, audio, light, or motion
  3. CombineMultiple devices and coordinated behaviors
  4. InspectSystem state, records, failures, and configuration
  5. DefineAn independent physical-system project

Related information

Project references, curriculum, and safety guidance.

Project gallery Review input–logic–output patterns and reference implementations. Curriculum path Review the sequence from electrical foundations to an independent capstone. Safety guidance Keep low-voltage work supervised, protected, and responsible.