If one has any idea about some workaround, please let me know.
At the moment, the only one I think about is to use the trigger SMB connector on the cRIO. A set of Vis is available on the NI website for that use, but the link is not valid !!
We have some known issues with DAQmx 8.7.1f2, but I doubt this is your case. However I advise you to get the latest version of it here : NI-DAQmx 8.7.1f3 .
Moreover, could you update your version of NI-RIO to the latest one here : NI-RIO 2.4.1 .
After all these installations, could you tell me if you still encounter the same problems ?
I don't think upgrading to NI-RIO 2.4.1 will help you in this particular case so I would hold off on trying that troubleshooting step for now. Your correct that if your reading 9205 AI channels with 4 usec convert rates you should be able to get an aggregate rate of 250k, which for two channels would be 125k per channel. If you add a third channel it should be 250/3 per channel, which from my understanding should include reading the DI channel.
Is it possible you could post some test code to help us all better understand how your using the IO nodes?
I know you mentioned you were using 4 usec convert rates but the project attached has them set for 8 usec and I couldn't find anyplace where they were being set programatically. Can you try the attached project with your module and let me know how many ticks it takes to perform the AI/DI reads?
You are right : the test project I posted sets the 9205 interchannel delay to 8µs (default value) instead of 4µs as I set it in my real project.
However, you can reproduce the problem even with the 8µs setting. If you want to test it with 4µs, you can just change the static setting in the project (I did it that way, not programmatically).