Allocate device memory at PXI 6115

Hallo,
I am using one PXI 6115 to acquire data. The acquisition is external clocked with 8 MHz. It should be triggered by an external digital trigger, and be able to read pretrigger scans.
Now I have 2 Problems:
1. The Trigger occurs only once a day or once a week. What can I do to prevent my application to run into timeout error ??
2. I want to measure about 200 ms of total time, meaning this are 1.6 million of sampling point per channel. For this reason I tried to allocate device memory, but I am getting always error messages (running in pretrigger mode; Error 10403)
Can anyone give me some hints or tips?
Many thanks Ruediger

Hi Ruediger,
The PXI-6115 is capable of doing an 8MHz digitally triggered analog acquisition assuming your system requirements do not restrict the acquisition. Below are answers to your specific questions:
1. Depending on the driver you are using, you can avoid a timeout error:
NI-DAQmx: Setting the timeout limit to -1 will tell the VI to wait indefinitely.
Traditional NI-DAQ: Unfortunately, there isn't an infinite wait time for traditional DAQ VI's, but the input for the timeout limit is a single precision number, so you can make it extremely large (2^32 seconds).
2. You should be able to acquire this much data. How large of a buffer did you use, and did you allocate the memory in the system or on the card? Allocating a larger buffer may eliminate the e
rror.
Thanks for contacting NI,
Marcus G.
Applications Engineer
National Instruments

Similar Messages

PXI-4461 Onboard device memory underflow

I am using a PXI-4461 to generate an aquire a singal. When i generate the signal i get error -200621( onboard device memory underflow) onDAQmx Stop VI. I donot understand what the error means.
Signal Information
Signal Type=Sine Wave
Frequency=3K
amplitude=0.3V
Sampling Rate=48K
Number of samples sent=48000 or 1sec
I have tried reducing my sample rate to 20000 but that didnot help much. How do i get rid of this error
I have attached an picture of my vi below
Thanks. Any help whould be much appreciated.
CS
Solved!
Go to Solution.
Attachments:
Code Image.png ‏82 KB

Welcome and thank you for using the Discussion Forums! This error is most likely due to the non-regeneration property you have set. What's happening is that LabVIEW generates your two sine waves continuously, but slower than the update rate of the DAQ card, so the buffer gets empty before it can write enough samples to the buffer so that the 4461 can keep generating the voltage values on the channel.
What you could do is simply set the Regeneration mode to "Allow Regeneration". I tried the non-regeneration and regeneration property on the "Voltage - Continuous Output.vi" and it works with regeneration enabled.
Regards,
Daniel REDS
RF Systems Engineer
Help us grow.
If a post solves your question, mark it as The Solution.
If a post helps, give Kudos to it.

Generate PXI Trigger Signals with PXI-6115

Hello,
I have a question.
I have a PXI-6115 and some other card in my mainframe.
These other cards nee 10 Mhz pulses on line PXI-Star1 and 2.5 MHz on PXI_trg7.
So I thought to apply (somewhere on my PXI 6115 card) 10 MHz, divide the 10 MHz with a counter to 4 and route all this things to the backplane.
But I don't understand how to do this.
There are no good examples.
And as far as I know the PXI-6115 isn't yet supported by DAQ-MX.
Can anybody give me some good advises or tips, white paper or so to make me solve my problem ???
Thanks Ruediger

I don't have time to write any example snippets right now, but I'll try to provide you the general idea and hopefully you can take it from there.
First, it's not clear whether you want to generate the 10 MHz from the 6115 and send it to other devices in the system or accept the 10 MHz externally and route it to the rest of the system. If you're bringing in the signal externally, I would simply using the DAQmx Connect Terminals VI to route the signal from a PFI line on the front connector of the board to one of the PXI trigger bus lines in the backplane. Check out the routing table in MAX to see what routes are possible. To perform this route, the driver will have to route through Counter 0 so you won't be able to use Counter 0 for anything else.
If you want to generate 10 MHz from the 6115, I would create a continuous pulse train task on Counter 0 using the CO Pulse Ticks version of the Create Channel VI with a value of 2 for both the high ticks and low ticks input. However, to achieve 10 MHz clock on a PXI trigger line, you'll have to perform a couple of modifications that typically aren't done with counter tasks. First, you'll need to use the DAQmx Export Signal Property Node to route the Counter Output Event to the desired PXI trigger line. You can find this property by navigating the following menu hierarchy Events->Counter Output Event->Output Terminal. By default, the driver routes this event to the Ctr0Output pin on the front connector of the board. Using this property will override this behavior and route the output of the counter to a PXI trigger line instead. Second, you will need to change the output behavior of the Counter Output Event from toggle to pulse. This can be through the Events->Counter Output Event->Output Behavior property. Normally, when generating pulse trains, the high ticks and low ticks parameters from the Create Channel VI determine the frequency and duty cycle of the pulse train. When the high ticks count expires, the output of the counter toggles. The low ticks value is then loaded into the counter, and the counter output toggles again when the low ticks value expires. This process repeats to produce a pulse train of the desired frequency and duty cycle. Since the counter uses a 20 MHz timebase and has a minimum low ticks and high ticks value of 2, you can only produce at maximum a 5 MHz pulse train using the toggle behavior. However, by changing the output behavior from toggle to pulse, the counter output will issue a short pulse each time the high ticks and low ticks counts expire yielding a 10 MHz clock signal.
Now that you have the 10 MHz signal taken care of, you need to generate a 2.5 MHz signal from it. My guess is that since you have a 6115, you already have plans for the AI engine so I'll describe a route that uses AO instead. First, create an AO task to perform continous waveform generation. Use the DAQmx Channel Property Node and set the Use Only Onboard Memory property to true. Setting this to true will cause the driver to download the waveform once upon starting the task and replay the waveform from the onboard FIFO. Since you're only using this task to generate a clock, you don't really care about the data and this will prevent unneccessary traffic across the PCI bus. Next, use the DAQmx Timing Property Node to set the Sample Clock->Timebase->Source to the PXI Trigger line that you're generating the 10 MHz clock on, and set the Sample Clock->Timebase Divisor to 4 (10 MHz / 4 should give you a 2.5 MHz sample clock). Last, use the DAQmx Export Signal Property Node to set the Clocks->Sample Clock->Output Terminal to the PXI Trigger Line you want to generate the 2.5 MHz signal on.
It requires some creative programming, but you should now have a 10 MHz and 2.5 MHz signal routed onto two different PXI Trigger lines. I know this solution is a bit involved so if you have any further questions be sure to post back.

PreTrigger Mode for PXI 6115

Is there a plan to make the PXI 6115 module run in the pretrigger mode in combination with the onboard memory in a further version of NI DAQ?
We are planning to build a fast Transient recorder with the PXI 6115 module.
We bought this device because we had the opinion that it is able to run either in pre and in post trigger mode.
As I learned in the last weeks is only possible to use the onboard memory when I�m using the post trigger mode.
Is there a hope of getting pretrigger events?

I was browsing through and saw this post from some time ago. This feature was added to the DAQmx driver in NI-DAQ 7.4. In fact, this behavior is now the default for all pre-triggered acquisitions (this is know as a reference triggered acquisition in DAQmx) in DAQmx. When in this mode, no data is transferred from the device to the host until after the acquisition completes. This eliminates bus bandwidth limitations as the number of devices in your system increases.

Why wont Labview recognize my PXI 6115 DAQ slot?

I have a PXI 6115 card that is placed in a PXI-1042 chassis. Everything is plugged in and turned on but the DAQ assistant doesnt recognize that it is there. HELP!

Hello Joe,
I have a
couple questions that may help diagnose this problem:
1. Does the
PXI-6115 show up in Windows Device Manager? This will tell us if the controller
is recognizing the card.
2. Does the
PXI-6115 show up in Measurement & Automation Explorer? This will tell us if
the card is being associated with the driver.
3. What
version of the NI-DAQmx driver do you have? The PXI-6115 is only supported by
newer versions of NI-DAQmx. If you have an older version, it may not be
supported. I would recommend visiting the driver download page here to make
sure that you have the latest version of your drivers.
Matt Anderson
Hardware Services Marketing Manager
National Instruments

PXI-6115 input voltage range configuration help

I need to set the analogue inputs on my PXI-6115 to +/-42V, however using Measurement & Automation Explorer, under Traditional NIDAQ Devices - PXI-6115- Configuring Device 1 : PXI-6115, Analogue Input Tab, the Polarity / Range pull down menu only has -10.0V - + 10.0V available for selection. Any help gratefully received.

Hi,
The range inside of MAX should read +/- 10 V, the range of the card with a gain of one.
To see a larger range in your application, you must configure the gain to be less than one. For example, the NI 6110 supports gains of 0.5 and 0.2, which allow ranges of +/- 20 V and +/- 50 V. (Remember that the card supports a maximum of 42 V.)
Depending on the range of your input signal, you would want to use the following gain setting:
Range
Gain Setting
-50 to 50 V (not to exceed +/- 42 V maximum)
.2
-20 to 20 V
.5
-10 to 10 V
1
-5 to 5 V
2
-2 to 2 V
5
-1 to 1 V
10
-500 to 500 mV
20
-200 to 200 mV
50
To set the gain in LabVIEW, use the Hardware Configure VI and set the input range of the signal you want to measure, and the VI will select the best gain. Refer to the link below for an example.
To set the gain using NI-DAQ Function Calls, pass in the gain as an integer. If the gain is 0.5 or 0.2, pass in a -1 or -2 respectively.
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E8A156A4E034080020E74861&p_...
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

How do I allocate more memory to my 1st Gen and 4th Gen to stop Safari crashes?

How do I allocate more memory to Safari to stop opening crashes?

Have you tried any troubleshooting?
Restart: Press On/Off button until the Slide to Power Off slider appears, select Slide to Power Off and, after It shuts down, press the On/Off button until the Apple logo appears.
Reset: Press the Home and On/Off buttons at the same time and hold them until the Apple logo appears (about 10-15 seconds).
Restore: Connect your iPhone to iTunes on your computer, backup, and then select Restore to Factory

How do i allocate more memory to my iphoto application? i am unable to add more photos to my library i keep getting a pop up saying not enough memory in my application

how do i allocate more memory from my hd to my iphoto application? i have over 80 gb on my hard drive, but only 1.7 gb allocated to my iphoto application & i am unable to add more photos to my library. i keep getting a popup that says not enough application memory.

There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
A long-running process with a memory leak (a kind of bug)
Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 ("Mavericks.") The procedure may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

Error while creating Move-In - How can i Allocate Device to Installation ?

Hello Experts,
while creating Move-In i am getting following Error "No Devices Allocated to Installation PC0301A0 on 10.03.2011"
How can i allocate device to installation, please advise where can i configure the settings and create Move-In without above error.
Regards,
Rajesh. G

Hi Bill,
Thanks for your responce it was helpfull, but i am trying to create Move-In with help of Contract Account. I was not able to create Move-In and i tried even with Bussiness Partner.
When i was trying to create Move-In with the help of Business Partner Option in Move-In i am getting error as "The required index has not been created yet in the search Engine", same is happening when i am trying for Business Partner in Business Master Data. This might be the reason for Move-In creation Error, please help me where can i configure index settings for search engine for Business Partner.
Please correct me if i am wrong.
Thanks,
Rajesh Gunda

Mysterious 'android' folder in device memory that cant be deleted

hi... i have a bb q5 and been using it since 2-3 months now... there is an 'android' folder that appears in the 'misc' folder of the device memory. i cant get rid of this from the bb file explorer as well as from the laptop. when i try to del it, it say permission denied. i guess it started when one of my friends used my sd card in their android based phones. this folder contains all those folders that are there in the device memory like photos, camera, music etc. and some other folders like dcim, notifications. sometimes it shows 11 items inside and sometimes 12 or 13. i dont know if it's a bug or something but it seems quite irritating as it contains nothing space wise. i cant del it from my laptop bcos when i press del, nothing really happens and its still there... so pls can anyone help get rid of this...

It's my understanding that folder is there for access by the Android runtime software.
Leave it.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Insufficient Device Memory to Update to 10.2.1

I went to install the new update (10.2.1.537) onto my Q5 through my phone, received the notification telling me device storage was almost full and the install failed.
I then cleared out my device memory, moving everything I had access to onto media card or simply deleting it.
When I go to install the update now before it begins it asks me to free up around 1.1-1.4GB (the exact value varies between attempts) of space on device memory even though I already have 1.5GB free and it says the size is 1008MB.
I have very few apps installed and most aren't very big (all below 50MB if you exclude BlackBerry Runtime for Android.) I also tried deleting email accounts and message history in Whatsapp but they made very little difference.
Of the 8GB total space 6.3GB is taken up by "Other data" and looking in file manager seemed to show 3GB of this was from the Device/misc/android folder in the form of hidden files. (Not within any of the folders inside the android folder.) All other device folders are completely empty as far as I can see.
Any advice of how to make up the space so I can upgrade would be really appreciated as I'm at a bit of a loss now.
Thanks!

Hi, sorry it took a while to reply but this was a bit of a lengthy process. Worked like a charm though, thank you ever so much!

While sync : can't allocate more memory !!!(WCE)

Hi All,
I'm synchronizing (/Orace/mSync.exe) several MB of data (not much more of 10 MB) on a CASSIOPEIA E-200 (64 MB) with a SD Card extension of 128 MB. While synchronizing, main memory decreases dramatically (main memory, not external memory) and finally i get the message:
-2000 can't allocate more memory -2000:0
Other synchronizations with a smaller amount of data are working ok.
It is posible for a sync of ~10 MB to drain >40MB of main memory?? !!
By now, i'm using the SD Card directory to store the synchronized client DB, but this is not enough to solve the problem.
I think that temporary files and processes on main memory are involved in this problem. It is posible to use memory cards for this??
Some ideas????
Thanks in advance.
Andris

Humm,
I think the problem may be the size of a single table replication.
The replication of 10000 registers from this table is working ok, but replicating 25000 i get the error ("Can't allocate more memory").
Anyone knows a limitation in the number of registers or size of a table replication????!!!
Thanks!!
Andris

Pushing the limits of continuous high-speed DAQ + processing, with PXI-6115 + PXI-8360

Hi all,
I'm trying to do continuous high-speed data acquisition + processing. I currently have:
Chassis: PXI-1042Q
AI card: PXI-6115 (x2)
Link: PXI-8360
PC CPU: Intel Xeon W3503 (dual-core, 2.40 GHz)
RAM: 4 GB
The idea is to continuously grab 8 channels' worth of analog inputs, scan for "events", and if found, log the events to disk.
My client would like to use the maximum sample rate of 10 MHz, but I found that above 5 MHz, DAQmx Read.vi can no longer keep up (e.g. at 6 MHz, it takes 110 ms to read 100 ms' worth of data).
Im thinking of getting beefier components, but I'm not sure where the bottleneck is. Here are some thoughts:
1) The MXI Express link
The PXI-8360 is rated for a sustained throughput of 100 MB/s.
I'm not sure how big the data is. PXI-6115's ADC is 12-bit. Does that mean each datum transferred through the MXI cable is 1.5 bytes? Is the data padded? Or is it 8 bytes per datum, because Dbls are being transferred?
2) The CPU
In Resource Monitor, I notice that the CPU usage is 0% at 60 kHz, 8% at 61 kHz, and 50% at 70 kHz (meaning that one core is maxed out). I'm surprised that it keeps up all the way until 5 MHz though.
What causes this high CPU usage? Is it due to the conversion of the data into 1D array of waveforms?
3) Something else?
Have I missed something completely? Is what I'm describing even possible?
Thanks in advance for any advice!

Hello,
Each sample will take up 2 bytes, 12 bits data + 4 empty bits. so the PXI-PCI 8360 is only able to transfer a maximum of 50S/s in this case.
Also, because the PXI bus is shared among all of the cards, two PXI 6115 cards will be trying to transfer 80MS/s or 160MB/s.
Finally, since the PXI 6115 are DAQ family cards, their specifications aren't really written for continuous data acquisition at the upper end of their sample rate, but I'm interested to know if you can get up to 10MS/s with only one card operating at a time?
-Jim B
Applications Engineer, National Instruments
CLD, CTD

PXI-6115 & PXI-6143 on Same Computer, RDA's Future

Today I installed several PXI-6115 cards and realized that they are only
supported with traditional DAQ under version 7.2. This is OK for now
because I'm already limited to traditional DAQ to be able to use RDA.
However, I was considering adding the new inexpensive S board, the PXI-6143,
to my system. According to the list of supported boards this board is only
supported by DAQmx. Questions:
1. How can these two S boards be used by the same system if programming with
LabVIEW?
2. Any guesstimate on if or when the PXI-6115 will be supported by DAQmx?
3. Any guesstimate on if or when RDA will be supported by DAQmx? RDA
(remote data acquisition) is an extremely valuable DAQ method and I hope it
will be supported by D
AQmx soon!

Hello,
You are correct about the support of both boards. The 6143 is only supported in DAQmx, and the 6115 is only supported in Traditional DAQ. Here is the best that I can do for the other questions.
1. You can program each card in a different driver. This is not a problem at all. The only conflict occurs when you try and program a card in both drivers at the same time. Such as trying to do analog output in Traditional DAQ and analog input in DAQmx.
2. This is internal information only. For further information I would contact your local sales representative, she/he might be able to assist you further.
3. Again, if and when is internal information. It is not currently supported. At the moment, you can use remote front panels, or create y
our own server/client VIs to control a remote DAQ board.
These are excellent pieces of feedback for our R&D department. I highly encourage anyone who reads this thread to submit product feedback using this link.
Best regards,
Justin T.
National Instruments

ORA-29855 - Unable to allocate shared memory

Hi,
We are encountering troubles (unable to allocate shared memory) while indexes creation. We tried to increase the share_size_memory (actually 52 mb) but this had no effect on this error. The Oracle error code is ORA-29855.
The database is version 8.1.7, hosted on a Linux machine (RedHat 7.2) with 512 mb of memory. The code used for the index creation works fine on other machines (code from 9iAS Wireless installation) running with Windows 2000 as operation system.
Any help or comment will be appreciated.
Thanks,
Fabrice Clari.
The error message is:
java.sql.SQLException: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13200: internal error [ROWID:AAAGDwAAFAAAAvjAAA] in spatial indexing.
ORA-13206: internal error [] while creating the spatial index
ORA-13011: value is out of range
ORA-00600: internal error code, arguments: [kope2ucoll700], [], [], [], [], [], [], []
ORA-04031: unable to allocate 16396 bytes of shared memory ("large pool","unknown object","koh-kghu sessi","kolcalm coll")
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 8
ORA-06512: at line 1

Which portion of shared memory did you increase? The error indicates you need to increase large_pool_size. It seems you may also have other problems since you have several errors, and this only relates to the ORA-04031 error.

Allocate device memory at PXI 6115

Similar Messages

Maybe you are looking for