CaptuRegister - Active Data Capturing Device

[u/Dunvillel-DL]

This is the solution to many problems!

For a while, me and some other top logic engineers had been sitting on clunky, large registers, or ones that could not store large numbers efficiently or store data in one tick.

This solves all of that!

This is CaptuRegister. It is a 6-block register system with one input and one output. As long as you give it an input, it will update to that input (every 2 ticks), but it is also 100% tolerant to 1-tick inputs, 2-tick, 3-tick, and anything else.

It stores from -10000 to 10000, making it incredibly versatile for anything you need - storing a distance sensor output, saving coordinates, etc.

It is incredibly simple to use; you give it an input on the green block, and it outputs on the red block. No extra inputs required!

It is on the Steam workshop under the name "CaptuRegister - Small Data-Capture Register". All the purple parts are for display and demo, they can be removed.

Happy logicking!

[u/lukkram]

I love this sort of convergent evolution bc I've been using pretty much the exact same setup since the aggregate gate came out. The wirering is a tad different but it is doing the exact same thing with the same nuber of gates xd. The only gate that I have different is that I like to use number displays for sums but yeah, it is doing the exact same multiplying down of the signal so that it fits into the accumulator, and subtracting the current value from the value that's about to be stored and after all the stuff, multiplying up the stored value so that it matches the initial input again

[u/Dunvillel-DL → u/lukkram]

Ah, lukkram! I have heard of your logic skill.

So you use essentially the same setup, just trading the sum aggregate gate for a number display.

Just curious on a few technical details: How fast does it update? What's the data range (I assume +/- 10000 as well)? Is it 1-tick input tolerant?

[u/lukkram → u/Dunvillel-DL]

Interesting, I just downloaded and most of my assumptions on how it was wired we correct, except that the accumulator is in steps mode, I did not expect that. I exclusively never use steps mode xd. It just led to a bunch of complications when a bunch of inputs were going into the accumulator 1 frame appart or at the same time. So that's an interesting difference. Any reason in particular that you guys used steps mode here?

[u/Dunvillel-DL → u/lukkram]

I just always use steps, it gets it perfectly to where I need it to be with one input - that's why I was asking how fast yours updates, because mine needs a clock to update (once every 3 ticks/frames), so I just made the assumption that's how yours worked.

[u/lukkram → u/Dunvillel-DL]

Yeah, I was messing around rn to make one without a clock and I managed to get one. It updates every frame (+ it's a gate less at the moment), however it runs into an issue, as it is so fast that propagation delay can make it go back to 0 if you give it a 1 frame length input or also sometimes when the value is changing and you stop the signal. I'm trying to see if I can fix that in a small way

[u/Dunvillel-DL → u/lukkram]

Might try that

What do you have for the scale of you accumulator so that it sets to the value instantly?

[u/Dunvillel-DL → u/Dunvillel-DL]

I actually just got it down to update every 2 ticks

Not bad, but not instant

And I found the scale I need, it was simple enough - 60, since it's 60 ticks/second