ArticleslgStudy

computer science

Kansas City standard

Kansas City standard is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Kansas City standard rather than just read about it. In short: The Kansas City standard (KCS), or Byte standard, is a data storage protocol for standard cassette tapes or other audio recording media at 300 bits per second. It originated in a symposium sponsored by Byte magazine in November 1975 in Kansas City, Missouri, to develop a standard for the storage of digital microcomputer data on inexpensive consumer quality cassettes.

Kansas City standard — main illustration
Kansas City standard — illustration

Key takeaways

  • Kansas City standard belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Kansas City standard to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Kansas City standard from memory before moving on to harder problems.

Reference excerpt

The Kansas City standard (KCS), or Byte standard, is a data storage protocol for standard cassette tapes or other audio recording media at 300 bits per second. It originated in a symposium sponsored by Byte magazine in November 1975 in Kansas City, Missouri, to develop a standard for the storage of digital microcomputer data on inexpensive consumer quality cassettes. The first systems based on the standard appeared in 1976. One variation on the basic standard is CUTS, which is identical at 300 bit/s, but with an optional 1200 bit/s mode. CUTS is the default encoding used by several later machine families, including those from Acorn and the MSX. MSX added a higher 2400 bit/s mode that is otherwise similar. The 1200 bit/s mode of CUTS was used as the standard for cross-platform BASICODE distribution. KCS originated from the earliest days of the microcomputer revolution, among other prolific protocols. Most home computers of the era have unique formats without any intercompatibility.

History Early microcomputers generally use punched tape for program storage, an expensive option. Computer consultant Jerry Ogdin conceived the use of audio tones on a cassette to replace the paper tapes. He took the idea to Les Solomon, editor of Popular Electronics magazine, who was similarly frustrated by punched tapes. In September 1975, the two co-authored an article on the HITS (Hobbyists' Interchange Tape System), using two tones to represent 1s and 0s. Soon after, several manufacturers started using similar approaches, all incompatible. Wayne Green, who had just started Byte magazine, wanted all the manufacturers to collaborate on a single cassette standard. He organized a two-day meeting on 7–8 November 1975 in Kansas City, Missouri. The participants settled on a system based on Don Lancaster's design. After the meeting, Lee Felsenstein (of Processor Technology) and Harold Mauch (of Percom) wrote the standard, which was published in Byte magazine's first issue. A KCS cassette interface is similar to a modem connected to a serial port. The 1s and 0s from the serial port are converted to audio tones using audio frequency-shift keying (AFSK). A "0" bit is represented as four cycles of a 1200 Hz sine wave, and a "1" bit as eight cycles of 2400 Hz. This gives a data rate of 300 baud. Each frame starts with one "0" start bit, followed by eight data bits (least significant bit first) followed by two "1" stop bits, so each frame is 11 bits, for a data rate of 27+3⁄11 bytes per second. The February 1976 issue of Byte has a report on the symposium, and the March issue features two hardware examples by Don Lancaster and Harold Mauch. The 300 baud rate is reliable, but slow; a typical 8-kilobyte BASIC program takes five minutes to load. Most audio cassette circuits support higher speeds. According to Solomon, the efforts were unsuccessful: "Unfortunately, it didn't last long; before the month ended, everyone went back to his own tape standard and the recording confusion got worse." The participants of the Kansas City symposium include these:

Ray Borrill, Bloomington, Indiana Hal Chamberlin, The Computer Hobbyist, Raleigh, North Carolina Richard Smith, The Computer Hobbyist, Raleigh, North Carolina Tom Durston, MITS, Albuquerque, New Mexico Bill Gates, MITS, Albuquerque, New Mexico Ed Roberts, MITS, Albuquerque, New Mexico Bob Zaller, MITS, Albuquerque, New Mexico Lee Felsenstein, LGC Engineering / Processor Technology, Berkeley, California Les Solomon, Popular Electronics Magazine, New York, New York Bob Marsh, Processor Technology, Berkeley, California Joe Frappier, Mikra-D, Bellingham, Massachusetts Gary Kay, Southwest Technical Products Corp, San Antonio, Texas Harold A Mauch, Pronetics/Percom Data, Garland, Texas Bob Nelson, Pacific Cyber/Metrix, San Ramon, California George Perrine, HAL Communications Corp, Urbana, Illinois Paul Tucker, HAL Communications Corp, Urbana, Illinois Michael Stolowitz, Godbout Electronics, Oakland, California Mike Wise, Sphere Corporation, Bountiful, Utah

Format and enhancements The original standard records data as "marks" (one) and "spaces" (zero). A mark bit consists of eight cycles at a frequency of 2400 Hz, and a space bit consists of four cycles at a frequency of 1200 Hz. A word, usually one byte (8 bits) long, is recorded in little endian order, which is least significant bit first. 7-bit words are followed by a parity bit. As each 8-bit byte is encoded into 11-bits for transmission, the total throughput is 27 bytes per second.

Tarbell The Tarbell Cassette Interface, which, according to early PC retailer Stan Veit, "became a de facto standard for S-100 computers", supported the Kansas City Standard in addition to the Tarbell "native" mode ("Tarbell standard"). The Tarbell standard is very different than the KC standard: it records "1" as "01" and "0" as "10", and typically ran at 1500 bit/s (187 bytes per second, 3000 Hz). 300-baud KC support is implemented by recording "1" as 00000000 (hence "1010" ×4) and "0" as 01010101 ("1001" ×4) at 4800 Hz.

CUTS Processor Technology developed the popular CUTS (Computer Users Tape Standard), which works at either 300 or 1200 baud. The 1200 baud version simply reduced the number of cycles per bit, with a mark being two cycles of 2400 and a space being one cycle at 1200. It was otherwise the same as the original KC standard, with a single "0" for the start bit and two trailing "1"s as stop bits, giving an effective data rate of 873 bits per second. The company provided the S-100 bus CUTS Tape I/O interface board, which offers both CUTS and Kansas City standard support to any S-100 system.

Quick CUTS The Quick CUTS standard proposed by Bob Cottis and Mike Blandford and published in the Amateur Computer Club newsletter operated at 2400 baud, encoding "0" as a half-cycle of 1200 Hz and "1" as a whole cycle of 2400 Hz. The receiver was self-clocking using a phase-locked loop. Published in 1978, it predates the 1982 patent for the similar coded mark inversion proposal (but not its priority date of July 27, 1978).

… excerpt ends here. Continue reading the full article.

Illustrations

Kansas City standard: The SWTPC AC-30 Cassette Interface implements the Kansas City standard. In May 1976, it was sold for US$80 (equivalent to about $500 in 2025).
The SWTPC AC-30 Cassette Interface implements the Kansas City standard. In May 1976, it was sold for US$80 (equivalent to about $500 in 2025).
Kansas City standard: Interface Age magazine May 1977 issue, with a Kansas City standard flexi disc floppy ROM
Interface Age magazine May 1977 issue, with a Kansas City standard flexi disc floppy ROM

Worked examples

Example 1 — a first encounter with Kansas City standard

Start with the simplest possible case. Write down what Kansas City standard claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Kansas City standard before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Kansas City standard ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Kansas City standard

In research
Kansas City standard appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Kansas City standard in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Kansas City standard is common in secondary-school and first-year university syllabi. It links to neighbouring topics Computer standards, Early microcomputers, Standards of the United States, so understanding it makes those chapters shorter.
In everyday life
Look for Kansas City standard outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.
Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “Kansas City standard” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Kansas City standard in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Kansas City standard means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Kansas City standard out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Kansas City standard in simple terms?

The Kansas City standard (KCS), or Byte standard, is a data storage protocol for standard cassette tapes or other audio recording media at 300 bits per second. It originated in a symposium sponsored by Byte magazine in November 1975 in Kansas City, Missouri, to develop a standard for the storage of…

Why does Kansas City standard matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Kansas City standard?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Kansas City standard.

Tags

  • Computer standards
  • Early microcomputers
  • Standards of the United States
  • Tape-based computer storage

Keep exploring