Skip to main content

Lab · Enclosure · Demo

Demo · noindex

Dayton Audio RS180-8

A single driver, transcribed by hand from the manufacturer's own datasheet, wired straight into the enclosure designer. This is a demonstration of what a licensed datasheet library produces — not a published catalogue.

Where these numbers came from

Manufacturer
Dayton Audio
Document
RS180-8 7" Reference Woofer 8 Ohm — specifications (2-page PDF)
Fetch result
HTTP 200 · application/pdf
Accessed
2026-08-05
Transcribed from
page 1, the PARAMETERS block

Hand-transcribed, and why that matters

Every value in the table below was read off the PDF linked above and typed in by a human. Nothing here was recalled from memory, scraped from a reseller listing, or inferred from a similar driver. The unit and the number of significant figures are the datasheet's, not ours.

The full catalogue stays blocked, deliberately

A driver-by-driver enclosure catalogue is the largest page set this studio could generate and it is the one we do not publish. There is no authoritative machine-readable Thiele-Small dataset, and a thousand pages of alignments computed over remembered parameters would look exactly like a thousand pages of correct ones. The blocker is the dataset, not the arithmetic — which is why one page from one verified datasheet is honest and a catalogue assembled the same way today would not be.

This page is noindex and is linked only from the designer, so it cannot be mistaken for that catalogue.

RS180-8 parameters, as printed

18 rows, each carrying the page of the datasheet it came from. 8 of them map onto a control in the enclosure designer and carry that control's query key in the last column — count them, the number is the same. The first link at the top of this page sends the 7 Thiele-Small rows among those; the second adds the eighth,pwr from the RMS power row, because rated power is a drive condition rather than a driver parameter. Nothing else is sent, and nothing is invented to fill a gap.

SymbolQuantityValueUnitDatasheetSent as
ImpedanceNominal impedance8ohmsp.1not sent
ReDC voice-coil resistance6.4ohmsp.1?re=
LeVoice-coil inductance at 1 kHz0.73mHp.1not sent
FsFree-air resonance35.7Hzp.1?fs=
QmsMechanical Q1.22p.1?qms=
QesElectrical Q0.42p.1not sent
QtsTotal Q0.31p.1?qts=
MmsMoving mass17.9gp.1not sent
CmsSuspension compliance1.12mm/Np.1not sent
SdEffective piston area124.7cm²p.1?sd=
VdPeak displacement volume74.8cm³p.1not sent
BLMotor force factor7.82Tmp.1not sent
VasEquivalent compliance volume24.4litersp.1?vas=
XmaxLinear excursion6.0mmp.1?xmax=
VC diameterVoice-coil diameter38mmp.1not sent
SPLSensitivity at 2.83 V / 1 m87.1dBp.1not sent
PowerRMS power handling60wattsp.1?pwr=
RangeUsable frequency range39 - 3,600Hzp.1not sent

Handing the set to the solver

This page computes nothing. It carries the transcribed parameters into the enclosure designer, which owns the sealed and vented solvers, and solves them there. One implementation of a measurement, in one place — the alternative is two copies that drift, which is how a template on this site once printed a divide-by-zero DC gain on 29 pages while every unit test stayed green.

Transcribed T/S set

/lab/loudspeaker-enclosure-designer?re=6.4&fs=35.7&qms=1.22&qts=0.31&sd=124.7&vas=24.4&xmax=6.0

Open →

…plus the rated power

/lab/loudspeaker-enclosure-designer?re=6.4&fs=35.7&qms=1.22&qts=0.31&sd=124.7&vas=24.4&xmax=6.0&pwr=60

Open →

Neither link sets a box volume or a tuning frequency. Those are not on the datasheet page this was transcribed from, so they are not ours to assert — the designer starts from its own defaults and you dial them in.

One rounding to know about, measured on the live designer rather than read off its markup: it carries Qms at one decimal, so the datasheet's 1.22 is solved as 1.2. Open the first link above, then open it again with qms=1.2 substituted: every readout is identical. Substitute qms=1.3 instead and the efficiency and sensitivity readouts both move — so those readouts do depend on Qms, and the third digit is genuinely not reaching the solver. The cause is not the control's step attribute, which is a common guess and is wrong: a number input accepts 1.22 unchanged. The designer rounds Qms for display and then reads its own display back before it solves. Every other transcribed value survives the trip exactly — 35.7, 0.31, 24.4, 6.4, 124.7 and 6.0 all arrive as printed. Saying so is cheaper than letting a reader find a number on the tool that does not match the number on this page.