First save I have made in almost 2 years. First attempt at making RAM as well.
Three things to know:
1. It is designed to be used as a component alongside the rest of your computer/device, and therefore I haven't included any form of user interface for entering addresses/values. I did include some instructions in the save so you can muck around with it and write/read some information though. You will need to enter the address/values by using binary.
2. Doesn't include clear function yet. I should probably just put it on quickly right now. I will do that later today, the only reason I haven't done that so far is because it's something that would be highly reliant on the system the RAM is connected to.
3. Don't attempt to use the 'enable read' button or enter any values into the value inputs if the "WAIT" button is lit up. That's just because the RAM needs to refresh itself every 20 seconds or so (in order to prevent the data from dissapearing) and if you attempt to use the RAM while it's refreshing, something undesired will result. If you were connected to an external system, you would be able to control the timing and therefore this wouldn't be a problem.
---------------------------------
Use batteries to send constant sparks to the address inputs.
Pause the game and use single sparks to the value inputs.
most computers use registers and don't need constant sparking and can handle delays from wait commands which is good because spark causes heat and, with instant-conduct, pressure. I'm so tired. I am waffling sooooo muchhhh. cool RAM!
I get what you mean with the continous sparking; I once spent an hour making a tripple-redundant device that sends one spark out for every one spark you send in. Then I realized...
yeah, my multiplyer and my old calculator were continuous sparked. Once I found ARAY and SWCH I switched to one-shot registers for most things such as the Turing Machine.
I might look into making a computer that runs from single sparks.
Also one other thing that annoys me about ARRAY. If you are constantly sparking ARRAY, the line it projects slowly fades away, and then leaves completely empty space for 2 frames before the next line emerges.
It seems to be very reliable however it is quite bulky and could probably be made smaller
Here is one i made:
The adress selector is much more compact and it stores data on a smaller grid
Yeah I saw that. I didn't use it because it's made by Crionis and I don't really want to include something that I didn't design myself.
I probably will in the future (just as everyone used lookup grids when they were first created). But I would rather just look at his and figure out how it actually works first. I imagine it's a look up table of some sort made with ARRAY?
edit: oh I get it, it's a binary pattern. Lol I should have zoomed in and checked it out earlier, took about 2 seconds to figure out what was going on >.>. I will definately look into using something like that. But I will still attempt to make my one regardless.
edit2: Does your RAM have a memory replacement function? Or is it just corrupt after reading it? All I did was loop the output back to the input (after quickly deleting the info) in order to restore the info.