Meas buffered semi-period continuous.vi with DAQPad-6020E

Hi,
Does anybody know if it's possible to use the meas buffered semi-period continuous.vi with the DAQPad-6020E? Or, if it's not, what workarounds might be possible?
LabVIEW responds with Error 200220 (Measurements: Device identifier is invalid). I know the hardware is definitely good because I can run other VI's with it.
Thanks,
Dave

Dave,
Are you able to make any kind of counter examples run on your device? There are two counters on your board, are you using any of the counters for something else while running this example? Do you also get the same error in Measurement and Automation Explorer (Start >> Programs >> National Instruments >> Measurement and Automation Explorer). You can create a new task and select Acquire Signals >> Counter Input >> Semi Period. Please let me know if you get the same error in this environment as well.
Also, what is your operating system and what is the DAQmx driver version that you are using?
Thank you and best regards,
Raajit L
National Instruments

Similar Messages

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.

CI Semi Period, Error -200141

I try to measure the semi-period of the signal in attach with a CI semi period counter in Labview 7.0.
I am using the example VI Meas Buffered Semi-period Continuous with a acquisition card PCI-MIO-16E-4.
I can measure the semi-period of a signal of 50KHz with a duty cycle of 25% but when I try to measure the signal in attach, signal that the frequency is lower, I obtain this message.
Error -200141 occurred at DAQmx Read (Counter 1D DBL 1Chan NSamp).vi
Possible reason(s):
Data was overwritten before it could be read by the system.
If using interrupt data transfer, try using DMA. Otherwise, divide input signal before measuring.
What can I do ??
Marc Ducommun
University of applied sciences
Switzerland
Attachments:
Signal_Capteur_modified.bmp ‏38 KB

Marc
Do you get this error when measuring the lower frequency signal? Or do you only get this error when switching from one signal to another?
How are you switching from one signal to another?
Switching from one signal to another usually causes high frequency noise which can cause this problem.
For example, if your program is running fine with a 50kHz signal, and then you flip a switch to measure a lower frequency signal, the switch could introduce high frequency which could overflow the counter.
Russell G.
Applications Engineering
National Instruments

Daqpad 6020E not communicating

Sometimes when my PC is first powered up, my daqpad 6020E (USB) will not communicate with my labview programs until I open up measurement and automation explorer and click on the 6020E. I have two computers with DaqPad 6020E and both of them have this intermitent problem.

The problem you are experiencing sounds very familiar to a commonly known issue with the DAQpad-6020E. It has been discovered that the problem occurs after you have placed desktop and or laptop PC into hibernate or Standby mode. When coming off of hibernate or standby mode the USB module does not come back up, unless the USB cable is disconnected and reconnected, or power to module is switched off and then back on. The problem occurs on OS Win 9x, WinXp, WinXp Professional.
Does this sound familiar to your instance? The problem has been reported to R&D. Unfortunately, there is no plan to fix such an issue with the DAQpad-6020E. The recommended solution to getting around the problem is to disconnect and reconnect the USB device or the power cycle to the devic
e. NI DAQPad-6020E for USB, NI USB-5102, and NI USB-4350 Failing to Respond When the PC Comes Off of St....
Let me know if you have any further questions.
Jared A

Samples Not Acquired on NI 660x or NI 6624 Devices When using pulse width, semi-period or two-edge separation buffered measurements with the NI 660x and NI 6624 on counters 0 and 1, some samples may not be acquired under certain circumstances.

In the DAQmx 9.4 Readme the following is stated:
Samples Not Acquired on NI 660x or NI 6624 Devices When using pulse width, semi-period or two-edge separation buffered measurements with the NI 660x and NI 6624 on counters 0 and 1, some samples may not be acquired under certain circumstances.
Could anyone elaborate on this? I am particularly interested in knowing under what circumstances this problem arises for the 6602 PCI devices.
How should I understand 'NI 660x and NI 6624 on counters 0 and 1'. Is it only a problem on counter 0 and 1 for the 660x or does this only apply for the 6624 devices.
/mola

Are there any NI Product Support Engineers out there who has an answer to this question and who are willing to share it with me?

NI PCI-6602: semi-period measurement stops unexpectedly or returns wrong values

Hi,
Using an NI PCI-6602 card we try to measure the semi-periods of a digital signal.
In "continuous sampling mode", 10 samples are collected in the buffer and then are read
out.
Up to 6 counters on this card are sampling the same signal in our testing configuration.
Here we found these issues:
1. Failure
In principle, the measurement runs correctly, but one or more counters sporadically may
suffer a complete failure. I.e. these counters don't provide samples anymore.
Only after stopping and restarting the assigned task, a failed counter works again.
Apparently, a counter failure is most likely to happen when
    - the sampled signal "changes", i.e. when the pulse width of the signal changes,
    - or when the computer load is high, e.g. when opening a window of another application.
Every counter occasionally failed, but the issue was found very often at counter 1 of
the PCI-6602 card, if we used counters 0 through 5 in parallel.
Using another PCI-6602 card, the failures happened preferably on counters labeled "near"
number 5.
2. Wrong values
Occasionally the "interpretation" of the sampled values changes, i.e. the length of the
"high level" period is returned, where the "low level" period length should be given, and
vice versa.
This is our task configuration:
Configuration done with MAX:
Signal input range:    2 usec - 2 sec
Custom Scaling:        None
Sample mode:        continuous
Buffer size:        10 Samples
In addition these calls are made:
ret = DAQmxSetDigEdgeArmStartTrigSrc( task->mHandle, <use the same terminal as is used for
the signal to be measured>);
ret = DAQmxSetArmStartTrigType( task->mHandle, DAQmx_Val_DigEdge);
ret = DAQmxSetDigEdgeArmStartTrigEdge( task->mHandle, DAQmx_Val_Rising);
ret = DAQmxSetCISemiPeriodStartingEdge( task->mHandle, <the channel>, DAQmx_Val_Falling);
Best regards
Manfred

Hi Manfred7,
did you already test this behaviour with a simple example from us?
Just go through the example database and try the examples there.
These examples should work.
If it works, there is a problem with your programm.
If it won't work, please tell me more about your software:
- Version
- DAQmx Version ,...
best regards
Dippi

How to synchronize two PCI-6602 via RTSI for semi-period counting of four signals?

Hello,
I try to measure 4 PWM signals. For that, I created 4 tasks (newest DAQmx), each with semi-period measuring one signal.
I want to use DMA so I have two 6602 for each two signals.
The task aquire a finite number of samples.
This works fine when starting the tasks subsequently.
Now I want to start the tasks via a trigger on the RTSI bus.
But I have no idea how to get this done.
I use the MX drivers for the first time an find it very difficult to get through the help files.
I looked at many examples but did not find a solution.
Most of the time my experiments end with an error message saying that the property is not applicable to this task, or s.th.similar.
Ans sometimes, when there seems to be a trigger defined, the task will not wait for the trigger and time out.
Is the anybody who can help me out of this?
Maybe a little sample program?
I program in CVI.
Many Thanks
Michael.

This topic is discussed here:
http://forums.ni.com/ni/board/message?board.id=250&message.id=13383&requireLogin=False
Hope this helps!

Multi counter PCI 6602 daqmx semi period measurement

Hi All, Currently I am working on 20 PWM input channels. I have some problem on my labview code. Would some one give some advice on my vi? I crated labview code for 2 channels for now. I am doing semi period measurement. I want to measure the frequency and duty cycle of the PWM signals. But when I run it, it has error. Please give some advice where I did wrong on my vi. thanks Johnny
Solved!
Go to Solution.
Attachments:
Multi PWM Reading.vi ‏118 KB
erorr message.doc ‏91 KB

Hi marconi,
This error that you are getting is a buffer overflow error and is likely due to the value that you used as an input to "number of samples" on the DAQmx Read VI. You had it set to 4 but depending on how fast the PWM that you are reading is, you may be acquiring values to the onboard buffer much faster than you are retrieving them with the DAQmx Read VI. Then when you call the DAQmx Read VI, which reads relative to a read pointer the data that you are expecting to read from the buffer has already been overwritten. One way to get around this is to increase the number of samples to read each time you call the DAQmx Read VI. I tried out your VI and got it to work with a slight modification to the start trigger (using PFI0 instead of the 20MHz timebase) and added a loop condition to stop from getting a buffer underflow error as well. Take a look and see if this helps out. Also, why are you triggering off the 20MHz timebase? is there a particular reason? This is essentially like using no start trigger since you should get the first rising edge of that almost immediately after the DAQmx Start VI is called. I am just curious, since using this start trigger did not actually work for me (though I didn't look into why).
Chris W
Attachments:
Multi PWM Reading.vi ‏51 KB

CI Semi Period Digital Filter

Hello!
I'm having difficulty configuring my counter inputs. Pretty new to Counter/Timer setups as well.
LabVIEW 8.5 and MAX 4.5.
The signals I am sampling are 200 Hz, PWM ranging from 5% to 95%, cycling back and forth.
I'm using 7 counters in a PCI-6602. The code I'm including is an example from my setup.
We are requiring the use of the Rising Digital Edge, and I'd like to include CI.PulseWidth.DigFltr.Enable to enable debouncing.
All inputs are connected to the Gate terminals on each counter.
Is my programming for the Risin edge correct? I am seeing the falling edge come through first on several occasions.
And for the debouncing programming, I always get error -200452. None of my searches revealed anything applicable.
I have also tried setting my Min value on the Semi Period configure to 0.0002 instead of 1e-7 with same results.
This is a hot project, so thank you for your time in advance!
Attachments:
Counter PWM Setup 0.vi ‏17 KB

Hi Oley,
It looks like there's two questions here:
1. Programming for the Rising Edge:
I'm assuming that you want to start the task on the rising edge of your input signal. It looks like you have set the 6602 to arm off of the rising edge of your 20 MHz timebase (which is independent of the input signal). Rather than setting the Arm Start Trigger, you can use a DAQmx Channel Property Node to set the starting edge (see below).
2. Error -200452 (Specified property is not supported by the device or is not applicable to the task.)
The property node that you have configured to enable the filter needs to be specific to the type of task that you are running (in your case, CI.SemiPeriod). You have selected CI.PulseWidth which is a different task type. The filtering is usable with a SemiPeriod task by simply changing the property node accordingly.
The property node that you configure should look like this:
This will both enable the filtering and tell the device to begin measuring on the first rising edge. Make sure that all the properties begin with CI.SemiPeriod--it can be easy to overlook at times since many of the different task types have identical properties available.
I hope this helps out, let me know if you have any questions or run into any issues implementing the above.
Best Regards,
John Passiak

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

Sharepoint list dataheet view error "Cannot connect to the server at this time. You can continue working with this list, but some data may not be available"

I have a List which is having around 14000 items in it.while opening that list in datasheet view it is giving error .
Below is a summary of the issue:
After selecting datasheet view beow error occurs:
    "Cannot connect to the server at this time. You can continue working with this list, but some data may not be available."
    "Unable to retrieve all data."
    The item counts displays say 100 out of 14000 items.
Exporting List to excel is giving only 2000 records out of 14000 records.
Other Observations   -
This is happening to only one list on the site .There are other lists in the site whose no. of records is equal to 8000 to 9000.They are working absolutely fine without any error.
Also, If I am saving this list as a template and creating another list with it ,then it is working absolutely fine with 14000 records,so the issue does not seem to be related with no. of records as the template list is working fine.
I have checked the Alternate access mapping setting ,its fine.
It should not be related to lookup,datefield or any other column as the list created from it template is working fine with all these columns.
I checked below links also ,but doesn't seem to work in my case.
http://social.technet.microsoft.com/forums/en-US/sharepointadminprevious/thread/974b9168-f548-409b-a7f9-a79b9fdd4c50/
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/87077dd8-a329-48e8-b42d-d0a8bf87b082
http://social.msdn.microsoft.com/Forums/en-US/sharepointgeneral/thread/dc757598-f670-4229-9f8a-07656346b9b0

I have spent two days to resolve this issue. Microsoft has released two KBs with reference to this issue...but are not appearing in search results at the top.
I am sharing my finding.
1. First install the
KB2552989 (Hopefully you might have already installed it. The KB detetcts it and informs the user.)
2. Then update registry by adding new key for data fetch timeout as mentioned inKB2553007
These two steps resolved the issue in our environment. Hope it might help others as well.
Pradip T. ------------- MCTS(SharePoint 2010/Web)|MCPD(Web Development) https://www.mcpvirtualbusinesscard.com/VBCServer/paddytakate/profile

Error: Could not continue scan with nolock due to data movement, DBCC proccache will clear the probelm

SQL Server: 2008 R2 SP2
Before describing my problem, I have gone via the forum, there is no view or functions inside my stored procedure
When running a particular stored procedure inside crystal report, the error " Could not continue scan with nolock due to data movement" comes once every few weeks. After I clear the query cache plan, it works again for few weeks and the problem
comes again. During these few weeks, there is no restart or query plan clearing.
If I run the stored procedure inside SSMS, where the SQL statement is copied and pasted from SQL profiler during crystal report run, there is no error.
I discovered running in SSMS and crystal report generate 2 different query plans even I copied the SQL from SQL profiler, I have actually saved the query plans. Unfortunately, this forum does not accept attachments, or otherwise I will post my query plans
here.
There is one thing I notice about the query plan is during nested loop operation, there is a warning "no join predicate". I don't use any views or UDF in the statement, nor did I use pre-1992 ANSI join syntax. However, I did use table variables.
My guess is whether this will cause " Could not continue scan with nolock due to data movement", after I clear the cache, I run crystal report again, and I look at the plan again, the "nested loop no join predicate" warning is gone.
Running this stored procedure took 1 second maximum, even when this error is popping up, it pop up within 1 second.
DBCC checkdb has been run
The same stored procedure running by crystal report in a SQL 2008 (non r2) live environment has no problems, so I am thinking this is R2 specific problems.
The "nested loop no join predicate" error SQL statment is below, no views, no udf, but table variables
INSERT @ChequeAccount
SELECT       PS.PaySummaryID, PS.EmployeeID, PS.CostCentreID,
           (PS.GrossPay   + PS.LumpSumA + PS.LumpSumB   + PS.LumpSumD+ PS.LumpSumE+ PS.ETP+ PS.PaymentsAfterTax   - PS.DeductionsAfterTax
- PS.Tax- PS.ETPTax   + PS.TaxRebate) * -1 AS Amount,
           CGLM.GLAccountID
FROM Pay_Summary PS JOIN Input_Sheet ISH ON PS.InputSheetID = ISH.InputSheetID AND ISH.PayrollID = @binPayrollID
AND PS.PaySummaryID NOT IN (SELECT PaySummaryID FROM @ChequeAccount)
JOIN Payroll P ON P.PayrollID = ISH.PayrollID AND P.EmployerID = @binEmployerID
JOIN CustomGLFixMapping CGLM ON CGLM.EmployerID = P.EmployerID AND CustomGLFixMappingNameID = 1 AND CGLM.CostCentreID IS NULL

The error Could not continue scan with nolock due to data movement can occur when you use the NOLOCK table hint, or use the command SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED. That is, so-called dirty reads. The error is not related to the
query plan per se, but when scanning a table, the storage engine will use an IAM scan rather than following the clustered index. If there is simultaneous activity, the storage engine may detect this and abort the operation to avoid returning incorrect data.
Or it may not detect it, and return uncommitted data or fail to return committed data.
All of these effects are transitory and they will not show up when you are alone on the system, only when there is concurrent activity in one or more of the tables in the query.
Using dirty reads is a risky business for the reasons explained above, and it takes careful analysis to understand whether you can live with the errors you can get from a particular query. The error about data movement can be handled: trap the error and
resubmit the query. But what about spurious incorrect results?
If you believe locking to be a problem, you should consider setting the database to READ_COMMITTED_SNAPSHOT
and take out all use of READ UNCOMMITTED/NOLOCK. When the database is in READ_COMMITTED_SNAPSHOT, readers read from the snapshot and only see committed data without blocking writers. This has some other effects like requiring a bigger tempdb,
and there is a risk for other types of concurrency errors, but they tend to be smaller risks.
I discovered running in SSMS and crystal report generate 2 different query plans even I copied the SQL from SQL profiler,
This is because SSMS by default runs with SET ARITHABORT ON. I discuss this in more detail in this article on my web site:
http://www.sommarskog.se/query-plan-mysteries.html
However, as I said, this problem is not related to the query plan as such, although some query plans are more susceptible to this error than others. (All plans are suscpeitble to produce incorrect results).
Erland Sommarskog, SQL Server MVP, [email protected]

Continue crashes with adobe Pr cc...

continue crashes with adobe Pr cc...why

FAQ: What information should I provide when asking a question on this forum?

Post Moved Continual-problem-with-SMTP-passwor...

Post Moved to Other BB Queries http://community.bt.com/t5/Other-BB-Queries/Continual-problem-with-SMTP-password-being-blocked/td-p/...
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

Post Moved to Other BB Queries http://community.bt.com/t5/Other-BB-Queries/Continual-problem-with-SMTP-password-being-blocked/td-p/...
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

Continual Crashes with CR 11

I'm experiencing continual crashes with Crystal Reports 11. Seemingly random in nature -- sometimes when I perform a refresh, sometimes when I close out a report, sometimes "just whenever".
Environment:
Virtualized XP Professional SP3 [VM Workstation version 6.5.0 build 118166]
CR Product Version 11.0.0.2495
ODBC Connection to Oracle 10g using 10.02.00.04 driver
Application event log shows:
1st Entry:
Faulting application crw32.exe, version 11.0.0.2495, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x0000100b.
2nd Entry:
Fault bucket 1251409985.
Any thoughts, hints, places to start?
Thanks.

Will try to see if this narrows down problem but isn't acceptable long-term solution.
Reports I write are distributed and run through another app that only supports ODBC connections.

Meas buffered semi-period continuous.vi with DAQPad-6020E

Similar Messages

Maybe you are looking for