Miura-Ori CubeSat Solar Array Reliability Testing

ISEF Category: Engineering Technology: Statics and Dynamics

Subcategory: Other  ·  Difficulty: Intermediate  ·  Setup: School Lab  ·  Time: 1 to 2 Months

The Hook

A tiny satellite can fail because one panel sticks. In space, a jammed solar array can mean weak power and a dead mission. That makes foldable structures a big deal, not a neat art project. You can study that problem with a scaled Miura-ori deployment system.

What Is It?

Miura-ori is an origami fold pattern that lets a flat sheet open and close in a very controlled way. Think of it like a cardboard fan with a built-in path. Instead of many loose hinges, the folds guide the motion. That can make a structure deploy smoothly and pack into a small space.

For CubeSats, which are small satellites, that matters a lot. A solar array has to fit inside a tight launch package, then open reliably in orbit. Your model can test whether a folded array returns to the same shape each time, whether it jams, and how stiff it feels once deployed. Stiffness means how much it resists bending after it opens.

Why This Is a Good Topic

This is a strong science fair topic because you can measure real engineering tradeoffs, not just build a cool model. You can compare fold geometry, material choice, and motor speed, then track how those choices affect repeatability, jam rate, and deployed stiffness. The project connects to space hardware, robotics, and structural design. You can also do real data analysis with cycle testing, failure rates, and graphs that show trends over many trials.

Research Questions

• How does fold angle affect deployment repeatability over many cycles?
• What is the effect of material choice, such as paper versus Mylar, on jam rate during deployment?
• Does motor speed change the number of incomplete deployments in a Miura-ori array?
• To what extent does repeated cycling reduce deployed stiffness in a folded panel model?
• Which fold pattern geometry gives the most consistent final deployed shape after 100 or more cycles?
• How does panel size affect the force needed to fully deploy a scaled CubeSat array?

Basic Materials

• Cardstock or thin paper.
• Mylar sheet or similar flexible plastic film.
• Ruler or calipers.
• Fine-tip marker.
• Small DC motor or hobby servo.
• Motor controller or microcontroller board.
• Battery pack or bench power supply.
• Basic IMU sensor module.
• Hot glue or tape.
• Binder clips or small clamps.
• Smartphone camera or phone tripod.
• Digital kitchen scale or spring scale.

Advanced Materials

• Laser-cut cardstock, polyimide film, or thin composite sheet.
• Servo with position feedback.
• 6-axis IMU with data logging.
• Load cell with amplifier.
• Force gauge or digital push-pull gauge.
• High-speed camera or smartphone high-frame-rate mode.
• Motion capture markers or tracking dots.
• Arduino or similar microcontroller.
• Data acquisition interface.
• Finite element or structural analysis tools.
• Precision hinge fixtures or 3D-printed mounts.

Software & Tools

• Python: Cleans sensor logs, calculates cycle-to-cycle variation, and plots deployment trends.
• ImageJ: Measures deployed shape, fold alignment, and panel symmetry from photos.
• Tracker: Tracks motion from video when you want a simple way to measure deployment timing and path.
• Excel or Google Sheets: Organizes trials, computes averages, and compares jam rates across conditions.
• RStudio: Runs statistics and makes graphs for repeated-measures data.

Experiment Steps

1. Define the one design variable you will change first, such as fold angle, material, or panel size.
2. Build a repeatable test rig that opens the panel the same way each time and logs motion data.
3. Set up a measurement plan for final shape, jam events, and stiffness after deployment.
4. Decide how you will detect and count partial deployments, misalignments, and recovery after a jam.
5. Create a cycle-testing schedule that compares early performance with performance after many repeats.
6. Plan your analysis so you can compare mean behavior, variation, and failure rate across designs.

Common Pitfalls

• Testing only one panel and calling it a pattern study, which makes the data too weak to compare designs.
• Changing lighting or camera position between runs, which makes image-based shape measurements drift.
• Ignoring sensor drift in the IMU, which can make repeatability look worse or better than it really is.
• Using a motor setup that adds extra slack or torque, which turns the actuator into the main source of failure.
• Counting a slow deployment as a success even when the array does not fully lock into the same final shape.

What Makes This Competitive

A class-level project shows that a fold works. A stronger project explains why it works better than another design. You can raise the level by testing more than one geometry, tracking failure modes across many cycles, and pairing video data with force or stiffness data. A solid statistical comparison, plus a clear design rule you can defend, makes the project much stronger.

Project Variations

• Compare Miura-ori panels made from paper, Mylar, and thin plastic to see how material stiffness changes deployment reliability.
• Test different actuator speeds to see how motion control changes jam rate and final alignment.
• Add a structural load test after deployment to compare how stiffness changes with cycle count.

Learn More

• NASA CubeSat 101 Materials: Search NASA for CubeSat design resources and deployable systems notes.
• MIT OpenCourseWare: Search for mechanics of materials, structures, and robotics courses to build your analysis background.
• NIH PubMed: Search review articles on origami engineering and deployable structures for background reading.
• NASA Technical Reports Server: Search for papers on deployable space structures, solar arrays, and origami-inspired mechanisms.
• Proceedings of the Royal Society A: Search for peer-reviewed papers on origami mechanics and folding structures.