Author Topic: Hard Drive (Default Events) *New* [Anatomy Video]  (Read 14618 times)

How long are you waiting when writing?

I recommend 100MS per value and waiting until 1800MS has passed before writing to the next block for safety.

I'm using the keyboard system I built, which will not allow you to type another key until 1500 have passed, and one key pressed emits a corresponding burst of relays into a queue system. There is an enter key which then fires the whole queue in the specified 100ms spaced bursts with 1500 seconds between triggers.

I've also tried making it fire 400-1100 instead of 100-800, which made offsets less frequent but still present. My experimenting continues.

Edit: Increasing the 1500 to 1800 did the trick. I now have a perfect keyboard input ability. I tested it by writing 15 random values, and then inputing the sequence to turn them all back to 1, and it worked seamlessly :)
« Last Edit: December 31, 2012, 09:46:03 AM by Remousamavi »


Difference between models

Rev 3 (January 2013) - 45500 MS "secure" read speed, 1x HDA port
Rev 2 (December 2012) - 20000 MS read speed, 1x HDA port, obsolete by upgrade
Rev 1 (December 2012) - 20000 MS read speed, no HDA port, obsolete by fault


MicroBlock Rev 3, January 2013

MicroBlock has released revision 3 of the Precision HD which adds "secure reading".  This increases read time 2x but provides solid output that works even on servers with latency 300+.

Revision 3, recommended to all who want 100% pure output, has a new timing system.

The first memory packet takes 2500 milliseconds to read. The next packet is read after 3000. MicroBlock recommends 2500 - 2700 MS reading time in between memory segments. The total read time takes 45000 MS.

Example.

Memory packet 1 - start read at 0, toggle read off at 2500 (this will account for all of 8 potential values)
Memory packet 2 - start read at 2900, toggle read off at 5400

Though not ideal, the read speed is solid.
« Last Edit: December 31, 2012, 10:45:43 PM by lcyGamma »

You should add RAID support
I would try to connect enough to make an entire MB of storage.
Though in the future i demand to see things such as:

mother boards
screens
cases
graphics cards? idk what it'd do for a blockland save, maybe provide easier rendering functions to the screen? better the graphics card the faster it renders to the screen

then i want to see you connect these together
inside a case.
i want to see the day
when i press the power button
on my blockland computer.



OH YEAH but cool
didn't expect any less from you icy.
and now I expect more.
« Last Edit: January 01, 2013, 08:50:58 AM by Brian Smithers »

Thanks :3

The closet thing I'm working on in terms of having hard drives connect to each other is the HDA port which'll let you connect two together. Currently this would be only for writing because of how the reading system works but, it wouldn't be hard to tweak to make it share reading as well.

My keyboard system now has an output capability with an output node on top for a planned monitor and a new key for reading.



I also recently started experimenting with specific uses of the harddrive's memory system.

I would try to connect enough to make an entire MB of storage.
Technically you cannot store a megabyte in these harddrives because it doesn't store data in binary.

Technically you cannot store a megabyte in these harddrives because it doesn't store data in binary.

What it be instead then?

Technically you cannot store a megabyte in these harddrives because it doesn't store data in binary.
Yes you can, what makes you think you couldn't?

What it be instead then?

Yes you can, what makes you think you couldn't?
You can store the same amount of information as a megabyte using this harddrive, but not the same way.

Explain to a caveman why you would need it and what it's used for cause I'm clueless

Explain to a caveman why you would need it and what it's used for cause I'm clueless

To make evented systems that can remember dynamic information.

To elaborate, you could store anything from pictures, to variables, and so on in one or many drives then connect them to other evented devices and so on.
« Last Edit: January 01, 2013, 03:03:04 AM by lcyGamma »

Explain to a caveman why you would need it and what it's used for cause I'm clueless
a giggled a bit at your name on THIS thread

I admit I've always had trouble understanding the projectile events, the second box confuses me.

There are two boxes. Each box specifies X, Y and Z velocity.
The first box specifies the base velocity. The second box specifies "derivative velocity".

Basically, to get the velocity, Blockland first takes the first box, then adds that to a random velocity within the limits of the second box.

First box: 5 0 10
Second box: 0 20 5

This would allow Y velocity derivation between -20 and 20, and Z velocity derivation between -5 and 5.
Basically, you'll get a random velocity between 5 -20 5 and 5 20 15, considering that it's added to the first box.

Thanks Port, now I understand.

I've fixed the speed in the save thanks to Rems values, in the future I'll be sure to be careful about how to use the projectile event.

I understand it was X Y Z for the first but then I was like, wat, why are there 2.  :cookieMonster:

Technically you cannot store a megabyte in these harddrives because it doesn't store data in binary.
Yes... you can.
I've already covered this you potato. It stores in octal which can be converted into binary. 3 blocks/digits is an octal number. 1 octal number is = to an 8 bit binary number. You can store 5 bytes inside 1 hard drive (40bits).
So you would need about 205 of these drives linked up to store 1Mb, plus 1 extra byte.

You can store large amounts of data. Just very impractically. The time it would take to write to 1024th byte would be kind of pointless so unless they could be read in any order using some kind of address system then 'eh. I would stick to storing just 10bytes or so.
If the process can be sped up so it's more efficient then brilliant! It can cut the time down drastically and make it practical to use.
Get your stuff right ._.