Closed leoscholl closed 3 years ago
the temporary solution to this problem is to only send one command to the nidaq at a time. to do this, the clock is now also a single 3 ms pulse for each cycle rather than a single low-high or high-low transition on each cycle.
the long term solution is to buy another nidaq card to use for anything we need to be independently controlled, since it seems this is just a limitation of the device and/or driver.
change was made in c198e86819547757ce3a8cdf6fbff16175dab8a9, sync version >= 1
Examples:
Data is on channels 17-24 Clock on channel 25
The clock signal is being overwritten by the data pulse