DAQ-Assist crashes Labview....

[emerino]

Hi,

  I'm running Labview 8.0.1

 I use the DAQ-Assist to read info from some channels.....

 I drag the icon on my block diagram, which automatically opens the wizard. I setup channels, type of signal (voltage, current, etc), hit OK and after ~30 seconds (where LV says first "Verifying task' and then "Building VI, please wait"), it creates an ExpressVI without any problems.

 The problem is whenever I try to edit/change/add settings.... Say that later I wanna change the voltage range on one of the channels, or add another channel. I go in (double click on the icon), make the changes and when I hit OK, LV crashes after about 15 or 20 seconds of displaying the "buidling VI, please wait" message.

 Usually I have to re-create the whole thing (drag a second icon, and delete the first one) to avoid the problem.

 I've seen this happen even with new VI's that I create from scratch. It happens 95% of the time, other times it works flawlessly.

 What's wrong?

[emerino]

It also gave me the error message attached next time I run LV....this however doesn't happen all the time....and I think the message is not the same (whenever it shows it)

[BrowningG]

Hello Emerino,

Thanks for contacting National Instruments. 

It looks like there is an issue with the installation of either your DAQ driver.  The knowledgebase LabVIEW Application Error: The instruction at address x referenced memory at address y. The memory c... goes over possible causes of the error you are seeing.  Most likely a file in your LabVIEW or DAQmx install has become corrupted and is causing LabVIEW to crash. 

First, attempt to repair all of your NI software.  This can be done by going to the Add or Remove Programs screen and clicking the change/remove button next to the National Instruments Software selection.  This will bring up a list of all of the installed NI software that is on your computer.  Highlight all of this software and choose to repair.  During this process the installer will ask for the LabVIEW CDs as well as locations of any installers that were downloaded to your hard drive. 

If you are still having trouble running your DAQ assistant, update to the latest version of DAQmx.  This will have updates to numerous known issues as well as increase the stability of the DAQmx driver. 

The Investigate Previous Internal Error window you are seeing after a crash is a way for you to report any unexpected errors in LabVIEW that caused it to shut down.  If you choose to report the error, National Instruments can use the information to improve its software products.  This window should only appear when opening LabVIEW after a crash occurs. 

Please post back if you continue to have issues or if you have any questions. 

[emerino]

Hi,

Well....I re-installed everything NI related as per the instructions and it didn't fix the problem.

After this, I got the error when going into Max and going into "test panels". So I re-installed Ni-DAQmx (8.6) one more time and now it's back to where it used to be....I opened a VI and tried to edit it by adding another channel. I got the error attached....

Any other ideas?

[Matt_A]

Hello emerino,

I can't say why you would be experiencing this issue, but I have a couple questions I'd like to ask and a possible workaround you could try. First, as the alternative to the DAQ Assistant, you could generate the DAQmx code that is used by the assistant. To do this, simply right-click on the DAQ Assistant and select Convert to NI-DAQmx Code. This should allow you to update the specific information including channels info, sample rates, etc without having to open the DAQ Assistant. While this may help get you up and running, it does not explain why you are receiving the error. A couple things I am wondering about:

1. What version of LabVIEW are you running?
2. Has the DAQ Assistant always behaved this way or did it work at one point?
     - If the answer to the above is "No, it hasn't always behaved this way", then what has changed since this behavior started?
3. What version of DAQmx were you running prior to the install of DAQmx 8.6?
4. Do any other Express VIs cause this problem? Like the Instrument I/O Assistant, File I/O Assistant, Create Signal Express VI, etc?
5. Does this problem occur on any other computers or just this one?
6. Does problem occur with all hardware selected or any specific hardware?

Let me know some details and I'd be happy to look into this further.

Message Edited by Matt A on 11-07-2007 10:10 PM

[Matt_A]

Message Edited by Matt A on 11-07-2007 10:11 PM

[Matt_A]

Hello emerino,

I can't say why you would be experiencing this issue, but I have a couple questions I'd like to ask and a possible workaround you could try. First, as the alternative to the DAQ Assistant, you could generate the DAQmx code that is used by the assistant. To do this, simply right-click on the DAQ Assistant and select Convert to NI-DAQmx Code. This should allow you to update the specific information including channels info, sample rates, etc without having to open the DAQ Assistant. While this may help get you up and running, it does not explain why you are receiving the error. A couple things I am wondering about:

1. What version of LabVIEW are you running?
2. Has the DAQ Assistant always behaved this way or did it work at one point?
   If the answer to the above is

[Matt_A]

Hello emerino,

I can't say why you would be experiencing this issue, but I have a couple questions I'd like to ask and a possible workaround you could try. First, as the alternative to the DAQ Assistant, you could generate the DAQmx code that is used by the assistant. To do this, simply right-click on the DAQ Assistant and select Convert to NI-DAQmx Code. This should allow you to update the specific information including channels info, sample rates, etc without having to open the DAQ Assistant. While this may help get you up and running, it does not explain why you are receiving the error. A couple things I am wondering about:

1. What version of LabVIEW are you running?
2. Has the DAQ Assistant always behaved this way or did it work at one point?
    If the answer to the above is

[Matt_A]

Message Edited by Matt A on 11-07-2007 10:11 PM

[Matt_A]

Message Edited by Matt A on 11-07-2007 10:10 PM