Mechanical Stabilizer

dOUBLEbAD - Custom level - from Android
PlayEdit3 players liked this.Log in to like this level.

In this iteration I set forth to use mechanical properties to stabilize the object's flight. Power up the rockets and adjust one or both up and down to change direction. I made it so you can toggle on and off the stabilization to see the difference. This build required ramping up the output of the Angular Velocity Meter and I also added graphers to show you the signal output involved.

Z= Left Rocket
X= Right Rocket
F= Toggle Stabilizer
(Starts On)

I turned the sound off on the rockets.

Comment below.
Like and Subscribe.

As always, Enjoy!

Views: 182 Downloads: 83 Unique objects: 1 Total objects: 53

Parent

Derivatives

Discuss this level

Log in to comment on this level.
  • dOUBLEbAD: @HXCTCreations: well... I suppose that would be the next logical step. I guess I could get that done as well.
  • dOUBLEbAD: @JD55: having two identical circuits with the same inputs (F button) to do the same job was simply a matter of preference for me to keep the individual sides of the angular velocity meter completely separate. The sparsifier to the y-splitter to the togglers could simply be split off into 2 additional y-splitters and connected to both of the in1 and in2 doing the same thing. Where it is indeed redundant they operate independently of one another they do not affect the outcome as the whole for that portion of the circuit. Often when I build something I like to leave the option to affect only one portion at a time, in this case I could add another button and toggle either cw or ccw independently. As for the switches, each one handles only one input from the meter, either cw or ccw and there is only one output connected at out0 opening the circuit when switched to any of the other outputs. I guess what I'm trying to say is that each side operates independantly from one another and handle a different signal. I could have used a sparsifier to only change from out0 to out1 as opposed to going all the way to out4 but it wasn't necessary for this application. Now after saying all that I am sure I have confused the issue and clarified nothing, lol.
  • HXCTCreations: You should make one using reaction wheel, you know.
  • JD55: @dOUBLEbAD Thanks for the follow-up. Maybe I wasn't clear though about where I'm a little fuzzy. On the Breadboard you have two Sparsifiers that get their input from the 'F' key. The Sparsifiers output to two Y-Splitters which feed into two sets of Togglers. Two Switches receive a signal from the CW and CCW outputs of the Angular Velocity Meter. The Switches also receive identical signals into IN1 and IN2 from the two sets of Togglers. Since IN1 and IN2 determine which output receives the signal, the previous or the next output, it seems to me they would cancel each other out. IN2 sends the signal to the next output, and IN1 sends to the previous output. This is where I'm going to hook up the Graphers. I'm sure I'm making it harder than it needs to be....just a newbie going through growing pains.
  • dOUBLEbAD: @JD55:

LEVEL ID: 27424