@compucat ,
Thank you for that !
Dammit, shoulda looked at the SHARC datasheet before posting…
As you say, it’s an understandable clunky/backwards fix to use the general ARM CPU for IR and capture calculation/computation…
I guess the only solution for now (for me) is to double up the IR blocks and use each block with 21ms portions of the IR (with a 21ms delay on the second one)…
Trying to find solutions here…
1 - Could this fix be implemented on a new IR or Capture block (that block being an “invisible to the eye” double block) ?
2 - Less development here : stop the IR upload limit (1024 actually) and add a start truncation knob to IR blocks. Let the user decide on the starting point and delay inside the IR block. That way the user could use whatever portion of the IR (in a double IR block for ex).
I’ve got a feeling we’re going to be stuck with “what you bought is what you got” but I’d love be wrong on this one.
Anyways, thanks @compucat