Error -2147220733 occurred at DAQ Assistant (in Measurement and Automation Explorer)

[Anti-Neutrino]

Actually the problem does seem to be persisting. Even when I shut down and start again it still produces the same errors. Even if I make a completely new NI_DAQmx Task it gives me the error when I first try and save it. I'm trying to make an 11Hz analog output signal between +/- 10V and it doesn't seem to want to let me.

Any ideas?

Thx

[Kahless]

In my episode, if a channel gave me that problem on a fresh MAX load, there was nothing that could be done to modify it.  Didn't matter if I restarted MAX again or not.  It had to be deleted.  And if I tried modifying a working channel after having received the error, the other channel would give me that error too.  So, somewhat painfully, I tried modifying my channels one by one from fresh reloads of MAX.  If it errored, I deleted it, reloaded MAX, and recreated the channel, then moved on to the next one, tried modifying it, if it errored, deleted it, reloaded MAX, etc.

This very 'picky' linear methodology was the only thing that worked for me, allowing me to successfully identify which channels were "corrupt" and replace them.  I don't know if you are trying to create a new task on a fresh load of MAX or not, but if not, or if you are not sure, perhaps try doing it that way (and deleting the old one before reloading max).

Again, this is by no means an elegant work around, but it worked for me being that there currently is no NI help file for this.  I still would love to know more details on the cause of the error myself aswell.

[Anti-Neutrino]

I have tried just about every combination you can think of... creating new tasks as well as editing existing ones in an existing MAX session and  in a fresh session. Sometimes I deleted faulty tasks, other times I didn't. I've given up for the day now and moved onto something else, I'l try again tomorrow when my patience is renewed 🙂 If problems persist I presume I can get it to do what I want it to through direct LabVIEW programming rather than VI logger tasks?

Cheers

[McKala[DE]]

Could you post your MAX data file and configuration?  The Data file is located at: C:\Program Files\National Instruments\MAX\Data if you used the default setup options.  To Export your MAX configuration, Open MAX and select File >> Export, export a NI Configuration Export File.  This will help troubleshoot the problem further.

Than I would recommend downloading a fresh copy of the latest NI-DAQmx from the Driver and Updates Page.  Uninstall your current copy of MAX and install the fresh copy from the website.  Let me know if that doesn't solve the problem.

Thanks!

[McKala[DE]]

Hi again Anti-Neutrino,

Instead of posting your Data Directory, could you zip and post your entire MAX directory? 

Also, do you remember the steps that happened before you got the -2147220733 Error?  Did you have any unusual errors or freezes?  Any information you could provide on how to reproduce this error would be very helpful.

Thanks!

Message Edited by McKala[DE] on 03-21-2006 03:05 PM

Message Edited by McKala[DE] on 03-21-2006 03:06 PM

[Anti-Neutrino]

Hi Thanks for helping,

I'll work on getting the MAX folder for you - it's not installed on this computer, but for now here is the config file you originally asked for.

I can't remember much about the way the error occurred but here's what I'm pretty sure happened.

First I was trying to make a VILogger task from an NIDAQ-mx task, and editted one of the properties (I think it was the frequency of an analog output signal, trying to make it 11Hz). When I attempted to save the task I got the error pop-up. HOWEVER the first error that pops up doesn't specify code 2147220733 in the body of the error box, only in the title. All subsequent errors DO list the error code, and as Kahless has pointed out, once a session has errored in this fashion the only workable solution is to delete the faulty task/channel and start a new session from scratch.

I have reproduced the error a number of times merely editting the default NIDAQ-mx task. I have an NI PXI-6251 which has 2 analog output channels, I have been trying to configure a task to produce an 11Hz sine wave output on channel AO0, 10V peak to peak (ie - 5V to +5V). The error crops up frequently when I try and edit two or more things in succession without saving in between, for example changing the default rate to 11Hz then changing the signal output range, then changing it to continuous for instance, all without saving.

I hope that makes sense, I'll try and get you my MAX directory.

cheers  

[Anti-Neutrino]

For some reason it won't let me attach the zipped MAX folder, perhaps it's too big? Any ideas?

Thx

[McKala[DE]]

Could you email it into support?  Use this link to create a support email and include the error number in the subject.  If you would, include both the zipped MAX folder and your configuration file just so that they are kept together.

Thanks!

[Anti-Neutrino]

OK I have done. The first time I entered the email, the surrounding text didn't appear (the whole page was blank and all the icons were red Xs) and I'm not sure if it sent. So I submitted a second one, which I tihnk has worked. Please let me know by email if there is any additional information you require.

[J Bowen]

Hello,

I just encountered the same problem with error 2147220733.  I have a DAQmx task that I switch from a real device to a simulated device.  The last time I switched to a simulated device it comes up with the error when I try to save.  I had some issues leading up to it with DAQmx not allowing me to select Built In cold junction compensation with the simulated thermo couple module.  I ran test panels on the simulated setup and it worked fine but when I try to run it in my VI I get an error pertaining to the last modification I made (evidence of it not saving the task).  I tried restarted MAX to no avail as well as creating a new task with just one temperature measurement on the simulated device and it also had the same error. 

I'll try upgrading the DAQmx driver and see if that helps at all.  And the good ole restart the machine.