This isn’t robot related... although I used ARC to make the software vc8e emulator. Read on...
I’ve always been a HUGE computer history buff and until recently, I’d get my fix at the Computer History Museum in San Jose. Thanks to an awesome guy named Oscar, I now have a functioning pdp8 emulated by a raspberry pi and simh. I’ve made quite a few modifications to it, mostly a few software fixes AND noticeably a vc8e oscilloscope terminal emulator!
The vc8e was a display controller and protocol for point-plot displaying with single coordinates. While the pdp-1 used a different setup for space war!, the pdp-8 used the vc8e and most notably the VR14 x/y display monitor.
I even came up with a little trick to emulate the phosphorous fade of a real oscilloscope. There's quite a few settings for configuring the refresh (simulated flicker), pixel size, intensity and color. While there aren't a lot of applications that I know of for the vc8e, having Space War! is good enough for me
Here's a link to download my vc8e emulator for anyone daring to play with Oscar's Pidp-8: VC8E-SpaceWarDisplay.zip
Here she is in all her glory connected to my vc8e terminal playing space war!
Oscar ships his PiDP-8's in a kit
So, building kits is just another way or experiencing what it's like to work on an electronic assembly line ugh
I used a raspberry Pi 2 with raspbian that i very-much modified. There's a dedicated serial terminal, a few custom disk & tape images and of course Space War!
Other robots from Synthiam community
Mereyes's Mereyes WALL-E
Daedalus's Android Robot
This is fantastic DJ! When I was at college many years ago we had a computer like this and it had its own room!
I am tempted to buy one myself, as for me many flashing lights/LEDs where what we thought computers were in the early seventies.
In my roof (somewhere) I have a working NewBrain, ZX80, Spectrum and a box of PCBs and ROMs to make up a number of Jupiter Ace computers which used FORTH which was very neat!
Tony
WOW what a cool build, Thanks for sharing. I was lucky enough to get to use a PDP 8 when I was 14 doing work experience at my fathers work in Sydney Australia. 4K of core memory programmed in octal using a bunch of toggle switches, lots of fun.
I think what you have done is fantastic! I have been to the computer history museum, and thought the Babbage analytical engine was amazing. I collect old mechanical calculators like this Friden
(a precursor to what you are working on, ha) and older hand-cracked examples. Amazing work. -Richard 'twitch' R.I won a Harvard Award some years back and while in Boston I visited the MIT Robot Museum - this is what 64K of memory looked in the fifties. It was a kind of non-volatile RAM as the copper rings always stay in there last axis position.
Tony
@DJ: Thanks for sharing!
How long it took to assemble ?
@Tony: "This is the fast 64k word index memory", is that the portable version ?
Hi Tony (Toymaker) , that core memory looks as big as a fridge, ha -- but pretty amazing to get 64k word (i assume that means 128KByte) from that. And i did not know there was a robot museum -- will have to check it out. Thanks, -Richard 'twitch' R.
Nah - the description on that core memory peice is kinda missing the word size. The 64k is the size of the whole memory in the picture. The Word size isn’t defined.
A Word (when used in computers) defines the number of bits that the cpu can handle in one instruction. For example, your x64 bit cpu would have a word size of 64 bits.
The size of a word doesn’t change the size of a Byte. The byte descriptor is a universal size construct for data exchange. However, since modern computer processors are designed with multiples of 8 bits, they Byte size descriptor is used much more integrated with development.
It’s bizarre about the word sizes on old processors, because they’d be odd numbers - mostly dictated by octal. 12 bit or 24 bit CPU’s we’re most common.
ASCII hadn’t been invented for many years to come - so the reference of characters was actually an afterthought for computers. They originally were designed for calculating numbers, and therefore a 12 or 24 bit word size made sense since the numbers would have decimal precession or be quite large.
When operating with characters to form sentences, lots of memory was either wasted or the cpus/software was updated to store multiple characters in a single word. This was mostly at the cost of performance though....
And that’s one of the beginning scenarios where the battle between performance and efficiency of computing began... since then, that responsibility has been handed off to compilers.
Bad programmers blame good compilers for compiled application performance. Take for instance the ongoing struggle with loops versus inline code.
The difference is this..
You have an option to write a short peice or code that loops with FOR or WHILE. But, you also have the option of not using a loop, and instead writing an instance of each command over and over and over again.
Well, the LOOP version looks pretty and compact to the programmer, but will run much slower than the inline version.
So trying to manage multiple characters in an old school numeric inspired processsor storage device had that same challenge - thus, the Byte was born and multiples of 8 for cpu architecture.
@rregister, The museum is small but has some amazing exhibits, well worth a look if you are in Boston!
Also the robot lab at MIT is pretty neat.
Tony