Introduction

This course teaches 3D design and digital fabrication using a fully accessible, command-line-driven toolchain centered on OpenSCAD (text-based CAD), 3DMake (non-visual build automation), and accessible editors (VS Code, Notepad++, command-line editors) with screen reader support.

The curriculum is explicitly designed for blind and visually impaired learners who use screen readers (NVDA, JAWS, VoiceOver). It eliminates GUI navigation and visual feedback in favor of keyboard-driven, text-based workflows that screen readers can fully access. Accessibility is not an add-on. It is the foundation of every tool, workflow, and lesson in this curriculum.

Curriculum Structure

Part 1: PowerShell Foundation (6 lessons + 4 guides)

Where to Start: PowerShell Introduction

Before learning 3D design, students master terminal/command-line fundamentals:

• PS Introduction - What is a terminal and why learn it (pre-terminal intro for absolute beginners)
• PS.0 through PS.5 - 6 progressive lessons covering command-line basics through error handling
• Screen Reader Accessibility Guide - NVDA & JAWS reference for terminal navigation
• PowerShell Curriculum Overview - Complete guide with learning paths

Time commitment: ~6 hours
Skills gained: Terminal navigation, file operations, basic scripting, keyboard-only workflow mastery

Part 2: 3dMake Foundation (11 lessons + 4 appendices)

Where to Start: 3dMake Introduction

Main Curriculum: 11 Progressive Lessons

Total: 14-18 hours instruction + projects

4 Comprehensive Reference Appendices

• Appendix A: Comprehensive Slicing Guide - 7 major slicers (1,500+ lines)
• Appendix B: Material Properties & Selection - 6 materials (1,200+ lines)
• Appendix C: Tolerance Testing & QA Matrix - Measurement procedures (1,200+ lines)
• Appendix D: PowerShell Integration for SCAD Workflows - 5 automation scripts (1,100+ lines)

The Accessible Toolchain

Screen Reader Compatibility Throughout

This course uses tools designed for screen reader access:

• Terminal/Command line - Text-based, fully accessible to NVDA, JAWS, VoiceOver
• OpenSCAD - Free, open-source text-based CAD (no visual-only GUI dependency)
• 3DMake - Command-line build tool eliminating GUI navigation
• Accessible editors - VS Code, Notepad++, Nano, Vim (all keyboard-driven, screen reader friendly)

See Screen Reader Coding Tips (NVDA & JAWS) for detailed keyboard shortcuts and configuration.

3DMake: Non-Visual Build Automation

3DMake makes the entire design-to-print pipeline accessible:

3dm build        -> Compiles main.scad to main.stl
3dm info         -> Validates geometry and runs diagnostics
3dm slice        -> Prepares model for printing

• No GUI navigation needed
• Automation eliminates repetitive manual steps
• Configuration files store parameters as human-readable text
• Error reporting is text-based (screen reader accessible)
• Works with command-line slicers

Iterative, Non-Visual Design

Students learn to design through code and testing, not visual previews:

• Write parametric OpenSCAD code in accessible editors
• Run 3dm build to compile to printable file
• Use measurement-based verification (calipers, scales, functional testing)
• Iterate by editing parameters and rebuilding
• No reliance on 3D preview or visual feedback

Project-Based Learning

Every 3dMake lesson includes hands-on projects:

• Lesson 6: Keycap with embossed text (3dm commands)
• Lesson 7: Phone stand (parametric transforms)
• Lesson 8: Stackable bins (interlocking features, tolerances)
• Lesson 9: Keychain automation (PowerShell batch processing)
• Lesson 10: QA testing + accessibility audit (measurement, troubleshooting)
• Lesson 11: Beaded jewelry holder (stakeholder-driven design)

Each project requires:

• Parametric OpenSCAD code (clean, well-commented)
• Functional prototype (tested, iterated)
• Complete documentation (reflections, measurements, decisions)

Learning Support

Reference Materials

Quick navigation to common topics:

• OpenSCAD Cheat Sheet - Syntax quick-reference
• 3dMake Setup Guide - Installation walkthrough
• VSCode Setup Guide - Accessibility configuration
• Vocabulary Glossary - Course terminology
• Filament Comparison Table - Material reference
• Master Rubric - Project assessment criteria

Navigation

• SUMMARY.md - Complete table of contents
• Curriculum Guide - Detailed overview of all lessons and appendices
• Quick Reference - At-a-glance command and syntax reference

Supplemental Resources & Textbooks

This course is enhanced by comprehensive textbooks and companion materials from the Programming with OpenSCAD project:

Free Textbooks (EPUB Format)

• Programming with OpenSCAD: A Beginner’s Guide to Coding 3D-Printable Objects - Comprehensive reference covering OpenSCAD syntax, geometry concepts, and design patterns. Ideal for deep dives into specific topics and as a reference guide throughout the course.
• Simplifying 3D Printing with OpenSCAD - Focused on practical workflows, optimization, and real-world printing scenarios.

Companion Teaching Resources

• Practice Worksheets - Printable worksheets for visualization practice, decomposition exercises, vocabulary building, and assessment.
• Visual Quick Reference - Command syntax guides and geometry reference.
• Code Solutions Repository - Working OpenSCAD examples organized by topic (3D shapes, transformations, loops, modules, if-statements, advanced techniques).

Getting Started

For Students:

1. Start with PowerShell Introduction
2. Complete PowerShell lessons (PS.0-PS.5)
3. Begin 3dMake Introduction
4. Follow Lesson 1: Environmental Configuration
5. Continue through Lesson 11

For Instructors:

1. Review Curriculum Guide
2. Use 11 Teacher Templates for assessment
3. Reference Master Rubric for grading
4. Check Syllabus for course policies and learning progression

3D Design & Printing Curriculum - Non-Visual Toolchain Edition

Author: Michael Ryan Hunsaker, M.Ed., Ph.D.
Last Updated: 2026-02-20
Target Audience: Blind and visually impaired high school students; anyone learning 3D design and printing through screen reader-accessible workflows.

Overview

This curriculum teaches 3D design and digital fabrication using a fully accessible, command-line-driven toolchain centered on OpenSCAD (text-based CAD), 3DMake (non-visual build automation), and accessible editors (VS Code, Notepad++, command-line editors) with screen reader support. Students progress from foundational command-line skills through guided projects to real-world, stakeholder-driven design challenges.

Who This Course Is For

This course is explicitly designed for blind and visually impaired learners who use screen readers (NVDA, JAWS, VoiceOver). It eliminates GUI navigation and visual feedback in favor of keyboard-driven, text-based workflows that screen readers can fully access.

Accessibility is not an add-on. It is the foundation of every tool, workflow, and lesson in this curriculum.

Core Philosophy

1. Text-First Design: All core work happens in text editors and command-line interfaces-no graphical CAD previews, no mouse-dependent menu navigation.

2. Parametric Thinking: Students learn to express geometry as code using OpenSCAD, enabling precise, reproducible, and iterable designs without visual feedback.

3. Automation and Independence: 3DMake automates the journey from code to printed object, handling compilation, slicing orchestration, and metadata management through simple command-line commands and text configuration files.

4. Screen Reader Mastery: Students develop fluency with accessibility technologies (NVDA, JAWS, VoiceOver) and accessible editors, building skills that apply to careers in software, engineering, and digital fabrication.

5. Real-World Impact: Projects culminate in designing assistive-technology solutions for real stakeholders, combining technical skill with human-centered design and documentation.

Curriculum Structure & Scope/Sequence

Part 1: PowerShell Foundation (Prerequisite - 6-8 hours)

Start here: PowerShell Introduction

Students who have never opened a terminal begin with foundational command-line skills:

Outcomes:

• Comfort with terminal/command-line interface
• File system navigation and manipulation
• Basic scripting and automation
• Screen reader optimization for terminal work
• Foundation for 3DMake automation tasks

Note: Students should complete PowerShell Foundation before starting 3dMake Lesson 9 (Automation). Lessons 1-8 can begin without PowerShell, but Lesson 9+ requires command-line fluency.

Part 2: 3dMake Foundation (Main Curriculum - 14-18 hours)

Start here: 3dMake Introduction

11 progressive lessons building from foundational concepts to leadership-level design thinking, organized in 5 parts:

Part 1: Foundations (Lessons 1-3 | ~3 hours)

Part 2: Verification & Safety (Lessons 4-5 | ~2 hours)

Part 3: Applied Projects (Lessons 6-8 | ~4 hours)

Part 4: Advanced Topics (Lessons 9-10 | ~3 hours)

Part 5: Leadership (Lesson 11 | ~2 hours)

Total: 14-18 hours of instruction + projects

4 Comprehensive Reference Appendices

Located in /3dMake_Foundation/ alongside the lessons:

Appendix A: Comprehensive Slicing Guide (1,500+ lines)

Reference for 7 major slicers:

• PrusaSlicer, Bambu Studio, Cura, SuperSlicer, OrcaSlicer, IdeaMaker, Fusion 360
• Setup guides, parameter explanations, troubleshooting, command-line integration
• Use when: Slicing questions, switching slicers, quality issues

Appendix B: Material Properties & Selection (1,200+ lines)

Complete material reference for 6 materials:

• PLA, PETG, ABS, TPU, Polycarbonate, Nylon
• Properties tables, printing parameters, quality verification, cost analysis
• Use when: Choosing material, troubleshooting prints, cost analysis

Appendix C: Tolerance Testing & QA Matrix (1,200+ lines)

Measurement-based quality assurance procedures:

• Caliper techniques, weight verification, functional testing, tolerance stack-up
• Step-by-step procedures, checklist templates, CSV tracking
• Use when: Starting a project, verifying dimensions, quality issues

Appendix D: PowerShell Integration for SCAD Workflows (1,100+ lines)

Complete automation guide for PowerShell + 3dMake:

• 5 complete PowerShell scripts for workflow automation
• Parametric sweeps, batch processing, print logging, printer communication
• Use when: Automating tasks, testing variations, batch printing

Learning Progression: Student Roles

Students move through roles across the curriculum:

The Accessible Toolchain: How It Works

OpenSCAD - Text-Based 3D Design

OpenSCAD is a free, open-source CAD tool that uses a programming language to describe 3D geometry. Students write code that defines shapes, transforms them, and combines them using Boolean operations.

Why OpenSCAD?

• Screen reader friendly: All work happens in a text editor; no visual-only 3D preview.
• Repeatable: Code is version-controlled, documented, and shareable.
• Parametric: Variables allow students to design once and generate variations by changing numbers.
• No visual dependency: Students reason about geometry through code structure and testing.

3DMake - The Non-Visual Build Bridge

3DMake is a command-line tool that automates the journey from OpenSCAD code to a printable file:

3dm build        
3dm info         
3dm slice        

Why 3DMake?

• No GUI navigation: All interaction is keyboard-driven and text-based.
• Automation: Eliminates repetitive manual steps.
• Metadata tracking: Configuration files store parameters as human-readable text.
• Error reporting: Diagnostic output is text that screen readers can read aloud.

Accessible Editors

Students write OpenSCAD code using screen reader-accessible editors:

• VS Code (Windows, macOS, Linux): Industry-standard with built-in screen reader support
• Notepad++ (Windows): Lightweight, keyboard-driven, excellent screen reader support
• Command-line editors (Nano, Vim, Emacs): Full keyboard control, no mouse needed

Prerequisites by Section

Grading Rubric

All projects are scored on a 0-9 scale across three equally weighted categories (3 points each):

Category 1: Problem & Solution (0-3 points)

Category 2: Design & Code Quality (0-3 points)

OpenSCAD code is central to this course. We evaluate the clarity, structure, and documentation of your code as much as the print quality.

Category 3: Documentation (0-3 points)

Score Interpretation

Resubmission Policy

Students may resubmit any project as many times as they need to improve their score. Resubmissions must include a one-paragraph explanation of what was changed and why. The resubmission score replaces the original score.

Quick Links to Essential Tools & Setup

Core Design Toolchain

OpenSCAD:

• OpenSCAD Download - Free, cross-platform CAD (all major OS)
• OpenSCAD Documentation - Official reference
• OpenSCAD Cheat Sheet - Quick syntax reference
• OpenSCAD on GitHub - Source code and issue tracking

3DMake:

• 3DMake Documentation & Installation - Command-line build tool for OpenSCAD
• 3dMake Quick Reference - Command and workflow reference
• 3DMake Terminal Quick Start - CLI basics for new users

Editors:

• VS Code Download - Free, screen-reader-accessible code editor
• VS Code OpenSCAD Extension - Syntax highlighting for OpenSCAD
• Notepad++ Download - Free, lightweight Windows editor with OpenSCAD syntax support
• Vim/Neovim - Terminal-based editor with full keyboard control

Screen Reader & Accessibility

Screen Readers:

• NVDA Download - Free, open-source screen reader (Windows)
• JAWS Screen Reader - Commercial screen reader (Windows, macOS)
• VoiceOver (macOS/iOS) - Built-in Apple screen reader
• NVDA User Guide - Complete NVDA documentation

Accessibility Configuration:

• Screen Reader Coding Tips (NVDA & JAWS) - Keyboard shortcuts and configuration
• VSCode Setup Guide - Accessibility-focused editor configuration
• Accessibility in VS Code - Official VS Code accessibility guide
• JAWS Script Repository - Custom JAWS scripts for developers

Terminal & Command Line:

• PowerShell & Command Line Fundamentals - Terminal navigation for screen reader users
• Windows Terminal Accessibility - Official accessibility guide
• Screen Reader Tips for Linux - Linux-specific guidance

Slicing & Printing

Slicer Software & Documentation:

• PrusaSlicer Documentation - Official Prusa slicer
• PrusaSlicer Download - Free slicer optimized for Prusa printers
• Cura Slicer Documentation - Official UltiMaker Cura documentation
• Cura Slicer Download - Free, open-source slicer for most printers
• OrcaSlicer Documentation - Community wiki for OrcaSlicer
• OrcaSlicer Download - Free, open-source slicer fork with advanced features
• Bambu Studio Documentation - Official Bambu Lab slicer documentation
• Bambu Studio Download - Free slicer optimized for Bambu Lab printers
• SuperSlicer Documentation - Community wiki for SuperSlicer
• SuperSlicer Download - Free, open-source advanced slicer
• IdeaMaker Documentation - Anycubic/Raise3D slicer documentation
• IdeaMaker Download - Free slicer for Anycubic and other printers
• Slic3r Documentation - Original open-source command-line slicer
• Fusion 360 Slicer - Integrated slicer in Fusion 360 CAD
• Repetier-Host Documentation - Host software with integrated slicing
• Appendix A: Comprehensive Slicing Guide - Detailed comparison and setup guides for all major slicers

OpenSCAD Learning

Tutorials & Documentation:

• OpenSCAD Official Tutorials - Step-by-step guides from the OpenSCAD project
• OpenSCAD User Manual - Community-maintained comprehensive reference
• OpenSCAD by Example - Practical examples with code
• CadHub OpenSCAD Guide - Real-world applications and best practices

Advanced Resources:

• BOSL2 Library Documentation - Advanced shapes and transforms
• OpenSCAD Libraries - Complete library ecosystem
• Dotscad - Parametric design patterns library
• OpenSCAD Performance Optimization - Tips for faster rendering

Supplemental Textbooks

EPUB Textbooks:

• Programming with OpenSCAD: A Beginner’s Guide to Coding 3D-Printable Objects - Complete reference textbook (EPUB format)
• Simplifying 3D Printing with OpenSCAD - Practical workflows and applications (EPUB format)

Online Companion Resources:

• Programming with OpenSCAD Companion Resources - Practice worksheets and teaching materials
• Visual Quick Reference Guides - Command syntax and geometry reference
• Code Solutions Repository - Working examples for all exercises
• Teaching Tech 3D Printing Guide - Video tutorials and workflows

Assistive Technology Design & Research

Organizations & Communities:

• e-NABLE Community Foundation - 3D printed hand/arm devices
• Makers Making Change - Open-source assistive designs
• NIH 3D Print Exchange - Medical and assistive models
• Printables - Assistive Technology - Community models
• Thingiverse - Adaptive/Accessibility - Model repository
• YouMagine - Open-source design platform

Research & Resources:

• MIT D-Lab - Design for development and assistive technology
• Design for All Institute - Universal design principles
• Inclusive Design Toolkit - Design resources for disability

Community & Forums

OpenSCAD Community:

• OpenSCAD Discord - Real-time chat and support
• OpenSCAD Reddit - Discussion forum for OpenSCAD users
• OpenSCAD Google Group - Email-based discussion list
• CadHub Community - Collaborative 3D design community

3D Printing Community:

• Reddit r/3Dprinting - General 3D printing community
• Prusa Community - Prusa-specific forum
• Bambu Lab Forum - Bambu printer community
• 3DPrinting Stack Exchange - Q&A platform for 3D printing

Troubleshooting Resources

Common Issues:

• Common Issues and Solutions - Course-specific troubleshooting guide
• Diagnostic Checklist - Step-by-step diagnostics
• OpenSCAD FAQ - Frequently asked questions
• PrusaSlicer Troubleshooting - Prusa-specific solutions

Tools for Debugging:

• Netfabb Online - Free online mesh repair tool
• Meshmixer - Advanced mesh editing and repair
• MeshLab - Open-source mesh processing
• STL Viewer Online - Quick STL preview without installing software

Printer-Specific Guides

Prusa Printers:

• Prusa Knowledge Base - Official documentation and troubleshooting
• Prusa Assembly Guides - Setup and calibration

Bambu Lab Printers:

• Bambu Lab Wiki - Complete documentation
• Bambu Lab Support - Customer support resources

Anycubic Printers:

• Anycubic Support - Official support
• Anycubic Community - User forum

Creality Printers:

• Creality Documentation - Official guides
• Creality Support - Customer service

Local Resources: Utah Makerspaces & Community Printing

Public Library Make Spaces

Salt Lake City Public Library:

• SLC Public Creative Lab - Main Library (Level 1)
  • Hardware: Prusa i3 MK3, LulzBot Taz 5, Elegoo Mars 2 (resin)
  • Pricing: Free for prints under 6 hours; $0.50/hr + material cost otherwise
  • Website: https://services.slcpl.org/creativelab

Salt Lake County Library System:

• County Library “Create” Spaces - Locations: Daybreak, Granite, Kearns, Syracuse, Tooele, and more
  • Hardware: Flashforge Adventurer 5M Pro, LulzBot Workhorse, laser cutters
  • Pricing: $0.06 per gram of filament used
  • Website: https://www.slcolibrary.org/what-we-have/create

Makerspaces & Community Centers

Make Salt Lake:

• Location: 663 W 100 S, Salt Lake City, UT 84101
• Website: https://makesaltlake.org/
• Equipment: Full metal shop, CNC machines, large-scale FDM and resin printing
• Membership: Required; offers certification classes for advanced tools
• Community: Active maker community with regular workshops

University of Utah Maker Spaces:

• Lassonde Studios - Entrepreneurship and innovation hub
• Marriott Library ProtoSpace - 3D printing and fabrication
• Eccles Health Sciences Library Technology Hub - Biomedical device development

Utah Valley University:

• UVU Maker Hub - Open to community members
• Equipment: Large format 3D printers, laser cutters, CNC machines

School & Educational Programs

Salt Lake City Schools:

• STEM Lab programs in select elementary and secondary schools
• Advanced manufacturing pathways in Career and Technical Education (CTE)
• Contact: Salt Lake City School District STEM Coordinator

Weber School District:

• Advanced Manufacturing Programs
• 3D Design and Fabrication courses in multiple high schools

Online Printing Services (When Local Access Unavailable)

National & International Services:

• Shapeways - Professional print service with multiple materials
• Sculpteo - Online 3D printing platform
• Ponoko - Custom manufacturing platform
• 3D Hubs - Community-based distributed manufacturing
• Local Motors - Custom manufacturing and consulting

Material Suppliers (Utah & Regional)

Local Filament Suppliers:

• MatterHackers - Online with local Utah roots; wide material selection
• Hatchbox - Reliable filament available at local retailers
• Prusament - Premium Prusa filament

Regional Retailers:

• Local Best Buy, Micro Center, and Fry’s Electronics locations carry common filaments
• Amazon Prime for next-day delivery on most materials
• Local makerspaces often sell filament at cost

Recycling & Sustainability

3D Printing Waste:

• Fused Filament Fab - Filament recycling programs
• Salt Lake City Recycling Center: Accepts PLA and PETG at select locations
• Local makerspaces: Often have filament recycling programs

Professional Development & Certifications

Organizations Offering Training:

• Make Salt Lake Workshops - Regular classes and certifications
• University of Utah Continuing Education - Professional development courses
• Weber State University - Continuing education programs

Troubleshooting & Getting Help

If you’re stuck:

1. Check Common Issues and Solutions
2. Post in OpenSCAD Discord or Reddit
3. Visit your local makerspace for hands-on support
4. Check printer-specific forums (Prusa, Bambu Lab, Anycubic, etc.)

For accessibility support:

• Contact your NVDA/JAWS vendor directly for technical assistance
• Post accessibility-specific questions in OpenSCAD community
• This course’s GitHub Issues page for curriculum-specific questions

PowerShell for Screen Reader Users - Complete Curriculum Overview

Welcome! This curriculum teaches you how to use PowerShell (Windows Terminal) as a screen reader user, starting from zero experience and building to professional-level skills.

Last Updated: February 2026
Total Duration: 12-15 hours of instruction + practice
Target Users: Anyone with a screen reader (NVDA, JAWS, or other)

Why Learn PowerShell?

For Everyone

• Speed: Text commands are often faster than clicking through menus
• Automation: Repeat tasks automatically instead of doing them manually
• Precision: Exact control over what your computer does
• Scripting: Create programs that solve real problems

For 3D Printing (Our Focus)

• Batch Operations: Process 100s of 3D models at once
• Accessibility: Many 3D design tools are scriptable
• Reproducibility: Same settings, every time
• Integration: Connect OpenSCAD, slicers, and tools together

For Screen Reader Users Specifically

• Great Accessibility: PowerShell works perfectly with NVDA, JAWS, and others
• No Mouse Needed: Everything is keyboard-based
• Text-Based: Output is naturally readable by screen readers
• Stability: Unlike GUIs, terminal interactions are consistent

Curriculum Structure

Phase 1: Absolute Beginner -> Comfortable User

Goal: You can navigate to any folder and see what’s in it with your screen reader.

Phase 2: Intermediate User -> Power User

Goal: You can create folders, manage files, and combine commands to accomplish complex tasks.

Phase 3: Professional Skills (Beyond Curriculum)

These topics extend beyond this curriculum but are natural next steps:

How to Use This Curriculum

If You’ve Never Used a Terminal Before

Start here and go in order:

1. Read Screen Reader Accessibility Guide completely
2. Do PS-Pre: Your First Terminal exercises
3. Continue with PS-0, PS-1, etc.

Don’t skip steps - each builds on the previous one.

If You’ve Used a Terminal Before (But Not with a Screen Reader)

Start here:

1. Skim Screen Reader Accessibility Guide (you’ll recognize most tips)
2. Quickly review PS-Pre (basics with screen reader focus)
3. Move to PS-0 for deeper learning

If You’re Experienced with Terminal + Screen Reader

You can:

1. Jump to specific lessons you need (PS-2, PS-3, etc.)
2. Use the Quick Reference sections
3. Skip the practice exercises, do the quizzes to verify knowledge

How Each Lesson is Structured

Every Lesson Contains:

1. Learning Objectives - What you’ll be able to do
2. Key Commands - The important ones to memorize
3. Step-by-Step Examples - How to actually do it
4. Practice Exercises - Hands-on work
5. Quiz Questions - Check your understanding
6. Extension Problems - Go deeper if interested

How to Get Through Each Lesson:

1. Read the learning objectives
2. Do the step-by-step examples alongside
3. Complete the practice exercises (critical!)
4. Take the quiz (don’t cheat)
5. Try extension problems if you have time
6. Move to next lesson when quiz is solid

Estimated time: 30-60 minutes per lesson (depends on practice time)

Screen Reader Tips Throughout the Curriculum

Every Lesson Includes:

• [SR] symbols marking screen reader-specific sections
• Tips for NVDA and JAWS users separately
• Solutions for common accessibility issues
• Workarounds for long outputs

Screen Reader Accessibility Guide

This is your companion resource used throughout:

• Detailed NVDA keyboard shortcuts
• Detailed JAWS keyboard shortcuts
• Solutions to common problems
• Pro tips for efficiency

Keep it open or printed as you work through lessons.

Quick Start Guide (First 15 Minutes)

If You Have 15 Minutes Right Now:

1. Open PowerShell (Windows key -> type PowerShell -> Enter)
2. Run these commands:

   pwd
   ls -n
   cd Documents
   pwd
   

3. See how your screen reader reads each output
4. Try Tab completion:
   • Type cd D and press Tab
   • Hear PowerShell auto-complete to Documents (or similar)
5. Create a file:

   echo "I am learning PowerShell" > learning.txt
   cat learning.txt
   

That’s it! You’ve done the key concepts. Now read PS-Pre for the details.

Common Questions Before Starting

Q: Do I have to use PowerShell? What about Command Prompt (cmd.exe)?

A: Command Prompt works, but PowerShell is better. PowerShell is:

• More powerful
• Better for modern tools
• Screen-reader-friendly
• The future of Windows automation

Use PowerShell for this curriculum.

Q: What if I use a different screen reader (not NVDA or JAWS)?

A: The fundamentals work the same. Check your screen reader’s documentation for the equivalent of these commands:

• Read current line
• Read to end of screen
• Read next/previous page

Most screen readers have these features.

Q: I’m intimidated. Is this really for me?

A: YES. This curriculum is specifically designed for people with no terminal experience AND with screen readers. You’ll start with absolute basics. There’s nothing to be afraid of - we’ve written this specifically to make it accessible.

Q: How long will this take?

A: Realistically:

• Minimum (just lessons, no exercises): 5-6 hours
• Normal (lessons + exercises): 12-15 hours
• With extension problems: 18-20+ hours

Spread it over weeks or months. Go at your pace.

Q: What if I forget things?

A: That’s normal and expected. Solutions:

1. Come back to this page for the overview
2. Jump back to that lesson for a quick review
3. Use the quiz questions to self-test
4. Check the Screen Reader Accessibility Guide for troubleshooting

Q: Will this help me with 3D printing?

A: Absolutely. Near the end of the 3dMake curriculum, you’ll use PowerShell to:

• Batch-process 3D models
• Automate slicing tasks
• Run scripts that generate designs
• Integrate tools together

Suggested Study Schedule

Beginner Goal (Weeks 1-2)

Week 1:

• Day 1: Read Screen Reader Accessibility Guide
• Day 2: PS-Pre lesson
• Day 3: PS-0 lesson
• Day 4: Practice PS-0 and PS-1 exercises
• Day 5: PS-1 lesson

Week 2:

• Review PS-0 and PS-1 quizzes
• Practice navigation exercises daily
• Do extension problems for PS-0 and PS-1
• Feel confident with file system navigation

Goal: Know how to navigate to any folder, list its contents, and understand paths.

Intermediate Goal (Weeks 3-5)

Week 3:

• PS-2 lesson (file manipulation)
• Complete exercises
• Take quiz

Week 4:

• PS-3 lesson (piping and output)
• Complete exercises
• Take quiz

Week 5:

• PS-4 and PS-5 lessons
• Complete all quizzes
• Practice combining commands

Goal: Create, modify, and move files. Combine commands for complex tasks.

Advanced Goal (Weeks 6+)

• Review any lessons you need
• Do all extension problems
• Start learning PowerShell scripting
• Begin 3D printing integration

Success Criteria

By the End of PS-1, You Should:

• Know where you are at all times (pwd)
• See what’s around you (ls -n)
• Navigate confidently with your screen reader
• Use Tab completion comfortably
• Understand absolute and relative paths
• Pass the PS-0 and PS-1 quizzes

By the End of PS-3, You Should:

• Create and delete files and folders
• Copy and move files
• Redirect output to files
• Pipe commands together
• Save long outputs to readable files
• Pass all quizzes PS-0 through PS-3

By the End of PS-5, You Should:

• Use command history effectively
• Create aliases and functions
• Understand your PowerShell profile
• Handle screen reader edge cases
• Feel comfortable experimenting
• Pass all quizzes

Important Rules

Rule 1: Always Know Where You Are

Every session, first thing:

pwd

If you don’t know your path, you’ll get lost. Don’t move until you know where you are.

Rule 2: Check Before You Delete

Before deleting anything:

ls -n

Make sure you’re deleting the right thing. Once it’s gone, it’s gone.

Rule 3: Use -n with ls

Always:

ls -n

Never:

ls

The -n (names only) is screen reader friendly. The default view is hard to read.

Rule 4: When Lost, Redirect to a File

If output is confusing:

command-name > output.txt
notepad.exe output.txt

This is always clearer for screen readers than terminal output.

Rule 5: Save Everything You Create

Every exercise, save your work:

mkdir my-practice-folder
cd my-practice-folder

Create a “learning” folder and keep everything there.

Troubleshooting: “Nothing Works!”

If you’re stuck:

1. Can’t hear PowerShell at all?

   • Make sure screen reader is running BEFORE PowerShell
   • Try Alt+Tab to cycle to PowerShell window
   • Restart both screen reader and PowerShell

2. Commands not working?

   • Check spelling carefully
   • Make sure you pressed Enter
   • Try Get-Help command-name

3. Can’t read the output?

   • Redirect to file: command > output.txt
   • Open in Notepad: notepad.exe output.txt
   • This always works

4. Something ran forever?

   • Press Ctrl+C to stop it

5. Completely confused?

   • Go back to PS-Pre and start over
   • Work through every single exercise slowly
   • Ask for help (ask an instructor or peer)

Resources

Official Documentation

• PowerShell Docs: https://docs.microsoft.com/powershell/
• Windows Terminal Docs: https://docs.microsoft.com/windows/terminal/

Screen Reader Guides

• NVDA: https://www.nvaccess.org/documentation/
• JAWS: https://www.freedomscientific.com/support/

Learning Resources

• Microsoft Learn: https://learn.microsoft.com/en-us/training/modules/
• PowerShell ISE: Built-in editor (open with ise)

3D Printing Integration

• OpenSCAD Scripting: See 3dMake lessons in this curriculum
• Batch Processing: See PS-3 and PS-5 for real examples

Getting Help

If You’re Stuck:

1. Read the relevant section of Screen Reader Accessibility Guide
2. Try a different approach from the “Solutions” sections
3. Go back one lesson and strengthen those concepts
4. Ask an instructor or peer with specific questions

Before You Ask for Help, Prepare:

1. What command are you running?
2. What do you expect to happen?
3. What actually happened?
4. What error message did you hear?

Example: “I ran cd Desktop but my screen reader said ‘Cannot find path’. I expected to go to the Desktop folder.”

This helps others help you quickly.

Next Steps

1. Right now: Read the Screen Reader Accessibility Guide completely
2. Next session: Start PS-Pre and do all exercises
3. Keep going: One lesson per day/week at your pace
4. Practice: Do exercises, not just read
5. Check yourself: Take the quizzes honestly
6. Celebrate: Each lesson completed is a real skill gained

Final Thoughts

Learning to use PowerShell with a screen reader is absolutely achievable. Many people do it successfully. This curriculum was designed based on real experiences of screen reader users.

You’ve got this. Start with PS-Pre, take it slow, do the exercises, and ask questions when stuck.

Welcome to the PowerShell community!

Curriculum Map (For Reference)

START HERE v
+---- Screen Reader Accessibility Guide (reference throughout)
+---- PS-Pre: Your First Terminal (absolute beginner entry point)
+---- PS-0: Getting Started (paths & navigation foundations)
+---- PS-1: Navigation (comfortable moving around)
+---- PS-2: File & Folder Manipulation (create/move/delete)
+---- PS-3: Input, Output & Piping (chain commands)
+---- PS-4: Environment Variables & Aliases (automation)
+---- PS-5: Filling in the Gaps (profiles & history)
+---- PS_Unit_Test (comprehensive practice & assessment)
        v
    NEXT: 3D Printing Integration Lessons
        v
    ADVANCED: PowerShell Scripting

Questions? Feedback? Stuck? Refer back to this page and the Screen Reader Accessibility Guide. You’ve got everything you need.

Now open PS-Pre and let’s get started!

Screen Reader Accessibility Guide for PowerShell

Target Users: NVDA, JAWS, and other screen reader users
Last Updated: 2026

This guide is used throughout the PowerShell Foundation curriculum to help screen reader users navigate and work efficiently with the terminal.

Table of Contents

1. Getting Started with Screen Readers
2. NVDA-Specific Tips
3. JAWS-Specific Tips
4. General Terminal Accessibility
5. Working with Long Output
6. Keyboard Shortcuts Reference
7. Troubleshooting

Getting Started with Screen Readers

Which Screen Reader Should I Use?

Both NVDA and JAWS work well with PowerShell, but they have different strengths:

Recommendation: Start with NVDA if you’re new to screen readers. Both will work for this curriculum.

Before You Start

1. Make sure your screen reader is running before opening PowerShell
2. Open PowerShell and let your screen reader read the title and prompt
3. If you don’t hear anything, press Alt+Tab to cycle windows and find PowerShell
4. Use your screen reader’s screen review features to understand the layout

NVDA-Specific Tips

NVDA is free and available from https://www.nvaccess.org/

Key Commands for PowerShell

Example: Reading Long Output

Scenario: You ran ls -n and it listed 50 files. You can’t hear them all.

Solution with NVDA:

1. After the command finishes, press NVDA+Home to read the current line
2. Press NVDA+Down Arrow repeatedly to read all output
3. Or press NVDA+F7 to open Review Mode and use arrow keys to scroll

NVDA Settings for PowerShell

Enable verbosity for better feedback:

1. Press NVDA+Ctrl+V to open NVDA menu
2. Go to Preferences -> Settings
3. Under “Speech”, increase verbosity
4. Look for “Report font changes” and enable it (helps with code)

JAWS-Specific Tips

JAWS is a commercial screen reader available from https://www.freedomscientific.com/

Key Commands for PowerShell

Example: Reading Long Output

Scenario: You ran ls -n | Out-File list.txt and saved output to a file.

Solution with JAWS:

1. Open the file: notepad.exe list.txt
2. In Notepad, press Insert+Ctrl+Down to hear all content
3. Use Insert+Down Arrow to read line by line at your own pace

JAWS Settings for PowerShell

Enable specific settings for terminals:

1. Press Insert+F3 to open JAWS menu
2. Go to “Options” -> “Settings Manager”
3. Search for “terminal” or “console”
4. Enable “Announce output” and “Speak when program speaks”

General Terminal Accessibility

Understanding the PowerShell Layout

The PowerShell window contains:

1. Title bar: Window name (e.g., “Windows PowerShell”)
2. Content area: Command history and output
3. Prompt: The PS> area where you type

Your screen reader reads from top to bottom, but focus is at the prompt (bottom).

Navigation Sequence

When you open PowerShell:

1. Your screen reader announces the window title
2. Then it announces the prompt line
3. Anything before the prompt is previous output
4. Anything after the prompt is where new output will appear

Reading Output Effectively

Strategy 1: Immediate Output (Small Amount)

• Run a command
• Your screen reader announces output immediately
• This works well for short outputs (a few lines)

Strategy 2: Large Output (Many Lines)

• Redirect to a file: command > output.txt
• Open the file: notepad.exe output.txt
• Read in Notepad (easier for long text)

Strategy 3: Searching Output

• Use findstr (find string) to filter:

  ls -n | findstr "pattern"
  

• Only results matching “pattern” are shown

Working with Long Output

This is one of the most common challenges for screen reader users. Here are proven solutions:

Solution 1: Redirect to a File

Command:

ls -n > list.txt

Then open:

notepad.exe list.txt

Advantages:

• Easy to navigate at your own pace
• Works with all screen readers
• Output doesn’t scroll away
• You can save it for later

Solution 2: Use Pagination

Command:

ls -n | more

How to use:

• Press Space to see next page
• Press Q to quit
• Note: Some screen readers struggle with more, so Solution 1 is preferred

Solution 3: Filter Output

Example: Find only .scad files

ls -n | findstr "\.scad"

How it works:

• findstr searches for a pattern
• \.scad means “files ending in .scad”
• Only matching items are displayed

Solution 4: Count Before Displaying

Command:

(ls -n).Count

What it does:

• Tells you how many items there are
• Helps you know if you should redirect to file
• If count > 20, probably use file method

Keyboard Shortcuts Reference

All Users (Works in PowerShell regardless of screen reader)

Screen Reader Navigation

Troubleshooting

Problem 1: “I Can’t Hear the Output After Running a Command”

Causes & Solutions:

1. Cursor not at prompt

   • Solution: Press End or Ctrl+End to go to the end of text
   • Then use Up Arrow or screen reader commands to review

2. Output scrolled off-screen

   • Solution: Redirect to file: command > output.txt
   • Then read file: notepad.exe output.txt

3. Screen reader focus on window title, not content

   • Solution: Press Tab or arrow keys to move to the content area
   • Then use screen reader commands to read

4. Large amount of output overwhelming screen reader

   • Solution: Use filtering: ls -n | findstr "pattern"
   • Or save to file for paced reading

Problem 2: “Tab Completion Isn’t Working”

Causes & Solutions:

1. Need at least one character

   • Wrong: Type cd then Tab (won’t work without a path)
   • Right: Type cd D then Tab

2. Exact path needed

   • If folder is “Documents”, typing cd Doc and Tab works
   • But typing cd X won’t find “Documents”

3. Check if item exists

   • Use ls -n first to see available items
   • Then Tab-complete to them

Problem 3: “Screen Reader Says ‘Access Denied’ or ‘Permission Denied’”

Causes & Solutions:

1. Need admin rights

   • Close PowerShell
   • Right-click PowerShell -> Run as administrator
   • Confirm the UAC prompt

2. File is in use

   • Close any programs using the file
   • Try the command again

3. File path contains spaces

   • Use quotes: cd "Program Files"
   • Or use Tab completion (handles spaces automatically)

Problem 4: “Command Runs Forever and Won’t Stop”

Solution: Press Ctrl+C

Examples of long-running commands:

• ping google.com (will ping forever until stopped)
• Connecting to a slow server
• Large file operations

Always press Ctrl+C when a command seems stuck.

Problem 5: “I Need to Edit My Last Command”

Solutions:

1. Press Up Arrow to show previous command
2. Use arrow keys to move through it
3. Edit the command as needed
4. Press Enter to run the modified version

Example:

• You typed: cd Document (missing the ‘s’)
• Press Up Arrow to show it again
• Press End to go to the end
• Type s to make it cd Documents
• Press Enter to run it

Problem 6: “My Screen Reader Keeps Interrupting Each Other”

Causes & Solutions:

1. NVDA verbosity too high

   • Press NVDA+Ctrl+V to open menu
   • Go to Settings -> Speech
   • Lower the verbosity level

2. Multiple applications speaking

   • Use Alt+Tab to make PowerShell active window
   • Minimize other programs

3. JAWS reading too fast

   • Press Insert+Down Arrow in settings
   • Look for speech rate and slow it down

Pro Tips for Efficiency

1. Create Aliases for Frequently Used Commands

Example in PowerShell:

Set-Alias -Name la -Value "ls -n -ad"

Now you can type just la instead of ls -n -ad.

2. Use Command History Effectively

See all recent commands:

history

Run a previous command by number:

Invoke-History 5

(Runs the 5th command in history)

3. Redirect Everything to Files for Accessibility

If a command produces output, save it:

command-name > results.txt
notepad.exe results.txt

This is always more accessible than reading from terminal.

4. Create a README for Yourself

Create a simple help file:

echo "ls -n means list names only (screen reader friendly)" > my-notes.txt
echo "cd means change directory" >> my-notes.txt
notepad.exe my-notes.txt

Come back to it whenever you forget something.

Recommended Workflow

For every new task:

1. Know where you are: pwd
2. See what’s around: ls -n
3. Plan your next step: Think before typing
4. Run the command: Type and press Enter
5. Check the output: Use screen reader or redirect to file
6. Move forward: Next command or cd to next folder

This workflow keeps you oriented and prevents errors.

Quick Reference Card

Print or save this:

EVERY COMMAND STARTS WITH:
1. pwd (where am I?)
2. ls -n (what's here?)
3. cd path (go there)

LONG OUTPUT?
-> command > file.txt
-> notepad.exe file.txt

STUCK?
-> Ctrl+C

WANT TO REPEAT?
-> Up Arrow
-> History

NEED HELP?
-> Get-Help command-name

Additional Resources

• NVDA Documentation: https://www.nvaccess.org/documentation/
• JAWS Documentation: https://www.freedomscientific.com/support/
• PowerShell Docs: https://docs.microsoft.com/powershell/
• Accessibility Best Practices: https://www.w3.org/WAI/

Feedback

This guide is meant to help YOU. If something isn’t clear:

• Try a different approach from the “Solutions” sections
• Reach out to instructors with specific questions
• Share what worked for you with classmates

Remember: Using a terminal with a screen reader is absolutely possible. These tools and techniques will help you master it.

PS-Pre: Your First Terminal - Screen Reader Navigation Fundamentals

Duration: 30-45 minutes
Prerequisites: None - this is the starting point
Accessibility Note: This lesson is designed specifically for screen reader users (NVDA, JAWS)

What is a Terminal?

A terminal (also called a command line or shell) is a text-based interface where you type commands instead of clicking buttons. Think of it like sending written instructions to your computer instead of pointing and clicking.

Why learn this?

• Faster and more precise work (especially for 3D printing scripts and automation)
• Essential for programming and using tools like OpenSCAD
• Accessibility: Many command line tools work perfectly with screen readers
• Scripting: Automate repetitive tasks

Part 1: Opening PowerShell for the First Time

On Windows

Method 1: Search (Easiest)

1. Press the Windows key alone
2. You should hear “Search”
3. Type: PowerShell
4. You’ll hear search results appear
5. Press Enter to open the first result (Windows PowerShell)
6. PowerShell will open in a new window

Method 2: Using the Start Menu

1. Press Windows key + X (opens the Quick Link menu)
2. Look for “Windows PowerShell” or “Terminal”
3. Press Enter

Method 3: From File Explorer

1. Open File Explorer
2. Navigate to any folder
3. In the menu bar, select “File” -> “Open Windows PowerShell here”
4. PowerShell opens in that folder location

First Connection: Understanding the Prompt

When PowerShell opens, your screen reader will announce the window title and then the prompt. The prompt is where you type commands.

What you’ll hear:

PS C:\Users\YourName>

What this means:

• PS = “PowerShell” indicator
• C:\Users\YourName = Your current location (the “path”)
• > = The prompt is ready for your input

Important: Your cursor is blinking right after the >. This is where you type.

Part 2: Your First Commands (Screen Reader Edition)

Command 1: “Where Am I?” - pwd

What it does: Tells you your current location

Type this:

pwd

Press Enter

What you’ll hear: Your screen reader will announce the current path, something like:

C:\Users\YourName

Understanding paths:

• Paths show your location in the file system (like a mailing address)
• Windows paths use backslashes: C:\Users\YourName\Documents
• Think of it like folders inside folders: C:\ (main drive) -> Users -> YourName -> Documents

Command 2: “What’s Here?” - ls -n

What it does: Lists all files and folders in your current location. The -n flag makes it screen-reader friendly (names only, one per line)

Type this:

ls -n

Press Enter

What you’ll hear: Your screen reader will announce each file and folder name, one per line:

Desktop
Documents
Downloads
Music
Pictures
...

Why -n?

• Without -n, PowerShell shows files in columns (hard to read with a screen reader)
• With -n, each file/folder is on its own line (perfect for screen readers)

Command 3: “Go There” - cd Documents

What it does: Changes your location (navigates to a folder)

Type this:

cd Documents

Press Enter

What you’ll hear: The prompt changes to show your new location. You might hear something like:

PS C:\Users\YourName\Documents>

Practice navigation:

1. Run pwd to confirm you’re in Documents
2. Run ls -n to see what files are in Documents
3. Try going back: cd .. (the .. means “go up one level”)
4. Run pwd again to confirm
5. Go back to Documents: cd Documents

Part 3: Reading Screen Reader Output (Critical Skills)

Dealing with Long Lists

When you run ls -n in a folder with many files, the list might be very long. Your screen reader might announce 50+ items rapidly.

Solution 1: Save to a File

ls -n > list.txt
notepad.exe list.txt

This saves the list to a file and opens it in Notepad where you can read it more slowly.

Solution 2: Search Within the Output

ls -n | findstr "search-term"

Example: If you’re looking for files containing “scad”, type:

ls -n | findstr "scad"

Navigating Tab Completion

One of the most powerful screen reader tricks is Tab completion:

How it works:

1. Type the first few letters of a folder or file name
2. Press Tab
3. PowerShell automatically completes the rest

Example:

1. You’re in C:\Users\YourName>
2. Type: cd Doc
3. Press Tab
4. PowerShell auto-completes it to: cd Documents
5. Press Enter to go there

With a screen reader:

1. As you type Doc, your screen reader announces each letter
2. When you press Tab, PowerShell types the rest and your screen reader announces the full command
3. This is much faster than typing the whole thing

Part 4: Creating and Editing Files

Create a Simple File

Type this:

echo "Hello, PowerShell!" > hello.txt

What this does:

• echo sends text to the screen (or file)
• "Hello, PowerShell!" is the text
• > redirects it to a file called hello.txt

Read the File Back

Type this:

cat hello.txt

What you’ll hear: Your screen reader announces:

Hello, PowerShell!

Open and Edit the File

Type this:

notepad.exe hello.txt

This opens the file in Notepad where you can edit it with your screen reader.

Part 5: Essential Keyboard Shortcuts

These work in PowerShell and are crucial for screen reader users:

Screen reader tip: These all work perfectly with your screen reader. Try them!

Part 6: Screen Reader-Specific Tips

NVDA Users

1. Reading Command Output:

   • Use NVDA+Home to read the current line
   • Use NVDA+Down Arrow to read to the end of the screen
   • Use NVDA+Page Down to read the next page

2. Reviewing Text:

   • Use NVDA+Shift+Page Up to review text above

JAWS Users

1. Reading Output:

   • Use Insert+Down Arrow to read line-by-line
   • Use Insert+Page Down to read by page
   • Use Insert+End to jump to the end of text

2. Reading All Text:

   • Use Insert+Down Arrow repeatedly
   • Or use Insert+Ctrl+Down to read to the end

Common Issue: “I Can’t Hear the Output”

Problem: You run a command but don’t hear the output

Solutions:

1. Make sure your cursor is at the prompt (try pressing End or Ctrl+End)
2. Use Up Arrow to go back to your previous command and review it
3. Try redirecting to a file: command > output.txt then open the file
4. In NVDA: Try pressing NVDA+F7 to open the Review Mode viewer

Part 7: Practice Exercises

Complete these in order. Take your time with each one:

Exercise 1: Basic Navigation

1. Open PowerShell
2. Run pwd and note your location
3. Run ls -n and listen to what’s there
4. Try cd Documents or another folder
5. Run pwd to confirm your new location
6. Run ls -n in this new location

Goal: You should be comfortable knowing where you are and what’s around you

Exercise 2: Using Tab Completion

1. In your home directory, type cd D (just the letter D)
2. Press Tab
3. PowerShell should auto-complete to a folder starting with D
4. Repeat with other folder names
5. Try typing a longer name: cd Down and Tab to Downloads

Goal: Tab completion should feel natural

Exercise 3: Creating and Viewing Files

1. Create a file: echo "Test content" > test.txt
2. View it: cat test.txt
3. Create another: echo "Line 2" > another.txt
4. List both: ls -n

Goal: You understand create, view, and list operations

Exercise 4: Going Up Levels

1. Navigate into several folders: cd Documents, then cd folder1, etc.
2. From deep inside, use cd .. multiple times to go back up
3. After each cd .., run pwd to confirm your location

Goal: You understand relative navigation with ..

Exercise 5: Redirecting Output

1. Create a list: ls -n > directory_list.txt
2. Open it: notepad.exe directory_list.txt
3. Read it with your screen reader
4. Close Notepad
5. Verify the file exists: ls -n | findstr "directory"

Goal: You can save long outputs to files for easier reading

Checkpoint Questions

After completing this lesson, you should be able to answer:

1. What does pwd do?
2. What does ls -n do?
3. Why do we use -n with ls?
4. What path are you in right now?
5. How do you navigate to a new folder?
6. How do you go up one level?
7. What’s the Tab key for?
8. What does echo "text" > file.txt do?
9. How do you read a file back?
10. How do you stop a command that’s running?

You should be able to answer all 10 with confidence before moving to PS-0.

Common Questions

Q: Do I need to use PowerShell? Can I use Command Prompt (cmd.exe)? A: PowerShell is more powerful and works better with modern tools. We recommend PowerShell, but Command Prompt basics are similar.

Q: Why is my screen reader not reading the output? A: This is common. Use command > file.txt to save output to a file, then open it with Notepad for reliable reading.

Q: What if I type something wrong? A: Just press Enter and you’ll see an error message. Type the correct command on the next line. No harm done!

Q: How do I get help with a command? A: Type Get-Help command-name (we’ll cover this in PS-0)

Q: Can I make PowerShell more accessible? A: Yes! We’ll cover customization in PS-5.

Next Steps

Once you’re comfortable with these basics:

• Move to PS-0: Getting Started for deeper path understanding
• Then continue through PS-1 through PS-5 for full terminal mastery

Resources

• Microsoft PowerShell Docs: https://docs.microsoft.com/powershell/
• NVDA Screen Reader: https://www.nvaccess.org/
• JAWS Screen Reader: https://www.freedomscientific.com/products/software/jaws/
• Windows Terminal Accessibility: https://docs.microsoft.com/windows/terminal/

Troubleshooting

Still stuck? The checkpoint questions and exercises are your best teacher. Work through them multiple times until comfortable.

PS-0: Getting Started - Layout, Paths, and the Shell

Estimated time: 20-30 minutes

Learning Objectives

• Launch PowerShell and locate the prompt
• Understand path notation and shortcuts (~, ./, ../)
• Use tab completion to navigate quickly

Materials

• Computer with PowerShell
• Editor (Notepad/VS Code)

Step-by-step Tasks

1. Open PowerShell and note the prompt (it includes the current path).
2. Run pwd and say or note the printed path.
3. Use ls -n to list names in your home directory.
4. Practice cd Documents, cd ../ and cd ~ until comfortable.
5. Try tab-completion: type cd ~/D and press Tab.

Checkpoints

• Confirm you can state your current path and move to Documents.

Quiz - Lesson PS.0

1. What is a path?
2. What does ~ mean?
3. How do you autocomplete a path?
4. How do you go up one directory?
5. What command lists only names (ls flag)?
6. True or False: On Windows, PowerShell uses backslashes () in paths, but forward slashes (/) are also accepted.
7. Explain the difference between an absolute path and a relative path.
8. If you are in C:\Users\YourName\Documents and you type cd ../, where do you end up?
9. What happens when you press Tab while typing a folder name in PowerShell?
10. Describe a practical reason why understanding paths is important for a 3D printing workflow.
11. What does ./ mean in a path, and when would you use it?
12. If a folder path contains spaces (e.g., Program Files), how do you navigate to it with cd?
13. Explain what the prompt PS C:\Users\YourName> tells you about your current state.
14. How would you navigate to your home directory from any location using a single command?
15. What is the advantage of using relative paths (like ../) versus absolute paths in automation scripts?

Extension Problems

1. Create a nested folder and practice cd into it by typing partial names and using Tab.
2. Use ls -n -af to list only files in a folder.
3. Save pwd output to a file and open it in Notepad.
4. Try cd into a folder whose name contains spaces; observe how quotes are handled.
5. Create a short note file and open it from PowerShell.
6. Build a folder structure that mirrors your project organization; navigate to each level and document the path.
7. Create a script that prints your current path and the total number of files in it; run it from different locations.
8. Investigate the special paths (e.g., $HOME, $PSScriptRoot); write down what each contains and when you’d use them.
9. Compare absolute vs. relative paths by navigating to the same folder using each method; explain which is easier for automation.
10. Create a PowerShell function that changes to a frequently-used folder and lists its contents in one command; test it from different starting locations.
11. Navigate to three different locations and at each one note the prompt, the path from pwd, and verify you understand what each shows.
12. Create a complex folder tree (at least 5 levels deep) and navigate it using only relative paths; verify your location at each step.
13. Document all shortcuts you know (~, ./, ../, $HOME) and demonstrate each one works as expected.
14. Write a guide for a peer on how to understand the PowerShell prompt and path notation without using GUI file explorer.
15. Create a troubleshooting flowchart: if someone says “I don’t know where I am,” what commands do you give them to find out?

References

• Microsoft. (2024). PowerShell scripting overview and documentation. https://learn.microsoft.com/powershell/scripting/overview
• Microsoft. (2024). Filesystem navigation in PowerShell. https://learn.microsoft.com/powershell/scripting/learn/shell/navigate-the-filesystem
• Microsoft. (2024). Accessibility features in PowerShell ISE. https://learn.microsoft.com/powershell/scripting/windows-powershell/ise/accessibility-in-windows-powershell-ise

Helpful Resources

• PowerShell Basics - Microsoft Learn
• Filesystem Navigation Guide
• Understanding Path Notation
• Tab Completion Reference
• Accessibility in PowerShell ISE

PS-1: Navigation - Moving Around Your File System

Duration: 1 class period
Prerequisite: PS-0 (Getting Started)

Learning Objectives By the end of this lesson, you will be able to:

• Use pwd to print your current location
• Use cd to move between directories
• Use ls (and its flags) to list files and folders
• Use wildcards * and ? to filter listings
• Navigate relative vs. absolute paths
• Search for files by name and extension

Materials

• PowerShell
• Text editor (Notepad or VS Code)

Commands Covered in This Lesson

pwd - Where Am I?

Type pwd and press Enter. PowerShell prints the full path to your current location.

pwd
# Output: C:\Users\YourName

When to use: Always run this if you’re unsure of your current location.

cd - Changing Directories

cd stands for “change directory.”

# Go to Documents
cd Documents

# Go up one level to parent directory
cd ..

# Go to home directory
cd ~

# Go to a specific path
cd C:\Users\YourName\Documents\3D_Projects

ls - Listing Files and Folders

Use ls -n for screen reader compatibility.

# List all files and folders (names only)
ls -n

# List only files (no folders)
ls -n -af

# List only folders (no files)
ls -n -ad

Wildcards - Finding Files by Pattern

Wildcards help you find files without typing the full name.

* (asterisk) matches any number of characters:

# List all .scad files
ls -n *.scad

# List all files starting with "part"
ls -n part*

# List all files ending with "_final"
ls -n *_final*

? (question mark) matches exactly one character:

# Find files like model1.scad, model2.scad (but not model12.scad)
ls -n model?.scad

Step-by-step Practice

1. Run pwd and confirm your location
2. Move to Documents: cd Documents
3. Confirm you moved: pwd
4. List files and folders: ls -n
5. List only files: ls -n -af
6. Go back up: cd ..
7. Search for files: ls -n *.txt

Checkpoints

After this lesson, you should be able to:

• Navigate to any folder using cd
• Confirm your location with pwd
• List files and folders with ls -n
• Use wildcards to find files by pattern
• Move between absolute and relative paths confidently

Quiz - Lesson PS.1

1. What does pwd show?
2. How do you list directories only with ls?
3. What wildcard matches any number of characters?
4. How do you list files with the .scad extension?
5. Give an example of an absolute path and a relative path.
6. True or False: The * wildcard matches exactly one character.
7. Explain the difference between ls -n and ls -n -ad.
8. Write a command that would list all .txt files in your Documents folder using a wildcard.
9. How would you search for files containing “part” in their name across multiple files?
10. Describe a practical scenario where using wildcards saves time in a 3D printing workflow.
11. What happens when you use ls -n part?.scad versus ls -n part*.scad?
12. How would you navigate to a folder whose name contains both spaces and special characters?
13. If you’re in /Documents/Projects/3D and you want to go to /Documents/Resources, what command would you use?
14. Write a command sequence that navigates to the Downloads folder, lists only files, then returns to home.
15. Explain the purpose of using ls -n -af specifically in a screen reader context.

Extension Problems

1. Write a one-line script that lists .scad files and saves to scad_list.txt.
2. Use ls -n ~/Documents | more to page through long listings.
3. Combine ls with Select-String to search for a filename pattern.
4. Create a shortcut alias in the session for a long path and test it.
5. Practice tab-completion in a directory with many similarly named files.
6. Build a PowerShell script that recursively lists all .scad and .stl files in a directory tree; save the results to a file.
7. Compare the output of ls, Get-ChildItem, and gci to understand PowerShell aliasing; document what each command does.
8. Create a filtering command that displays only files modified in the last 7 days; test it on your documents folder.
9. Write a non-visual guide to PowerShell navigation; include descriptions of common patterns and how to verify directory contents audibly.
10. Develop a navigation workflow for a typical 3D printing project: move between CAD, slicing, and print-log folders efficiently; document the commands.
11. Create a complex wildcard search: find all files in a folder and subfolders that match multiple patterns (e.g., *_v1.* OR *_final.*).
12. Build a script that navigates through a folder tree, counts files at each level, and reports the structure.
13. Document the output differences between ls -n, ls -n -af, ls -n -ad, and Get-ChildItem; explain when to use each.
14. Create a navigation “cheat sheet” as a PowerShell script that prints common paths and how to navigate to them.
15. Design a project folder structure on your computer, document each path, then create a script that validates all folders exist.

References

• Microsoft. (2024). Get-ChildItem cmdlet reference. https://learn.microsoft.com/powershell/module/microsoft.powershell.management/get-childitem
• Microsoft. (2024). PowerShell wildcards and filtering. https://learn.microsoft.com/powershell/scripting/learn/shell/using-wildcards
• Microsoft. (2024). Navigation best practices in PowerShell. https://learn.microsoft.com/powershell/scripting/learn/shell/navigate-the-filesystem

Helpful Resources

• Get-ChildItem Cmdlet Reference
• PowerShell Wildcards and Filtering
• Navigation Best Practices
• Relative and Absolute Paths
• Screen Reader Tips for PowerShell

PS-2: File and Folder Manipulation

Estimated time: 30-45 minutes

Learning Objectives

• Create, copy, move, and delete files and folders from PowerShell
• Use ni, mkdir, cp, mv, rm, and rmdir safely
• Understand when operations are permanent and how to confirm results

Materials

• PowerShell
• Small practice folder for exercises

Step-by-step Tasks

1. Create a practice directory: mkdir ~/Documents/PS_Practice and cd into it.
2. Create two files: ni file1.txt and ni file2.txt.
3. Copy file1.txt to file1_backup.txt with cp and confirm with ls -n.
4. Rename file2.txt to notes.txt using mv and confirm.
5. Delete file1.txt with rm and verify the backup remains.

Checkpoints

• After step 3 you should see both the original and the backup file.

Quiz - Lesson PS.2

1. How do you create an empty file from PowerShell?
2. What command copies a file?
3. How do you rename a file?
4. What does rm -r do?
5. Why is rm potentially dangerous?
6. True or False: cp requires the -r flag to copy both files and folders.
7. Explain the difference between rm and rmdir.
8. If you delete a file with rm, can you recover it from PowerShell?
9. Write a command that would copy an entire folder and all its contents to a new location.
10. Describe a practical safety check you would perform before running rm -r on a folder.
11. What happens if you cp a file to a destination where a file with the same name already exists? How would you handle this safely?
12. Compare mv old_name.txt new_name.txt vs mv old_name.txt ~/Documents/new_name.txt. What is the key difference?
13. Design a workflow to safely delete 50 files matching the pattern *.bak from a folder containing 500 files. What commands and verifications would you use?
14. Explain how you could back up all .scad files from a project folder into a timestamped backup folder in one command.
15. When organizing a 3D printing project, you need to move completed designs to an archive folder and delete failed prototypes. How would you structure this as a safe, auditable process?

Extension Problems

1. Create a folder tree and copy it to a new location with cp -r.
2. Write a one-line command that creates three files named a b c and lists them.
3. Move a file into a new folder and confirm the move.
4. Use wildcards to delete files matching a pattern in a safe test folder.
5. Export a listing of the practice folder to practice_listing.txt.
6. Create a backup script that copies all .scad files from your project folder to a backup folder with timestamp naming.
7. Build a safe deletion workflow: list files matching a pattern, verify count, then delete with confirmation; document the steps.
8. Write a PowerShell script that organizes files by extension into subfolders; test it on a sample folder tree.
9. Create a file operation audit trail: log all copy, move, and delete operations to a text file for review.
10. Develop a project template generator: a script that creates a standard folder structure for a new 3D printing project with essential subfolders.
11. Implement a file conflict handler: write a script that handles cases where cp would overwrite an existing file by renaming the existing file with a timestamp before copying.
12. Create a batch rename operation: use a script to rename all files in a folder from old_prefix_* to new_prefix_*; test with actual files and verify the results.
13. Build a folder comparison tool: list all files in two folders and identify which files exist in one but not the other; output to a report.
14. Write a destructive operation validator: before executing rm -r, create a script that lists exactly what will be deleted, shows file counts by type, and requires explicit user confirmation to proceed.
15. Design a complete project lifecycle workflow: create folders for active projects, completed designs, and archive; include move operations between folders, backup steps, and verification that all files arrive intact.

References

• Microsoft. (2024). New-Item cmdlet reference. https://learn.microsoft.com/powershell/module/microsoft.powershell.management/new-item
• Microsoft. (2024). Copy-Item and Move-Item cmdlets. https://learn.microsoft.com/powershell/module/microsoft.powershell.management/copy-item
• Microsoft. (2024). File system operations guide. https://learn.microsoft.com/powershell/scripting/learn/shell/manipulating-items

Helpful Resources

• New-Item Cmdlet Reference
• Copy-Item and Move-Item
• Remove-Item Cmdlet Reference
• File System Operations Guide
• Safe Deletion Practices

PS-3: Input, Output, and Piping

Duration: 1 class period Prerequisite: PS-2 (File and Folder Manipulation)

Learning Objectives

By the end of this lesson, you will be able to:

• Use echo to print text to the screen
• Use cat to read file contents
• Use > to redirect output into a file
• Use | (pipe) to send one command’s output to another
• Copy output to the clipboard with clip
• Open files with a text editor from the command line

Commands Covered

echo - Printing Text

echo prints text to the screen. It is useful for testing, for writing text into files, and for understanding how piping works.

echo "Hello, World"
echo "This is a test"

cat - Reading Files

cat prints the contents of a file to the screen.

# Read a text file
cat ~/Documents/notes.txt

# Read an OpenSCAD file
cat ~/Documents/OpenSCAD_Projects/project0.scad

With a long file, use cat filename | more to read it page by page (press Space to advance, Q to quit).

> - Redirecting Output to a File

The > symbol redirects output from the screen into a file instead.

# Create a file with a single line
echo "Author: Your Name" > header.txt

# Confirm the file was created and has content
cat header.txt

Warning: > overwrites the file if it already exists. Use >> to append instead:

echo "Date: 2025" >> header.txt
echo "Project: Floor Marker" >> header.txt
cat header.txt

| - Piping

The pipe symbol | sends the output of one command to the input of the next. This lets you chain commands together.

# List files and send the list to clip (copies to clipboard)
ls -n | clip

# Now paste with Ctrl + V anywhere

# Search within a file's contents using Select-String (like grep)
cat project0.scad | Select-String "cube"

clip - Copying to Clipboard

clip takes whatever is piped to it and puts it on the Windows clipboard.

# Copy your current directory path to the clipboard
pwd | clip

# Copy a file listing to clipboard
ls -n | clip

# Copy the contents of a file to clipboard
cat notes.txt | clip

After any of these, press Ctrl + V in any application to paste.

Opening Files in Notepad

# Open a file in Notepad
notepad.exe ~/Documents/notes.txt

# Open a .scad file
notepad.exe ~/Documents/OpenSCAD_Projects/project0.scad

# Create a new file and open it
ni new_notes.txt
# PS-3: Input, Output, and Piping 

Estimated time: 25-40 minutes

**Learning Objectives**
- Use `echo`, `cat`, `>` and `>>` for basic IO
- Use `|` to pipe outputs between commands
- Copy command output to the clipboard with `clip`

**Materials**
- PowerShell
- Example text files for practice

Step-by-step Tasks
1. Create `practice.txt` with three lines using `echo` and `>`/`>>`.
2. Read the file with `cat practice.txt`.
3. Pipe the file into `Select-String` to search for a word.
4. Copy the file contents to clipboard with `cat practice.txt | clip`.
5. Redirect `ls -n` into `list.txt` and open it in Notepad.

Checkpoints
- After step 3 you should be able to find a keyword using piping.

## Quiz - Lesson PS.3

1. What is the difference between `>` and `>>`?
2. What does the pipe `|` do?
3. How do you copy output to the clipboard?
4. How would you page through long output?
5. How do you suppress output to nowhere?
6. True or False: The pipe operator `|` connects the output of one command to the input of another.
7. Explain why redirecting output to a file is useful for screen reader users.
8. Write a command that would search for the word "sphere" in all `.scad` files in a directory.
9. How would you count the number of lines in a file using PowerShell piping?
10. Describe a practical scenario in 3D printing where you would pipe or redirect command output.
11. What would be the difference in output between `echo "test" > file.txt` (run twice) vs `echo "test" >> file.txt` (run twice)? Show the expected file contents.
12. Design a three-step piping chain: read a file, filter for specific content, and save the results; explain what each pipe does.
13. You have a 500-line `.scad` file and need to find all instances of `sphere()` and count them. Write the command.
14. Explain how `clip` is particularly valuable for screen reader users when working with file paths or long output strings.
15. Describe how you would use pipes and redirection to create a timestamped backup report of all `.stl` files in a 3D printing project folder.

## Extension Problems
1. Use piping to count lines in a file (hint: `Select-String -Pattern '.' | Measure-Object`).
2. Save a long `ls -n` output and search it with `Select-String`.
3. Chain multiple pipes to filter and then save results.
4. Practice copying different command outputs to clipboard and pasting.
5. Create a small script that generates a report (counts of files by extension).
6. Build a data processing pipeline: read a CSV file, filter rows, and export results; document each step.
7. Write a script that pipes directory listing to Count occurrences of each file extension; create a summary report.
8. Create a log analysis command: read a log file, filter for errors, and save matching lines to a separate error log.
9. Design a piping workflow for 3D printing file management: find `.stl` files, extract their sizes, and generate a report.
10. Develop a reusable piping function library: create functions for common filtering, sorting, and reporting patterns; test each function with different inputs.
11. Build a complex filter pipeline: read a `.scad` file, extract lines containing specific geometry commands, count each type, and output a summary to both screen and file.
12. Create an interactive piping tool: build a script that accepts user input for a search term, pipes through multiple filters, and displays paginated results.
13. Develop a performance analysis tool: use piping to combine file listing, metadata extraction, and statistical reporting; export results to a dated report file.
14. Implement a comprehensive error-handling pipeline: read output, catch errors, log them separately, and generate a summary of successes vs failures.
15. Design and execute a real-world project backup workflow: use piping to verify file integrity, count files by type, generate a backup manifest, and create audit logs-all in one integrated command pipeline.

## References

- Microsoft. (2024). *Out-File cmdlet for redirection*. https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/out-file
- Microsoft. (2024). *Select-String piping reference*. https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/select-string
- Microsoft. (2024). *PowerShell pipeline concepts*. https://learn.microsoft.com/powershell/scripting/learn/shell/using-the-pipeline

## Helpful Resources

- [Using Out-File for Redirection](https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/out-file)
- [Piping and Select-String](https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/select-string)
- [Get-Content Cmdlet Reference](https://learn.microsoft.com/powershell/module/microsoft.powershell.management/get-content)
- [Measure-Object for Counting](https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/measure-object)
- [PowerShell Pipeline Concept](https://learn.microsoft.com/powershell/scripting/learn/shell/using-the-pipeline)

PS-4: Environment Variables, PATH, and Aliases

Estimated time: 30-45 minutes

Learning Objectives

• Read environment variables with $env:VARNAME
• Inspect and verify programs in the PATH
• Create temporary aliases and understand making them persistent via the profile

Materials

• PowerShell (with rights to open profile if desired)

Step-by-step Tasks

1. Show your username and home path with echo $env:USERNAME and echo $env:USERPROFILE.
2. Inspect echo $env:PATH and identify whether openscad or code would be found.
3. Run Get-Command openscad and note the result.
4. Create a temporary alias: Set-Alias -Name preview -Value openscad and test preview myfile.scad.
5. Open your profile (notepad.exe $PROFILE) and add the alias line to make it persistent (advanced).

Checkpoints

• After step 3 you can determine whether a program will be found by PATH.

Quiz - Lesson PS.4

1. How do you print an environment variable?
2. What is the purpose of PATH?
3. How do you check whether openscad is available?
4. How do you create a temporary alias?
5. Where would you make an alias permanent?
6. True or False: Environment variables are case-sensitive on all platforms.
7. Explain why having a program in your PATH is useful compared to always using its full file path.
8. Write a command that would create an alias called slicer for the OpenSCAD executable.
9. What file would you edit to make an alias persist across PowerShell sessions?
10. Describe a practical benefit of using the $env:TEMP directory for temporary files in a 3D printing workflow.
11. You have a custom script at C:\Scripts\backup_models.ps1 that you want to run from anywhere as backup-now. What steps would you take to make this work?
12. Explain the difference between setting an environment variable in the current session vs. adding it to your profile for permanence.
13. Design a profile strategy for managing multiple 3D printing projects, each with different tool paths and directories; show how to structure environment variables for each.
14. If a program is not found by Get-Command, what are the possible reasons, and how would you troubleshoot?
15. Describe how you would verify that your PowerShell profile is loading correctly and how to debug issues if aliases or environment variables don’t appear after restarting PowerShell.

Extension Problems

1. Add a folder to PATH for a test program (describe steps; do not change system PATH without admin).
2. Create a short profile snippet that sets two aliases and test re-opening PowerShell.
3. Use Get-Command to list the path for several common programs.
4. Explore $env:TEMP and create a file there.
5. Save a copy of your current PATH to a text file and examine it in your editor.
6. Create a PowerShell profile script that loads custom aliases and environment variables for your 3D printing workflow; test it in a new session.
7. Build a “project profile” that sets environment variables for CAD, slicing, and print directories; switch between profiles for different projects.
8. Write a script that audits your current environment variables and creates a summary report of what’s set and why.
9. Design a custom alias system for common 3D printing commands; document the aliases and their purposes.
10. Create a profile migration guide: document how to export and import your PowerShell profile across machines for consistent workflows.
11. Implement a safe PATH modification script: create a utility that allows you to add/remove directories from PATH for the current session only; show how to make it permanent in your profile.
12. Build a comprehensive profile framework with modules: create separate .ps1 files for aliases, environment variables, and functions; have your main profile load all of them dynamically.
13. Develop an environment validation tool: write a script that checks whether all required programs (OpenSCAD, slicers, etc.) are accessible via PATH; report findings and suggest fixes.
14. Create a project-switching alias system: design a function that changes all environment variables and aliases based on the current project; test switching between multiple projects.
15. Build a profile troubleshooting guide: create a script that exports your current environment state (variables, aliases, PATH) to a timestamped file, allowing you to compare states before and after changes and identify what broke.

References

• Microsoft. (2024). Environment variables in PowerShell. https://learn.microsoft.com/powershell/scripting/learn/shell/using-environment-variables
• Microsoft. (2024). Set-Alias cmdlet reference. https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/set-alias
• Microsoft. (2024). Creating and using PowerShell profiles. https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_profiles

Helpful Resources

• Environment Variables in PowerShell
• Understanding the PATH Variable
• Set-Alias Cmdlet Reference
• Creating a PowerShell Profile
• Get-Command for Locating Programs

PS-5: Filling in the Gaps - Control Flow, Profiles, and Useful Tricks

Estimated time: 30-45 minutes

Learning Objectives

• Use history and abort commands (history, Ctrl+C)
• Inspect and edit your PowerShell profile for persistent settings
• Run programs by full path using the & operator
• Handle common screen reader edge cases when using the terminal

Materials

• PowerShell and an editor (Notepad/ VS Code)

Step-by-step Tasks

1. Run several simple commands (e.g., pwd, ls -n, echo hi) then run history to view them.
2. Use Invoke-History <n> to re-run a previous command (replace <n> with a history number).
3. Practice aborting a long-running command with Ctrl + C (for example, ping 8.8.8.8).
4. Open your profile: notepad.exe $PROFILE; if it doesn’t exist, create it: ni $PROFILE -Force.
5. Add a persistent alias line to your profile (example: Set-Alias -Name preview -Value openscad), save, and reopen PowerShell to verify.

Checkpoints

• After step 2 you can re-run a recent command by history number.
• After step 5 your alias should persist across sessions.

Quiz - Lesson PS.5

1. How do you view the command history?
2. Which key combination aborts a running command?
3. What does echo $PROFILE show?
4. How does the & operator help run executables?
5. What is one strategy if terminal output stops being announced by your screen reader?
6. True or False: Using Ctrl+C permanently deletes any files created by the command you abort.
7. Explain the difference between history and Get-History in PowerShell.
8. If you place code in your profile but it doesn’t take effect after opening a new PowerShell window, what should you verify?
9. Write a command that would run a program at the path C:\Program Files\OpenSCAD\openscad.exe directly.
10. Describe a practical workflow scenario where having keyboard shortcuts (aliases) in your profile would save time.
11. Explain how to re-run the 5th command from your history, and what would happen if that command had file operations (creates/deletes).
12. Design a profile initialization strategy that separates utilities for different projects; explain how you would switch between them.
13. Walk through a troubleshooting workflow: your screen reader stops announcing output after running a long command. What steps would you take to diagnose and resolve the issue?
14. Create a safety checkpoint system: before any destructive operation (mass delete, overwrite), how would you use profile functions and history to verify the command is correct?
15. Develop a comprehensive capstone scenario: integrate everything from PS-0 through PS-5 (navigation, file operations, piping, environment setup, history) to design an automated 3D printing project workflow with error handling and logging.

Extension Problems

1. Add an alias and an environment variable change to your profile and document the behavior after reopening PowerShell.
2. Create a short script that automates creating a project folder and an initial .scad file.
3. Experiment with running OpenSCAD by full path using & and by placing it in PATH; compare results.
4. Practice redirecting Get-Help output to a file and reading it in Notepad for screen reader clarity.
5. Document three screen reader troubleshooting steps you used and when they helped.
6. Build a comprehensive PowerShell profile that includes aliases, environment variables, and helper functions for your 3D printing workflow.
7. Create a script that troubleshoots common PowerShell issues (module loading, permission errors, command not found); test at least three scenarios.
8. Write a PowerShell function that coordinates multiple tasks: creates a project folder, starts OpenSCAD, and opens slicing software.
9. Design a screen-reader accessibility guide for PowerShell: document commands, outputs, and accessible navigation patterns.
10. Develop an advanced PowerShell workflow: implement error handling, logging, and confirmation prompts for risky operations.
11. Implement a “undo” system using history: create a function that logs destructive commands (rm, mv, cp -Force) and allows you to review/rollback the last operation.
12. Build a profile debugger: create a script that compares two PowerShell sessions’ environment states (variables, aliases, functions) to identify what loaded/failed to load.
13. Develop a multi-project profile manager: design a system where you can switch entire environments (paths, aliases, variables) for different 3D printing projects by running a single command.
14. Create a comprehensive accessibility analyzer: write a script that tests whether key PowerShell commands produce screen-reader-friendly output; document workarounds for commands that don’t.
15. Design a complete capstone project: build an integrated automation suite that manages a 3D printing workflow (project setup, file organization, CAD/slicing tool automation, output logging, error recovery, and audit trails) with full error handling and documentation.

References

• Microsoft. (2024). PowerShell history and recall functionality. https://learn.microsoft.com/powershell/scripting/learn/shell/using-history
• Microsoft. (2024). Understanding and creating PowerShell profiles. https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_profiles
• Microsoft. (2024). The call operator (&) for running executables. https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_operators#call-operator-

Helpful Resources

• PowerShell History and Recall
• Understanding Profiles
• Invoke-History Cmdlet Reference
• The Call Operator (&)
• Screen Reader Tips and Tricks

PS-6: Advanced Terminal Techniques - Scripts, Functions & Professional Workflows

Duration: 90 minutes
Prerequisites: Complete PS-0 through PS-5
Skill Level: Advanced intermediate

This lesson extends PowerShell skills to professional-level workflows. You’ll learn to automate complex tasks, write reusable code, and integrate tools for 3D printing workflows.

Learning Objectives

By the end of this lesson, you will be able to:

• Create and run PowerShell scripts (.ps1 files)
• Write functions that accept parameters
• Use loops to repeat tasks automatically
• Automate batch processing of 3D models
• Debug scripts when something goes wrong
• Create professional workflows combining multiple tools

Part 1: PowerShell Scripts Basics

What’s a Script?

A script is a file containing PowerShell commands that run in sequence. Instead of typing commands one by one, you put them in a file and run them all at once.

Why use scripts?

• Repeatability: Run the same task 100 times identically
• Documentation: Commands are written down for reference
• Complexity: Combine many commands logically
• Automation: Schedule scripts to run automatically

Creating Your First Script

Step 1: Open a text editor

notepad.exe my-first-script.ps1

Step 2: Type this script

# This is a comment - screen readers will read it
Write-Output "Script is running!"
pwd
ls -n
Write-Output "Script is done!"

Step 3: Save the file

• In Notepad: Ctrl+S
• Make sure filename ends in .ps1
• Save in an easy-to-find location (like Documents)

Step 4: Run the script

.\my-first-script.ps1

What happens: PowerShell runs each command in sequence and shows output.

Important: Script Execution Policy

On some Windows systems, you might get an error about “execution policy”. This is a security feature.

To fix it temporarily:

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process

Then try your script again:

.\my-first-script.ps1

Note for screen readers: Your screen reader will announce the error if there is one. Use Get-Help Get-ExecutionPolicy for more information.

Part 2: Variables and Parameters

Using Variables

Variables store values you want to use later.

Example script:

$mypath = "C:\Users\YourName\Documents"
cd $mypath
Write-Output "I am now in:"
pwd
ls -n

Breaking it down:

• $mypath = variable name (always starts with $)
• = = assign the value after this
• "C:\Users..." = the value (a path)
• cd $mypath = use the variable (replace $mypath with its value)

Functions with Parameters

A function is reusable code that you can run with different inputs.

Example: A function that lists files in a folder

function ListFolder {
    param(
        [string]$path
    )
    
    Write-Output "Contents of: $path"
    cd $path
    ls -n
}

# Use the function:
ListFolder -path "C:\Users\YourName\Documents"
ListFolder -path "C:\Users\YourName\Downloads"

What’s happening:

• function ListFolder = name of the function
• param([string]$path) = the function accepts a parameter called $path
• Inside the function, use $path like any variable
• Call the function with -path "value"

Screen reader tip: When you call a function, PowerShell will announce the results just like any command.

Part 3: Loops - Repeating Tasks

Loop Over Files

Imagine you have 10 SCAD files and want to print their contents. You could do it 10 times manually, or use a loop.

Example: Print every .scad file in a folder

$scadFiles = ls -n *.scad

foreach ($file in $scadFiles) {
    Write-Output "=== File: $file ==="
    cat $file
    Write-Output ""
}

What’s happening:

• $scadFiles = ls -n *.scad = find all .scad files and store in variable
• foreach ($file in $scadFiles) = for each file, do this:
  • Write-Output "=== File: $file ===" = announce which file
  • cat $file = show contents
  • Write-Output "" = blank line between files

Result: All files printed one after another, organized and readable.

Loop with a Counter

Example: Do something 5 times

for ($i = 1; $i -le 5; $i++) {
    Write-Output "This is iteration number $i"
    # Do something here
}

What’s happening:

• for ($i = 1; $i -le 5; $i++) = loop from 1 to 5
• $i = counter variable (starts at 1, increases each loop)
• -le = “less than or equal to” (stop when $i > 5)
• $i++ = add 1 to $i each time through

Part 4: Real-World Example - Batch Processing SCAD Files

Scenario

You have 10 OpenSCAD (.scad) files in a folder. You want to:

1. List them all
2. Check how many there are
3. For each one, verify it exists

The Script

# Batch Processing Script for SCAD Files

$scadFolder = "C:\Users\YourName\Documents\3D_Projects"
$scadFiles = ls $scadFolder -Filter *.scad -Name

Write-Output "Processing SCAD files in: $scadFolder"
Write-Output "Found $($scadFiles.Count) files"
Write-Output ""

foreach ($file in $scadFiles) {
    $fullPath = Join-Path -Path $scadFolder -ChildPath $file
    
    if (Test-Path -Path $fullPath) {
        Write-Output " Found: $file"
    } else {
        Write-Output " Missing: $file"
    }
}

Write-Output ""
Write-Output "Batch processing complete!"

Breaking it down:

• $scadFolder = where to look
• ls $scadFolder -Filter *.scad -Name = find .scad files, show names only
• foreach = process each file
• Join-Path = combine folder and filename into full path
• Test-Path = check if file exists
• if = do different things based on condition

Running the Script

1. Save as batch-process.ps1
2. Edit $scadFolder to match your real folder
3. Run it:

   .\batch-process.ps1
   

Screen reader output:

Processing SCAD files in: C:\Users\YourName\Documents\3D_Projects
Found 10 files

 Found: model1.scad
 Found: model2.scad
 Found: model3.scad
[... more files ...]
Batch processing complete!

Part 5: Error Handling

Try-Catch Blocks

What if something goes wrong? Use try-catch:

Example:

try {
    $file = "C:\nonexistent\path\file.txt"
    $content = cat $file
    Write-Output $content
} catch {
    Write-Output "Error: Could not read file"
    Write-Output "Details: $_"
}

What’s happening:

• try = run these commands
• If an error happens, PowerShell jumps to catch
• catch = handle the error gracefully
• $_ = the error message

Screen reader advantage: Errors are announced clearly instead of crashing silently.

Validating Input

Example: Make sure a folder exists before processing

function ProcessFolder {
    param([string]$folderPath)
    
    if (-not (Test-Path -Path $folderPath)) {
        Write-Output "Error: Folder does not exist: $folderPath"
        return
    }
    
    Write-Output "Processing folder: $folderPath"
    ls -n $folderPath
}

ProcessFolder -folderPath "C:\Users\YourName\Documents"

What’s happening:

• Test-Path = check if folder exists
• -not = if NOT true
• return = exit the function early if error

Part 6: Debugging Scripts

Common Errors and Solutions

Error 1: “Command not found”

Cause: Typo in command name

Fix: Check spelling

# Wrong:
writ-output "hello"

# Correct:
Write-Output "hello"

Error 2: “Variable is null”

Cause: Variable was never assigned

Fix: Make sure variable is set before using it

$myvar = "hello"  # Set first
Write-Output $myvar  # Then use

Error 3: “Cannot find path”

Cause: Wrong folder path

Fix: Verify path exists

# Check if path exists:
Test-Path -Path "C:\Users\YourName\Documents"

# If false, the path is wrong

Error 4: “Access denied”

Cause: Don’t have permission

Fix: Run PowerShell as administrator

• Right-click PowerShell -> Run as administrator

Debugging Technique: Trace Output

Add Write-Output statements to track what’s happening:

$path = "C:\Users\YourName\Documents"
Write-Output "Starting script. Path is: $path"

$files = ls -n $path
Write-Output "Found $($files.Count) files"

foreach ($file in $files) {
    Write-Output "Processing: $file"
    # Do something with $file
    Write-Output "Done with: $file"
}

Write-Output "Script complete"

Your screen reader will announce each step, so you know where errors happen.

Part 7: Creating Professional Workflows

Example 1: Automated Project Setup

Scenario: You start a new 3D printing project regularly. Instead of creating folders manually:

function SetupNewProject {
    param([string]$projectName)
    
    $baseFolder = "C:\Users\YourName\Documents\3D_Projects"
    $projectFolder = Join-Path -Path $baseFolder -ChildPath $projectName
    
    # Create folder structure
    mkdir $projectFolder -Force
    mkdir "$projectFolder\designs" -Force
    mkdir "$projectFolder\output" -Force
    mkdir "$projectFolder\notes" -Force
    
    # Create a README
    $readmeContent = @"
# $projectName

Created: $(Get-Date)

## Designs
All .scad files go here.

## Output
STL and other exports go here.

## Notes
Project notes and observations.
"@
    
    $readmeContent | Out-File -FilePath "$projectFolder\README.txt" -Encoding utf8
    
    Write-Output "Project setup complete: $projectFolder"
}

# Use it:
SetupNewProject -projectName "MyKeychain"
SetupNewProject -projectName "PhoneStand"

What it does:

• Creates folder structure for a new project
• Sets up subfolders for designs, output, notes
• Creates a README file automatically

Example 2: Batch File Verification

Scenario: Before processing, verify all required files exist:

function VerifyProjectFiles {
    param([string]$projectFolder)
    
    $requiredFiles = @(
        "README.txt",
        "designs",
        "output",
        "notes"
    )
    
    $allGood = $true
    
    foreach ($item in $requiredFiles) {
        $path = Join-Path -Path $projectFolder -ChildPath $item
        
        if (Test-Path -Path $path) {
            Write-Output " Found: $item"
        } else {
            Write-Output " Missing: $item"
            $allGood = $false
        }
    }
    
    if ($allGood) {
        Write-Output "All checks passed!"
        return $true
    } else {
        Write-Output "Some files are missing!"
        return $false
    }
}

# Use it:
$verified = VerifyProjectFiles -projectFolder "C:\Users\YourName\Documents\3D_Projects\MyKeychain"
if ($verified) {
    Write-Output "Safe to proceed with processing"
}

Part 8: Screen Reader Tips for Scripts

Making Script Output Readable

Problem: Script runs but output scrolls too fast or is hard to follow

Solution 1: Save to file

.\my-script.ps1 > output.txt
notepad.exe output.txt

Solution 2: Use Write-Output with clear sections

Write-Output "========== STARTING =========="
Write-Output ""
# ... script ...
Write-Output ""
Write-Output "========== COMPLETE =========="

Solution 3: Pause between major sections

Write-Output "Pausing... Press Enter to continue"
Read-Host

Your screen reader will announce the pause, give you time to read output.

Announcing Progress

For long-running scripts:

$files = ls -n *.scad
$count = 0

foreach ($file in $files) {
    $count++
    Write-Output "Processing $count of $($files.Count): $file"
    
    # Do something with $file
}

Write-Output "All $count files processed!"

Practice Exercises

Exercise 1: Your First Script

Goal: Create and run a simple script

Steps:

1. Create file: notepad.exe hello.ps1
2. Type:

   Write-Output "Hello from my first PowerShell script!"
   pwd
   ls -n
   

3. Save and run: .\hello.ps1

Checkpoint: You should see output for each command.

Exercise 2: Script with a Variable

Goal: Use a variable to make the script flexible

Steps:

1. Create file: notepad.exe smart-listing.ps1
2. Type:

   $targetFolder = "C:\Users\YourName\Documents"
   Write-Output "Listing contents of: $targetFolder"
   ls -n $targetFolder
   

3. Edit $targetFolder to a real folder on your computer
4. Run: .\smart-listing.ps1

Checkpoint: You should see listing of that specific folder.

Exercise 3: Function

Goal: Create a reusable function

Steps:

1. Create file: notepad.exe navigate.ps1
2. Type:

   function GoTo {
       param([string]$path)
       
       if (Test-Path -Path $path) {
           cd $path
           Write-Output "Now in: $(pwd)"
           Write-Output "Contents:"
           ls -n
       } else {
           Write-Output "Path does not exist: $path"
       }
   }
   
   # Test the function:
   GoTo -path "C:\Users\YourName\Documents"
   GoTo -path "C:\Users\YourName\Downloads"
   

3. Run: .\navigate.ps1

Checkpoint: Both commands should work, showing contents of each folder.

Exercise 4: Loop

Goal: Use a loop to repeat an action

Steps:

1. Create file: notepad.exe repeat.ps1
2. Type:

   Write-Output "Demonstrating a loop:"
   
   for ($i = 1; $i -le 5; $i++) {
       Write-Output "Iteration $i: Hello!"
   }
   
   Write-Output "Loop complete!"
   

3. Run: .\repeat.ps1

Checkpoint: Should print “Iteration 1” through “Iteration 5”.

Exercise 5: Real-World Script

Goal: Create a useful script for a real task

Steps:

1. Create a folder: mkdir C:\Users\YourName\Documents\TestFiles
2. Create some test files:

   echo "test" > C:\Users\YourName\Documents\TestFiles\file1.txt
   echo "test" > C:\Users\YourName\Documents\TestFiles\file2.txt
   echo "test" > C:\Users\YourName\Documents\TestFiles\file3.txt
   

3. Create script: notepad.exe report.ps1
4. Type:

   $folder = "C:\Users\YourName\Documents\TestFiles"
   $files = ls -n $folder
   
   Write-Output "=== FILE REPORT ==="
   Write-Output "Folder: $folder"
   Write-Output "Total files: $($files.Count)"
   Write-Output ""
   Write-Output "Files:"
   foreach ($file in $files) {
       Write-Output "  - $file"
   }
   Write-Output ""
   Write-Output "=== END REPORT ==="
   

5. Run: .\report.ps1

Checkpoint: Should show report of all files in the test folder.

Quiz - Lesson PS-6

1. What is a PowerShell script?
2. What file extension do PowerShell scripts use?
3. What is a variable and how do you create one?
4. What is a function and why would you use one?
5. How do you run a script?
6. What is a loop and what does foreach do?
7. What does Test-Path do?
8. How do you handle errors in a script?
9. When would you use Try-Catch?
10. What technique makes script output readable for screen readers?

Extension Problems

1. Auto-Backup Script: Create a script that copies all files from one folder to another, announcing progress
2. File Counter: Write a function that counts files by extension (.txt, .scad, .stl, etc.)
3. Folder Cleaner: Script that deletes files older than 30 days (with user confirmation)
4. Project Template: Function that creates a complete project folder structure with all needed files
5. Batch Rename: Script that renames all files in a folder according to a pattern
6. Log Generator: Create a script that records what it does to a log file for later review
7. Scheduled Task: Set up a script to run automatically every day at a specific time
8. File Verifier: Check that all SCAD files in a folder have corresponding STL exports
9. Report Generator: Create a summary report of all projects in a folder
10. Error Tracker: Script that lists all commands that had errors in your recent history

Important Notes

• Always test scripts on small sets of files first before running them on important data
• Save your work regularly - use version control if possible
• Test error handling - make sure errors don’t crash silently
• Document your scripts - use comments so you remember what each part does
• Backup before batch operations - if something goes wrong, you have the original

References

• Microsoft PowerShell Scripting Guide: https://docs.microsoft.com/powershell/scripting/
• Function Documentation: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_functions_advanced
• Error Handling: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_error_handling
• Loops: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_foreach

Next Steps: After mastering this lesson, explore PowerShell modules, remoting, and 3D printing integration in the main curriculum.

PowerShell Introduction - Screen-reader friendly (JAWS/NVDA)

Estimated time: 20-30 minutes

Target audience: Users who are new to the command line and use screen readers.

Learning Goals

• Open and identify the PowerShell prompt
• Run basic commands: pwd, ls -n, cd, ni, cat, echo
• Redirect and page through long outputs for screen readers
• Use Get-Help and Get-Command to learn more

Starting PowerShell

Windows

1. Press Windows, type PowerShell, then press Enter.
2. If you need elevated rights, press Windows+X then choose Windows PowerShell (Admin).

macOS / Linux

1. Open Terminal.app (macOS) or your preferred terminal (Linux).
2. Type pwsh and press Enter (PowerShell Core / pwsh must be installed).

When PowerShell starts you will hear the prompt and usually your current path. The default prompt often includes PS followed by the path, e.g., PS C:\Users\YourName>.

Essential commands - short list

• pwd - print working directory (where you are now)
• ls -n - list file and folder names only (recommended for screen readers)
• cd <path> - change directory
• ni <filename> - create a file (alias for New-Item)
• cat <file> - show file contents
• echo <text> - print text

Quick examples:

pwd
ls -n
cd Documents
ni notes.txt
echo "hello" > notes.txt
cat notes.txt

Paging long outputs for screen readers

• If an output is long, redirect to a file and open it in an editor: some-command > output.txt ; notepad.exe output.txt.
• Or pipe to more: some-command | more (press Space to advance pages, Q to quit).
• For very long listings prefer ls -n | Out-File -FilePath list.txt -Encoding utf8 then open list.txt.

Help and discovery

• Get-Help <command> shows help: Get-Help ls or Get-Help Get-ChildItem.
• Get-Command <name> locates a program or cmdlet: Get-Command openscad.

Tip: Redirect Get-Help into a file for easier reading: Get-Help Get-Command | Out-File help.txt ; notepad.exe help.txt.

Running scripts and executables

• Use the call operator & to run files with spaces or when PowerShell might treat them differently: & "./script.ps1".
• To run an executable by path: & 'C:\Program Files\OpenSCAD\openscad.exe'.

Screen reader specific tips (JAWS, NVDA)

• Use ls -n to avoid cluttered, multi-column listings.
• Redirect large outputs to a text file and open it in an editor that your screen reader handles well.
• If output stops being announced, try moving focus with Alt+Tab and back, or briefly pressing Ctrl or Shift to force announcement.

Suggested learning path

1. Open PowerShell, run pwd, ls -n, cd into Documents.
2. Create a file with ni test.txt, add a line with echo "hi" > test.txt, and read it with cat test.txt.
3. Use Get-Help ls and redirect output to a file to read comfortably.

Hands-on: Explore the terminal (Beginner)

1. Run pwd and speak or note the output.
2. Run ls -n in your home directory. If the list is long, save it: ls -n > listing.txt ; notepad.exe listing.txt.
3. Create a folder and file: mkdir PS_Practice ; cd PS_Practice ; ni notes.txt.
4. Add a line: echo "My first note" > notes.txt ; cat notes.txt.

Extension Exercises

1. Use wildcards to list only .scad files: ls -n *.scad. Proceed to search for other types of files.
2. Save a long command’s output and search it with Select-String.
3. Create a small script that prints a timestamp and test it with &.
4. Build a project template generator: write a script that creates a folder structure for a new 3D printing project.
5. Create a personalized PowerShell profile with aliases for frequently used commands; test it after restart.
6. Write a PowerShell script that combines multiple concepts: navigates folders, creates files, and performs file operations.
7. Create a screen-reader navigation guide for PowerShell ISE; test with actual screen reader if available.
8. Build a data analysis script: read a CSV file, filter and process data, and generate a report.
9. Develop a troubleshooting aide: common PowerShell error messages, their causes, and solutions.
10. Design a comprehensive PowerShell learning portfolio: document skills developed, commands mastered, scripts created, and practical applications.

Quick Quiz (10 questions)

1. What command shows your current directory?
2. How do you list names only for screen readers?
3. How do you create an empty file?
4. What operator runs a script or executable by path?
5. How do you page through long output?
6. True or False: PowerShell only runs on Windows.
7. What does the ~ symbol represent in a PowerShell path?
8. Explain why redirecting output to a file (e.g., command > output.txt) is helpful for screen reader users.
9. What is the difference between Get-Help and Get-Command?
10. Describe a practical scenario where you would use piping (|) in PowerShell.

References

• Microsoft. (2024). PowerShell scripting language documentation. https://learn.microsoft.com/powershell/
• Microsoft. (2024). Out-File cmdlet reference. https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/out-file
• Wadhwa, K. & others. (2024). PowerShell for DevOps and system administration. https://learn.microsoft.com/powershell/scripting/learn/shell/navigate-the-filesystem

PowerShell Tutorial

Estimated time: 30-45 minutes

Learning Objectives

• Launch PowerShell and identify the prompt
• Understand and use basic path notation (~, ./, ../)
• Use pwd, ls -n, and cd to navigate the filesystem
• Open files in an external editor and run simple commands

Materials

• A computer with PowerShell installed
• Access to a text editor (Notepad, VS Code)

Pre-Requisite Knowledge

• Typing and basic text-editing skills
• Familiarity with file/folder concepts and basic OS navigation
• Basic screen-reading familiarity (if applicable)

What is PowerShell?

PowerShell is a cross-platform command-line shell and scripting language that runs on Windows, Linux, and macOS. It lets you control your computer with text commands instead of a graphical user interface (GUI). In this course we use PowerShell to run CLI tools (like OpenSCAD, slicers, or 3DMake), move files, and automate repetitive tasks.

What we’ll do and why

You’ll use PowerShell to run CLI programs, navigate the filesystem, and manipulate files - tasks that are especially efficient when using a keyboard or a screen reader.

Quick tutorial & core concepts

Paths and navigation

• ~ - home directory
• . - current directory
• .. - parent directory
• ./ - current directory shortcut
• ../ - parent directory shortcut
• Use Tab to autocomplete files and folders (try typing ~/D then press Tab)

Paths typically use \ on Windows and / on Unix-like systems; PowerShell accepts / in most contexts.

Useful commands (examples)

pwd                # show current directory
ls -n              # list names only (screen-reader friendly)
cd path/to/dir     # change directory
whoami             # current user

Wildcards

• * matches zero or more characters
• ? matches a single character

Use ls -n *.scad to filter by extension, for example.

Common operations

File and folder manipulation

mkdir my-folder          # create folder
cp -r src dest           # copy (use -r for directories)
mv oldname newname       # rename or move
rm file                  # remove file
ni filename.txt          # create new file (New-Item alias)

Input, output, and piping

echo 'hello' | clip      # copy to clipboard
command > output.txt     # redirect output to file
command > $null          # discard/suppress output

Use | to pipe output and > to redirect into files.

Editing and running programs

notepad.exe file.txt     # open in Notepad (Windows)
code file.txt            # open in VS Code (if in PATH)
& './script.ps1'         # call operator to run a script or executable

On Linux/macOS, use ./myapp for local executables where appropriate.

Screen-reader friendly tips

• Prefer ls -n for name-only output.
• Filter lists with -af (files) or -ad (directories): ls -n -af ~/Documents.
• Redirect very long outputs to a file and open it in an editor.

Error handling and control

• Abort a running command: Ctrl+C
• View history: Up/Down arrows or Get-History
• Clear screen: clear
• If an error is long, read the first few lines for the gist and copy short snippets into an editor to examine.

Environment variables & PATH

Environment variables configure your session. PATH tells the shell where to find executables.

echo $env:PATH
[Environment]::SetEnvironmentVariable("Path", $env:Path + ";C:/mytools", "Machine")

Setting machine-level environment variables requires Administrator privileges.

Running PowerShell as Administrator

1. Press Windows+X and choose Windows PowerShell (Admin).
2. If a UAC dialog appears, press Alt+Y to accept.

Running CLI applications and archives

To extract ZIP archives:

Expand-Archive -Path file.zip -DestinationPath folder

Aliases and cross-platform notes

PowerShell provides aliases (ls, cp, mv) mapping to cmdlets (Get-ChildItem, Copy-Item, Move-Item). They make PowerShell feel familiar but can behave differently than native Linux tools. Concepts transfer to WSL, macOS, and Linux, but watch path and permission differences.

Step-by-step Tasks (Hands-on)

1. Open PowerShell; listen for the prompt and current path.
2. Run pwd to confirm your location.
3. Run ls -n in your home directory and note the output.
4. Practice cd Documents, cd ../, and cd ~ to move between folders.
5. Create and open a file: ni example.txt ; notepad.exe example.txt (or code example.txt).

Checkpoints

• After step 3 you should be able to state your current directory.
• After step 5 you should be able to create and open a text file from PowerShell.

Quick Quiz (10 questions)

1. What command prints your current directory?
2. What does ~ represent?
3. How do you list only names with ls?
4. How do you go up one directory level?
5. How would you open notes.txt in Notepad from PowerShell?
6. True or False: The pipe operator | sends output to a file.
7. Explain why running commands with elevated privileges (as Administrator) might be necessary.
8. What is the difference between running a script with ./script.ps1 versus & './script.ps1'?
9. Describe how you would handle a very long command output when using a screen reader.
10. What does the PATH environment variable do, and why is it important when running programs like OpenSCAD?

Extension Problems

1. Create a folder OpenSCAD_Projects in Documents and verify its contents.
2. Create three files named a.scad, b.scad, c.scad and list them with a wildcard.
3. Save ls -n ~/Documents output to doc_list.txt and open it.
4. Try tab-completion in a deeply nested folder and note behavior.
5. Capture pwd output into a file and open it: pwd > cwd.txt ; notepad.exe cwd.txt.
6. Build an automated setup script that creates a complete project directory structure, initializes placeholder files, and generates a README.
7. Create a PowerShell cheat sheet for your most-used commands; organize by category (navigation, files, scripting, troubleshooting).
8. Write a non-visual tutorial for PowerShell basics; use audio descriptions and keyboard-only navigation as the primary learning method.
9. Develop a workflow automation script: combines multiple PowerShell concepts (folders, aliases, piping) to solve a real 3D printing task.
10. Create a PowerShell proficiency self-assessment: list all concepts covered, provide test commands for each, and reflect on what you learned.

References

• Microsoft. (2024). Accessibility in PowerShell ISE. https://learn.microsoft.com/powershell/scripting/windows-powershell/ise/accessibility-in-windows-powershell-ise
• Microsoft. (2024). Learn PowerShell scripting language. https://learn.microsoft.com/powershell/scripting/overview
• Microsoft. (2024). Environment variables and PATH configuration. https://learn.microsoft.com/powershell/scripting/learn/shell/using-aliases

Helpful Resources

• Accessibility in PowerShell ISE (Microsoft): https://learn.microsoft.com/powershell/scripting/windows-powershell/ise/accessibility-in-windows-powershell-ise
• Learn PowerShell (Microsoft Docs): https://learn.microsoft.com/powershell/scripting/overview
• Environment Variables & PATH: https://poshcode.gitbook.io/powershell-faq/src/getting-started/environment-variables
• Alias Reference: https://learn.microsoft.com/powershell/scripting/learn/shell/using-aliases

PowerShell Unit Test - Comprehensive Assessment

Estimated time: 60-90 minutes

Key Learning Outcomes Assessed

By completing this unit test, you will demonstrate:

1. Understanding of file system navigation and path concepts
2. Proficiency with file and folder manipulation commands
3. Ability to redirect and pipe command output
4. Knowledge of environment variables and aliases
5. Screen-reader accessibility best practices in terminal environments
6. Problem-solving and command chaining skills

Target Audience:

Users who have completed PS-0 through PS-5 and need to demonstrate mastery of PowerShell fundamentals.

Instructions:

Complete all sections below. For multiple choice, select the best answer. For short answers, write one to two sentences. For hands-on tasks, capture evidence (screenshots or output files) and submit alongside your answers.

Part A: Multiple Choice Questions (20 questions)

Select the best answer for each question. Each question is worth 1 point.

1. What is the primary purpose of the PATH environment variable?

   • A) Store your home directory location
   • B) Tell the shell where to find executable programs
   • C) Configure the visual appearance of the terminal
   • D) Store the current working directory name

2. Which command prints your current working directory?

   • A) ls -n
   • B) cd
   • C) pwd
   • D) whoami

3. What does the ~ symbol represent in PowerShell paths?

   • A) The root directory
   • B) The current directory
   • C) The parent directory
   • D) The home directory

4. How do you list only file names (not full details) in a way that is screen-reader friendly?

   • A) ls
   • B) ls -n
   • C) ls -l
   • D) cat -n

5. Which command creates a new empty file?

   • A) mkdir filename
   • B) ni filename
   • C) touch filename
   • D) echo filename

6. What is the difference between > and >>?

   • A) > redirects to file, >> displays on screen
   • B) > overwrites a file, >> appends to a file
   • C) They do the same thing
   • D) > is for text, >> is for binary

7. What does the pipe operator | do?

   • A) Creates a folder
   • B) Sends the output of one command to the input of another
   • C) Deletes files matching a pattern
   • D) Lists all processes

8. Which command copies a file?

   • A) mv
   • B) rm
   • C) cp
   • D) cd

9. How do you rename a file from oldname.txt to newname.txt?

   • A) cp oldname.txt newname.txt
   • B) mv oldname.txt newname.txt
   • C) rename oldname.txt newname.txt
   • D) rn oldname.txt newname.txt

10. What is the purpose of Select-String?

    • A) Select files in a directory
    • B) Search for text patterns within a file
    • C) Select a string to copy to clipboard
    • D) Select which shell to use

11. Which key combination allows you to autocomplete a path in PowerShell?

    • A) Ctrl + A
    • B) Ctrl + E
    • C) Tab
    • D) Space

12. How do you copy text to the Windows clipboard from PowerShell?

    • A) cat filename > clipboard
    • B) cat filename | clip
    • C) copy filename
    • D) cat filename | paste

13. What does Get-Command openscad do?

    • A) Opens the OpenSCAD application
    • B) Gets help about the OpenSCAD command
    • C) Locates the full path of the openscad executable
    • D) Lists all available commands

14. Which wildcard matches any single character?

    • A) *
    • B) ?
    • C) %
    • D) #

15. What is the purpose of the & call operator?

    • A) Run a script or executable by full path
    • B) Execute all commands in parallel
    • C) Combine multiple commands
    • D) Create an alias

16. How do you create a temporary alias for a command?

    • A) alias preview='openscad'
    • B) Set-Alias -Name preview -Value openscad
    • C) New-Alias preview openscad
    • D) Alias preview = openscad

17. Where is your PowerShell profile typically stored?

    • A) C:\Program Files\PowerShell\profile.ps1
    • B) The location returned by echo $PROFILE
    • C) ~/PowerShell/profile.ps1
    • D) ~/.bashrc

18. How do you abort a long-running command in PowerShell?

    • A) Press Escape
    • B) Press Ctrl + X
    • C) Press Ctrl + C
    • D) Press Alt + F4

19. What command shows the history of previously run commands?

    • A) history
    • B) Get-History
    • C) Show-History
    • D) Both A and B

20. How do you permanently set an alias so it persists across PowerShell sessions?

    • A) Use Set-Alias in the terminal every time
    • B) Add the Set-Alias line to your PowerShell profile
    • C) Use the Windows Control Panel
    • D) Aliases cannot be made permanent

Part B: Short Answer Questions (10 questions)

Answer each question in one to two sentences. Each question is worth 2 points.

1. Explain the difference between absolute and relative paths. Give one example of each.

2. Why is ls -n preferred over ls for screen reader users? Describe what flag you would use to list only files.

3. What is the purpose of redirecting output to a file, and give an example of when you would use > instead of >>?

4. Describe what would happen if you ran rm -r ~/Documents/my_folder and why this command should be used carefully.

5. How would you search for all files with a .scad extension in your current directory? Write the command.

6. Explain what happens when you pipe the output of ls -n into clip. What would you do next?

7. What is an environment variable, and give one example of how you might use it in PowerShell.

8. If a program is not in your PATH, what two methods could you use to run it from PowerShell?

9. Describe how you would open a file in Notepad and also add a line to it from PowerShell.

10. What is one strategy you would use if your screen reader stops announcing terminal output while using PowerShell?

Part C: Hands-On Tasks (10 tasks)

Complete each task and capture evidence (screenshots, output files, or command transcripts). Each task is worth 3 points.

Tasks 1-5: File System and Navigation

1. Create a folder structure ~/Documents/PowerShell_Assessment/Projects using a single command. Capture the ls -n output showing the creation.

2. Create five files named project_1.scad, project_2.scad, project_3.txt, notes_1.txt, and notes_2.txt inside the Projects folder. Use wildcards to list only .scad files, then capture the output.

3. Copy the entire Projects folder to Projects_Backup using cp -r. Capture the ls -n output showing both folders exist.

4. Move (rename) project_1.scad to project_1_final.scad. Capture the ls -n output showing the renamed file.

5. Delete notes_1.txt and notes_2.txt using a single rm command with wildcards. Capture the final ls -n output.

Tasks 6-10: Advanced Operations and Scripting

6. Create a file called my_data.txt with at least four lines using echo and >>. Then read it with cat my_data.txt and capture the output.

7. Use Select-String to search for a keyword (e.g., “project”) in my_data.txt and pipe the results to clip. Paste the results into Notepad and capture a screenshot.

8. List all files in the Projects folder and redirect the output to projects_list.txt. Open it in Notepad and capture a screenshot of the file.

9. Create a temporary alias called myls that runs ls -n, test it, and capture the output. Then explain what would be required to make it permanent.

10. Run Get-Help Get-ChildItem and redirect the output to help_output.txt. Open the file in Notepad and capture a screenshot showing at least the first page of help content.

Grading Rubric

Passing Score: 49 points (70%)

Helpful Resources for Review

• PowerShell Command Reference
• Navigation and File System
• Using Pipes and Filtering
• Profile and Aliases
• Screen Reader Accessibility Tips

Submission Checklist

• All 20 multiple choice questions answered
• All 10 short answer questions answered (1-2 sentences each)
• All 10 hands-on tasks completed with evidence captured
• Files/screenshots organized and labeled clearly
• Submission includes this checklist

Lesson 1: Environmental Configuration and the Developer Workflow

Estimated time: 60-90 minutes

Learning Objectives

• Install and verify 3dm¹, openscad², and a slicer are discoverable in the terminal
• Initialize a 3dMake project and understand the project scaffold (src/, build/, 3dmake.toml)
• Edit src/main.scad using OpenSCAD’s parametric design capabilities³, run 3dm build, and inspect the generated build/main.stl

Materials

• Terminal with 3dMake installed
• Editor (VS Code or Notepad)
• Example scaffold or classroom repository

Step-by-step Tasks

1. Run ./3dm setup or follow instructor’s installation notes; confirm tools with which 3dm and which openscad. Verify your 3dMake installation is properly configured¹.

2. Create a project scaffold with 3dm new and open src/main.scad using 3dm edit-model. For a comprehensive introduction to the workflow, consult the OpenSCAD documentation².

3. Add three top-level parameters (e.g., width, height, thickness) and a minimal model. This demonstrates the parametric design philosophy central to OpenSCAD³.

   Example src/main.scad:

   // Top-level parameters (change these to customize your model)
   width = 50;      // mm
   height = 30;     // mm
   thickness = 5;   // mm
   
   // Main model
   cube([width, height, thickness]);
   

4. Run 3dm build and verify build/main.stl exists. Compare this build process to standard OpenSCAD workflows⁴.

5. Open the STL in your slicer to check for thin walls or non-manifold geometry⁵; if issues appear, iterate on main.scad and rebuild.

6. Try modifying the parameters and running 3dm build again to see how parametric design allows you to quickly create variants.

Checkpoints

• After step 2 you can locate 3dmake.toml and the build/ directory. Ensure your project scaffold matches the expected structure described in the 3dMake repository¹.
• After step 4 the build/ folder contains a valid main.stl. Verify the geometry using your slicer’s validation tools⁶.

Understanding 3D Printing Technology: The FDM Pipeline

Before you send your first print, it’s important to understand how 3D printers work and how the choices you make in the slicer affect the final result. This section builds on the workflow you learned above by explaining what happens after 3dm build.

The FDM (Fused Deposition Modeling) Process

FDM printing builds objects layer by layer, where each layer is a thin horizontal slice of your STL file. Here’s the complete pipeline:

1. STL File -> Your 3dMake model exported as an STL geometry file
2. Slicer Analysis -> Software like PrusaSlicer reads the STL and divides it into layers
3. G-code Generation -> The slicer converts layers into machine instructions (coordinates, temperature, speed)
4. Printing -> The printer reads G-code, heats the nozzle to ~200-230C, and extrudes plastic one layer at a time
5. Cooling & Solidification -> Each layer cools and bonds to the layer below

Critical Settings That Affect Your Print

When you open your STL in a slicer, you’ll encounter several parameters that directly impact quality, time, and strength:

Layer Height

• Definition: The thickness of each printed layer (typically 0.15-0.30 mm)
• Effect on Time: Smaller layers = more detail but longer print time. A layer height of 0.15 mm prints slower than 0.30 mm because more layers must be printed
• Effect on Quality: Smaller layers produce smoother surfaces; larger layers print faster but appear more “stepped”
• Common Choice: 0.20 mm is a good balance for classroom projects

Infill

• Definition: The interior solid percentage of your model (0-100%)
• Purpose: Infill provides internal strength without using solid material throughout (which would be wasteful and heavy)
• Common Values for Classroom: 15-20% infill is typical; 10% for very light parts, 50% for functional parts
• Infill Patterns: Grid, gyroid, or honeycomb patterns determine how the internal structure looks. Grid is simple and fast; gyroid is strong but more complex
• Rule of Thumb: Higher infill = stronger, heavier, and longer print time

Supports

• Definition: Temporary structures the printer creates to hold overhanging geometry during printing
• When Needed: Any geometry that “hangs” at a steep angle (typically > 45 from vertical) requires supports
• Post-Processing: Supports must be removed after printing (breaking them off, dissolving them, or picking them away)
• Cost: Supports increase print time and waste material, so good STL design minimizes them

Why This Matters for Your Design

When you wrote src/main.scad in the tasks above, you created a parametric model. Those parameters become constraints that affect how well your part prints:

• A thickness of 0.5 mm might be too thin for FDM (will break easily)
• A width of 300 mm will take many hours to print
• Sharp corners and thin walls can cause printing failures

Understanding the FDM pipeline helps you design parts that not only look correct in OpenSCAD but will actually print successfully.

Next Steps: The Slicer

After you create an STL with 3dm build, you open it in a slicer to:

1. Verify geometry (check for thin walls or non-manifold faces)
2. Set layer height, infill, and supports
3. Preview the layers to see what the printer will do
4. Export as G-code to send to the printer

You’ll practice this workflow in Lesson 2, where you’ll iterate on a simple part and resolve common printing issues.

Getting Started: Guided Projects & Extension Resources

Once you’ve completed this lesson, you’re ready to work on hands-on projects. The curriculum includes several guided projects and extension resources:

Extension Projects (Beginner to Advanced)

These projects are located in the Lesson 1 assets folder and are designed to reinforce your skills in practical contexts:

• Your First Print (Lesson 1 Assets - Your First Print)

  • Goal: Low-friction introduction to the complete printing workflow
  • Skills: Setup, basic slicing, first-time print validation
  • Best for: After completing Lesson 1
  • Asset folder: assets/Lessons_3dMake_1/Your_First_Print/

• Basic Project Scaffold Template (Lesson 1 Assets - SCAD Template)

  • A starter template for your own 3D printing projects
  • Includes parameter configuration and TODO sections

Learning Series Sample Projects

The 3dmake_learning_series/ folder contains worked examples aligned with this curriculum:

• 01_cube_keycap (Beginner) - Text embossing basics
• 02_parametric_phone_stand (Intermediate) - Transforms and Minkowski fillets
• 03_stackable_bins (Advanced) - Tolerance and assemblies

Reference Materials

Quick-reference guides are available in Reference_Materials/:

• 3dmake-setup-guide.md - Complete setup walkthrough and command reference
• openscad-cheat-sheet.md - Keyboard shortcuts, syntax, and common functions
• filament-comparison-table.md - Material properties for different print scenarios
• master-rubric.md - Assessment criteria for evaluating student work
• markdown-starter-guide.md - Documentation best practices

Quiz - Lesson 3dMake.1 (10 questions)

1. What command initializes a 3dMake project?
2. What folder holds generated STLs?
3. How do you open the main model editor from the CLI?
4. Why is it useful to run 3dm build frequently during development?
5. Give one reason to prefer an external editor over editing inline.
6. True or False: 3dMake requires a graphical user interface to use effectively.
7. Explain what the 3dmake.toml file does in your project.
8. Describe what the src/, build/, and other project scaffold folders are used for.
9. How would you compare the 3dMake build workflow to traditional OpenSCAD workflows?
10. What validation steps should you perform after running 3dm build and before sending a file to print?

Extension Problems (10)

1. Add a README entry explaining your top-level parameters and expected units. Reference best practices from the OpenSCAD documentation².
2. Create a parameter variant by changing width by 20% and build both variants; compare dimensions with calipers. This demonstrates the power of parametric design discussed in programming resources³.
3. Script a 3dm command sequence that automates new -> edit -> build for the scaffold. Review the 3dMake test suite for inspiration⁷.
4. Intentionally create a thin-wall error and document the steps you took to find and fix it. Consult slicing guides⁸ for identifying common geometry issues.
5. Prepare a short instructor sign-off checklist describing safety checks before printing.
6. Build a variant testing suite: create 5+ parameter combinations, export STLs, and compare file sizes and estimated print times.
7. Create a 3dMake project template with best-practice structure, documentation, and reusable modules for future projects.
8. Develop a screen-reader accessibility guide for 3dMake CLI commands and parameter syntax.
9. Design a parametric part library in 3dMake format; document all parameters, units, and example usage.
10. Write a comprehensive troubleshooting guide for common 3dMake build errors, with solutions and prevention tips.

Supplemental Resources

For deeper exploration of OpenSCAD and parametric design, consult these resources:

• Programming with OpenSCAD EPUB Textbook - Comprehensive reference with examples of parametric design, transformations, and modules
• CodeSolutions Repository - Working OpenSCAD code organized by topic, including 3D primitives and parametric examples relevant to Lesson 1
• OpenSCAD Quick Reference - Visual syntax guide and command reference

1. 3DMake GitHub Repository - https://github.com/tdeck/3dmake ↩ ↩2 ↩3

2. OpenSCAD Manual - https://en.wikibooks.org/wiki/OpenSCAD_User_Manual ↩ ↩2 ↩3

3. OpenSCAD Parametric Design - https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/The_OpenSCAD_Language#Variables ↩ ↩2 ↩3

4. OpenSCAD Review - Worth learning? - CadHub, accessed February 18, 2026, https://learn.cadhub.xyz/blog/openscad-review/ ↩

5. OpenSCAD Prompt Creation - DocsBot AI, accessed February 18, 2026, https://docsbot.ai/prompts/technical/openscad-prompt-creation ↩

6. Slicer Validation Tools - PrusaSlicer Documentation - https://docs.prusa3d.com/en/guide/39012-validation-tools/ ↩

7. 3dmake/e2e_test.py at main - GitHub, accessed February 18, 2026, https://github.com/tdeck/3dmake/blob/main/e2e_test.py ↩

8. Slicing Guides and Common Geometry Issues - PrusaSlicer Documentation, accessed February 18, 2026, https://docs.prusa3d.com/en/ ↩

3dMake Setup & Workflow Guide (Comprehensive)

This guide walks you through installing 3dMake, creating projects, and managing your workflow efficiently.

Part 1: Installing 3dMake

Prerequisites

Before installing 3dMake, ensure you have:

• Windows or Linux operating system (macOS is not currently supported)
• Terminal or PowerShell access
• Internet connection to download 3dMake
• At least 100 MB of free disk space

Platform Support

Supported:

• Windows (32-bit and 64-bit)
• Linux (x86-64 architecture)

Not Supported:

• macOS - Currently no macOS version is available

Step-by-Step Installation

Step 1: Download 3dMake for Your Operating System

Visit the 3dMake releases page and download the appropriate version:

Windows:

1. Go to 3dMake Windows Download
2. This downloads 3dmake_windows.zip to your computer
3. Right-click the file and select “Extract All…” (or use your preferred extraction tool)
4. Remember where you extracted it (e.g., C:\Users\YourName\3dmake or C:\Program Files\3dmake)

Linux:

1. Go to 3dMake Linux Download
2. This downloads 3dmake_linux.tar.gz to your computer
3. Extract it using: tar -xzf 3dmake_linux.tar.gz
4. Remember where you extracted it (e.g., ~/3dmake or /opt/3dmake)

Step 2: Open Your Terminal

Windows:

• Press Win + X and select “Windows PowerShell” or “Terminal”
• For screen reader users: Use Alt + F2 and type powershell if needed

Linux:

• Open your terminal application (Terminal, Konsole, GNOME Terminal, etc.)

Step 3: Navigate to 3dMake Directory

Navigate to where you extracted 3dMake:

Windows:

cd C:\Users\YourName\3dmake

Linux:

cd ~/3dmake

For screen reader users: Use pwd (print working directory) to confirm your location.

Step 4: Run the Setup Command

From inside the 3dMake directory, run:

Windows:

.\3dm setup

Linux:

./3dm setup

Follow the prompts to configure:

• Your default printer profile (e.g., Prusa MK4, Bambu Lab)
• OctoPrint connection (if you use OctoPrint)
• AI integration (optional - for model descriptions)
• Preferred text editor

Step 5: Complete Installation

After setup finishes, 3dMake will be available from any directory. You can now use the 3dm command from your terminal.

Do not delete the original 3dMake directory where you extracted the files, as 3dMake needs to reference it.

Step 6: Verify Installation

3dm --version

You should see the installed version number. If you see an error, verify:

• You’re in the 3dMake directory
• The extraction completed successfully
• Your terminal has access to the extracted files

Step 7: Get Help

3dm help

This displays all available 3dMake commands.

Part 2: Creating and Managing Projects

What Is a 3dMake Project?

A 3dMake project is a folder structure that organizes:

• src/ folder - contains your OpenSCAD (.scad) files
• build/ folder - stores outputs that 3dMake generates (STL files, sliced GCODE, etc.)
• 3dmake.toml file - project configuration and settings
• README.md - project documentation

Creating Your First Project

Step 1: Choose or Create a Project Directory

Decide where you want your project. Examples:

Windows:

C:\Users\YourName\Documents\3d-projects\
C:\Users\YourName\Desktop\MyProject\

Linux:

~/3d-projects/
~/Documents/3d-projects/

Create the directory if it doesn’t exist:

Windows:

mkdir C:\Users\YourName\Documents\3d-projects\FirstProject

Linux:

mkdir -p ~/3d-projects/FirstProject

Step 2: Navigate Into Your Project Directory

Windows:

cd C:\Users\YourName\Documents\3d-projects\FirstProject

Linux:

cd ~/3d-projects/FirstProject

For screen reader users: Use pwd (print working directory) to confirm you’re in the right folder.

Step 3: Initialize a 3dMake Project

3dm new

This creates the project structure:

FirstProject/
+------ src/              (stores your .scad files)
+------ build/            (stores generated files: STL, GCODE, etc.)
+------ 3dmake.toml       (project configuration)
+------ README.md         (project documentation)

The src/main.scad file is created as a starting template.

Step 4: Verify Project Creation

Windows:

Get-ChildItem -Force

Linux:

ls -la

You should see the src/, build/, 3dmake.toml, and README.md files listed.

Part 3: Working With Your Project

Creating OpenSCAD Models

Step 1: Create or Edit OpenSCAD Files

The main model file is src/main.scad. You can edit it directly using 3dMake:

3dm edit-model

This opens src/main.scad in your configured text editor.

To edit a different model (if you create additional .scad files):

3dm edit-model -m mymodel

This opens src/mymodel.scad.

Manual File Creation:

You can also create .scad files directly in the src/ folder using your preferred text editor:

• Visual Studio Code
• Notepad++ (Windows)
• Gedit (Linux)
• Nano or Vim (terminal-based)

Step 2: Building Your Model

Before exporting, build the model from your OpenSCAD code:

3dm build

This converts your OpenSCAD code into a 3D mesh (geometry). The output is build/main.stl.

For a different model:

3dm build -m mymodel

This creates build/mymodel.stl.

Step 3: Viewing Model Information

To see statistics about your model:

3dm info

Output includes:

• Bounding box - dimensions (X, Y, Z in millimeters)
• Volume - cubic millimeters of material
• Face count - total triangles in the mesh
• Manifold status - whether model is watertight (printable)

Example output:

Volume: 1234.56 mm
Bounding Box: 50.0 x 40.0 x 30.0 mm
Faces: 2048
Manifold: Yes 

Step 4: Previewing Your Model

3dMake can create flat “tactile previews” of your model (fast-printing 2D silhouettes):

3dm preview slice

This generates a preview STL and slices it (ready to print in minutes).

To print the preview directly:

3dm preview print

Available preview types:

• 3sil - Three silhouettes (front, left, top) - default
• frontsil - Front-facing silhouette only
• topsil - Top-down silhouette only

Change preview type:

3dm preview -v topsil print

Step 5: Slicing and Preparing for Print

To slice your model (convert STL to GCODE for your printer):

3dm build slice

This creates both:

• build/main.stl - the 3D model
• build/main.gcode - sliced for your printer

Step 6: Printing Directly from 3dMake

If your printer is connected via OctoPrint or Bambu Labs (LAN mode):

3dm build slice print

This builds, slices, and sends directly to your printer in one command.

Or simply:

3dm build print

(The print command automatically includes slicing)

Part 4: Managing Multiple Projects

Switching Between Projects

Method 1: Navigate via Terminal

# Leave current project
cd ..

# Enter a different project
cd ../SecondProject
pwd  # Verify you're in the right place

For screen reader users, always use pwd after navigating to confirm your location.

Method 2: Create a Projects Directory Structure

Create a central folder for all projects:

3d-projects/
+------ FirstProject/
|   +------ src/
|   +------ build/
|   +------ 3dmake.toml
+------ SecondProject/
|   +------ src/
|   +------ build/
|   +------ 3dmake.toml
+------ README.md (project index)

Method 3: Use a Project Index

Create a README.md in your 3d-projects/ folder to track all projects:

# My 3D Projects

## Project List

1. **FirstProject** - My initial test models
   - Location: `./FirstProject/src/`
   - Status: In progress
   - Latest model: `main.scad`

2. **SecondProject** - Parametric keychain designs
   - Location: `./SecondProject/src/`
   - Status: Complete
   - Latest model: `keychain.scad`

3. **ThirdProject** - Functional brackets for printing
   - Location: `./ThirdProject/src/`
   - Status: In progress
   - Latest model: `bracket_assembly.scad`

Building from All Projects

To build models from all projects:

Windows:

Get-ChildItem -Directory | ForEach-Object {
    cd $_.FullName
    3dm build
    cd ..
}

Linux/Bash:

for project in */; do
    cd "$project"
    3dm build
    cd ..
done

Part 5: Workflow Best Practices

File Naming Conventions

Use clear, descriptive names for your .scad files:

Good:

• cube_5cm.scad
• parametric_box_v2.scad
• bracket_for_motor.scad
• main.scad (default project model)

Avoid:

• test.scad
• model1.scad
• final_final_FINAL.scad

Understanding TOML Configuration Files

What is TOML?

TOML (Tom’s Obvious, Minimal Language) is a human-readable configuration file format. It’s designed to be simple and clear, making it easy to read and edit in any text editor.

Basic TOML Formatting Rules:

1. Key-value pairs - Each setting has a name and value separated by an equals sign:

   project_name = "My Project"
   

2. Strings use quotes - Text values must be wrapped in double quotes:

   editor = "code"
   printer_profile = "prusa_MK4"
   

3. Numbers don’t need quotes - Numeric values stand alone:

   scale = 1.05
   copies = 3
   

4. Boolean values are true or false - Lowercase, no quotes:

   auto_start_prints = true
   edit_in_background = false
   

5. Arrays use square brackets - Lists of values separated by commas:

   overlays = ["supports", "PETG"]
   libraries = ["bosl", "braille-chars"]
   

6. One setting per line - Each configuration on its own line

7. Comments start with # - Use for notes (not processed):

   # This is my default printer
   printer_profile = "prusa_MK4"
   

How 3dMake Uses TOML:

3dMake has two TOML configuration files:

• Global config (defaults.toml) - Settings for all your projects (run 3dm edit-global-config to edit)
• Project config (3dmake.toml) - Settings specific to one project (located in your project root)

Project settings override global settings. For example, if your global config says printer_profile = "prusa_MK4" but your project’s 3dmake.toml says printer_profile = "bambu", the project setting wins.

Project Configuration (3dmake.toml)

The 3dmake.toml file in your project root contains project-specific settings:

project_name = "My Project"
model_name = "main"
printer_profile = "prusa_MK4"
overlays = []
editor = "code"

Edit your project configuration:

3dm edit-global-config

This opens your configuration file in your text editor.

Version Control (Optional)

If you’re using Git, add a .gitignore to avoid committing large build files:

Create .gitignore in your project root:

build/
*.stl
*.gcode
*.png
.DS_Store
__pycache__/

Then initialize Git:

git init
git add .
git commit -m "Initial project setup"

Backup Strategy

Regularly backup your src/ folder:

Windows:

Copy-Item -Path "src" -Destination "backups/src_$(Get-Date -Format 'yyyy-MM-dd')" -Recurse

Linux:

cp -r src backups/src_$(date +%Y-%m-%d)

Documentation

Keep a src/README.md describing each model:

# Models in This Project

## main.scad
- **Purpose:** Primary design for this project
- **Parameters:** width, height, depth
- **Last modified:** 2026-02-20
- **Notes:** Standard model for printing

## alternate.scad
- **Purpose:** Alternative design variant
- **Parameters:** width, height, depth, wall_thickness
- **Last modified:** 2026-02-15
- **Notes:** Experimental version with snap-fit features

Configuring Your Text Editor

By default, 3dMake uses:

• Windows: Notepad
• Linux: Nano (or your EDITOR environment variable)

To use a different editor, edit your global configuration:

3dm edit-global-config

Add or modify the editor line. Examples:

Windows (Visual Studio Code):

editor = "code"

Windows (Notepad++):

editor = '''C:\Program Files (x86)\Notepad++\notepad++.exe'''

Linux (Visual Studio Code):

editor = "code"

Linux (Gedit):

editor = "gedit"

Part 6: Troubleshooting

Common Issues

“3dm command not found”

Cause: 3dMake isn’t in your PATH or you haven’t completed setup.

Solution:

1. Verify you extracted 3dMake and completed 3dm setup
2. Restart your terminal completely (close and reopen)
3. Check that you’re not inside the 3dMake directory when running commands
4. On Linux, ensure you’re using ./3dm if 3dMake isn’t in your PATH yet

“No such file or directory: src/main.scad”

Cause: You’re not in a valid 3dMake project directory.

Solution:

Verify you’re in the project directory:

pwd
ls -la

You should see src/, build/, and 3dmake.toml files. If not, run:

3dm new

“OpenSCAD error: syntax error at line 5”

Cause: Your .scad file has incorrect OpenSCAD syntax.

Solution:

1. Open your model file: 3dm edit-model
2. Check the line number mentioned in the error
3. Verify correct OpenSCAD syntax (matching parentheses, semicolons, etc.)
4. Save and try building again: 3dm build

“Model won’t render or build”

Checklist:

• File is saved with .scad extension
• File is in the src/ folder
• File has valid OpenSCAD syntax
• Build output has a specific error message (check line number)

Debug mode:

3dm build --debug

This provides more detailed error messages.

Screen reader isn’t reading 3dMake output clearly

Solution: Use the --debug flag for more verbose output:

3dm build --debug

This logs each step, making it easier for screen readers to follow.

“Permission denied” error (Linux)

Cause: 3dMake executable doesn’t have run permissions.

Solution:

chmod +x 3dm
./3dm setup

Cannot connect to printer

Cause: OctoPrint or Bambu printer settings not configured correctly.

Solution:

1. Verify printer is running and connected to network
2. Edit configuration: 3dm edit-global-config
3. Check these settings:
   • octoprint_host - correct IP/URL
   • octoprint_key - valid API key
   • print_mode - set to “octoprint” or “bambu_lan”
4. Test connection: 3dm build print (without actually printing first)

Part 7: Quick Reference

Essential Commands

Directory Structure Reference

YourProject/
+------ src/                 <- Place .scad files here
+------ build/               <- Built STL, GCODE auto-save here
+------ 3dmake.toml          <- Project settings
+------ README.md            <- Project documentation

Configuration Options (3dmake.toml)

Common settings you can modify:

project_name = "My Project"
model_name = "main"              # Default model to build
printer_profile = "prusa_MK4"    # Your printer
overlays = ["supports"]          # Default slicing overlays
editor = "code"                  # Text editor to use

For full configuration options, see the GitHub repository: https://github.com/tdeck/3dmake

Part 8: Next Steps

Once you’re comfortable with basic projects:

1. Learn parametric design - Make reusable models with variables
2. Explore modules - Organize code into reusable functions
3. Add libraries - Use pre-built OpenSCAD libraries (BOSL, etc.)
4. Optimize workflows - Chain commands (3dm build slice print)
5. Automate models - Use loops and conditionals in OpenSCAD
6. Collaborate - Use Git to share projects with others

For advanced topics, see:

• OpenSCAD Manual
• 3dMake GitHub Documentation
• BOSL Library Documentation

Sources

3dMake GitHub Repository. (2026). 3dMake - Non-visual 3D design and printing. Retrieved from https://github.com/tdeck/3dmake

3dMake Documentation. (2026). Terminal quick start guide. Retrieved from https://github.com/tdeck/3dmake/blob/main/docs/terminal_quick_start.md

OpenSCAD Community. (2025). OpenSCAD user manual. Retrieved from https://en.wikibooks.org/wiki/OpenSCAD_User_Manual

Revarbat (Ed.). (2024). BOSL - Belfry OpenSCAD Library. Retrieved from https://github.com/revarbat/BOSL/wiki

VSCode Setup Guide - Accessible OpenSCAD Development

For use with NVDA or JAWS on Windows

This guide walks you through setting up Visual Studio Code (VSCode) as an accessible code editor for writing OpenSCAD files, with a task runner that automatically previews your .scad code in OpenSCAD whenever you save.

Why VSCode Instead of the OpenSCAD Editor?

The built-in OpenSCAD editor has inconsistent behavior with screen readers - focus can jump unexpectedly, and the editor sometimes stops being read after certain actions. VSCode is a mainstream code editor with strong, well-tested accessibility support for both NVDA and JAWS.

You write your code in VSCode. OpenSCAD runs in the background (or in a separate window) to render the preview. You never have to interact with the OpenSCAD editor itself.

Part 1: Install Required Software

1.1 Install VSCode

Download from: https://code.visualstudio.com/

During installation:

• Check “Add to PATH” - this is important for running VSCode from PowerShell
• Check “Register Code as an editor for supported file types”

1.2 Install OpenSCAD

Download from: https://openscad.org/downloads.html

Use the installer version (not the portable version). After installing, confirm OpenSCAD is in your PATH by opening PowerShell and typing:

openscad --version

You should hear a version number. If you get an error, see the PATH setup section in the PowerShell Foundation guide.

1.3 Install the OpenSCAD VSCode Extension (Optional but Recommended)

1. Open VSCode
2. Press Ctrl + Shift + X to open the Extensions panel
3. Type openscad in the search box
4. Install “OpenSCAD Language Support” - this adds syntax highlighting and keyword completion for .scad files

Part 2: Configure the Task Runner

VSCode uses a file called tasks.json to define custom commands you can run from the keyboard. We’ll set up a task that opens your current .scad file in OpenSCAD for preview whenever you press a key.

2.1 Open or Create Your Workspace Folder

All your .scad files for a project should be in one folder. Open that folder in VSCode:

cd ~/Documents/OpenSCAD_Projects
code .

The . tells VSCode to open the current folder as a workspace.

2.2 Create the Tasks File

1. In VSCode, press Ctrl + Shift + P to open the Command Palette
2. Type Tasks: Configure Task and press Enter
3. Select “Create tasks.json file from template”
4. Select “Others”

This creates a .vscode/tasks.json file. Replace its entire contents with the following:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Preview in OpenSCAD",
      "type": "shell",
      "command": "openscad",
      "args": ["${file}"],
      "group": {
        "kind": "build",
        "isDefault": true
      },
      "presentation": {
        "reveal": "silent",
        "panel": "shared"
      },
      "problemMatcher": []
    },
    {
      "label": "Export STL",
      "type": "shell",
      "command": "openscad",
      "args": [
        "-o",
        "${fileDirname}/${fileBasenameNoExtension}.stl",
        "${file}"
      ],
      "group": "build",
      "presentation": {
        "reveal": "always",
        "panel": "shared"
      },
      "problemMatcher": []
    }
  ]
}

Save the file with Ctrl + S.

2.3 Run the Preview Task

With any .scad file open and focused:

• Press Ctrl + Shift + B to run the default build task (Preview in OpenSCAD)
• OpenSCAD will open and display your model
• Switch back to VSCode with Alt + Tab to keep editing

To export an STL:

1. Press Ctrl + Shift + P
2. Type Tasks: Run Task
3. Select “Export STL”
4. The .stl file will be saved in the same folder as your .scad file

Part 3: NVDA Settings for VSCode

3.1 Recommended NVDA Settings

Open NVDA Menu (NVDA + N) -> Preferences -> Settings:

Speech category:

• Symbol level: Most (so you hear brackets, semicolons, and other syntax characters)

Browse Mode category:

• Uncheck “Use browse mode on page load in web content” - not needed for VSCode

3.2 Useful NVDA + VSCode Keyboard Shortcuts

3.3 Punctuation Level

When reading code, you need to hear all punctuation - semicolons, brackets, parentheses, and commas are all part of OpenSCAD syntax.

In NVDA: NVDA + N -> Preferences -> Settings -> Speech -> Symbol level: Most

You can also toggle punctuation level on the fly: NVDA + P cycles through None, Some, Most, All.

Part 4: JAWS Settings for VSCode

4.1 Virtual Cursor

JAWS may try to activate Virtual/Browse mode in VSCode. If VSCode stops responding to arrow keys for navigation and starts reading the page as HTML, press JAWS Key + Z to toggle Virtual mode off. You want to be in Application mode (not Virtual mode) when using VSCode.

4.2 Recommended JAWS Settings

• Punctuation level: All - JAWS Key + Shift + 2 cycles through levels. Set to All for code editing.
• Reading rate: Adjust with Alt + Ctrl + Page Up / Page Down
• Spell current line: JAWS Key + Up Arrow twice quickly

4.3 Useful JAWS + VSCode Keyboard Shortcuts

Part 5: Notepad++ as an Alternative

If VSCode is too complex to set up, Notepad++ is a simpler screen-reader-friendly option for editing .scad files.

Setup

1. Download from: https://notepad-plus-plus.org/
2. Install the OpenSCAD syntax highlighting plugin:
   • Go to Plugins -> Plugin Admin
   • Search for “OpenSCAD” - install if available
   • Alternatively, download a UDL (User Defined Language) file from the OpenSCAD community and import it via Language -> User Defined Language -> Import

Running OpenSCAD from Notepad++

Use the Run menu (F5) to configure a custom command:

openscad "$(FULL_CURRENT_PATH)"

Name it “Preview in OpenSCAD” and assign it a shortcut key (e.g., Ctrl + F5).

NVDA + Notepad++ Tips

• Punctuation level: set to Most or All
• Use Ctrl + G to go to a specific line
• Use Ctrl + F to find text
• The status bar at the bottom of Notepad++ announces line and column numbers - useful for finding where errors are

Part 6: Workflow Summary

Here is the complete workflow from writing code to printing:

1. Open VSCode (or Notepad++) code ~/Documents/OpenSCAD_Projects

2. Open or create a .scad file Ctrl + P -> type filename

3. Write your OpenSCAD code

4. Preview in OpenSCAD Ctrl + Shift + B (VSCode) Ctrl + F5 (Notepad++)

5. If the shape looks right, export STL Run “Export STL” task in VSCode OR: In OpenSCAD, press F6 then File > Export > Export as STL

6. Open PrusaSlicer, import the STL, slice, export G-code

7. Load G-code onto SD card or USB and print

Troubleshooting

OpenSCAD doesn’t open when I run the task

• Confirm OpenSCAD is installed and in your PATH: openscad --version in PowerShell
• If not found, add the OpenSCAD install folder to your PATH (see PowerShell Foundation guide)

VSCode isn’t being read by my screen reader

• For JAWS: Press JAWS Key + Z to toggle out of Virtual mode
• For NVDA: Make sure you are focused inside the editor panel, not a sidebar
• Try clicking directly in the editor area with the mouse once to confirm focus

I hear “unlabeled” for some VSCode elements

• This is a known VSCode accessibility limitation for some UI panels
• Use keyboard shortcuts rather than trying to navigate by element - the editor itself reads well

My .scad file has an error but I can’t find it

• OpenSCAD will display an error in its console - use Alt + Tab to switch to OpenSCAD and arrow through the console to read the error
• Errors always include a line number - use Ctrl + G in VSCode to jump to that line

References

Microsoft. (2024). Visual Studio Code accessibility. https://code.visualstudio.com/docs/editor/accessibility

NV Access. (2024). NVDA user guide. https://www.nvaccess.org/files/nvda/documentation/userGuide.html

OpenSCAD. (n.d.). OpenSCAD documentation. https://openscad.org/documentation.html

Navigating This Curriculum - mdBook Guide

This curriculum is published as a web book using mdBook. This page explains how to find what you need, navigate between chapters, and use the book with a screen reader.

What Is mdBook?

mdBook is a tool that turns a collection of Markdown files into a navigable web book - similar to an online textbook. Each lesson or document is its own page (chapter), and they are organized into sections visible in the sidebar table of contents.

You can access the book from any web browser on any device.

Basic Navigation

Sidebar Table of Contents

The left side of the page contains a table of contents showing all chapters organized by unit and lesson. You can click or tap any chapter title to jump directly to it.

On a small screen (phone or tablet), the sidebar may be hidden. Look for a hamburger menu icon (three horizontal lines) to show it.

Arrow Navigation

At the bottom of every page there are Previous and Next links that take you through the chapters in order. You can also use keyboard arrow keys:

• Left Arrow - go to the previous chapter
• Right Arrow - go to the next chapter

Search

The mdBook search feature indexes all content across all chapters.

• Click the search icon (magnifying glass) in the top bar, or press S
• Type your search term
• Results appear as a dropdown list with the chapter name and a snippet of context
• Click any result to jump to that chapter; the matching term will be highlighted
• Press Escape to close the search panel

Other Keyboard Shortcuts

Screen Reader Navigation

With NVDA (Chrome, Firefox, or Edge recommended)

Reading the page:

• Use Up / Down Arrow to read line by line
• Use H to jump between headings - this is the fastest way to skim a long lesson
• Use Ctrl + F (browser Find) or S (mdBook search) to find specific content

Table of contents:

• The sidebar is a navigation landmark. Press D to move between landmark regions, or use NVDA + F7 to open the Elements List and select “Landmarks” to navigate to the sidebar directly.
• Within the sidebar, arrow through the list of links and press Enter to follow one.

Code blocks:

• Code examples are marked up as <code> elements. NVDA will read them inline.
• Punctuation level should be set to Most or All to hear semicolons, brackets, and other syntax characters in code examples.
• To copy a code block: navigate to the code, press Ctrl + A to select all, or use the copy button if present.

Tips:

• NVDA + P to cycle punctuation level - do this before reading code blocks
• NVDA + F7 -> Links list - useful for navigating between major sections quickly
• H key (headings navigation) is your best friend on lesson pages with many sections

With JAWS (Chrome or Edge recommended)

Reading the page:

• Use Up / Down Arrow in virtual cursor mode to read line by line
• Press H to jump between headings
• Press JAWS Key + F6 to get a list of all headings on the page

Table of contents:

• Press R to move between landmark regions to reach the sidebar
• Within the sidebar, Tab through the links or use Up / Down Arrow

Code blocks:

• Set punctuation to All before reading code: JAWS Key + Shift + 2
• JAWS reads code blocks as regular text - navigate through them line by line

Tips:

• JAWS Key + F5 - links list
• JAWS Key + F6 - headings list
• Ctrl + F - browser find, works alongside mdBook search

With VoiceOver (Mac / iOS)

Mac:

• VO + U to open the rotor - select Headings to navigate by heading
• VO + Command + F to search the page
• H (with Quick Nav on) to move between headings

iOS:

• Swipe left/right to navigate elements
• Use the rotor (two-finger rotate) to set navigation mode to Headings
• Double-tap to activate links

Finding What You Need

If you know which unit or project you need

Open the table of contents and look for the unit or project name. The structure follows this pattern:

• Unit 0 - Foundation lessons (safety, how printing works, calipers, OpenSCAD basics, slicing)
• Unit 1 - Guided projects (Project 0 and Project 1)
• Unit 2 - Intermediate skills (parametric design, tolerances, advanced slicing, materials)
• Unit 3 - Open-ended projects (Project 2, 3, and 4)
• Reference Materials - Quick-reference sheets you can keep open while working
• PowerShell Foundation - Command-line navigation guide

If you are looking for a specific term or command

Use the Search function (S). Search for:

• An OpenSCAD command (e.g., difference, translate, module)
• A vocabulary word (e.g., infill, tolerance, stakeholder)
• A project name (e.g., floor marker, jewelry, assistive technology)

If you are looking for reference material while working

Keep a second browser tab open to the Reference Materials section. Useful pages to bookmark:

• OpenSCAD Cheat Sheet
• Slicing Settings Quick Reference
• Filament Comparison Table
• Screen Reader Coding Tips (NVDA/JAWS)

Printing or Saving Pages

To save or print any page for offline use:

• Ctrl + P opens the print dialog in any browser
• Use “Save as PDF” to save a local copy
• For the whole book: if your instructor has provided a PDF version, use that - it contains all chapters in one file

Reporting a Problem

If a page is missing content, has a broken link, or is difficult to navigate with your screen reader, let your instructor know:

• Which page (chapter title)
• What you were trying to do
• What happened instead

This helps improve the curriculum for future students.

Terminology

How to Use This Terminology File

• Review the glossary before lessons that reference terms (e.g., the OpenSCAD lessons, Make3D build walkthroughs, and PowerShell guides).
• Encourage students to keep a personal glossary when they encounter new words during projects and prototyping.
• Maintain and extend this file as new tools or workflows are adopted.

General Terms

Shape - Any graphical 2D or 3D object created by OpenSCAD. Design - An OpenSCAD creation (an OpenSCAD program) which usually consists of a combination of multiple shapes and operations. Operation - An OpenSCAD command that changes the appearance or properties of one or more shapes (for example translate(), rotate(), difference(), union()). Parameter - A named value passed into a module, function, or used as a variable to control dimensions and behavior. Preview - A fast, approximate display of a design in OpenSCAD used for checking structure before full render. Render - Full evaluation of a design’s geometry in OpenSCAD; required before exporting to an STL for printing. Units - The measurement units used in designs. OpenSCAD is unitless by default, but in 3D printing contexts millimeters are conventionally used; be explicit about units when sharing models. Width / Length / Height - X, Y, and Z axis dimensions respectively. 2D shape - A planar geometry with width and length but negligible height (e.g., a 2D profile used for extrusion). 3D shape - A solid geometry with width, length, and height.

3D Printing Terminology

Layer Height - The vertical thickness of each printed layer, typically measured in millimeters; smaller values give finer Z resolution. Nozzle (Extruder) - The heated tip on the printer that melts filament and deposits it onto the print surface. Filament - Thermoplastic material supplied as a long strand (e.g., PLA, PETG, ABS, TPU) used by FDM printers. Infill - The internal lattice or pattern printed inside a solid object to provide strength while saving material; expressed as a percentage. Shell (Wall) - The outer perimeters printed around each layer that form the visible surface and structural walls of a part. Brim / Raft / Skirt - Temporary structures printed to improve bed adhesion or prime the extruder; removed after printing. Retraction - A printer motion that withdraws filament to reduce ooze when moving between print areas. Overhang - A portion of a model that extends outward such that it has little or no support underneath; critical for printability. Support - Additional printed material used to hold up overhangs during printing; removed after printing (manually or dissolvable). Bed Adhesion - Methods and materials used to keep the first layer attached to the build plate (tape, glue stick, PEI, heated bed). Print Speed - The rate at which the printer moves while extruding; faster speeds reduce time but can reduce print quality. Layer Cooling - Use of fans to cool freshly extruded plastic; affects bridging and overhang quality. G-code - The low-level instructions sent to a 3D printer describing moves, extrusion, temperatures, and other commands. STL - A common 3D model file format (surface tessellation) used for 3D printing; does not hold scale or unit metadata. Slicing - The process of converting a 3D model (e.g., STL) into per-layer toolpaths and G-code for a specific printer and filament. Print Bed / Build Plate - The surface on which prints are produced. Warping - Distortion caused by uneven cooling, often lifting corners from the build plate; mitigated by bed adhesion and enclosure. Calibration - The process of adjusting printer settings (e.g., steps/mm, nozzle height) to ensure accurate prints.

OpenSCAD-Specific Terms

Module - A reusable block of OpenSCAD code defined with module name(){} which can be called with different parameters to produce geometry. Function - A small, parameterized computation defined with function that returns a value used in modules or expressions. Boolean Operations - union(), difference(), intersection() used to combine or subtract solids. Transform - Operations that change object position or orientation, including translate(), rotate(), and scale(). Children - In module calls, the nested code that becomes part of the module’s execution context when using children(). CSG (Constructive Solid Geometry) - The technique of building complex shapes by combining primitive solids with boolean operations. Primitive - Simple built-in shapes like cube(), cylinder(), sphere(), and polyhedron(). Linear Extrusion - linear_extrude() which creates a 3D shape from a 2D profile by extruding along the Z axis. Rotate_extrude - rotate_extrude() which sweeps a 2D profile around an axis to form rotationally symmetric solids. Children() - A special OpenSCAD construct that allows a module to render nested content passed into it. Preview vs Render - Preview is quick and approximate; render (F6) evaluates the final geometry for export. Parameterization - Designing with variables and parameters so that a single file can generate many variants by changing inputs.

3dMake / Make3D Terminology (CLI-based toolchain concepts)

3dMake (Make3D) - A command-line workflow or helper scripts that automate building, slicing, and managing OpenSCAD-based projects. Build Script - A script that automates repetitive steps (rendering, slicing, packaging) for reproducible builds. Pipeline - The sequence of steps from source (.scad) to final G-code (render -> export STL -> slice -> generate G-code). Artifacts - Files produced by the build pipeline (STL, G-code, logs). Parameter File - External file (JSON, TOML, or similar) that provides default parameter values to feed into OpenSCAD builds. Headless Render - Running OpenSCAD from the command line (no GUI) to render models and export STLs programmatically. Automation - Using scripts or CI to produce builds and test changes without manual GUI interaction.

PowerShell Terminology (relevant to automation and workflows)

PowerShell - A task automation and configuration management framework from Microsoft that uses cmdlets and a scripting language. Cmdlet - A lightweight command in PowerShell (e.g., Get-ChildItem, Set-ExecutionPolicy) with structured input and output. Script - A .ps1 file containing PowerShell commands, functions, and logic used to automate tasks. Module (PowerShell) - A package of functions, cmdlets, or scripts that can be imported with Import-Module. Pipeline (PowerShell) - Passing the output of one cmdlet as the input to another using the | operator for chained processing. Object - PowerShell passes rich objects (not plain text) between commands, enabling structured data manipulation. PSProvider - A PowerShell interface that exposes data stores as drives (e.g., HKLM:, Variable:), enabling uniform access. Execution Policy - Security setting controlling whether scripts can run on a machine (e.g., Restricted, RemoteSigned). Cmdlet Parameters - Named options passed to cmdlets (e.g., -Path, -Recurse) to customize behavior. Remote Session - Using Enter-PSSession or Invoke-Command to run commands on a remote system. Error Handling - Using try{ } catch { } finally { } and $Error variables to handle script failures gracefully. Splatting - Passing a collection of parameters to a cmdlet using @{} or @array for cleaner code. Format-Table / Format-List - Cmdlets for controlling how objects are displayed in the console; for automation prefer raw objects to formatted text.

Testing, Documentation, and Workflow Terms

Linting - Static analysis to detect style or simple errors in code (e.g., PowerShell Script Analyzer). Unit / Integration Test - Automated checks that verify functions or the build pipeline produce expected outputs. Versioning - Tracking changes to files (git) to manage collaboration and releases. Release Assets - Packaged files attached to a release (useful for distributing large binaries or fonts without committing them to the repository). Accessibility (a11y) - Ensuring materials and workflows work for people using assistive technology (screen readers, braille displays, keyboard navigation).

Vocabulary Glossary - 3D Design & Printing

Overview

A reference for all key terms used in this curriculum. Terms are organized alphabetically.

Terms

Additive manufacturing - A family of processes that build objects by adding material layer by layer. 3D printing is a form of additive manufacturing.

ABS (Acrylonitrile Butadiene Styrene) - A common plastic filament, stronger and more heat-resistant than PLA, but harder to print and emits more fumes.

Bed adhesion - How well the first layer sticks to the print bed. Poor adhesion causes warping. Improved by using a heated bed, glue stick, or painter’s tape.

Boolean operation - An operation that combines or subtracts 3D shapes. The three types in OpenSCAD are union(), difference(), and intersection().

Brim - A flat ring printed around the base of a model to help it stick to the build plate. Removed after printing.

Build plate / print bed - The flat surface on which the 3D object is built. May be heated.

CAD (Computer-Aided Design) - Using software to create 2D or 3D models. OpenSCAD is a form of CAD.

Caliper - A precision measuring tool used to measure the length, width, height, diameter, or depth of objects to the nearest 0.1 mm or finer.

Clearance - An intentional gap added to a design so that two parts fit together with the desired level of looseness or tightness.

Constructive solid geometry (CSG) - A modeling approach where complex shapes are built from simple primitives using Boolean operations (adding, subtracting, intersecting).

Cooling fan - A fan on the printer that cools the extruded plastic as it is deposited, helping layers set quickly and maintain shape.

difference() - OpenSCAD command that subtracts one shape from another, creating holes or recesses.

Direct drive extruder - An extruder mounted directly above the hot end. Better for flexible filaments (TPU) because the filament path is short.

Extruder - The mechanism that grips and feeds filament into the hot end.

FDM (Fused Deposition Modeling) - The most common type of 3D printing. Melts plastic filament and deposits it layer by layer.

Filament - The plastic material used as “ink” in FDM printing. Comes on spools in 1.75 mm diameter rolls.

Functional requirement - A testable statement describing what a design must do. Example: “The marker must support the weight of a desk rolling over it.”

G-code - The machine instruction language that tells the 3D printer exactly where to move and at what temperature. Generated by the slicer.

Hot end / nozzle - The heated component that melts and extrudes the filament. Typically heated to 200-250C depending on material.

Infill - The internal structure of a printed object. Usually expressed as a percentage (e.g., 15% infill = 15% solid inside). Common patterns include grid, gyroid, and honeycomb.

intersection() - OpenSCAD command that keeps only the region where two shapes overlap.

Layer height - The thickness of each printed layer. Typical values: 0.1 mm (fine detail) to 0.3 mm (fast/draft). Affects surface quality and print time.

Linear extrusion - In OpenSCAD, linear_extrude() turns a 2D shape into a 3D object by extending it upward.

Module - In OpenSCAD, a reusable block of code that can be called with different parameters to create variations.

Overhang - A portion of a model that extends beyond the layer below it. Overhangs above ~45 require support structures.

Parameter / parametric design - A design approach where dimensions are stored as variables, so changing one number updates the whole model.

PETG (Polyethylene Terephthalate Glycol-modified) - A durable, moderately flexible filament. More impact-resistant and heat-resistant than PLA; easier to print than ABS.

PLA (Polylactic Acid) - The most common beginner filament. Bio-derived, easy to print, low-emission. Brittle under impact and heat-sensitive.

Primitive - A basic 3D shape in OpenSCAD: cube, sphere, cylinder. Complex objects are built by combining primitives.

Render - In OpenSCAD, pressing F6 generates a full, final 3D model from your code. Slower than Preview (F5) but required for export.

Retraction - A slicer setting that briefly pulls the filament backward when the nozzle moves without printing, to prevent strings of plastic between features.

rotate() - OpenSCAD command that rotates a shape around the X, Y, or Z axis.

Slicer - Software (e.g., PrusaSlicer) that converts a 3D model (.stl) into G-code instructions for a specific printer.

Stakeholder - A person who has a meaningful interest in whether a design succeeds - typically the person you are designing for.

STL file (.stl) - The standard file format for 3D models used in most slicers. Describes the geometry of a shape as a mesh of triangles.

Support structures - Temporary scaffolding material generated by the slicer to support overhangs during printing. Removed after the print is complete.

Tolerance - The acceptable amount of dimensional variation in a printed part. FDM printers typically have a tolerance of +/-0.15-0.30 mm.

TPU (Thermoplastic Polyurethane) - A flexible filament used for rubber-like parts: phone cases, wearables, shock absorbers. Harder to print than PLA.

translate() - OpenSCAD command that moves a shape along the X, Y, and/or Z axis.

union() - OpenSCAD command that combines two or more shapes into a single solid.

Warp / warping - A print defect where the corners or edges of a print lift off the build plate due to uneven cooling.

$fn - OpenSCAD special variable that sets the number of faces on rounded shapes (spheres, cylinders). Higher = smoother. Typical values: 20-100.

Screen Reader Coding Tips - NVDA & JAWS

A consolidated reference for using NVDA or JAWS while writing OpenSCAD code in VSCode or Notepad++. Tips that were previously scattered across lesson files are collected here.

General Principles for Coding with a Screen Reader

• Turn punctuation up. All OpenSCAD syntax - semicolons, brackets, parentheses, commas - is meaningful. If your screen reader skips punctuation, you will miss syntax errors. Set punctuation to Most or All before coding.
• Navigate by line. Arrow up and down to move through code one line at a time. Use Ctrl + Left/Right to move word by word within a line.
• Use go-to-line. Both VSCode and Notepad++ let you jump to a specific line number with Ctrl + G. OpenSCAD errors always give a line number - use this to find them fast.
• Spell when uncertain. If you are not sure what a character is, spell the line character by character using your screen reader’s spell command.
• Comment as you go. Adding a short comment after a block of code lets you navigate by searching for recognizable words with Ctrl + F.

NVDA Quick Reference

Setting Punctuation Level

NVDA + P - cycles through: None -> Some -> Most -> All

For code: set to Most or All.

You can also set a permanent default: NVDA + N -> Preferences -> Settings -> Speech -> Symbol level

Essential Reading Commands

Navigation in VSCode with NVDA

If NVDA Stops Reading the Editor

1. Click in the editor area once with the mouse (or press Escape and then click)
2. Press NVDA + Space to toggle between Browse and Application mode - for code editors, you want Application mode

JAWS Quick Reference

Setting Punctuation Level

JAWS Key + Shift + 2 - cycles through punctuation levels

For code: set to All.

Essential Reading Commands

Adjusting Speech Rate

Navigation in VSCode with JAWS

If JAWS Stops Reading the Editor

1. Press JAWS Key + Z to toggle Virtual/Browse mode off - for VSCode you want Virtual mode off
2. Focus the menu bar with Alt, then press Escape to return to the editor
3. If still not working, press Alt + F4 to close VSCode and reopen it

Window Focus

When you launch OpenSCAD from VSCode (via the task runner), focus stays in VSCode. To switch to OpenSCAD to read the console or error messages:

• Alt + Tab to cycle through open windows
• JAWS will announce the application name as you cycle

OpenSCAD-Specific Tips

Reading Errors

When OpenSCAD can’t render your code, it outputs an error. The error message always includes:

• Line number - use Ctrl + G in VSCode to jump there
• Error type - usually a missing semicolon, a typo in a command name, or mismatched brackets

Common errors and what they sound like:

Bracket Matching

All OpenSCAD shapes and operations use brackets and braces:

• Parentheses () - hold parameters: cube([10, 10, 10])
• Square brackets [] - hold vectors (lists of numbers): [10, 10, 10]
• Curly braces {} - hold groups of shapes for boolean operations

Every opening bracket must have a closing bracket. If you are missing one, OpenSCAD will report an error somewhere near (but not always exactly at) the problem.

VSCode can help: when your cursor is on a bracket, VSCode highlights the matching bracket. With NVDA, you can navigate to the matching bracket with Ctrl + Shift + \.

Commenting Out Code

To test part of your code without deleting it, comment it out:

• Single line: position cursor at start of line, type //
• Multiple lines: select the lines, press Ctrl + / in VSCode (adds // to each selected line)
• Block comment: type /* before and */ after the block

To uncomment: select the commented lines, press Ctrl + / again.

Navigating Large Files

Use Ctrl + F (Find) to locate sections of your code:

• Search for your module names to jump to them: e.g., module round_bead
• Search for comments you wrote: e.g., // Step 2
• Search for line numbers in error messages

Caliper and OpenSCAD Workflow Tips

When measuring an object and entering it into OpenSCAD, say the measurement aloud before typing it to reduce transcription errors. Then read the number back after typing it to confirm.

Recommended sequence:

1. Measure -> say “seventy point three millimeters”
2. Type 70.3 in OpenSCAD
3. Read back: “seven zero point three” to confirm

mdBook Navigation (Web Version of This Curriculum)

If you are reading this curriculum through the web version (mdBook), here are tips for navigating with a screen reader:

NVDA + Browser

• H to jump between headings (chapter navigation)
• Ctrl + F to search within the current page
• The sidebar table of contents is a navigation landmark - use NVDA + F7 to list landmarks, or press D to jump between landmark regions
• Previous/Next chapter links are at the bottom of each page

JAWS + Browser

• H to move between headings
• Ctrl + F (browser Find) to search
• JAWS Key + F6 to list headings
• R to jump to regions/landmarks
• Use the search box in the mdBook header to search across all chapters

Keyboard Navigation (No Screen Reader)

• Left Arrow / Right Arrow - previous/next chapter
• S - focus the search box
• Escape - close search results
• T - toggle the table of contents sidebar

References

NV Access. (2024). NVDA user guide. https://www.nvaccess.org/files/nvda/documentation/userGuide.html

Freedom Scientific. (2024). JAWS for Windows help. https://support.freedomscientific.com/Content/Documents/Manuals/JAWS/JAWS-Screen-Reader-Help.pdf

Microsoft. (2024). Visual Studio Code accessibility. https://code.visualstudio.com/docs/editor/accessibility

More on mdBook navigation

• mdBook (general / keyboard navigation): https://rust-lang.github.io/mdBook/ - includes documentation and basic navigation/usage for the mdBook web UI.
• Curriculum mdBook navigation (with accessibility tips): mdBook Navigation Guide - local guide in this curriculum with notes for using mdBook with and without screen readers.

Your First Print - Guided Extension

Estimated time: 2-4 hours (including setup and print monitoring)

Learning Objectives

• Select a simple ready-made model and evaluate its printability for a classroom printer
• Configure slicer settings for a short-duration print and prepare the printer safely
• Document print parameters and reflect on the physical outcome

Materials

• Computer with slicer and access to the online repository
• Prusa Mini+ or classroom-approved printer, filament spool

Step-by-step Tasks

1. Choose a simple model (<2 hours print) from Thingiverse or Printables and save the STL.
2. Inspect the model: note overhangs, thin features, and dimensions; write two short reasons why this model is appropriate for a first print.
3. Load the model in your slicer, select the classroom profile, and adjust settings only if necessary (layer height, infill, supports). Record the final print time and filament estimate.
4. Perform safety checks, start the print, and monitor the first 10 minutes for adhesion and extrusion problems.
5. After cooling, measure three critical dimensions and compare to the models stated dimensions; record deviations.

Probing Questions

• Why did you select this model? What risks did you anticipate and how did you mitigate them?
• Which slicer setting most affects print time for this model and why?
• If a thin feature failed, what minimal change would you make to ensure success next time?

Quiz - Your First Print (10 questions)

1. What is the first-check you do after loading filament? (short answer)
2. Name two slicer settings that affect strength. (short answer)
3. Why monitor the first layers of a print? (one sentence)
4. How do you document filament used for reproducibility? (short answer)
5. What is one sign of poor bed adhesion? (one sentence)
6. True/False: Selecting a model with support requirements is not recommended for your first print. (Answer: True)
7. Short answer: Describe two characteristics of a “printability-friendly” model that would be good for a beginner’s first print.
8. Practical scenario: Your first print is showing stringing (thin lines between parts). What are two possible causes and how would you troubleshoot?
9. Multiple choice: When measuring a printed dimension, where should you measure multiple times (three different spots) to account for print variation? (A) Never, measure once (B) Only if you suspect error (C) Always measure at least three locations - Answer: C
10. Reflection: Explain why carefully selecting your first print model (simple, robust, known to work on your printer) is better than immediately attempting a complex design. What will you learn from success that prepares you for harder projects?

Extension Problems (10)

1. Re-slice the model with a finer layer height and compare surface finish and print time; document differences.
2. Modify the model in OpenSCAD to thicken a failing feature and reprint a small test piece.
3. Create a short checklist script (or text checklist) that verifies spool metadata and bed temperature before printing.
4. Produce a one-page reflection that includes three lessons learned and one parameter you will change next time.
5. Share your measurements and photos in the class folder and give feedback on two peers’ prints.
6. Conduct a post-print analysis: compare actual measurements to STL specifications; identify and document any deviations.
7. Print the same model in two different materials or with two different slicer profiles; compare durability, appearance, and accuracy.
8. Create a detailed documentation package: CAD file, slicer settings, print log, measurements, and lessons learned.
9. Design a quality assurance test: define pass/fail criteria and systematically verify your print meets all requirements.
10. Write a “first print troubleshooting guide” based on your experience: common issues you encountered and how you solved them.

Deliverables

• Short report: model chosen, key slicer settings, measured deviations, and answers to probing questions.
• Photos of the final print and the measured values table.

Your First Print - Student Documentation Template (Extension Project)

• Author:
• Date:
• Description: Select a simple 3D model, configure slicer settings, and complete your first independent print job.

Ideas and Concept

Model Selection

• Model name and source (Thingiverse, Printables, etc.):
• Link or file reference:
• Why did you choose this model?

Printability Assessment

• Estimated print time (from slicer):
• Estimated filament:
• Expected challenges (overhangs, thin features, supports needed):
• Why is this model appropriate for a first print?

Measurements and Printer Configuration

Printer Setup Log

Safety Checks (Completed)

• Bed clean and level
• Bed adhesive/prep applied (if needed)
• Filament loaded correctly
• Nozzle at correct height
• Print area clear of obstructions
• Buildplate secured

Object Notes

Print Monitoring Notes

• What did you observe in the first 10 minutes?
• Any adhesion issues?
• Any extrusion problems?
• Print completed successfully: Yes / No

Printed Part Measurements (After Cooling)

Use and Assembly Notes

• How does the print feel and look compared to the model?
• Did any features fail or print poorly?
• If there were issues, what do you suspect caused them?

Reflections

What Went Well

• Which aspect of the print was most successful?
• Did anything surprise you positively?

What Didn’t Go Well

• Were there any defects or failed features?
• What challenges did you encounter?

Learning and Next Steps

• What did you learn from this first independent print?
• What would you do differently next time?
• If you printed this again, what settings would you change?

Post-Print Analysis

• Compare this print to others you’ve seen in the classroom
• What variables (temperature, layer height, infill) do you think most affected the outcome?
• How would you test that hypothesis?

Attachments

• Exported .stl model file (or link to source)
• Slicer settings (screenshot or export)
• Photo of final print (multiple angles if possible)
• Safety checklist (signed/dated)
• Print log with timestamps (if available from printer)

Teacher Feedback

Feedback:

Resubmission (if applicable)

What Was Changed

(One-paragraph explanation of changes made and why)

Revised Score

Your First Print - Teacher Template (Extension Project)

Briefing

A foundational extension project where students select a ready-made 3D model from online repositories, configure slicer settings, and complete their first independent print job. This project builds confidence and establishes safe printing practices.

Key Learning: Printer safety; slicer configuration; print monitoring; dimensional verification.

Real-world Connection: Production environments rely on safe print setup and quality verification. This project establishes habits that transfer to any 3D printing context.

Constraints

• Model must be 2 hours print time
• No or minimal support requirements recommended
• Student must document printer configuration and safety checks
• Student must compare printed dimensions to model specifications

Functional Requirements

• Model selected and deemed appropriate for beginner
• Printer configured safely with classroom profile
• Print completes successfully with good adhesion
• Printed part is measured and deviations documented

Deliverables

• Completed documentation template with:
  • Model selection rationale and printability assessment
  • Printer setup log (materials, temperature, settings)
  • Print monitoring observations (first 10 minutes, monitoring during print)
  • Dimensional measurements and deviation analysis
  • Reflection on first print experience
  • Post-print analysis and troubleshooting notes
• Photograph of final print
• Slicer settings (screenshot or text export)

Rubric

All projects are scored on a 0-9 scale across three equally weighted categories (3 points each):

Category 1: Problem & Solution (0-3 points)

Category 2: Design & Code Quality (0-3 points)

Category 3: Documentation (0-3 points)

Score Interpretation

Resubmission Policy

Students may resubmit to improve their score. Resubmissions must include:

1. A one-paragraph explanation of what was changed and why

The resubmission score replaces the original.

Assessment Notes

• Strong submissions show careful model selection reasoning, thorough printer documentation, and specific observations about print behavior
• Watch for: Poor printer documentation, dismissive attitude toward safety checks, or generic reflections
• Reinforce: Safety first; documentation enables learning and troubleshooting
• Next Step: Extension problem suggestions include print quality analysis or variant material testing

Basic Project Scaffold

Lesson 2: Geometric Primitives and Constructive Solid Geometry

Estimated time: 60 minutes

Learning Objectives

• Use OpenSCAD primitives (cube(), sphere(), cylinder()) and transforms (translate(), rotate(), scale())¹
• Apply CSG operators (union, difference, intersection) safely and diagnose common numerical issues²
• Use quick diagnostic renders and validate geometry in a slicer³

Materials

• 3dMake project scaffold with src/main.scad
• Example primitive snippets (provided in assets)
• Reference: openscad-cheat-sheet.md for syntax quick-reference

1. Open src/main.scad; identify and run simple examples using cube(), sphere(), and cylinder()¹.

   Example primitives:

   // Primitive shapes - uncomment one to try
   
   // Cube (x, y, z dimensions)
   cube([20, 20, 20]);
   
   // Sphere (radius, resolution)
   // sphere(r=10, $fn=32);
   
   // Cylinder (radius, height, resolution)
   // cylinder(r=10, h=20, $fn=32);
   

2. Create three short examples demonstrating union(), difference(), and intersection() and render with reduced $fn. Review CSG best practices².

   Example CSG operations:

   // UNION - Combine multiple shapes
   union(){
     cube([20, 20, 20]);
     translate([15, 0, 0]) sphere(r=10, $fn=32);
   }
   
   // DIFFERENCE - Subtract shapes
   // difference(){
   //   cube([20, 20, 20]);
   //   translate([10, 10, 10]) sphere(r=8, $fn=32);
   // }
   
   // INTERSECTION - Keep only overlapping volumes
   // intersection(){
   //   cube([20, 20, 20]);
   //   sphere(r=12, $fn=32);
   // }
   

3. Reproduce a failing difference() case and apply the 0.001 offset strategy to the subtractor; re-render and confirm fix. This technique addresses common manifold issues⁴.

   Fix technique:

   // Problem: Coincident faces cause non-manifold issues
   difference(){
     cube([20, 20, 20], center=true);
     // Use translate with small offset (0.001) to prevent coincident faces
     translate([0, 0, 0.001]) sphere(r=10, $fn=32);
   }
   

4. Build an STL with 3dm build and open it in your slicer to check for thin walls or islands³.

5. Document any fixes in the project README and commit the working main.scad and STL.

Debugging, Resolution, and Common Issues

As your OpenSCAD models become more complex, you’ll encounter rendering errors, non-manifold geometry, or slow previews. Learning to debug efficiently is essential for productive design work.

Understanding OpenSCAD Console Errors

When you press F5 to preview or F6 to render your model, OpenSCAD displays warnings and errors in the console at the bottom of the editor. Here’s what to look for:

• Error Line Numbers: The console message tells you the exact line where the problem was detected. Look for missing semicolons, unmatched braces, or undefined variables
• Syntax Errors: These prevent the model from rendering at all (common causes: missing ;, unclosed { or [, typos in function names)
• Warnings (Non-Manifold Geometry): Your geometry is technically valid but has internal inconsistencies that may prevent printing

Example Console Output:

ERROR: Unexpected token 'sphere' at line 15, column 5
  Expected one of: } ) ]

This tells you that line 15 has a syntax issue-likely a missing closing bracket on the previous line.

The 0.001 Offset Strategy (Revisited)

One of the most common issues with CSG operations is coincident faces-when two shapes touch exactly at their boundaries. This creates a non-manifold geometry that slicer tools flag as unprintable.

The Fix: Add a tiny offset (0.001 mm or smaller) to move one surface slightly:

// BEFORE (problematic):
difference(){
  cube([20, 20, 20], center=true);
  sphere(r=10, $fn=32);
}

// AFTER (fixed):
difference(){
  cube([20, 20, 20], center=true);
  translate([0, 0, 0.001]) sphere(r=10, $fn=32);  // Tiny offset prevents coincident faces
}

This 0.001 mm offset is invisible to the human eye but fixes the non-manifold warning and makes the model printable.

Using $fn to Balance Speed and Quality

The $fn parameter controls the resolution of curved surfaces (spheres, cylinders, etc.). It represents the number of polygonal faces used to approximate the curve:

• $fn = 12 - Very fast preview, coarse geometry (useful for quick testing)
• $fn = 32 - Good balance for most designs (default for many situations)
• $fn = 100+ - High quality but slow to render; use only for final export

Debugging Workflow:

1. During design iteration: Use $fn = 12 or $fn = 20 for quick feedback
2. Before export: Increase to $fn = 32 or higher for final quality
3. For complex assemblies: Keep $fn low during iteration to save preview time

Incremental Rendering: The F5/F6 Workflow

• F5 (Preview): Quick render to check overall geometry and catch layout errors
• F6 (Full Render): Slower but more accurate; use before export
• Strategy: Press F5 frequently while editing to get immediate feedback, then F6 once before exporting

This workflow catches errors early and saves you from spending 10 minutes rendering only to discover a syntax error.

Diagnosing Non-Manifold Geometry

A model might render in OpenSCAD but still be unprintable. The slicer will report errors like “non-manifold edges” or “holes in surface.” Common causes:

1. Coincident Faces -> Use small offsets (0.001 mm)
2. Zero-Thickness Walls -> Ensure all walls are at least 0.8-1.0 mm
3. Gaps Between Shapes -> Check that boolean operations have no small gaps; use minkowski() for rounded edges if needed
4. Inside-Out Geometry -> A shape might be flipped; use scale([1, 1, -1]) to flip normals if needed

When your slicer reports non-manifold issues, use the slicer’s visualization to locate the problem, then reference the line numbers in your OpenSCAD code and test fixes incrementally using F5/F6.

Checkpoints

• After task 3 the problematic boolean should render without non-manifold warnings⁴.
• After this section, you should be able to interpret at least three common console error messages and apply appropriate fixes.

Quiz - Lesson 3dMake.2 (10 questions)

1. Name three primitive functions in OpenSCAD¹.
2. What does difference() accomplish²?
3. Why might two coincident faces cause a render failure⁴?
4. What is the 0.001 rule and why is it useful⁴?
5. How does lowering $fn help during debugging²?
6. True or False: union() combines shapes while intersection() keeps only overlapping volumes.
7. Describe what Constructive Solid Geometry (CSG) is and give an example of where it’s useful.
8. Explain how scale(), translate(), and rotate() transforms change a primitive’s behavior.
9. How would you diagnose and fix a non-manifold issue in your model?
10. When validating geometry in a slicer, what specific issues should you look for?

Lesson 2 Assets & Projects

Your Lesson 2 assets are located in the centralized assets folder:

• Lesson 2 Asset Overview (assets/Lessons_3dMake_2/README.md) - Folder contents and learning resources
• Your Second Print Project (assets/Lessons_3dMake_2/Your_Second_Print/) - Adapt models to real-world needs
• Bonus Print Project (assets/Lessons_3dMake_2/Bonus_Print/) - Practice resizing and parametric variation

These projects reinforce the boolean operations and CSG concepts you learned in this lesson.

Extension Problems (10)

1. Create a small assembly using union() of three primitives and export the STL. Reference best practices from OpenSCAD documentation¹.
2. Intentionally create a failing boolean and fix it using offsets; explain your approach. Document the manifold issues encountered⁴.
3. Write a short test script that generates three variants with varying $fn values and compare render times. Consider using 3dMake workflows³.
4. Use 3dm info (if available) to generate a report on your model and document any recommendations³.
5. Explore using a library module (e.g., a fillet helper) to fix a sharp corner and note the difference in final STL².
6. Build a geometry validation toolkit: test all basic transformations (union, difference, intersection) with edge cases and document failure modes.
7. Create a parametric assembly generator that produces 5+ configurations and validates each for printability.
8. Develop a boolean operation troubleshooting guide with visual examples and step-by-step fixes.
9. Design a library module system for common geometric operations (fillets, chamfers, arrays); test reusability across projects.
10. Write an accessibility guide for boolean operations: describe methods for validating geometry non-visually using model properties and slicer feedback.

Supplemental Resources

For additional examples and practice with 3D primitives and boolean operations, explore these resources:

• Programming with OpenSCAD EPUB Textbook - Comprehensive guide to primitives, boolean operations, and CSG fundamentals
• CodeSolutions: 3D Primitives - Working examples of cube, sphere, cylinder, and other 3D shapes
• CodeSolutions: Combining Shapes - Examples of union, difference, intersection, and hull operations
• Practice Worksheets: 3D Shapes - Visualization and decomposition exercises

1. OpenSCAD Manual - Primitives and Transforms - https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Using_the_2D_Subsystem ↩ ↩2 ↩3 ↩4

2. Gonzalez Avila, J. F., Pietrzak, T., & Casiez, G. (2024). Understanding the challenges of OpenSCAD users for 3D printing. Proceedings of the ACM Symposium on User Interface Software and Technology. ↩ ↩2 ↩3 ↩4 ↩5

3. Slicer Validation - PrusaSlicer Documentation - https://docs.prusa3d.com/en/guide/39012-validation-tools/ ↩ ↩2 ↩3 ↩4

4. Google. (2025). Vertex AI Gemini 3 Pro Preview: Getting started with generative AI. https://docs.cloud.google.com/vertex-ai/generative-ai/docs/start/get-started-with-gemini-3 ↩ ↩2 ↩3 ↩4 ↩5

OpenSCAD Quick Reference - Cheat Sheet

Keep this handy during all OpenSCAD work. For full documentation: https://openscad.org/documentation.html

Basic Shapes (Primitives)

cube([length, width, height]);          // rectangular box
cube([l, w, h], center = true);        // centered at origin

sphere(r = radius);                     // sphere by radius
sphere(d = diameter);                   // sphere by diameter

cylinder(h = height, r = radius);       // cylinder
cylinder(h = height, d = diameter);     // cylinder by diameter
cylinder(h = height, r1 = 5, r2 = 2);  // cone (different top/bottom radii)

$fn = 50;  // sets smoothness for spheres/cylinders (higher = smoother, slower)

Transformations

translate([x, y, z]) shape;             // move
rotate([x_deg, y_deg, z_deg]) shape;    // rotate
scale([x, y, z]) shape;                 // scale (1.5 = 150%)
mirror([1, 0, 0]) shape;               // mirror across YZ plane (use [0,1,0] for XZ, [0,0,1] for XY)

Boolean Operations

union() { shape1; shape2; }            // combine shapes
difference() { base; subtract; }       // remove one shape from another
intersection() { shape1; shape2; }     // keep only overlapping region

Tip for difference(): Always make the subtracting shape 1 mm taller on both ends than the base shape to avoid zero-thickness artifacts.

// Example - box with a hole:
difference() {
    cube([30, 30, 10]);
    translate([15, 15, -1]) cylinder(h = 12, r = 5);  // extends -1 to +11
}

Variables

length = 70;      // define a variable
width = 16;
height = 5;

cube([length, width, height]);    // use the variables
cube([length * 2, width, height]); // math works too

Modules (Reusable Functions)

// Define a module:
module my_box(l = 20, w = 15, h = 10) {
    cube([l, w, h]);
}

// Call the module:
my_box();               // uses all defaults
my_box(30, 20, 8);     // positional arguments
my_box(l = 50);         // named argument; others use defaults

Loops

// Repeat a shape N times:
for (i = [0 : 4]) {         // i goes 0, 1, 2, 3, 4
    translate([i * 20, 0, 0]) cube([15, 15, 5]);
}

// Step size:
for (i = [0 : 5 : 20]) {   // i goes 0, 5, 10, 15, 20
    translate([i, 0, 0]) sphere(r = 3);
}

2D Shapes (for extrusion)

circle(r = 10);            // 2D circle
square([w, h]);            // 2D rectangle
polygon([[0,0],[10,0],[5,10]]);  // arbitrary 2D shape

// Extrude a 2D shape into 3D:
linear_extrude(height = 5) circle(r = 10);  // makes a cylinder
rotate_extrude() translate([15, 0]) circle(r = 3);  // makes a torus

Useful Functions

len([a, b, c])         // returns 3 (length of a vector)
sqrt(25)               // returns 5
pow(2, 8)              // returns 256 (2^8)
abs(-5)                // returns 5
min(3, 5, 1)           // returns 1
max(3, 5, 1)           // returns 5

Comments

// Single-line comment

/*
  Multi-line
  comment
*/

Keyboard Shortcuts