Your question is the same as mine, paraphrased as "What special procedure must I follow to get the buffer written to on-board memory?" I want you to know that I think your question makes good sense and points to a shortcoming in the documentation.
Your experience is the same as mine, i.e. (in the documentation) there is no distinction between the 6534, which has on board memory and the 6533, for example, which has no on board memory. There is nothing that ships with the 6534 that explicitly addresses this issue, other than a few brief comments in the 653x manual. For instance, on p.2-22, the manual indicates that a person wishing to output the same block repeatedly with the 6534 must set the Pattern Generation Loop Enable attribute to ON. There is no comm
ent that indicates that the function calls would otherwise be identical. Furthermore, the DIO pattern generation examples all utilize the half-buffer writing strategy to stay ahead of the output. There is no description of how this strategy changes with the on-board memory capability. It is not intuitively obvious that the identical software calls would write to PC memory or on-board memory. It is apparently left to the programmer to surmise that the destination of the buffer in the "DIO write.vi" is determined internally by the particular hardware being controlled. In the case of the 6534, it goes to on-board memory. In the case of the 6533, it goes to PC memory.
jc
Mac 10.4
LV7.1
CLD