Strange bug with timer and oneshot
Intent was to vary the timer so the first time at turn-on, it only does a short mute, and then for a fault during normal operation, it does a much longer mute. So I made this circuit, and it behaves bizarrely. On turn-on, the OneShot timer rises to 1 after the 2 second delay, even though the Timer output that's driving it doesn't rise to 1 until the 10 second delay. The OneShot is predicting the future?
After turn-on, the OneShot stays forever on, and switching the switch causes the Timer to change after a 10 second delay, which is as expected.
So I think it's a bug? I'll try to find another way to implement the desired function
bug_report
sigma studio
Tried another method and it's also having problems.
Readback shows that ABCD is outputting the smaller time constant at turn-on, yet the Timer2 is initialized with the larger one.
Maybe the ABCD block outputs the wrong value for one sample at turn-on or something? Putting a Peak Hold on it doesn't show this happening, though.
Oh I think I know what's happening. The timer is switching to 1 output, for one sample, but then its time delay changes, which causes its output to go back to 0 and wait for the new time delay to finish. Changing the time delay causes it to act as if it had been triggered with that time delay instead, even if it hasn't been triggered again since it last went high.
Timer w/ External Reset
This question has been assumed as answered either offline via email or with a multi-part answer. This question has now been closed out. If you have an inquiry related to this topic please post a new question in the applicable product forum.
Thank you,
EZ Admin
Please log in to reply.



