Period measurement Error 20308

I'm trying to measure the period of a very slow frequency (0.083 Hz) coming into my DAQ(6009).
However it comes with "Error -20309 occurred at "NI_MAPro.lvlibulse Measurements 1 chan.vi:2" when called from "NI_MAPro.lvlibulse Measurements N chan.vi:1" (waveform index 0 of 1)".
The DAQ is capturing method is set to "on demand" however I have also tried various (frequency + buffer) such as 10k by 2k.
but it still comes up with the error.
I know why it comes up with this error but don't know how to fix it.
I have attached the vi (the simulate signal is replicating my DAQ)
Solved!
Go to Solution.
Attachments:
untitled.PNG ‏17 KB
Period.vi ‏35 KB

The error is explaining that not the wave didn't cross the reference levels enough times to do the calculations. Check that your signal reaches both the high and the low levels and that you have enough data in your signal to do a couple of whole signal periods. (with a signal frequency of 0.8 it will take 12 seconds to do a whole cycle) In the simulated example, I got it to work just by increasing the number of samples to 100.
Ian S
Applications Engineer CLD
National Instruments UK&Ireland

Similar Messages

Measure Period with error out.vi

I am using LV6.0. Can Measure Period With Error Out be found in the functions panel? If not where it is? If not there can it be imported into LV6.0?

labview1958,
Are you looking for a specific VI called Measure Period with Error Out.vi or are you asking about any general function that can be used to measure the period of a signal and includes error handling? If you are looking for a specific VI, I'm unaware of it, so I won't be much help there. If you're looking for any function to do it, have you looked at the VIs called Measure Pulse Width or Period.vi or Pulse Width or Period Meas Config.vi? They are located in the Data Acquisition>>Counter palette. The Measure Pulse Width or Period.vi does not include error handling, but it would be extremely easy to add it. The Pulse Width or Period Meas Config.vi DOES contain error handling, but it only configures the counter to measure the period, it doesn't actually measure it. These, of course, are for TTL signals coming into your hardware device. If you are reading waveform data from a file and want to calculate the period of that signal, these won't do much for you. So what exactly are you wanting to take a period measurement on, a physical signal, physical signal data points from a file, or some other method?
Tyler S

-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

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.

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

Pulse measurement Error

I used the Pulse measurement 1 Chan VI in my project and could see that the VI pops up an error in few cases (Error -20308 occurred at "NI_MAPro.lvlib:ma_ptmFetch.vi:2" when called from "NI_MAPro.lvlibulse Measurements 1 chan.vi:1").
I have attached the data cluster of a failed case. Please let me know, wat is going wrong?
Attachments:
Pulse Measurement.vi ‏16 KB

HI
The data you are passing to pulse measurement vi is very small because of that it is giving the error.
Please find attached image for more detail. I have just appended the same siganl four times
Hope this helps
Regards
Santosh
Attachments:
data.JPG ‏232 KB

Huey Pro calibrator- error message display measurement Error

i am using this huey pro calibration.. it had been a year without problem... but now i am trying to calibrate my apple cinema display LCD 30 inch it keep saying error message- display measurement error.. and huey support never answer my e-mail. any idea? how can i fix it.. i did re install software many times but same thing happen.. so right now i can;t calibrate my monitor.. any help please

>a nice NVidia card... Please help Adobe!
1a - what is the model nVidia card, and what is your driver version?
1b - for instance, I have a GTX 285 and driver 296.10
2a - aside from the occassional Adobe employee, this is a user to user forum, not Adobe suport
2b - how to contact Adobe...
Adobe contact information
http://www.adobe.com/support/contact
In the US - Adobe General support 800-833-6687 M-F 5am-7pm Pacific
In the US - Adobe Install Problems 800-642-3623
In the US - Adobe Activation 866-772-3623 Open 24/7

Huey Pro Calibration Error message- measurement error

i need using this huey pro calibration for year. but now i am trying to calibrate my apple cinema display LCD 30 inch it keep saying error message- display measurement error.. and huey support never answer my e-mail. any idea? how can i fix it.. i did re install software many times but same thing happen.. so right now i can;t calibrate my monitor.. any help please?

Hi,
Which Wireless-Card you used?
Best you use the Cisco CB21AG PCMCIA Card. I had similar problems with intel wireless chipsets
Sincerely,
Frederik

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

11.5.5 - OPEN PERIOD PROGRAM 수행시 ERROR

제품 : FIN_GL
작성날짜 : 2003-05-12
OPEN PERIOD PROGRAM 수행시 ERROR
=============================
PURPOSE
GL Open Period Program 수행시 발생하는 Error를 해결한다.
Problem Description
11.5.5 에서 GL Open Period Program 수행시 gllock 모듈에서 stuck되었다는 error가 발생한다.
정확한 error message는 다음과 같다.
Current system time is 03-JAN-2003 13:22:27
main() 03-JAN-2003 13:22:27Set_of_books_id = 3
Chart_of_accounts_id = 50214
Application_id = 101
execution_mode = P
User_name = INTERFACE
Request_id = 106736
Login_id = 87859
SHRD0181: glooap() - request_data_value =
gllock() 03-JAN-2003 13:22:27Current system time is 03-JAN-2003 13:22:42
Current system time is 03-JAN-2003 13:22:57
Workaround
Solution Description
1. 다음 query문을 수행한다.
select * from gl_concurrency_control
where concurrency_class = 'OPEN_PERIOD';
2. 위의 문장으로 조회하여 CONCURRENCY_ENTITY_NAME 에 해당 set of books id 가 있는 row의 concurrency_entity_id 값이 확인한다.
3. 만약 값이 -1 이 아닌 경우에는 -1 로 update 하신 후 다시한번 open
period 프로그램을 수행한다.
Reference Documents
Note 204080.1

Hi,
There is function called get_company_name in the before report trigger and the function gives TRUE/FALSE output. (below is the function code)
FUNCTION get_company_name RETURN BOOLEAN IS
l_chart_of_accounts_id gl_sets_of_books.chart_of_accounts_id%TYPE;
l_name gl_sets_of_books.name%TYPE;
l_sob_id NUMBER;
l_report_start_date DATE;
BEGIN
l_report_start_date := sysdate; -- Get the report start date from sysdate
l_sob_id := :p_set_of_books_id; -- Copy from parameter to PL/SQL variable
SELECT name,
chart_of_accounts_id
INTO l_name,
l_chart_of_accounts_id
FROM gl_sets_of_books
WHERE set_of_books_id = l_sob_id;
:c_company_name_header := l_name;
:c_chart_of_accounts_id := l_chart_of_accounts_id;
:c_report_start_date := l_report_start_date;
RETURN (TRUE);
RETURN NULL; EXCEPTION
WHEN OTHERS THEN
RETURN (FALSE);
END;
Try making the set of books to be same and run the program.
karthik

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.

SE30 - Unable to end the measurement (error number 5, Time limit reached)

Hello there,
I wish to perform a complete ABAP trace using SE30 for a program running for 4 hours. The system is R/3 4.6C.
However I got the error message below once I clicked "Back" button or F3 when the program finished after 4 hours.
Please note that ST12 is not available in the system I logged on.
=============================================================
Error message:
"Unable to end the measurement (error number 5, Time limit reached)
Message no. S7 068"
Meas. type           Fully aggregated
Session type         In current session
Status               Time limit reached
Error message text   Time limit exceeded. LIMIT: 1800000000, ELAPSED TIME: 1800957266
File user            XXX
User                 XXX
File ID              ATRAFILE
Release              46C
Version              6
Operating system     HP-UX
Number of processors ???
=============================================================
The ABAP trace results only managed to capture the first 45 minutes of the ABAP calls (due to timeout i think). I would need the whole and complete ABAP trace result for 4 hours, NOT the first 45 minutes. Is there any setting in SE30 can be set for this purpose? Note that there is no ABAP error for the program I traced.
The following link didn't answer my question as well. Hope you can provide clue in this case.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm
Runtime analysis, SE30, ERROR
Thanks,
KP

Hi Kim,
The Limit is expliced on the Doc.
http://help.sap.com/saphelp_nw70/helpdata/en/4d/4e2f37d7e21274e10000009b38f839/frameset.htm
It's 4293 Actually and you set it on SE30 by change the Measurement Restrictions, tab Duration/Type.
regards.

PXI 6229 pulse period measurement

Hi there,
I try to make pulse period measurement using PXI 6229 counter, I have 0.5Vcc according to DMM and 1.05V peak2peak based on scope. Then, I connected 0.5Vcc (incoming pulses) into SCB68 pin 3 and GND pin 55. I used the DAQ assistant to perform measurement n the setting for Signal Input range is min= 1ms and max = 23ms, those values I got it from scope i.e pulse period. I set it to the Rising and Acquisition Mode to 1 sample(on demand). But, I can’t get the measured values and I have no ideal why?
Please help
Walter.

Hi Walter,
the counter input of the PXI-6229 accepts standard TTL digital signals. You can find its specifications on page 7 of this document.
I will repeat the relevant parts here:
Input high voltage: Min: 2.2 V; Max: 5.25 V
Input low voltage: Min: 0 V; Max: 0.8 V
If I'm correct, your signal does not meet these specifications, so in this case you will have to connect the signal to an analog input and measure the pulse width as if it was an analog signal.
Please check this page for an example.
Daniel

2 channels on semi period measurements M series 6221

Can I perform measurements of semi period on 2 seperate channels with my M series 6221?

Hello rawpaw,
The NI-6221 has two general-purpose counter/timers, which means that you should be able to perform a semi-period measurement with each one (for a total of two semi-period measurements).
For more information on performing these measurements, please refer to the "Counters" chapter of the M Series User Manual. Hope this helps,
Daniel S.
National Instruments

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

Period measurement Error 20308

Similar Messages

Maybe you are looking for