David: Thanks for taking the time to whip up a sample, unfortunatly I do not have access to LabVIEW as I am writing my application in C++ with the NIDAQmx driver.
As to my timing diagram, I have included it below. There are two different types of commands that I can do, a "read" and a "write." When doing a "write" I don't need to acquire any samples from the DUT. When doing a "read," I generate 2 samples, followed by acquiring two samples. The top bar represents 8 bits of input data, DUT -> 6536. The second bar represents 8 bits of output data, 6536 -> DUT. The RD, DS and EN bit are all generated by the 6536.
By overflow/underflow conditions, are you refering to write and read buffer issues? If so, I dont think I have to worry about them. I just want to issue one of these commands and hold until I want to issue the next command. (Which at its most basic is keeping EN high I guess.)
Thanks for the help.
-Rob
