PulsePosition is incompatible with FreqMeasureMulti because they both use FTM0.
It would be nice to use FreqMeasureMulti to capture several individual pulsewidths, and output a multiplexed stream of them with PulsePosition.
FreqMeasureMulti is the more widely useful library, and it would be rare for a project to require more than one PPM input and one PPM output. Therefore, it makes sense for PulsePosition to use one of the other FTM modules with only 2 channels by default.
I've started working on that by copy/pasting all the FTM0 register configurations, changing 0 to 1,2,3 and surrounding with #ifdef. Then it occurred to me that you may have a broader universal plan for passing FTM arguments to your libraries. If not, it warrants some thought.
If requested, I will post post what I have so far.
PulsePosition is incompatible with FreqMeasureMulti because they both use FTM0.
It would be nice to use FreqMeasureMulti to capture several individual pulsewidths, and output a multiplexed stream of them with PulsePosition. FreqMeasureMulti is the more widely useful library, and it would be rare for a project to require more than one PPM input and one PPM output. Therefore, it makes sense for PulsePosition to use one of the other FTM modules with only 2 channels by default.
I've started working on that by copy/pasting all the FTM0 register configurations, changing 0 to 1,2,3 and surrounding with #ifdef. Then it occurred to me that you may have a broader universal plan for passing FTM arguments to your libraries. If not, it warrants some thought. If requested, I will post post what I have so far.