DAQmx period measurement- buffer is cut when frequency is too high

Hello,
I'm using the DAQmx period measurement in order to measure a low frequency pulses. Even though the average frequency is low I still sometime get two pulses that arrive within a short time . When that happens I get an error message and the buffer is cut. I'm wondering if there is any way to ignore one of the pulses (in the case that the pulse arrives at a time that is too short for the program to read) and for the measurement to keep running until the buffer is full??
Thank you ,
Shafran

Hi all, thanks for your help.
I'll give more details:
1. I'm using PCI-6602
2. The error code number I'm getting is: 200141       Possible reason(s):
                                                                                     Data was overwritten before it could be read by the system.
3. I'm measuring photon emission from biological samples where each photon is converted to a pulse of a 35.2 ns width. I can control the concentration of the sample and therefore the average frequency of the pulses. I have started with an average intensity of 100 kHz and I went down to 10kHz. My final goal is to run the period measurement program in loops where I decide the buffer size so each loop will take approximately 10 seconds. The problem is that even if one out of all the buffers is cut all my calculations after that are wrong. A filter sounds like the perfect solution for my problem (I need to find out more about that option).
4. I have checked the limitations of the program and I know that it can't measure pulses that arrive at a higher frequency than a few MHz, therefore I assume that even at an average frequency of 10kHz I still get some pulses that arrive within a frequency of a few MHz.
Thanks again for all your help. I hope I didn't bore you with to many details...
Shafran

Similar Messages

BluRay error message "code 6, audio buffer underflows. Total bitrate is too high near time = 000000 seconds."

Hello,
I’m trying to create BluRays using Encore and I keep getting the following error messages: ‘code 6, audio buffer underflows. Total bitrate is too high near time = 000000 seconds.”
For info, I created a H264 Bluray - NTSC 24fps master from an Apple prores HQ in Adobe Media Encoder. Duration: 52m, size: 11go. I'm on Mac OSX 10.9.5, the bluray burner is Samsung SE-506CB/RSWD and the BR disks are TDK Blu-ray Disc 50 Spindle - 25GB 4X BD-R - Printable.
I looked around in forums and tried the following without success: replacing disk name to shorter name without space, creating bluray without menu frame, I also tried with a Mpeg2 bluray master. I tried to export a new master but I can't seem to be able to change the audio bitrate.
Can anyone please help ?
Thanks.

Hi Stan, thanks for getting back.
I tried to create a new master from Media Encoder but I can only export audio in PCM, I don't get a dolby option. See pic below.
I tried a new project in Encore and chose PCM instead of Dolby in the preference menu, but I still got the same error. Should I try again limiting bitrate to 15 ? I was on 30 before.
Please help, I've already wasted 10 bluray and this is getting really frustrating!

The temp of my Nvidia g105m when using firefox too high

i have a seriusly problem with firefox. The temp of my grafic card (nvidia geforce g105m), it very high (about 95C) event when firefox load new website, i only see this problem when using firefox, i not coming when i use anyother brower! i think i discover newproblem firefox and i must tell you to fix this problem!

Check for updated Nvidia drivers for that video card.

Blu-ray Error: "file already exists", Code: "6", "Audio buffer underflows. Total bit rate too high

Hopefully someon can help me out here - I'm stuck in my tracks. I'm reading through lots of threads on this topic, but don't understand what is going wrong here. CS6. Note: I have used Encore prior to put this material on a disc. I presently have a separate sequence paired down with only about 1/5 of the whole production. 1920x1080i, 29.97, H.264 Blu-ray, VBR 2-pass, PCM inside PP to produce .m4v/.wav. Here is what is confusing me - I tried a target of 10 and a max of 20 and I still get this error. I have tried different max bit rate "Default Transcode" settings in Encore as well. Note the time code listed "0.000000" - maybe that tells someone something. I don't really understand Encore yet, so maybe it is something I set wrong in Encore vs. my exports?

There are many similar, but not identical errors. And I assume you had already followed John's advice to review older threads. It is true they never quite pin a single set of issues down.
What specific version of Encore? Updated to 6.0.2.004? Encore staff once said updates solved some of these errors.
You say .wav for source files in Encore. But what format in the project? ac3?
Your versiono f the error is different from other one I see because it has a "audio buffer" rather than "video buffer" underflow.

Blu-ray Error: "fatal error". Code: "6". "Video buffer underflows. Total bitrate is too high near time = 1.456333 seconds -

Every time i try to burn a blu-ray, this message appears and i can't proceed to the process.
Can anybody help me? I need it for my job.

I could swear I posted this yesterday. But no, the forum did not. Here is the recovered version....
From http://forums.adobe.com/message/6004943#6004943
You will find a number of other threads with this error message.
I think it usually reflects a real datarate problem, but sometimes because there are spikes that should not have occurred with the transcode settings used.
But the solution/workaround is to reduce datarate.
There may also be times where changes in the type of transcoding (CBR, VBR one or two pass) has fixed the issue for a particular project.
In this thread, Jon Geddes recommends a max of 27 or less.
http://forums.adobe.com/message/5214691#5214691

Satellite P775 shuts down when temperature is too high

hello,
I have a toshiba laptop Satellite P775 more than 3 years.
I paid a lot of money for this laptop.
So each time it get too hot laptop that falls immediately.
So yesterday I had my laptop completely disassembled, what a job. but realized that all my fan was clogged with dust. *So problem solved.*
I think this is dangerous because of fire or am I wrong?
There was a dust layer of 5 cm by 1 cm.
Is this normal for this laptop?
Do not think so because it was really an effort to get there.
Sorry for my bad english, a happy 2014.
thnx, greating .
here is a picture: http://www.afbeeldinguploaden.nl/photo/view/55466/wV4LNFC
Message was edited by: jvc101

Thank you so much for this photo. I really hope that many forum users will see it and realize how much dust can be found inside of notebook.
On this forum a lot of people have problems with overheating and notebook switch offs.
Last year I have disassembled my machine too and was surprised how many dust I found inside.
The dust is not dangerous because of fire but it can be dangerous for notebook hardware. Due to critical hardware temperature hardware can be damaged.
Im pretty sure your notebook will run perfectly and much quieter than before.
Bye and good luck.

Frequency measurement keep reading value when stop rotation

Hi,
i am doing the program in the attachment
in this program i am using ni9401 and cDAQ 9188 to measure frequency from motor driver
but i am facing some problems
1. the reading sometimes different than osciliscpe.
2. when i stop the motor the program still read values and not going to zero |
Note my driver send the feed back as a signal"Pulses" with difference frequencies depend on my speed . i send digital values to the driver pins 111 to make it rotrate forward and 100 to make it stop rotating + analog value to change the speed
can i have help in that ?
thanks
Attachments:
speed calibration.vi ‏161 KB

As I understand this you are trying to read the frequency of an quad encoder and the reading is fine as long as the quad encoder is at a steady speed but when it is changing speed you are getting random frequency values. I looked at your code and nothing seemed to jump out at me as being wrong with it but I do have a couple suggestions to see if we can narrow down where the issue may lie.
If you could just try running on of the examples found in the example finder (Help»Find Examples...) specifically example Hardware Input and Output»DAQmx»Counter Measurements»Digital Frequency»Meas Dig Frequency-Buffered-Cont-High Freq 2 Ctr.vi. And just wire the output to a waveform chart or a dial and see if you are seeing the same results there. If that is giving expected results i would just implement your formula node and averaging into that example and save it as your code. I have attached an image of such an implementation.
Doug Farrell
Product Manager - Condition Monitoring
National Instruments
National Instruments Condition Monitoring
Attachments:
example code.png ‏44 KB

Doing Data acq. and buffered period measurement using counters simultaneously, gives an buffer overflow error

Iam doing Data acquisition using NI-PXI 4472 and buffered period Measurement using NI-PXI 6602 simultaneously,my program gives an buffer overflow error

murali_vml,
There are two common buffer overflow and overwrite errors.
Overflow error -10845 occurs when the NI-DAQ driver cannot read data from the DAQ device's FIFO buffer fast enough to keep up with the acquired data as it flows to the buffer (i.e., the FIFO buffer overflows before all the original data can be read from it). This is usually due to limitations of your computer system, most commonly the result of slow processor speeds (< 200 MHz) in conjunction with PCMCIA DAQ boards, which have small FIFO buffers (e.g., the DAQCard-500). Sometimes using a DAQCard with a larger FIFO can solve the problem, but a better solution is to lower the acquisition rate or move to a faster system. Another cause of the -10845 error could be due to an interrupt-driven
acquisition. For example, PCMCIA bus does not support Direct Memory Access (DMA). If the system is tied up processing another interrupt (like performing a screen refresh or responding to a mouse movement) when it is time to move data from the board, then that data may get overwritten.
Overwrite error -10846 occurs when the data in the software buffer that you created for an analog input operation gets overwritten by new data before you can retrieve the existing data from the buffer. This problem can be solved by adjusting the parameters of your data acquisition, such as the lowering the scan rate, increasing the buffer size, and/or increasing the number of scans to read from the buffer on each buffer read. Additionally, performing less processing in the loop can help avoid the -10846 error.
See the NI-DAQ Function Reference Manual for a listing of all NI-DAQ error codes.
Have a great day.

-10920 error when executing buffered period measurements on a PCI 6602 timer.

I frequently encounter the -10920 NI-DAQ error when I run the C code for single buffered data period measurement .
The error message is "One or more data points may have been lost during buffered period measurements due to speed limitations of the system". I am unable to resolve this error. I have a Win2K environment and am using VC++ to compile and execute the code. Please help.

When doing buffered period measurements, the rate at which you can transfer data from the counter is system dependant. To try to get around this there are two things you can try. The first is to set the 'number of counts to read at a time' to a greater number. This way, the 6602 board will use less calls across the PCI bus. If possible, try to limit the number of pulses coming in on the gate that you are using to latch the counts, though in many applications this is not possible.
Make sure that you minimize the PCI bus activity on your computer. This includes, video activity and any network activity along with anything else that is connected to the PCI bus.
Brian

Period measurement timebase apparently lower

I'm performing buffered low frequency period measurement using 1 counter, with an NI 6624. I am using the maximum timebase, which is 20MHz. The gate signal has a frequency of about 25kHz.
The expected period "resolution" due to quantization should be 1/timebase, in this case 1/20MHz=5E-8s.
The problem is that I am getting an effective "resolution" of 5E-7s, or an apparent timebase of 2MHz. What could be wrong?
I've checked digital filtering (DAQmx Channel Properties) on the source and gate signals, and are both enabled with the timebase of 20MHz.
Any comments apreciated.

Hello Daniel,
I agree that you should have a period measurement resolution of 50ns. This means that if you have a perfect 25kHz input signal, you should count 800 pulses of the 20MHz timebase within the 40us window. If you count 799 or 801 pulses, you will get 1/(39.95us) = 25.031289kHz or 1/(40.05us) = 24.968789kHz.
However, the thing to keep in mind is that you must have very accurate 25kHz source in order to determine if this is the case. Using the calculations from above, you would need a signal source with an accuracy of at least +/-0.1249% at 25kHz.
You may want to verify that your signal is at least this accurate before determining if something is wrong with your board or configuration.
Regards,
Bill B
Applications Engineer
National Instrume
nts

Buffered semi period measurement: discard EVERY first value?

Hello,
I perform the buffered semi period measurement. The data aquisition last very long (maybe over one day...).
I arm the counter and then I execute the "read buffer.vi" in an while loop to read the data continuously into a circular buffer.
In the 6602-manual I read the first value ist always bogus.
My question is:
Will I have to discard always the first value when the while-loop restarts? Or will I have to discard only the first value after the first iteration of the while-loop.
Regards Peter

Peter,
You will only need to discard the first value from the first iteration of the While Loop (Counter Read Buffer.vi). Unless you implement a start trigger, the counter could begin counting in the middle of a pulse. Since the counter does not stop and start counting during each iteration of the While Loop, only the very first value buffered is bogus (great choice of words).
Good luck with your application.
Spencer S.

Triggered finite acquisition and period measurement

Hello,
My problem is this: I'm not sure on how Labview accesses devices and how setting up multiple tasks affects loop iteration speed.
The vi I have attached uses a rotary encoder to generate a pulse triggering the acquisition. I have noticed that trying to also perform a period measurement on this pulse causes the iteration time to double. For that reason I have included the case structure so the program reads once every 50 iterations.
I am using the PCI 6250 (dev2) and PCI 6220 (dev1) which are connected by an RTSI cable. The 6220 and 6250 are connected to CB-68LP and TBX-68T terminal blocks respectively. The latter of which causes some problems due to incompatibility.
Any help on either te reasons for the slower iteration time and how to solve it would be most appreciated.
Thank you
Ingram
Solved!
Go to Solution.
Attachments:
new.vi ‏64 KB

Hi Ingram,
Thank you for your forum post and for including your VI. On reviewing your code I am aware of the following:
Acquiring 3 Analogue Voltages using a PCI-6220 (Temperature and Torque readings)
Acquiring 1 Analogue Voltage on the PCI-6250 which represents "Percentage Metallic Content", this task starts when a Trigger is recieved on PFI9
Acquiring 1 Counter Input on the PCI-6220 which represents the RPM of a motor
You are also logging test data to a ASCII text file, this data is only logged when the user presses the stop button on the Front Panel.
As the Counter and Analogue input tasks are seperate from one another it would be worth placing them in their own loops, I think with a bit of rearranging we should also be able to avoid the scenario where you have a while loop embedded inside another while loop. The initialisation of the DAQ tasks should only really be performed once, outside any loops. Another issue dependant on how long the application is executed is the dynamic arrays that are being created, these could become really large slowing down the application the longer it is run for.
An architecture I would recommend for your application is "Producer/Consumer" outlined in the community example available here.
The producer loop will be acquiring data and runs really fast (High Priority), the consumer loop logs data to file (Low Priority), data is shared between the loops using a Queue structure, no other wires should be shared between the 2 loops as these might cause a data dependancy.
Do you require all 3 input tasks to be perfectly syncronized with one another?
Many Thanks
Jamie S.
Applications Engineer
National Instruments

Analog period Measurement

Hello,
I need to measure the frequency of the sinuoidal signal that is acquired using LabVIEW FPGA. I tried to use the block Analog Period Measurement.
The value that i have used are: threshold level 0, hysteresis 0.5.
However, no matter what the frequency, the period is always zero.
I also tried different threshold and hysteresis values, but it was in vain.
I would be grateful if you could be of any help.
Regards, Keshav
Solved!
Go to Solution.

Hi keshasvew,
This function has a valid output signal that only becomes true once per period, so it's likely that you're actually getting a good result, but never seeing it. You will need to add a bit of code on the output that uses the output valid signal to latch the latest valid measurement result. You should also monitor the timeout output, as that will generally stay true if you're not getting any results at all.

BPC 75NW YTD / Periodic Measure query

The Application is currently set to YTD. The Inputs are therefore done on YTD level for Costs. Headcount is a statistical account with AST account type, so YTD/Periodic measures become irrelevent.
Now, What I need is Periodic Costs Divided by HC to get Cost/HC (Cost_HC_Centre) and this is the script that I am running:
*SELECT (%BUS%, "[ID]", BUSAREA, "[CALCULATION]=Y")
*FOR %YEAR%=2011,2012
*FOR %MONTH%=JAN,FEB,MAR,APR,MAY,JUN,JUL
*FOR %BA%=%BUS%
*RUNALLOCATION
*FACTOR=1/USING
*DIM CATEGORY WHAT=ACTUAL; WHERE=<<<; USING=<<<
*DIM TIME WHAT=%YEAR%.%MONTH%; WHERE=<<<; USING=<<<
*DIM DATASRC WHAT=INPUT; WHERE=<<<; USING=<<<
*DIM FLOW WHAT=F_999; WHERE=<<<; USING=<<<
*DIM CURRENCY WHAT=INR; WHERE=<<<; USING=<<<
*DIM COSTCENTER WHAT=[BUSAREA]="ADM_%BA%"; WHERE=<<<; USING=NO_COSTCENTER
*DIM PROCESS WHAT=NO_IO; WHERE=<<<; USING=BAS(%BA%)
*DIM ACCOUNT WHAT=BAS(Salary_and_Benefits); WHERE=Cost_HC_Centre; USING=HC
*ENDALLOCATION
*COMMIT
*NEXT
*NEXT
*NEXT
By doing so, it is calculating it as YTD Cost / HC where I need Periodic Cost / HC
Please let me know how can I achieve the same.
Thanks.

Is measure formula for PERIODIC working as expected ?If not ,you might need to calculate periodic values and store in PERIODIC measure . and then use periodic measure in the logic.

The desktop of MacBookPro is cut when displayed in the 27"LED cinema disply

the desktop of MacBookPro is cut when displayed in the 27" LED cinema display although the resolution of the display is 2560 x 1440 how can i make it cover all the display ?
i found a resolution with comment called stretch but i didn't like the quality
Regards

Try moving the cursor off both the left and right sides of the MBP's display. It could be the displays are just not arranged as you expect them.
This can be altered by going into Displays Preferences and, under the Arrangement tab, you can move the small blue rectangles, meant to represent the two displays, into an order which matches their true arrangement.

DAQmx period measurement- buffer is cut when frequency is too high

Similar Messages

Maybe you are looking for