What, specifically, is your "exact same problem."
If you want the two measurements to be sync'ed and properly *correlated*, you need to deal with a few distinct things properly:
1. Share a sample clock signal so both tasks sample at the same time.
2. Start the tasks before starting the sample clock (if possible).
3. Read the same # samples from both tasks to keep the data *correlated*.
4. Make sure the initial data is also properly correlated. This one takes a little explaining.
When you start the task, the counter will start tracking encoder position immediately, even in the absence of a sample clock signal. The 1st sample will reflect the amount of motion that happened between task start and the 1st sample clock signal.
One way to deal with this is that both tasks can subtract off this 1st sample value from all its measurements. This is analogous to a "tare" operation on a weight / force measurement.
Another way to deal with it is to configure both tasks to use the same "Arm Start" trigger. This lets you control when the encoder tasks start tracking position. Again, this is separate and distinct from sampling the position value.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
