Machine Kinematics
solved, then drawn
Concept

Flat state — where it appears

The unfolded configuration of a crease pattern, where every crease lies in the plane and every branch of every folding meets. The constraint matrix loses one rank there per interior vertex, so its nullity counts the tangent directions of all the branches at once and reports the same number for a pattern that folds and one that cannot.

Named by 3 essays across 2 fields — each of them below, with the objects they name alongside it.

Two branches, meeting where the sheet is flat. The same vertex's two folding modes, plotted as one crease's fold angle against another's. Both curves pass through the origin, which is the flat sheet, and they cross there and nowhere else. That crossing is what a rank cannot see: at the origin the tangent directions of both branches are available to the constraint matrix at once, so the nullity there counts them all and the mechanism has only one of them once it has left. Every branch argument this site has made — a four-bar's assembly configurations, an arm's eight postures, the components a solve's paths turned out to run between — is this picture with different axes.

Where the branches meet

A flat sheet is the one configuration every folding of a pattern passes through, and it is the one configuration where the rank is wrong about all of them. Three of a three-by-three Miura sheet's four apparent freedoms are not motions — and a grid that folds to no angle at all reports exactly the same four.

networks · Network Six assemblies, one routine, three disagreements and one accident. Every row is the same three steps: write down the constraint Jacobian, take its rank, and subtract it from the number of unknowns. The representations differ — bars between points, bodies joined by pins, panels joined by creases, one cell of a pattern that repeats for ever — and the routine does not. The counted column is the arithmetic on the numbers of bodies and joints; the measured column is the nullity of the matrix. They agree on the lazy tong and on the kagome cell and disagree on the other four, most sharply on the deployable ring, which the count declares immobile and which is sold as a mechanism that opens. The right-hand column is the reason: constraints that repeat what another constraint has already said, which the count has no way of seeing and the rank cannot help seeing. The fourth row is worth reading twice: the count says nothing can move and nothing can, so the two agree — and they agree for the wrong reason, because that pattern's flat state shows four freedoms and not one of them is a motion.

Six things a network is not

A count that is right about a difference and read as an answer, a nullity taken for a mobility, a flat state that cannot tell a mechanism from a structure, a scissor ring that closes nowhere, a vertex that folds while its sheet does not, and a null space computed with an instrument whose floor is above the answer. Six claims, each with the number that kills it.

wrong · Misconception A 4-stage scissor, open and as flat as it goes. On paper a scissor stack's height is n·L·sin φ and goes to nothing as the bars lie down. The bars are made of something: the two colours are the two planes the stack needs — two, at any number of stages, which is why a scissor folds at all — and the bars that share a plane are the ones two stages apart. They meet at φ = 0.0951, leaving each stage 0.0949 high, which is exactly the two bosses that touch: 2 × 0.0473. The stowed height of the whole stack is 0.380 rather than zero, and it grows with the stage count in the way a stowed lift's does.

A stack that has to fit

A scissor stack's height is n·L·sin φ and goes to nothing as the bars lie down — on paper. The bars are made of something, and what stops the fold is two bosses meeting: every stage keeps 0.0949 whatever the stack does, which is exactly twice the boss radius.

networks · Network

Named alongside it

The objects these essays reach for when they reach for this one.

DeployableMobilityNetworkNull spaceRankAssembly branchBifurcationBossConfiguration spaceConflict graphDesign ruleGrübler's criterion

All concepts