AO Group COnfig Error

I have created a sine and a square waveform according to the user requirements but when i write the two waves to the AO generate waveforms i get an error saying AO config error. I have also configured the input channels using AI config and other input SUb vi's. I dont knwo what to do.

Vaidehi,
Are you using LabView 7.0 or newer (with DAQmx) or are you using an older version of LabView that only has the Traditional DAQ? Either way, there are several examples of analog waveform output included in LV. You can find them in the help menu under "Find Examples."
You coud get the AO config error for several different reasons. Its very hard to tell what it is without having the code. Are you doing simultaneous AI and AO? There is a shipping example for that also.
If you can't get this solved using the shipping examples please feel free to respond to this with your code attatched. It may give me some insight into whats going on.
-Sal

Similar Messages

AI Group Config Error 10001 using Virtual Channels

In my LabVIEW block diagram, I usually enter in numbers, e.g. 0,1,2 for the channel string input of AI Config. When I try to use a virtual channel, I simply type in the virtual channel, e.g. 0,K Thermocouple,2. However, this causes AI Group Config Error 10001, which applies to an invalid channel string. What is the correct way to enter a virtual channel into the channel string?

Do you have channels with virtual names of "0", and "2"?
If not you may be confusing MAX by using both naming conventions.
Try using only Virtual names.
I generally will use an array of strings where each element is the vitual channel name with no problems.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

PCI-6601 - Group Config error -10444 after 9 hours running

We developed a vi in order to acquire from the unique dma channel of the PCI-6601 counter 4 multiplexed inputs for a period measurement. We use the national VI buffered_measured_period_TIO. Each cycle the VI is supplied with one of the 4 input line.
Everything works fine until the 32211 second of measurement (about 9 hours) and after we receive the -10444 error on the group config block and the card freezes (not the software). We need to switch off and on again the PC to start again.
The cycle of measurement is exactly the one from the original Ni Vi and each cycle the reset is performed.
Looking in the database we found a similar problem after a long running (10hours) and a PCI-6602.
We suppose that after s
everal initialization some internal counter goes in overflow (maybe the TAskID counter?).
Does exist any explanation and workouround to solve this?
Is it possible initialize the card only one time for the 4 channel and how?
Regards
Andrea Pede

Hi Andrea,
What is probably happening is that your memory is becoming increasingly fragmented and after 9 hours there are no continuous blocks of memory available. If you are continuously reconfiguring your counters, that is what is morelikely causing the problem. I included an example that uses all 8 counters and only needs to configure them once. A couple other suggestions:
1) What happens when you create a larger buffer? Can you run the program for longer?
2) Have you tried running a disk defrag program on your memory? One suggestion I found on the net was mem-turbo from a shareware site.
3) What happens if you only use 1 counter? Does the error still occur?
4) Some issues (including error 10444) with the NI-DAQ driver and analog input were solved
by upgrading to NI-DAQ 6.9.3. What is your current computer configuration (software, hardware, driver version etc.)? This might help narrow the problem down.
Simultaneous Buffered-Event Counting on All Eight Counters of the 6602 or 6608 Devices
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3DC9F56A4E034080020E74861&p_node=DZ52325&p_source=External
Hope that helps. Have a good day.
Ron
Applications Engineering
National Instruments

AI Group Config error -10403 when using DAQPad-6070E

I am using a DAQPad-6070E with attached device SCB-68.
Yesterday, I was able to read in analog waveforms using the attached file. Today, without any changes made to the file, I get an error -10403 in AI Group Config.
What could be causing this error since no changes were made in the file or in Measurement and Automation Explorer configuration?
My system configuration is as follows:
Windows XP
Measurement and Automation Explorer v. 2.2.0.3010
NI-DAQ v. 6.9.2f4
LabVIEW v. 6.1
Attachments:
AIGroupConfigError.vi ‏256 KB

I haven't been able to run your VI since I'm lacking one of the subVIs in your design, but taking a look I have a few suggestions. I noticed that the device and channels controls for AI Config are both hidden on the front panel. The default values for these controls should be checked to make sure that they agree with the device number in MAX. You could place a probe on all of the inputs to the AI Config VI and let us know what values are being sent.
Also, try resetting the device driver through MAX, just in case another program did not release some resources that are needed by your VI.

How do I fix error 10001 with AI Group Config.vi

I have written a VI which uses the AI Sample Channels.vi in it. One of the sub-sub...sub vi's of this is the AI Group Config. I keep getting error 10001 when trying to run it, regardless of the order of the channels (I have tried ascending and descending).
Any advice would be helpful
thanks in advance

Hello,
First, make sure you use the channel names and numbers as in the Measurement and Automation Explorer (MAX). If you already do, then doing the acquicition on those channels in MAX and see if that works. From there, I would then check the example vi to make sure the channel settings match those in MAX.
Here are some documents that will help you troubleshoot this error further:
How Do I Handle the DAQ -10001 Error?
Error -10001 When Using Virtual Channel and Remote Device Access (RDA)
Why do I Receive Error -10001 with the AMUX-64T when Reading Multiple Channels in LabVIEW?
AI Group Config Error 10001 using Virtual Channels
Hope this helps.
Zvezdana S.
National Instruments

Error -10401 occurred at AI Group Config - in relation to USB-6008

I'm attempting to run a simple vi that uses AI Aquire Waveforms.vi to input voltage data that I have coming in from the USB-6008 DAQ. However, when I try running the program, I receive the error:
Error -10401 occurred at AI Group Config
Possible reason(s):
NI-DAQ LV: The specified device is not a National Instruments product, the driver does not support the device (for example, the driver was released before the device was supported), or the device has not been configured using the Measurement & Automation Explorer.
And I'm not sure how to fix it. In MAX, the device seems to be working properly and everyhting seems to work fine in the test panel, so I'm slightly at a loss. I'm running Labview 7.1, and installed NI-DAQmx 7.5 which came with the USB-6008.

Never mind. I'm new to Labview, and didn't realize that I could not use the traditonal Data Aquisition components with the USB-5008 (I didn't even realize that NI-Daqmx was different).

Help resolving "Error 10401 occurrred at AI/AO Group Config"

Hello, I know this is a common error but I'm unable to find a solution looking through these forums and other websites. I am trying to convert a program wrote on an old computer running LabVIEW 6 to a new computer (with newer hardware) running LabVIEW 8.5. I've resolved all issues that have came up so far (installing the traditional legacy drivers and such). The only error I am getting now is a run-time error that pops up and reads:
"Error 10401 occurred at AI Group Config" and "Error 10401 occurred at AO Group Config"
I've already run the Measurement and Automation Explorer (MAX) and that did not help. I'm using Windows XP and my hardware is a NI PCI-6281 M series DAQ.
Do I have to re-write the sub-VI's, or is this fixable? Is there an easier way to convert a program?
If anyone can provide any help or insight what so ever it is greatly appreciated.
Thanks,
Alex

Alex,
This Developer Zone article may also be of some help to
see the differences between Traditional DAQ and DAQmx for the most common tasks.
Mark E.
Precision DC Product Support Engineer
National Instruments
Digital Multimeters (DMMs) and LCR Meters
Programmable Power Supplies and Source Measure Units

Config error, account determ, group missing for paid by company exp.type

Hi All,
When I am adding an Expense type to an Expense report,I am getting the following error message:
"Config error, account determ, group missing for paid by company exp.type"
I have maintained the configuration in Business configuration>Fine tune activity>Expense reporting-US.
I have maintained Expense Reimbursement Group as Z1(Customized) as well asExpense Account:- but not maintained offsetting Account For Paid Expenses.
Please find the screenshot.
Sincerely,
Rajitha

Dear All,
SAP development has created a software correction related to the issue.
Software correction is deployed in customer systems on 25th August,2014.
Sincerely,
Manasa Anantapur

I'm getting a syntax error (#10001) with my AI Group Config. What could be causing it?

When I go to run my program, shortly after it starts, it spits out an error #10001 involving the AI Group Config. This is it's suggested explanation:
Ni-DAQ LV: An error was detected in the input string; the arrangement or ordering of the characters in the string is not consistent with the expected ordering.
I've looked to make sure the assigned device name is the same as the expected one, so I know that's not it. Does anyone have any idea what could be causing this?

Hi,
First, i must mention that the way u put it "it spits out an error #10001" sounds horribly good!
Now to the problem, this error is usuall given if you enter an improper channel number(a string instead of numeric)
AI group config is a traditional daq function and channels are reperesented by numerals.
check if you have entered channel numbers in proper syntax.
regards
Dev

Help with Error -10401 occurred at AO Group Config

I am receiving the error: "Error -10401 occurred at AO Group Config" and have been unable to fix it.
Some background: This is someone else's program who has since left, so I am not very familiar with it. It was running fine a little while ago, until the PCI-GPIB card broke. We got a new GPIB card (essentially the exact same model; the old one was 183619B-01; the new one is 183617K-01) and now this error appears every time I try to run it.
I believe this is being thrown by the "AO Config.vi" in my VI Hierarchy. From reading other forums, such as this: http://digital.ni.com/public.nsf/allkb/46F78EDD19BA0CC386256CEE007201FC and this: http://forums.ni.com/t5/LabVIEW/Change-in-PCI-Device-Number/m-p/2312186#M726679, it seems it may be a problem with properly assigning device numbers. (The new GPIB card may have been assigned a new device number while the program is calling the old one). However, the solution offered is to right-click on the device in MAX and change the device number, but when I right-click I am not given that option (see attached image). On the other hand, it could also be some sort of driver problem.
I am running LabVIEW 8.2.1 and Measurement and Automation Explorer 4.2.1.3001 on Windows XP SP2. Any help is greatly appreciated.
Attachments:
error.PNG ‏89 KB
right click.PNG ‏77 KB
hierarchy.PNG ‏94 KB

Hi bh424,
I would make sure that you have updated drivers as you mentioned. If you are using TDAQ make sure to reset the device driver mentioned in the KB you listed.
Another thought would to be to remove and readd the device in MAX to refresh it, and potentially change the naming in your program to reference a new named device. If you cannot rename the device in MAX you could look at repointing the device in your code.
Are you able to communicate with the device at all in MAX through simple queries? From the right click screenshot it looks like *IDN did not communicate properly.
Have you also refreshed the list or rebooted your machine?
http://digital.ni.com/public.nsf/allkb/23B5918E5604915B86256C2B005F4D70?OpenDocument
I would first ensure you can communicate with the new card in MAX alone. Here are some troublehsooting steps if that is not the case:
http://digital.ni.com/public.nsf/allkb/A80DBFCCAC36EBDE862562C80058856E?OpenDocument
There is also the possibility that the card is broken as well. If it was indeed purchased from a 3rd party vendor, there is less we know about the card or what could have been done to it before you acquired it.
Regards,
James W.
Applications Engineer
National Instruments

An error occurred loading VI'AI Group Config.vi,.

I am trying to move a program from windows 98 to my laptop which runs XP and I keep getting the following two error messages when I try to run the program:
1. An error occurred loading VI'AI Group Config.vi,. LabVIEW load error code 21: An external subroutine required for execution could not be found
2. Error - 10243 occurred at DIO Port Config.
Does anybody have suggestions as how to fix these errors?

Hello,
It it very possible that you have developed your application (.exe) with one version of the NI-DAQ driver on the 98 machine and have loaded a different version of NI-DAQ on to the XP machine. This would explain both error 21 and 10243. There are only a couple of versions of the NI-DAQ driver that support both 98 and XP. Thus, it is very likely that you could have developed on the 98 machine with a version of NI-DAQ that does not support XP. Please check that you are developing on 98 with either of these versions of NI-DAQ 6.9.0, 6.9.3 with patch 6.9.3f5, 7.0, or 7.1. I would recommend using 7.1, since it is the most recent of the Traditional NI-DAQ drivers that support both OS. If you find that your .exe was developed with a version older than 6.9.0 you might need to upgrade the driver on the developement machine.
For error 21, please refer to the KnowledgeBase linked below for more detail.
KB 0ZTKCAWV: Error 21 While Loading LabVIEW Executable on Target Machine
For error 10243, it is looking for a the configuration that it can not open or acces. Please also refer to the linked KnowledgeBase.
KB 3ADBL74B: LabVIEW Error 10243
KB 18K8B88U: All my LabVIEW DAQ VIs return error -10243
Please also make sure that you are using the same version of LabVIEW and DAQ driver on both the developement and target machine.
Samantha
National Instruments
Applications Engineer

Exception occurred: "AI Group Config"

Recently I have gotten a problem with my LabVIEW VI, used to acquire data from a MEA-Chip. As soon as I try to change the setup of my
PCI 6071 E I get he following error:
Exception occurred within the external code called by a call library function Node. This might have corrupted LabVIEWs memory. Save....
After closing the popup: The VI was stopped at node 0x214 of sub VI "AI Group Config".
I use "AI Config" to initialize and change the setup of the PCI 6071 E. While the initialization works without any problems, an attempt to change any parameter (for example the sample rate), by resetting the device and calling "AI Config" again, leads to that particular exception.
Yet the actual problem is, that the VI worked perfectly for months until last week. There haven't been any changes to the measurement system, but suddenly this error pops up and I have not found any solution so far.
I even tried the PCI 6071 E on an older PC, which had formerly been used, but the problem remains.
The LabVIEW version is 7.1, both PC's run on windows XP, whereas the hardware components are fairly different, but that should not be a problem I suppose.
If anyone knows what might suddenly cause this problem please let me know.
Thanks and regards
Robert Bestel

Hello Robert Bestel,
when reading your post my first guess was that a reinstallation of the traditional DAQ driver might fix this problem.
After some research i found some similar cases in the past. Most of the time reinstalling the driver didnt fix the problem, but its worth a try.
Other users had the same problem when their PC Hardware (RAM) got corrupt. To eliminate this possiblity i suggest to run "Memtest" and "Scandisk".
Here is another Forum thread dealing with a different issue, but the suggestions might work here was well:
http://forums.ni.com/t5/LabVIEW/corrupted-LabVIEW-s-memory/m-p/558031?requireLogin=False
Its also possible that this problem might have been caused by some faulty Windows Update. So a complete reinstalltion of windows as well as all NI software could help as a last solution.
Regards
Moritz M.

Is anyone else having Config error 16 issue when trying to start PSE 12 or Premier Elements after Mac upgrade to Yosemite 10.10 on iMac

Is anyone else having Config error 16 issue when trying to start PSE 12 or Premier Elements 12 after the Mac upgrade to OS X Yosemite 10.10 on iMac. I have had a number of issues with software and things after upgrading to OS X Yosemite 10.10 and even 10.10.1. I have uninstalled and reinstalled both PSE 12 and Premier Elements 12 a number of times and everything goes fine until its ready to launch and then you get an error message. Numerous uninstalled and reinstalls don't removing the problem. Strangely enough PSE 11 still appears to boot up and I never owned Premier Elements 11 so I don't know if it will start. I thought with Apple dropping its Apeture software and greater integration of iPhoto and Apeture files into Lightroom 5.7 all would be harmonious between these two players. Im not sure where Adobe wants us to go it recently removed the plugin to allow you to update files from LR to Adobe Revel, whats up with that. I now own two version of Adobe software that no longer work with my Mac and now way of uploading pictures from Lightroom to Revel. Needless to say I am pretty reluctant to sign on to a subscription of Creative Cloud with long term financial obligations when I can't even get my current Adobe software to work independently much less integrate with Lightroom. Frustrated with it all!

Get rid of 'put disks to sleep when possible' and you may see a dramatic improvement (not necessarily a cure).
That specific problem is a multiple-Processor (including graphics processor) problem, where one of the processors lost track of whether it should be responding to interrupts. You may have a Hardware problem.

Acrobat X Pro Config Error 130:11

Hello,
I've now un-installed & re-installed Acrobat X Pro a couple of times in order to get over the issue of Config Error 130:11 - which causes the application to quit (see link to original thread below).
However, I cannot afford to do this continuously - where do I go from here?
Thanks,
Kieran
http://forums.adobe.com/thread/1013013?tstart=30

Hi there,
The workaround we have right now is to:
Launch any other CS6 product (such as Photoshop or InDesign)
It will pop-up trial screen at launch.
Click on License this software and restart subscription.
Launch Acrobat X after this. It should launch fine
Our engineering team is working on getting a permanent fix available for this issue.
I'm sorry for the inconvenience!
-David

Apple Outlook DAV Config error with Windows7; Any help?

I have updated Windows7 and I have downloaded the icloud control panel. I keep getting the Apple Outlook DAV Config error. Any help?

I encountered the same problem yesterday. I have not found a solution but take a look at this thread. https://discussions.apple.com/thread/3377753?start=0&tstart=0 The conclusion (at that time) was a conflict between iClound and reoccurring appointments in Outlook. The only solution: delete all of your reoccurring appointments in outlook (and stop using them going forward too?)........not very feasible for me.
Let me know if you find anything.

AO Group COnfig Error

Similar Messages

Maybe you are looking for