error -200010 during hardware timed single point analog input

[Brooks_C]

Hello Peter,

I've played with your VI more and I'm still not able to reproduce this error.  I've done some looking around and I haven't see this as a reported issue with earlier versions of DAQmx, however, I am using the current version and it may be worth upgrading your system to NI-DAQmx 8.7.1 if you aren't already using it.

Another possible solution (more of a work around) would be to modify the case structure that control's the "disable AI" feature in your program.  You could move this case structure to be just around your "Analog Input" indicator--then the DAQmx Read would run every loop iteration and the indicator would only update points in the same manner.  Essentially you'd observe the same behavior, but it may help avoid this error.

I'll do some more looking around to see if this was a bug that's been fixed, because as far as I can tell, the overflow error is not being thrown on my computer for hardware timed single point acquisitions.

On an unrelated note, I did end up getting a puppy shortly after my last post--we've frequented the off leash park ever since.  Her name is Abby and she is awesome!

Cheers!

Message Edited by Brooks_C on 08-07-2008 03:59 PM

[Peter_B]

Hi Brooks,

Great shot of your new dog. What breed is she?  Its good you're taking her to leash free parks at a young age. Doggy social skills are best learnt young.

I already had the latest version of NI-DAQmx installed (8.7.1f2).

My reason for casing out the DAQmx AI read is to simulate the real situation where the timed loop is halted for a couple of seconds when windows decides to hog the CPU for whatever reason.  I wouldn't be simulating the problem if I just cased out the indicator.

I was hoping you could reproduce the error as I am able to every time.  Because the error happens for me on two different PCs , the remaining thing in common is the DAQ card or the dev environment (LV 8.5.1) & NI-DAQmx drivers. I am using a PCI-6014.  I'll try to get my hands on another PCI card to see if the problem is still there    I tried using a simulated DAQ card, but the timed loop didn't automatically start the task as its supposed to (probably a bug).

I'll see if my local NI App Engineer can reproduce the problem.

regards

[Peter_B]

Hi Brooks,

I have just tried with a PCI-6036 and I still get the same error -200010 when I hold down the Disable AI button for >2.5 seconds.  This is now two PCs (one 4 years old, the other a brand new quad core) and two different DAQ cards that it happens for me.

regards

[Peter_B]

My local NI App'n Eng. tried out the vis on two separate systems, but couldn't repeat the problem either !!

I am now wondering if it could either be

i) some setting in MAX that is different on my setup. OR
ii) something different about the architecture of the PCI-6014 and PCI-6036 DAQ cards compared to the type you and my local App'n Eng. are using (what are you using ?) OR
iii) some persistent parameter in both of my PCI DAQ card's EEPROMs which I am not configuring with the vis but is different between my cards (6014 and 6036) and other cards you and and my local App'n Eng. are using

regards

[Brooks_C]

Hello Peter,

I believe that Abby is a Vizsla mix--though I can't figure out what she's mixed with.  She’s about 40 lbs. at 8 months, and she'll probably top out around 50...

I had been using a PCI-6251, but this morning I checked out a PCI-6014 and still haven't been able to reproduce this issue.  Let’s compare the rest of our setup.

1.  Operating system:  Windows XP Service Pack 2.
2.  LabVIEW Version:  8.5.1
3.  DAQmx Version:  8.7.1
4.  Hardware:  Successfully tested PCI-6251 and PCI-6014

My computer is a dual core Dell desktop, but from your testing (single and quad core) it would be surprising if that had anything to do with it.

If you'd like to generate a technical report in the Measurement and Automation Explorer (MAX) that would allow for a more complete comparison of the systems.  You can do this by opening MAX and selecting File» Create Report.  Select "Technical Report" and follow the steps in the wizard.  This will generate a zip file with detailed information about the driver versions and hardware you're using.

A possible, though unlikely, explanation is a corrupted DAQmx driver (especially unlikely since you've confirmed it on two computers--unless you used the same installation file).  It may be worth running a repair on the DAQmx Driver and/or LabVIEW, or you can install DAQmx 8.7.2 which was released in the past day or two.  If you did use the same installation source that would make this a more likely fix.

If you're uncomfortable posting this zip file on the forums, with your permission, I can look up your email address and send you an email that you can reply to with the file.

Let me know what you'd like to do.

Cheers,

[Brooks_C]

Accidentally duplicated my post... please disregard this one.

Message Edited by Brooks_C on 08-08-2008 01:02 PM

[Peter_B]

Hi Brooks,

I certainly appreciate your thorough approach in helping me out with this problem.

I am attaching the zip file.  There wasn't any proprietry info in it.  The PCI-6014 was resident, I had just taken the PCI-6036 out but some of its details still show in the ni_max_report.html file within ni_support.zip

The installed S/W on my my quad core PC is nearly identical to yours. (I have an f2 after my DAQmx version)

1.  Operating system:  Windows XP Service Pack 2.
2.  LabVIEW Version:  8.5.1
3.  DAQmx Version:  8.7.1f2
4.  Hardware:  Unsuccessfully tested both a PCI-6035 and a PCI-6014
5. 3.25 GB RAM

The installed S/W on my my single core PC is as follows

1.  Operating system:  Windows 2000 5.00.2195 Service Pack 4.
2.  LabVIEW Version:  8.5.1
3.  DAQmx Version:  8.5.0f3
4.  Hardware:  Unsuccessfully tested PCI-6014
5. 3.25 GB RAM

I'll wait to hear back from you befor I install and try out NiDAQmx 8.7.2 as I am nearing a delivery stage of a major project and I'd rather not make too many changes to the system unless warranted (I'll upgrade if you think it stands a reasonable chance).  It's worth pointing out that my single core PC only has DAQmx Version:  8.5.0f3 so that would have come from a different installation to to that on my newer PC.

I tried uploading a photo of my dogs but my server wouldn't let me, I'll try again later.

regards


 

[Peter_B]

Hi Brooks,
My server got its act together. Meet Simba and Nessa. Our two 3.5 year old Golden Labradors

Simba has Canine DLE on his nose which has proven difficult to get into remission, apart from that they are pretty healthy and active.  They are always inside when anyone is home.

re. the problem at hand, I had another idea to try out.  I have a DAQ card which has never been calibrated by our local calibration agency (NI approved).  Just in case they are putting our DAQ cards into a certain state that causes this error I will give this other DAQ card a try.  I do know that once in the past they calibrated a DAQ card for us and it came back and its behaviour changed in some way (I can't recall the details) but they had written something to the DAQ's EEPROM to give it a different/bad response.  So I had to send it back and they fixed it up (IIRC it was a case of them not understanding exactly how to use the NI S/W and H/W setup program to calibrate the card).

If I'm keen I'll do that tomorrow, else I'll do it on Monday.  Either way if you only work Mon-Fri I should have an answer for you before you reply again.

regards

[Peter_B]

             EUREKA !!!!      

I just tried a PCI-6251 we have at work which has never been sent out for calibration and I DON'T get error -200010 !!!!

So what settings in the other DAQ cards EEPROMS are being mushed up when they are being sent out for cal ???  (This confirmed behaviour is exhibited on THREE of our DAQ cards, two PCI-6014s and a PCI-6036 - all of which have been calibrated locally ). As I wrote above I have seen something like this in the past, I'll have to dig up the info as to exactly how they fixed it.

This is a problem that now needs to be worked out between our local NI office and the local Calibration Agency we use.  Brooks, can you possibly suggest where they start looking ?  Cna I download the EEPROM config data on my error prone PCI-DAQ cards to compare it with the contents of a known good DAQ card ?

regards

[Peter_B]

BTW if I disable AI for >40seconds (at the default CLK rate of 200Hz) I do however get another error (-200714) , whereas error -200010 would always come after 2.5 seconds at the CLK rate I am using.  This new error is understandable and it is not a problem at all for me because it takes so long to happen.  FWIW both errors (-200010 and -200714) happen sooner if I up the clk rate. But I don't need to up the CLK rate >200Hz for my application.

regards