Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site ssc-vax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!ssc-vax!esco
From: esco@ssc-vax.UUCP (Michael Esco)
Newsgroups: net.arch,net.micro
Subject: Re: Re: How to fab One-Of-A-Kind systems?
Message-ID: <735@ssc-vax.UUCP>
Date: Mon, 13-May-85 21:03:28 EDT
Article-I.D.: ssc-vax.735
Posted: Mon May 13 21:03:28 1985
Date-Received: Thu, 16-May-85 03:05:51 EDT
References: <202@ganehd.UUCP> <183@geowhiz.UUCP> <1143@sjuvax.UUCP>
Organization: Boeing Aerospace Co., Seattle, WA
Lines: 27
Xref: watmath net.arch:1191 net.micro:10359

> Things to beware of, however:
> 
> 	At high speed, wire wrap temds to crap out.
> 	(i.e. > 8 Mhz or so).  Then again, so do sockets.

Not necessarily true. At NCR we used twisted pair wire wrap in a large,
multiboard, 38-nanosecond processor.

> 	Beware of kinked wires - these *do* go with time, but are easy
> 	to spot once gone. In particular, the repair time given a known break
> 	is quite low.
> 
> Also, get yourself an electric wire wrap gun - it will save many many hours
> of precious time, and will prevent a lot of bad wraps.
> 
> Jon Shapiro

Wire wrap is a perfectly good technique for limited-production devices. But it
requires careful assembly with the proper tools. I'd venture to say that most
complaints about wire wrap come from those who didn't put it together carefully
or handled it roughly after assembly (No, you can't play frisbee with it).

						Michael Esco
						(formerly of)
						NCR E&M San Diego
						(but now at)
						Boeing Aerospace