Hello DSPC Team,
Is there a way to control the order of execution between 2 not-wired modules?
For example, in the layout attached, can I have the 'Arrayset1' module change the 'FirCoeff' module buffer values before the 'FirCoeff' module writes them to the SinkProperties1 sink module?
Can the order of execution be:
1. Copy data from 'SourceProperties1' to 'Arrayset1'.
2. Copy data from 'Arrayset1' to 'FirCoeffs'.
3. Copy data from 'FirCoeffs' to 'SinkProperties1'.
Thanks,
Sharon.
1:32am
Hi Sharon,
You should be able to do this utilizing the control pin on the ArraySet module and if your use case requires it, logic modules:
The optional control pin enables copying the input data to the MOD.VAR array when the first value of the control pin data !=0.
Thanks,
Kevin
3:25pm
Thanks for your reply Kevin,
Still, the data that will be written to the SinkProperties module are the data that was stored in FirCoeffs at the beginning of the current sample processing.
The flow of the process stays the same. I want to change the flow. I want the the data from 'FirCoeffs' will be read after it was written by 'Arrayset'.
I want the flow of data to be:
SourceProperties1 -> Arrayset1 -> FirCoeffs -> SinkProperties1.
All in the same sample processing time.
Thanks,
Sharon.
5:34pm
Hi Sharon,
In the Build tab of Properties window, you can set the FiirCoeffs clockDivider to 1B. This will effectively split the AWD into 2 layouts, and when running the AWD on a single target (no parallel processing on different cores or in separate threads) the modules in the 1B layout will execute their processing functions only after all of the 1A modules execute. Both layouts will operate at the same sampling rate and block size.
Thanks,
Michael