Hi,
DAQ operations are processor intensive, usually in a DAQ program you can see your CPU jumping to 100% for a high period of time. In most cases having two different operations running on the same program does not gives any problem, but programming techniques and running conditions can cause misbehaviour. In your case in which you are combining DAQ and Motion on the same program, I would advise that you make all your Configuration at the beginning of your program, my guess is that when calling DIO Port Config the processor is completely focusing in the DAQ portion and leaving the Motion board careless causing some reset condition on the encoder registers. Make sure that you have the latest drivers for both DAQ and Motion (6.9.3 and 5.2) and make sure your LabVIEW is s
et up for multithreading. If putting the configuration VIs at the beginning of your program does not helps, then run two VIs simultaneously and lets see what happens. Board ID and Device number are NOT related, you can have motion board ID = 1 and DAQ device = 1 and should not have any issue.
Good luck!
Nestor.
Nestor