DSP Robotics Support

...may require some updates?

Different output vs different reading. Play with input values 0-2.

Well spotted! - very strange behaviour, usually it matches exactly with a regular trigger counter, and I can't make sense yet of why an extra S&H makes the difference!

I bet that this might have something to do with recent FS updates. Thus - other tools might need to update too.

It partially works in SM, i.e. shows correct values but wrong amount of triggers. I remember there was some change in boolean and/or trigger behaviors between SM and FS3. BTW, why would you not add the S&H on input in your tools by default? Should not the inputs be rather separated from what comes in?

I've isolated the issue. The "Last Switch" primitive somehow blocks duplicated triggers (or maybe it limits the frequency). I've attached a demonstration.

As far as I can remember, this is a new behaviour. Don't think that this is correct.

Edit: Last S|M Version has the same behaviour... so this change was long time ago.

Somehow "switch" behaves logical to me. It reduces... "entangled triggers"
(a series of triggers associated with 1 value resend?).

But more seriously. If the issue is the same in SM and FS, then why Troggies tool behaves differently in SM and differently in FS?

So it looks, that besides the trigger queue - there might be something else (a marker), that determines triggers as separate "dots" or as a "series". That behavior would explain why adding a timer for "trigger separation" I used in some places - makes the change no mattero how rediculous it sounded.