Scientific calculator with a brain built out of relays.

Similar projects worth following
This project is about building the fastest relay-cpu in the world.

Once you have a homebuilt CPU (and also before it is ready), anyone will ask: What can it do ? So it is important to have a good application to show what the CPU can do. That will also give some focus for the design.

I took a calculator as application. So the device should have calculator keys and a display. It will be a scientific calculator, using floating point calculations, and capable of logarithms and trigonometric functions.

The aim is a speed of a at most a few seconds for add and multiply, and at most 5 to 10 seconds for the scientific functions.

The design will have solid state memories, but might be prepared to work with a diode-ROM
and/or capacitor-RAM if the application does not need too much memory.

How will the fast speed be accomplished ?

Relays are slow, and to get acceptable performance, many measures must be taken.


  • Microcode will not be used
  • Harvard architecture, so fetch and execute will be in parallel
  • Have enough registers so we're not loading and storing all the time
  • Have a good instruction set
  • Some special instructions tailored to the algorithms that are used


  • Design in such a way that for executing an instruction a very low number of consecutive switching relays is needed. At this moment, there are only four consecutive switching relays for an instruction.
  • Use small relays, these can be fast (datasheets show 2 msec switching time). Using small relays means they take less space on a pcb, so not much pcb area will be needed.

The design is shown in the following block diagram (click on it for a larger version):

The block diagram also shows which functions the twelve PCB's and the backplane contain.

Now that all schematics and also all pcb's are designed, I can give a quite accurate listing of the number of main components:

The architecture is explained in the architecture document (see Files section). Highlights are:

  • All instruction, register, word and memory sizes are 16 bit.
  • Most instructions operate in a single cycle.
  • There are eight 16-bit registers, one of them is the PC.
  • Six registers can be paired to form three 32-bit registers (like the H and L registers in the 8080 / Z80 ). Many instructions have a 32-bit variant that operates on register pairs (using 2 cycles but single instruction word).
  • It is a 2-operand design, 1 operand is a register and the other one can be register, memory, or immediate. If the immediate is only 8 bits (7bits + sign), it is included in the 16-bit opcode and the instruction executes in a single cycle.
  • Memory addressing always has a small displacement within the instruction opcode, facilitating addressing of variables in a stack frame, or addressing of structure members. Instructions that use this need only a single cycle.
  • The ALU has also decimal instructions (in addition to the normal binary instructions), to support the calculator functions.
  • There is a special instruction to support (decimal) multiplication.
  • The ALU has special instructions to convert the 4 nibbles in a register to bits that control a 7-segment display.

The architecture is independent from the technology, so it could also be used for a TTL or FPGA design. It can be upgraded to a full 32-bit design. Actually, since there are 32-bit register pairs, it would be easy to support a 32-bit address bus.

Use of the architecture is free for non-commercial use :), but I would like to get a mail when you are going to use it.

One of the images shows how the device could look. The base PCB has the keys, displays, instruction registers and decoders. There are four processing boards. These are all equal, and every processing board has 4 bits of the ALU and of each register. (Edit... this has changed... )

Next to the processing boards can be one or more boards to implement the memory.

What has to be done:

  • Have an architecture.
  • Have a schematic. I'm making good progress on that.
  • Have a simulation. The 4-bit boards have been low-level simulated in Logisim. I do not have a good logisim model for a relay, so the simulation might not catch all problems. Many instructions have also been simulated.
  • Built an assembler and simulator. Simulating the application before the design is finished gives a chance to optimize the CPU for the application.
  • PCB design 
  • PCB ordering
  • Build (now, december 2017)
  • Have a test strategy, and test.
  • Find the causes of problems, and correct them.

    PCB signals

    A collection of spreadsheets with quite accurate description of the signals at the connectors of the pcb's

    x-zip-compressed - 76.96 kB - 10/14/2017 at 15:25


    Adobe Portable Document Format - 81.05 kB - 10/14/2017 at 14:45


    Instruction list 20171014.pdf

    Up-to-date list of instructions

    Adobe Portable Document Format - 97.42 kB - 10/14/2017 at 14:41


    Block diagram, and full schematics of the Risc Relay CPU !

    x-zip-compressed - 1.12 MB - 10/14/2017 at 14:38


    x-zip-compressed - 103.28 kB - 04/16/2017 at 14:52


    View all 9 files

    • Assembling and testing pcb's

      roelh12/30/2017 at 19:16 2 comments

      Around two weeks ago I ordered all remaining pcb's and a lot of parts. They arrived just in time for some happy soldering in the days after Christmas. Each pcb was (sometimes partially) built and then it's main functions were tested, revealing soldering errors but also a few design errors. This is the state today (click it for bigger version):

      1) clock and control pcb

      2) program counter pcb (6 bits) 

      3) instruction decoder pcb (only it's LED's are visible)

      4) program memory and instruction register pcb

      5) RUN button

      6) STOP button

      The pcb's are connected to the main pcb with DIN41612 connectors.

      I started with the program memory and instruction decoder. (All pcb's in this project were intended to have a white color, but apparently I forgot to select the color when I uploaded the gerbers of this pcb). The flash memory itself is not yet assembled. There is a connector (where the ribbon cable connects) that is intended to connect to a flash memory programmer. It is now connected to 16 pushbuttons, to control the contents of the instruction register manually. The instruction register worked (but several of the 2K2 resistors in the hold circuits had to be lowered in value, apparently the current was not enough to keep the relays attracted).

      Next was the clock and control pcb. The clock circuit did not work as expected and had to be modified. Two 100uF elco's (visible on top of the pcb) set the clock to approx. 5 instructions per second, slow enough to have a sense of what is going on during testing. Asymmetry in the clock signal will have to be solved (and higher speed will be set at a later time). One of the board's input signals was not connected, a wire was needed to correct this. Another problem: The single-step button should start executing one instruction and then stop. Unfortunately, the stop function works too well, so much that pressing the single step a second time does not run a next instruction... 

      The program counter pcb also has decoders for reading and writing to the registers. Only the program counter section was mounted for now. After re-soldering a resistor, I started the clock and watched the PC counting...  0, 1, 2, 4, 8, 16 ....  Oh what's wrong ?  Did I build a shift register instead of a counter ?  After following the signals on several wires, it occurred to me. The PC has a master and a slave section, they each have a CLR signal. If one of the registers is not cleared, the bits stay 1 and you get this behaviour.  This is not visible on the LED's if the leds are connected to the slave section and the non-cleared part is the master section. Well, the CLR of the master could be interrupted by relay RL341, and that was not placed because it was considered part of the decoder section. After placing RL341, it was happy counting !

      Now the instruction decoder. It has led's that show the addressing mode ( Memory, Zero page, Immediate, register, test-and-branch) and the instruction ( LD, ADD, AND, OR, XOR ) and a few other output signals. This was simply tested by letting the clock run and manually put something in the instruction register. Many instructions could be tested this way. It revealed an error in the decoding for the DMPY instruction, were inputs to a diode gate had to be connected to IR_Y0 instead of IR_Y0_N. This diode gate was on the pcb with the instruction register, leading to a small modification there. For a LD instruction, also the OR led was on, could be corrected with an extra diode. The led for the PC was connected to a wrong point, not changed yet.

      Some changes were made in the schematics and pcb design files before they were ordered, so the file section is no longer uptodate. One of the changes was another change in the instruction set...   New instructions to subtract two registers without storing the result, providing compare instructions. Logic instructions (and, or,...

      Read more »

    • All design work has been done !

      roelh10/14/2017 at 16:55 0 comments

      All schematics and pcb designs are finished now. But I will do several checks before I send the PCB's out for production. (I already found some mistakes, can you find them too ?)

      Today I uploaded in the file section:

      • The schematics of all pcb's
      • A block diagram that clearly shows the main functions of the pcb's
      • An accurate description of pcb interface signals
      • Updated instruction list and architecture description

      This info should be enough to understand the design.

      I also posted the number of main components (327 relays). On the MEM pcb, I used BAW56 double-diodes because 1N4148 would cost me too much pcb area.

    • Speed Limit !

      roelh06/10/2017 at 20:43 2 comments

      Time to check the maximum reachable speed !

      The CPU needs 4 clock signals:

      • Phase 1 CLR
      • Phase 1 Activate
      • Phase 3 CLR
      • Phase 3 Activate

      There are also phase 2 and phase 4, but they have no clock signal, these phases are the relay 'layers' that follow the state of the relays that are switched by state 1 and 3.

      As the name implies, a CLR pulse clears a relay, and an Activate pulse can set a relay (if its input signal is true). But the CLR only disables the hold circuit of the relay. At the same time, the activate signal can be busy setting the relay, and even the circuits that follow the relay can already start switching while the CLR is still active ! So the clearing of a relay does not take time because it takes place at the same time as the activation (see technology file in the file section). The phase 1 CLR pulse falls within the phase 1 Activate pulse (so CLR can only be active if Activate is also active). And also, the phase 3 CLR pulse falls within phase 3 Activate.

      I did built a clock generator that has 4 relays (one for each clock signal), driven by a few transistors, and the transistors driven by a function generator. I attached the new clock to my test-setup (that has an ALU and a Register pcb). Phase 3 loads the ALU latch A with the data from register D, and phase 1 loads register D with the ALU output.

      On the test pcb, setting function to ADD and loading 1 in ALU latch B. This lets the ALU increment at each clock pulse.

      Well thats nice... what they call blinkenlights.... see the bytes incrementing at 3 places: at the ALU output, in register D, and at ALU input A.

      Yes and that sound.... Ohhhh...

      Cranking the frequency up, until errors begin to occur.... then a little bit down again where everything seems ok.... 136 Hz !!

      Power consumption around 600mA at 24 Volt. It's not really optimized for watts per megahertz....

      The other circuits in the CPU ( like instruction decoder, and PC incrementer ) will operate concurrently, and have the same technology as the ALU and registers (so they will reach the same speed). Most instructions use a single cycle, so the CPU could reach a speed of 136 instructions per second ! Probably will have to run it slightly slower for good reliability.

      The used relays have 2 mSec operating time. Relays with 1 mSec exist ( like IM06N ) but I found these too expensive. These could double the speed....

    • Main board layout

      roelh05/13/2017 at 15:30 0 comments

      Still working on the schematics. A lot of little details must be handled:

      • splitting clock signals, in order not to overstress relay contacts
      • program counter is 12 bits, add 4 bits and a selector knob to switch between several programs in two 64K x 8 flash chips
      • how to get the program in flash... provide connector for dedicated AVR-based programmer with RS232/USB connection to PC
      • The dedicated programmer should have buttons for manually composing an instruction and execute it
      • The clock signals must be made. Clock must be started and stopped.
      • User input buttons must be handled
      • The remaining pcb's (except main pcb) will be made smaller than the first ones, now I discovered that 10 x 10 cm boards are a lot cheaper than bigger ones (at certain pcb makers).
      • How to distribute the remaining circuits over several pcb's, and how to allocate signals on the 96 pin connectors

      The last point has great influence on the routing of the main board. So, the main board is routed first. The connector allocation can still be changed if needed (except for the existing register and ALU pcbs). Here is the current status:

      There are two rows of 6 connectors. At the front, there are 12 displays. The yellow signals must still be routed. But there will be more to do, since the schematics are not complete yet. This will keep me busy for a while...

      The ALU has now all 8 bits built, and is working after solving a few soldering issues.

    • PCB's for ALU and registers

      roelh04/16/2017 at 19:13 2 comments

      The first two PCB's have arrived ! This is the pcb for the registers:

      The pcb implements four 8-bit registers (registers C, D, X, Y). Only 8 bits (4 bits in 2 registers) are mounted. At the topside of the PCB, you see that each register has its own 8 LED's to indicate the contents. The pcb is labeled "REG1710" (top left) meaning the design is from 2017 week 10.

      The other PCB is the 8-bit ALU "ALU1710":

      Only 4 bits of the 8-bit ALU are mounted. The 4x4 relay section is the basic ALU, that includes two input registers (latches, to be honest). The sections with 2 relays are for the ADD-6 section and decimal correction. On the top of the pcb you see LEDs for input data, output data, function selection and flags. The ALU has the normal Load, AND, OR, XOR, binary ADD, but can also ADD decimally and convert BCD data to 7-segment display code. Subtraction needs help from outside of the ALU. It is done by inverting one of the register outputs (and setting the CY-input).

      The placement system is all diodes and relays on top, and the resistors on the bottom. Relays are surface mount types, this gives more space for routing at the bottom. Diodes are through-hole 1N4148. I did not use BAV99 or other SOT23 types (otherwise I could be accused of using transistors secretly ;). Mini-Melf were also avoided since they tend to roll away when you try to solder them. Some signal wires drive many circuits, in that case the diode is 1N4004 or similar.

      Of course, something was wrong. The connector DIN41612 was not close enough to the edge of the pcb (placement was based on the silkscreen of the footprint, I interpreted one of the silkscreen lines as the edge of the pcb, but that was wrong). I had to remove about 1mm of the pcb to make it fit. This destroyed only a few traces, that must be replaced by a wire.

      Schematics and gerbers of REG1710 and ALU1710 are in the Hackaday files section.

      I did built a simple test device. The ALU and REG pcb's can be connected to it. The 3x4 buttons transfer data from a register to the input A of the ALU and from the ALU to a register. The 8 buttons on top control data on input B (next to it are a CLR input B button and a CY-input button). The big knob selects one of the ALU functions, the function is displayed by one of the green LEDs.

      For the curious readers, here is the bottom side of the test device:

      And of couse, I tested my new pcb's. Found a small problem:

      It was intended that all diodes point in the same direction. But a few diodes on the ALU picked an older diode footprint, that had the silkscreen in the other direction. The result was a few diodes had to be reversed.

      After that was done, all assembled functions were working ! (But the tester does not test the second output ports of the registers).


      Some new instructions were added to the instruction set:

      - An instruction to load data from the program memory. The simulator has a unified memory, so the instruction was not needed there.

      - Added XOR with immediate value

      - Added a powerful instruction: Test a bit and branch. Within a single instruction, a single bit from a register pair can be tested, and a branch forward is done if the bit is 1 (or 0). In each register pair, the bits that can be tested are 0, 1, 2, 3, 4, 7, 15, 31. So this also replaces the clumsy sequence that was needed to test the upper bit of a value in a register. Instead of adding to the PC, this instruction can also conditionally add to register C. The branch forward has a reach of 31. In the instruction space, some space in the register-mode was sacrificed to make the test-and-branch possible.

      Work will continue with the details of the control functions, and planning the "backplane".

    • New project: NeuronZoo

      roelh01/05/2017 at 15:31 0 comments

      There was not much progress for the relay computer lately, mostly because I was working on a new project called NeuronZoo ! The NeuronZoo project is on Hackaday now !

    • Schematics of 3 pcb's

      roelh12/18/2016 at 20:42 0 comments

        There was not much progress the last months, mostly because of a new project that I hope to show soon.

        I have new ideas now about the distribution over several pcb's. Each pcb will have a DIN41612 96-pin connector to a backplane. For several subsystems, it is very easy to get over 96 signals, so reshuffling was needed. Also there is a limit to the number of relays that will fit on a pcb, the maximum is now 40. The size of the pcb's will be approx 10 x 14 cm.

        1. The register pcb implements 4 registers of 8 bits (32 relays). Of this pcb, 4 will be needed to implement the 7 16-bit registers (not all parts will be placed).
        2. The PC and decoder pcb. Implements 6 bits of the program counter (3 relays per bit), and circuits for decoding the registers. Two of these are needed for a 12 bit program counter, the decoder parts are not needed on the second pcb.
        3. The ALU pcb implements the 8 bit ALU, with both input registers A and B included. Two pcb's are needed for the 16 bit ALU.
        4. Instruction decoder
        5. Memory card. Two are needed, one for the program memory and one for the data memory. Includes the data shifter.
        6. The backplane will have connectors for all mentioned PCB's, and will hold the displays and buttons for the calculator. There will not be a straight 1-to-1 wiring of all connectors, every card will only work in its own position on the backplane.

        For pcb's 1,2 and 3 I did put complete schematics in the Hackaday file section. The PCB design is almost complete for registers and pc/decoder, and halfway for the ALU.

        The instruction set was again changed. Only half of the registers had logic instructions, this turned out to be impractical. Now, all registers have the same instructions. The price to be paid for this was that conditional instructions are now only for the PC and not for other registers (The ARM-like conditional instruction were not needed so much). In the Hackaday file section, the architecture and instruction list were updated. (My doc-to-pdf converter has trouble with the lines around tables, sorry about that).

    • Instruction decoder

      roelh05/24/2016 at 20:41 0 comments

      In this log I give some schematic info. I will explain the principles of the instruction decoder. (The ALU and registers are already discussed in one of the files).

      In the HAD files section, the schematic RRC1613.pdf is a “summary” of the total design. There may be differences between the descriptions. It is hard to keep everything in sync as long as the design is not yet final.

      Above the long line of RRC1613.pdf, you see the data path essentials for 1 bit (register and ALU). Below the line, the essentials of the instruction decoder are shown. The schematic is intented to give an overview of the polarities and pull-up/pull-down capabilities of the signals.

      The clocking is not yet in the drawing. For every instruction there are four phases:

      • 1) Called PH1 in schematic. Write to relays of register latch 1 group (CPU registers)
      • 2) Write to relays of "Next state function 1"
      • 3) Called PH3 in schematic. Write to relays of register 2 latch group (like the ALU input registers)
      • 4) Write to relays of "Next state function 2", like the carry relays and logic result relays.

      Phase 2 and 4 are not clocked, they are are direct result of the actions of phase 1 and 3.

      At the lower left, you see the relays of the instruction register:

      Y0 Y1 mode zpage/immediate/memory/register
      A1 A0 addressregister / src register
      R2 R1 R0 dst register
      M2 M1 M0 operation code

      The upper contacts of these relays are for the hold function, and deliver the signal (sometimes also in inverted version) for further decoding.

      Actions for decoding phase 2 and 3 of the instruction:

      The lower contacts of these relays are for decoding that has to take place immediately (to decide what data to put in ALU A and B registers)

      Relays R2, R1, R0 select 1 of the 8 registers at output port 1 (via resistors at left and right above the ADD-6 circuit).

      Relays A1 A0 select 1 of 3 registers at output port 2 (via lowest contacts in the register bank, with pull-up signals "to_addr"). ( The architecture doc specifies 4 address registers, but the implementation has only 3.)

      Relays "A0 slave" and "subtract" select 1 of 2 register pairs (register X or Y) for register mode on port 2 (it uses pull-down signals). The register pair is 32 bits, the shifter selects 16 bits out of these 32 bits (in 4 bit increments). The subtract relay chooses between normal or inverted output at port 2.

      "A0 slave" means that this register has the same function/state as relay A0, and it is controlled by a contact of A0 so it switches a little later than A0 itself. This is no problem here because the shifter does not introduce a delay, so the register data will be in time to be loaded into the ALU_B register.

      But when A1 and A0 select an address we can not use a slave register, because there is an extra relay level for address decoding (for capacitor-RAM or diode-ROM, not needed in the case of solid state memory). After the address has been decoded, the data will be immediately available to be loaded in the ALU_B register.

      A capacitor RAM will be similar to Rory Mangles TIM8 design. Refresh will be different, the idea is that after the cap has activated the relay, it will immediately be refreshed through the hold function of the relay. The circuit of the caps will be such that there is no need to switch between discharge and charge.

      Generation of control signals for the shifter and immediate addressing is not yet on the drawing, but this is not very difficult because the timing allows to use an extra level of relays here. Also the Store function is not on the drawing.

      Relay Y0 selects if the A0/A1 selection is a pull-up (to 24V, address selection for memory mode) or a pull-down (to 0V, for register mode). Relay Y1 simply disconnects the address selection for Z-page mode, so for Z-page mode only the displacement is connected to the address (bits A0/A1 are not used, in contrary to architecture doc).

      Actions for decoding phase 4 and 1 of the instruction:

      Decoding for phase 2 is less difficult, because there...

      Read more »

    • 3rd log, about log

      roelh05/22/2016 at 21:07 0 comments

      I've been busy with the log(x) function. It works quite nice, see CALC_6.TXT. The simulator counts the cycles between key presses, the log function takes 271 cycles for log(2) .

      The ln(x) is calculated with the log function, as log(x) * ln(10). This is slower because the general multiply function is used after the log(x). The ln(2) takes 413 cycles. (So to reach my 10-second calculation goal, at least more than 40 instructions per second must be executed).

      A faster, native ln(x) was also built but abandoned, to save program space.

      The 10^x function is also in CALC_6, but is not yet accurate enough and only handles a small range at this time.

      After the sin/cos/tan functions are also available, I will put the program in the logisim simulator to test everything on the gate level (eh.... coil and contact level).

      And about the hardware.... it is expected to have approx. 270 DPDT relays.

    • First programming

      roelh05/16/2016 at 14:31 0 comments

      Started programming in the new assembler.... it didn't go very fast. One of the reasons was, that there were still some bugs in the assembler and simulator. Also I made some changes in the instruction set because some features were missing, like a bit test instruction (TSTB). The CL, DL and DH registers were given more functions, at the cost of functions for the X and Y registers.

      Floating point number entry was more difficult than floating point multiply....

      All files are now updated to the newest version. You can paste the CALC_4.TXT into the simulator to see the floating point number entry, add, sub and multiply.

      Next thing that I will do, is make LOG and 10^x functions. (I will use the method of An Wang, inventor of the LOCI calculator).

    View all 11 project logs

    Enjoy this project?



    Bartosz wrote 11/08/2017 at 16:46 point

    lufa ot contiki works on this machine?

      Are you sure? yes | no

    Yann Guidon / YGDES wrote 04/24/2017 at 22:30 point

    It's looking better every day !

      Are you sure? yes | no

    Yann Guidon / YGDES wrote 12/20/2016 at 01:33 point

    I looked at some of the PDF (webpages/logs are more practical though) and I appreciate the efforts you made to polish your design :-)

    Now tell me : did you prototype some of the circuits you designed, with real parts ? Even a small subset... Relays can have surprising behaviours !

      Are you sure? yes | no

    roelh wrote 12/20/2016 at 14:55 point

    Thanks for the compliment...

      Are you sure? yes | no

    roelh wrote 12/20/2016 at 14:58 point

    No I did not test anything yet... When problems occur I hope to fix them with extra parts or wires on the pcb....

      Are you sure? yes | no

    Yann Guidon / YGDES wrote 12/20/2016 at 15:12 point

    Hi :-)
    I advise you against this approach: you might discover big problems after you have soldered everything. You would lose both all the relays and all the PCBs...

    Testing small circuits, such as the ring oscillator, helped me uncover many issues I hadn't considered while drawing on paper. It made my design more reliable and I even ended up with configurations I had never seen in the litterature.

    One example is the problem of fanout (which is, funnily, very similar to the issues in transistor-based circuits).

    At least now I have characterised my parts beyond the mere indications of the datasheet and can estimate delays and consumption with good confidence.

    Get that soldering iron and oscilloscope to work ! :-) Who knows what mistake you will find and how this will influence your next revision ? For example, how did you estimate the latches' feedback resistors and did you measure all the currents in all the driving combinations ?

      Are you sure? yes | no

    Alex Martin wrote 12/19/2016 at 23:43 point

    Great project! I like the ambitious goal of "fastest relay cpu in the world".

      Are you sure? yes | no

    Yann Guidon / YGDES wrote 12/20/2016 at 04:29 point

    I'll see if I can run #YGREC16 - YG's 16bits Relay Electric Computer faster ;-)

      Are you sure? yes | no

    Yann Guidon / YGDES wrote 12/18/2016 at 00:04 point

    Ohhhhh... I just notice today, only now... Your sick trick for the 32-bits mode. Do you mind if it inspires me ? :-)

      Are you sure? yes | no

    roelh wrote 12/18/2016 at 20:57 point

    Hi Yann, your question triggered me to update this project...

    Yes, I like sick tricks. Of course you can use the 32-bit mode. What will be your instruction set ?

      Are you sure? yes | no

    Yann Guidon / YGDES wrote 12/18/2016 at 21:07 point

    your "32 bits mode" looks to me like a "microvector", but I suspect is has already been used in other systems, such as the 68K.

    For now, I have no target for this trick because 1) #AMBAP: A Modest Bitslice Architecture Proposal and #YASEP Yet Another Small Embedded Processor have too few registers 2) #F-CPU has a different approach (superscalar) 3) There is no need of dual-sized registers in pure RISC systems...

    But it's good to know and I had actually considered an architecture with maybe 1K registers to create a "pseudovector" machine, using something along these lines.

    For F-CPU this made me think about "binding" ou "pairing" execution units to increase throughput if the computations are identical in two globules... but this remains "single cycle", not "hold on a cycle and toggle a bit" :-)

    Damn, there are so many possible combinations !

    Regards :-)

      Are you sure? yes | no

    Yann Guidon / YGDES wrote 05/22/2016 at 22:30 point

    The online JS assembler and simulator is sick.

    You have done some awesome work ! I'm jealous :-P

      Are you sure? yes | no

    roelh wrote 05/23/2016 at 16:12 point

    Thank you Yann. But the Javascript simulator is not very fast. The relay computer ifself would probably be faster...

      Are you sure? yes | no

    Yann Guidon / YGDES wrote 05/23/2016 at 16:57 point

    At least I can compute Mandelbrot sets with my own simulator ;-)

      Are you sure? yes | no

    Winston wrote 04/13/2016 at 23:31 point

    Very much looking forward to seeing (and hearing) this after you build it.

      Are you sure? yes | no

    Yann Guidon / YGDES wrote 04/18/2016 at 22:23 point

    Yep. The noise it makes will sound like music...

      Are you sure? yes | no

    Similar Projects

    Does this project spark your interest?

    Become a member to follow this project and never miss any updates