Petr Hradsky Thank you for your response – When we are developing with Code warrior and PE we often build simple separate test project - Test_Componets with not much in there so if the code/component that we think we need does not work (Which seems to be always the case) we use the great help typical usage code to try in understand what we do not understand about the functionality of the Component (bean) we are using (and start off simple as possible minimal interrupts and no RTOS)
In the case of the Real Time Counter (RealTime_LDD) we want to use this for our sample rate so that we could adjust how many samples we would take from ADO (Hall effect sensor input) and FTM 1 (Linear Quadrature Encoder input) and also output them DAC0 and DAC1 outputs so we could look at them on a conventional scope (or what we are doing now is getting AS1 to work so we can output them to a terminal and also use Freemaster)
So the problems we saw with the using the RealTime_LDD component are:
This thread - We could not get it to work with using the default FTM0_MOD it did work with FTM0_C0V
AND - In addition as we were testing we saw that the sample rate we would expect with the property setting of Resolution 1 usec Resolution 1 us – (actual shows – 1.001 us) – This would not put out correct timing (1 usec) on our production code. To get correct timing (as verified by DAC1 output an scope comparing traces of Un-sampled signal (DC to 1K Hz) input ADC0 output DAC0 with sampled input ADC0 output to DAC1) needed to use -Resolution 100 us – (actual shows – 99.993 us)
Attached are the properties listing that we are using and the Help example code that worked in our initial testing (here for convenience.)