02-16-2010 05:29 AM
02-19-2010 08:21 AM
Hi Rainer,
the PCI-Bus does not limit the amount of DMA-Busmaster itself, but instead, the whole system does limit the transfer rates, bound to
the chipset, and the sharing of PCI-Bandwidth bewteen the PCI-Cards. So you can´t tell what the actual transfer rate would be without benchmarking it.
But there should not be a limit of DMA-channels in general. LabVIEW 32Bit can naturally allocate up to 2GB of RAM, but there is a switch in the windows boot.ini
which allows 32 Bit applications to use uo to 3GB of RAM. Naturally, a true 64Bit System can allocate much more RAM.
http://technet.microsoft.com/en-us/library/bb124810(EXCHG.65).aspx
Do you actually need to keep all the samples in RAM all the time?
Marco Brauner NIG
02-19-2010 09:49 AM
Hi Marco,
thank you, for yor reply. What you've written about DMA Channels meets my supposition. I will do several benchmarks and see what happens.
Nevertheless, the memory problem is getting more confused. In the time beetween my first posting and your reply, I found the article about the /3GB tag - and tried it. The result was really dissapointing. The maximum allocatible Memory for my application was LESS than without the tag...
But I did some tests with the LabView profile tool and found, that my assumption was correct with 8 Byte per reading of my sampled data. But now I'm helpless. The buffer memory that I allocated was less than 200 MByte but LabView suggested that there's no more memory available although my machine has 3 GByte of RAM!
For explanation, I attached several screenshots. My 'application' (LV Appl.bmp, only for test...) shows the six DAQmx VI and one for sampling clock generation (on top). The setup shows 5 MIO samplings and the assosiated screenshot (NoWork.bmp) the profile of the memory usage. Fault-1.bmp and LV Message-2 show the resulting error messages. Work.bmp shows the setup with 3 MIO samples that worked.
Have you any idea, what the reason for the memory limitation could be?
Best regards
Rainer