Support

If you have a problem or need to report a bug please email : support@dsprobotics.com

There are 3 sections to this support area:

DOWNLOADS: access to product manuals, support files and drivers

HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects

USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here

NEW REGISTRATIONS - please contact us if you wish to register on the forum

Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright

What To Do When Value Doesn't Propagate

For general discussion related FlowStone

What To Do When Value Doesn't Propagate

Postby Perfect Human Interface » Wed Dec 17, 2014 10:17 pm

Definitely one of the most frustrating problems I've run into while working in Flowstone is when a value doesn't propagate correctly through a schematic. It will seemingly get stuck at a specific point where the next node doesn't receive the correct value unless you manually click on it, even though everything connected before it has updated correctly. It of course doesn't appear to make any sense, but there does seem to be a solution.

When you find the point at which the value looks to be stuck, place a trigger blocker in the connection between it and the previous node. Then, wire a "trigger pass" (a module that contains only an input wired to an output with both nodes set to trigger) from the beginning of that block of code (e.g. the input of the module you're working in) to the node after the trigger blocker. Make sure this trigger link is connected last.

Cross your fingers and test your schematic again, and hopefully things will be working without a hitch now.

My hope is that if anyone else is finding themselves frustrated with this sort of issue they'll find this post!
Perfect Human Interface
 
Posts: 643
Joined: Sun Mar 10, 2013 7:32 pm

Re: What To Do When Value Doesn't Propagate

Postby JB_AU » Thu Dec 18, 2014 12:11 am

Thankyou! :D
"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."

Albert Einstein
User avatar
JB_AU
 
Posts: 171
Joined: Tue May 21, 2013 11:01 pm

deleted by uploader

Postby tiffy » Wed Dec 31, 2014 12:08 pm

deleted
Last edited by tiffy on Mon Aug 24, 2015 7:51 pm, edited 1 time in total.
User avatar
tiffy
 
Posts: 400
Joined: Wed May 08, 2013 12:14 pm

Re: What To Do When Value Doesn't Propagate

Postby Perfect Human Interface » Wed Dec 31, 2014 12:54 pm

The trigger blocker is useful for when you want to control when something updates or limit triggers. Basically, you'd feed triggers from somewhere else. That way the value updates from the "somewhere else" triggers rather than passing the triggers you've blocked. A common example would be when redrawing GUI elements; because redraws are expensive and you might be sending 500 triggers in a second to a redraw even though your monitor can't refresh faster than 60 times a second, it's much better to just block the triggers and then feed more controlled triggers from a ticker instead.
Perfect Human Interface
 
Posts: 643
Joined: Sun Mar 10, 2013 7:32 pm

Re: What To Do When Value Doesn't Propagate

Postby billv » Wed Dec 31, 2014 7:18 pm

tiffy wrote:I still don't understand the logic behind the need for a trigger blocker in any schematic

Trigger blocker is awesome.... combined with a s+hold you can easily control
how your circuits behave.
Trog's Trigger Tutorial is a must read....explains it all really well..he even breaks down the trigger order
with pictures so you can see how the signal moves..
http://synthmaker.co.uk/forum/download/file.php?id=6297&sid=e1d16e22338a5329b1b59032efbcae75
billv
 
Posts: 1157
Joined: Tue Aug 31, 2010 3:34 pm
Location: Australia


Return to General

Who is online

Users browsing this forum: No registered users and 79 guests