I'd like to revisit the subject of my previous thread which was never resolved; unfortunately I wasn't able to work on this project for some time and so the thread has been locked in the meantime, so I'm starting a new one. the original is here.
To answer Dylan's questions from his last post, the mode pins are indeed remaining unchanged, and as far as the relationship between the time the output stays low and the input frequency, I can give for example the case of a 29.9kHz input causing the output to stay low for 355ms, so presumably about 10600 cycles (29.9kHz x 355ms).
To clarify my design goals: my max input frequency is 154kHz, and the max rate at which I'd like to change the jam inputs is about 100Hz.
Through my testing, I've observed that the slower and slower I limit the rate at which the jam inputs can change, it seems that the freezing happens less often. However, I've still observed cases of it freezing even with the fastest changing jam input being something like 55ms (and even that's changing not periodically, but rather sporadically). So unfortunately I'm well off of my target 'refresh rate' for the jam inputs.
One thing I'm wondering is whether there's any chance that the fact that I'm changing several jam inputs at once is also potentially contributing to or even causing this issue? When the jam inputs update happens, I update all of the inputs one after the other pretty quickly (I haven't measured the delay but I believe it should be <50us). I'm wondering if there's any merit in investigating cascading the jam input update; for example, if I inserted a 1ms delay between changing jam inputs. I have 8 inputs to update, so I could still execute the update in ~8ms, achieving my target goal. But if the root cause of this issue is rather just any jam input changing too quickly, then this would actually make the problem worse.
Any further insight on what could be causing this issue, and suggestions for what to try, would be greatly appreciated!
