LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

writing to 6534 memory

How do I write to a PCI-6534 card's onboard memory in LabVIEW? Is this done using the Buffer config VI? I can't seen to find any information in any of the manuals.

Thanks
0 Kudos
Message 1 of 5
(3,045 Views)
Use the "DIO Write" VI. The output from the PCI-6534 is started with the "DIO Start" VI. Look at any of the Buffered Output DAQ Examples. You can find them by selecting Help/Examples... and choosing I/O Interface Examples then DAQ Examples. The VIs Documentation explains things fairly well.

Kelly Bersch
Anadigm, Inc.
Message 2 of 5
(3,045 Views)
Hello;

You can refer to the Pattern Output Generation.vi as a start point for your application.

In case you have less than 32 M bytes of data to trasnfer out, you can even enable the loop generation of the board. That will make the transfer to be completely system independent, since all the data will be dumped to the on board memory.

Hope this helps.
Filipe A.
Applications Engineer
National Instruments
0 Kudos
Message 3 of 5
(3,045 Views)
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
Message 4 of 5
(3,045 Views)
By the way, Lei, the answer is that the function calls are the same and the drivers "just know" where to write the buffer. -jayme
jc
Mac 10.4
LV7.1
CLD
0 Kudos
Message 5 of 5
(3,045 Views)