Magnetic memory picture brought back memories (pun intended). Lucky enough to work for Dr An Wang at Wang Labs in MA. Dr Wang is credited with the write-after-read which made magnetic core memories possible. They were still used in some of the machines they were building at the time (yes I am that old). When you're a young technician and have desktop programmable calculators and machines that ran BASIC readliy accessible to you, very cool indeed!
Hmm. The reference to the 1401 and 36-bit words is wrong. The 1401 was a character machine, with each location consisting of 6 data bits, a word-mark bit and a parity bit. Based on the following reference to the 36-bit words of the 701, perhaps that was what was meant.
Yes, I programmed a 1401 in autocoder. It was my second computer and second assembly language. By the way, it is possible to see a live 1401 at the Computer History Museum in Mountain View if you are there at the right time. The smell of the mechanical card equipment sure brings back memories.
When I was programming conveyor systems I was introduced to, but thankfully never had to use, "Ball memory". It consisted of a series of wagon wheels(?) with a U channel carved in the rubber diameter. These wheels would be mounted a a single shaft with each wheel controlling a single diverter. The rotation of these wheels was geared to the movement of the conveyor belt. When a carton was destined for a certain lane, there was a solenoid that would inject a steel ball bearing into the U channel of the wheel. A microswitch would be positioned around the wheel at the location timed with the carton being at the diverter. The ball would be scooped out before making a complete rotation. A common problem was that the operators would forget to refill the input tray with the balls in the output tray.
I know, not really electronics, but the mercury delay memory reminded me of it.
Magnetic memory, I was reminded, when recently clearing out my attic, that as a cross between magnetic bubble memory and the latest racetrack memory, the magnetic CrossTie memory was once expected to do great things in the world of disc replacement and NV memory. Its structure was characterized by a series of sawtooth shaped films facing each other with the magnetic bits stepping along between opposing teeth.
The other memory museum piece I found in the attic is a non-destructive readout magnetic square-loop core. This is a normal core with a second hole in the annulus that allowed the state of the main core to be read non-destructively. It appears to be wound with five wires. I think in application it was intended to serve as both a logic and memory device.
Thank you Kristin! interesting article.
In the 1980s, for a few years, magnetic bubble memory was going to be the future of mass storage. Magnetic domains coded as North-South or South-North were steered around loops on a specially contructed ferromagnetic substrate.
Bubble memory was too slow and never quite made it and the Winchester disk (and its derivatives) only now becoming overtaken by 'Flash' solid state technology.
I remember these types of ROMs. I worked with one that worked as a character generator for a graphics display terminal, Computer Dispays Inc. ARDS.
It was made of wires passing, or not passing, through the magnetic circuits (ferrite posts). The bottom had a bed of posts and a lid that (I think) completed the magnetic circuit.
To edit, one had to lift the lid, clip a wire and then add a new one, going a different rout through the posts, connect the new wire and replace the lid.
Besides programming computers that used core memory, I bought some from a computer museum along with a silicon wafer. I took both to work one day to show the other programmers. Our 17 year old genius programmer thought the wafer was pretty cool, but when he looked at the core memory, he turned to me and asked, "How does it hold a charge?"
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.