DSP Robotics Support

Under this heading I may (or may not) in future upload some combination circuits - for those not against it.

The first is a schematic of a Clocked JK Flip-Flop (Basic unit) and a Clocked Master-Slave JK Flip-Flop in one schematic (for Green).

Inside the schematic I also left the GATES Configuration and the Truth table I used the day that I constructed this schematic, long ago, as well as two push buttons, two Clocks and four LED's which are all optional. So, I uploaded it here as is.

Someone on the forum, some time ago, requested a JK Flip-Flop (for Green)... so, here is my Clocked version of it.

# Corrected and uploaded here again: The two input terminals J & K of both JK Flip-Flops (Graphics versions only) were not connected to their corresponding LED's - they were connected the wrong way around. This is now fixed in this version.

Cool stuff, thanks for sharing!

Here is a schematic of a Clocked (CLK) T (Toggle) Master-Slave Flip-Flop. The same conditions apply as in the first post, uploaded as is on the day when I constructed it.

Here is a schematic of a Clocked (CLK) D Flip-Flop (Basic Unit) as well as a Clocked (CLK) D Master-Slave Flip-Flop. The same conditions apply as in the first post, uploaded as is on the day when I constructed it.

Here is a schematic of a Clocked (CLK) RS Flip-Flop (Basic Unit) [Clocked RS Master-Slave Flip-Flop Not included] - some would call it a Clocked SR Flip-Flop, but it is exactly the same thing - S means Set and R means Reset. The same conditions apply as in the first post, uploaded as is on the day when I constructed it.

Thanks Tiffy,

These go right along with my "Digital Circuit" modules posted is User Examples.

Keep them coming!

Take care, BobF.....

Switching Problem with regard to using the MULTIPLEX PRIMITIVE.

DO NOT REPLACE THE SWITCH WITH A KNOB, AS IT WILL CAUSE HUNDREDS OF TRIGGERS AT THE OUTPUTS. THE SCHEMATIC WAS INTENDED TO BE USED WITH A SWITCH/BUTTON AS IS AND WITH ONLY TWO OUTPUTS.

I had a problem with the Multiplex Primitive in that I could not get it to clear any output that it was not switched to, as it remembered the input on all of it's outputs.

# This Multiplex Modification 2 produce much less triggers at its outputs than the previous version.

But be cautioned that you still have an additional trigger at the outputs, but that additional trigger is needed to clear/reset an output to which the Multiplex is not switched to. I don't think one will get it any better than this.

tiffy wrote:Switching Problem with regard to using the Multiplex Primitive.

This one is nothing new to the guru's, but in the beginning when I was a complete rookie with Flowstone (I never even used their previous software i.e. Synthmaker) I had a problem with the Multiplex Primitive in that I could not get it to clear any output that it was not switched to, as it remembered the input on all of it's outputs. So, here is a small schematic of what I did to rectify this, but maybe there is other better alternatives as well - I don't know.

Jeez! That's SO simple and yet SO effective

I came across that issue before and didn't think there was a solution so I just accepted it as a "feature" of the multiplex prim. I was expecting to find some real clever stuff in that trigger module but

I really do appreciate you sharing that. I've learnt something new and useful today; always a good thing.

What next?

Cheers

Spogg

Spogg wrote:

tiffy wrote:Switching Problem with regard to using the Multiplex Primitive.

This one is nothing new to the guru's, but in the beginning when I was a complete rookie with Flowstone (I never even used their previous software i.e. Synthmaker) I had a problem with the Multiplex Primitive in that I could not get it to clear any output that it was not switched to, as it remembered the input on all of it's outputs. So, here is a small schematic of what I did to rectify this, but maybe there is other better alternatives as well - I don't know.

Jeez! That's SO simple and yet SO effective

I came across that issue before and didn't think there was a solution so I just accepted it as a "feature" of the multiplex prim. I was expecting to find some real clever stuff in that trigger module but

I really do appreciate you sharing that. I've learnt something new and useful today; always a good thing.

What next?

Cheers

Spogg

The multiplexer really is a beast and I try to avoid it whenever possible. Tiffy provided a simple yet effective way of updating the states.

However, you have to realize that this is updating, which means additional triggers are sent. So for example the boolean section of the schematic (lower right): The boolean which is linked will send 2 triggers and the other boolean still 1. To compensate that you might want to add a trigger reduction, so that really only the boolean that gets linked will propagate a trigger through the schematic.
Regarding this very example, the trigger div prim with an integer set to 2 will do.

EDIT: When thinking about it, the trigger div won't do. There are 3 triggers to deal with, alternating as 1 and 2. But trigger div only sends each 2nd trigger, so +1 -> 0, +2 -> 1, +1 (now the total count is 4) -> 1, etc.
So forget about that. It needs another approach.

tulamide wrote:The multiplexer really is a beast and I try to avoid it whenever possible. Tiffy provided a simple yet effective way of updating the states.

However, you have to realize that this is updating, which means additional triggers are sent. So for example the boolean section of the schematic (lower right): The boolean which is linked will send 2 triggers and the other boolean still 1. To compensate that you might want to add a trigger reduction, so that really only the boolean that gets linked will propagate a trigger through the schematic.
Regarding this very example, the trigger div prim with an integer set to 2 will do.

EDIT: When thinking about it, the trigger div won't do. There are 3 triggers to deal with, alternating as 1 and 2. But trigger div only sends each 2nd trigger, so +1 -> 0, +2 -> 1, +1 (now the total count is 4) -> 1, etc.
So forget about that. It needs another approach.

It seems this is another optimisation opportunity then. I guess it only becomes important though if there's lots of trigger activity while playing a synth or using an effect. Otherwise, a trigger avalanche won't matter too much will it?

Cheers

Spogg