Triggered One-Shot - OFF/Mode & ON/Mode

[tiffy]

Often I need a One-Shot either in OFF/Mode or ON/Mode which must be triggered by an incoming signal, rather than a Push Button, which then functions as an automatic trigger device to control other items in a schematic by turning them ON or OFF - All in ONE Module now.

EDIT: New Version with GUI - Logically it will have more components now.

[tester]

So many components?

[tiffy]

So many components?

Thank you tester, I have put these on since it is surprising that there is so little info about 'self triggering' devices on the forum - I have seen only one other one-shot but it is in the form of a button and thus does not fit my requirements and it is unstable as well.

Yes, I agree about the 'many components' - my lack of experience with Flowstone and Ruby.

[tester]

Hey tiffy - there is a lot info on triggers on Synthmaker forum, no need to know ruby for that. FS is the next generation of SM so to speak.

[Nubeat7]

So many components?

if you delete all the useless nodes its about the same then yours and it is a smart solution too, just not shure if it is always set to default after load because when you close it between the trigger and the delayed trigger it doesnt set the state default when reloaded..

i know tiffy you like straight lines in your schematic, for this you also could set the curving in the advanced FS options to the left endlike this you get sharp corners instead of curves.. but think about that most of useres work with default option here so it will look different for others with different setting on the curves ..

i would recommend to use not that many nodes because it is always an input and an output which increases the size of the schematic, sometimes nodes are needed specially when a sourcesignal have to be splitted to different targets in a special trigger order, and sometimes just for collecting triggers to avoid chaotic cablesalad, but to use them for a single green line just to make it look nice is a waste of recources, and it also makes it look more complicated than it is..

[RJHollins]

hmmm ... I do the same thing using those 'GROUP' connectors.

I've tried using some of the 'curvy' technique seen in others schematics, and at times use that idea.

I don't like to waste resources, but the 'straight' connection design is much easier for me to follow.

I actually could use a 'connector' option that would allow 'Top/Bottom' tap points, rather than only 'Left/Right' sides.
It seems the logic I use to solve for a condition is either backward or upside down

The use of a 'Bus' connector is something I'd like to use more in my schematic. Certain sections of my modules always have multiple traces to run. Adding to that, I like to have 'TEXT' boxes displaying array outputs to allow troubleshooting or visual confirmation.

Something else I've not seen ... Is there a way to use a 'Bus' prim with the RUBY module ?

[nix]

square corners.png (15.11 KiB) Viewed 24878 times

here is a trick-
if u put 2 dots/spline locators close to each other u can make square corners.
U can also dock nodes like in the shot.
IMO-use all the nodes you want.
It can be easier to route things if you have used a dummy/node

[tester]

if you delete all the useless nodes its about the same then yours and it is a smart solution too, just not shure if it is always set to default after load because when you close it between the trigger and the delayed trigger it doesnt set the state default when reloaded.

I was refering to useless nodes and modules.

Afterload and afterduplicate set the switch always to default (end state). Theoretically it is not needed, because if you copy/paste switches, they remember their states. But everything can happen. As for timer states - you can connect the afterload/duplicate to stop timer first, then the "last" switch, to get sure.