NI Daq / Labview error 10243

I'm using NI-DAQ 6.6 with Mac OS9 and have encountered a configuration error. I can't open the configuration utility because the system says that it's still checking the system. Question: Is the original file extension for this utility niconfig.daq? I tried to save this file as a different named file just prior to this crash.

It sounds like something became corrupted and is no longer functioning. I would try to uninstall NI-DAQ then download and install the latest drivers for your machine.
NI-DAQ Version 6.6.1 for Mac OS
Otis
Training and Certification
Product Support Engineer
National Instruments

Similar Messages

Ni-DAQLV error -10243, error-10008 & error-10401

I am using labvirew6.0. I have the following errors "Ni-DAQLV error -10243, error-10008 & error-10401" Do I need to install the latest drivers on my system?I still want to use labview6.0?

Hello
I am using labview 7.0, Max 3.1.1.3004 and i am having the same problem.
We currently have two pc's running labview 7.0. This system is step up with one
pc as the main controlling pc and the other pc mainly collect data and
transfers it to the main pc. PC1 is the main controlling pc and PC2 is the
data collecting pc it has a daq card 6025E and two 6527 cards.
The
6025E is used to collect and monitor transducer and collect pressure readings.
The 6527 are you use to trigger I/Q points to open and close doors, trigger
LEDS and other functions on our system. This current system works fine. What we
are attempting to do is recreate a complete back system, the PCs.
This Code written by a third party and we no longer have them as a resource.
The un-complied code is broken up into to sections one set of code is for PC1
and the other set of code is for PC2. So we took the un-complied code for PC1
and complied on what is going to be our back up PC1, all went good and the back
for PC1 is ready. Here is where we run in problems. We took the un-complied
code for PC2 and complied it on back up PC2.
BackUp
PC2 contains one 6025E card and two 6527 cards. When we try to run the
EXE file we get a 10001 only if a file called niconfig.daq is within the folder
containing the exe file. When I remove this file called niconfig.daq, we now
get 10243 error code. Since we are unable to contact the original programmer I
have not clue it that niconfig.daq file needs to be there or not.
How do you read a .daq file anyway in text pad it's unreadable.
Error code 10243 says occurred at DIO Port
Config, I can find that .vi within the code but how do I know what needs to be
changed in that .vi, DIO Port
Config is a labview pre-built vi and not
a customer vi. any ideas of what that could be? I saw the post suggesting the driver update i will try that and let you know if it fixes the problem. anyone have any ideas?
FYI lvdaq.dll 7.256.3.1 is also complied and place in the same folder with our EXE

E-Series Diagnostic Utility gives Error 10243

NI-DAQmx recognizes and works well with my PCI-6024E but Tradional NI-DAQ does not recognize board.
E-Series Diagnostic Utility returns "Error 10243 occurred at cwdaq. The driver could not locate or open the configuration file, or the format of the configuration file is not compatible with the currently installed driver."
No *.DAQ files can be found on root drive (including C:/Windows).
MAX 3.1 repeated installed and un-installed (includes Traditional NI-DAQ 7.3.0f1 & NI-DAQmx 7.3.1f0) does not help.
Un-installing and re-installing PCI-6024E in Device Manager does not help.
Running Windows XP Home Edition, SP 2, logged in as user with administrator privileges. Also running Norton Antivirus, Norton Firewall, Norton Intrusion Detection. No messages of logs from security software.
Next move: un-install NI software, turn off security software and reinstall.
Question: is it necessary to be logged in administrator when installing, or is a user with administrator privileges sufficient?
Question: Why do I not have a configuration file?
Thanks!

OK, I've done the following and Traditional NI-DAQ still does not even show up under "Devices and Interfaces" in MAX:
1) Uninstall of ALL NI software using the usual Windows Add/Remove Programs.
2) Removed the PCI-6024E and checked it in a different computer. Traditional NI-DAQ recognizes it. NI-DAQmx in current computer has seen PCI_6024E. HARDWARE IS GOOD!
3) Searched for files containing DAQ, NI or National and manually deleted them.
4) Downloaded fresh copy of NIDAQ731CD1, extracted and installed Traditional NI-DAQ only. I see NO DIFFERENCE between this the prior sets of files. Shut down computer.
5) Installed PCI-6024E. Started computer, allowed card to be recognized.
6) Started MAX. Card is not only not recognized by Traditional NI-DAQ, but My System / Devices and Interfaces does not have a line for Traditional NI-DAQ.
7) Went to Device Manager. Data Acquisition Devices / PCI-6024E is listed in good condition. Oddly enough the Properties for this devices show Driver Date and Driver Version as "Not Available". IS THIS CORRECT?
WHAT IS MY NEXT MOVE?
A) I counted +175 Registry values containing "National". No telling how many more DAQ entries there are. DO I HAVE TO MANUALLY REMOVE THESE?
B) After supposedly unintalling NI software I found A LOT of directories, files and registry values left behind. I'm guessing that one of these is bad and is being inherited by the new installation. HOW DO I REMOVE EVERYTHING? Is there a utility available that wipes EVERYTHING (short of reformating the drive)?
You can probably tell by the capitalized words that I'm getting irate. I've spent a couple of days working on this and am disappointed.
GDR

How to disable drive upon LabView error

I'm running a closed loop PD position controller in Labview 8.5 and NI PCI-6259 M series card and BNC-2120. I'm sending an analog voltage signal (+/- 10) to a Copley Xenus amplifier (current command) as well as a +5v signal to enable the amplifier. The controller uses position for feedback. When labview errors out, the daq card stays in its current state (and keeps sending the 5v enable signal). For safety reasons, how can I configure my system so that this signal stops being sent out, and the amp is disabled?
Maciek

The program crashed. I shut off the amp. The actuator shaft, which is positioned vertically, dropped to its lowest position due to gravity (it's a linear actuator). The daq card kept pumping out a high force command, due to the large position error created by the disturbance, as well as the 5v enable signal. Upon turning the amp back on, the PD controller saw a large difference between desired and actual position, and the actuator shaft shot up forcefully, creating a very dangerous situation. In the program, I have a case structure which won't enable the amp. unless the difference between desired and actual position is small enough. But the amp stays enabled when labview crashes.
m

Labview error GPIB controller not adressed correctly

I get this Labview error: GPIB controller not adressed correctly (LV5.1, win NT4) when i try to send data to a HP4275A LCR meter. How ever it works on an older system running with LabView 5.0 (also NT)!!!
How can I get rid of this problem????

Hi Diego, thanks for the hints!
I tried to configure (GPIB) everything standard.
when I try a 488 command initialze, I get the controller conflict, when i don't do this I get atime out problem either by 488 write-command or by 488.2 send-command.
the differences between the systems where it works and where not are:
working: Win 95, LV 5.0, GPIB-card/TNT (plug & play)
not-working: WinNT, LV 5.1, GPIB-card/PCI
i tried to set baord config to the same parameters...
on the faulti system however I see the instrument with the MAX and I can send commands, without problems !!!!
Also the driver you posted does not work (but the NI-communicate program ;-)
i have no clue what else to do!
btw. how do I copy the spy output when running the program? I may provide
this to find errors.
Since MAX indicates the board is all right I guess it is not necessary to reinstall the boarddrivers?!

LabVIEW error code3: Could not load front panel.

Hi
I am getting second time the "LabVIEW error code3: Could not load front panel." when working with the development environment of LabVIEW 2009 SP1.
It is really annoying as I loose time as I have to revert to saved previously code.
Does anybody know where it may be coming from and how to avoid it?
Thanks
Pawel
Solved!
Go to Solution.

Pawel,
the panel has an origin which you can see in your VI:
Every element will be placed in a position in regard to this origin:
The position has a limit in regard to the bound. I am not sure about the value, but it should be around -35k...35k (or the double of it)....
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

General Labview Error Handler question discussion

Recently two functions were brought to my attention, the General Error Handler and the Simple Error handler.
And I cannot wrap my hand around these two features. While I have been using Labview I have always used the Labview error cluster. When would you use these two features? As I feel the cluster error is much help.
Maybe it is my defnition that I have confused:
The general error handler will display a dialogue box describing the error that will be passed and shuts down the code?
The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated. "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error." How is this not the same as an error cluster?
If anyone has any simple code examples for this or knowledge I greatly appriciate it.
Caleb

Jacobson wrote:
Psireaper9 wrote:
The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated. "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error." How is this not the same as an error cluster?
You are correct that they give the same information. The difference is that if you want to use an error cluster you will need an indicator on your front panel. If you use the simple error handler you won't have to have an error cluster on your front panel but the user will be notified if an error does occur.
Think about all the programs you normally use (excel, chrome, etc.). As a user you expect that errors aren't happening, and if errors do occur then the application will usually just close out and you get an error dialog about the error.
I use the simple error handler with no user interaction to extract the error text. Is there an easier way of doing that?

How to force TestStand to ignore LabVIEW errors

Hi,
usually where there is an error in the LabVIEW code module TestStand stops and gives a pouup message .
Is there any way to force TestStand to ignore LabVIEW errors and contiouse testing?
Thanks

You can also work more globally - go to the Configure menu item and select Station Options.
At the bottom of the execution tab, there's a section for what to do on Run-time errors. -> Show dialog, Cleanup, Ignore or Abort.
Whilst not specific to steps configured to use the LabVIEW adapter (assuming you're mixing some programming languages) that at least get you continuing on to the next step without the dialog.
If you need to assess if it's specifically LabVIEW modules causing the error, then you need to use the Station, Process Model or Sequence File callback for On run-time error, and the step gets passed as a parameter. That would allow you to work out if the step was LabVIEW specifically and then make a decision as to what to do next.
Hope that helps.

How to terminate TestStand Application after a LabView error.

We've just started launching TestStand from a command line, and when it (TS) stops sequence execution due to a LabView error, the command window doesn't know its status. So, I have a two part question:
1) Is there a way to COMPLETELY STOP the TestStand application when a LabView error is encountered? (I have been able to get the error popup to stop, but TestStand is still active and the command line is still sitting there thinking everything is fine).
2) Assuming that there is a solution to #1, is there also a way to get LV or TS to report the error to an external command prompt or batch file?
Thanks,
   - Paul Iovanna
Solved!
Go to Solution.

Hi Manooch,
We've managed to get the TestStand sequence to stop when we want it to (by using the /quit option in the command line), but now we can't seem to get Reports to generate.
Specifically what we are doing is including a particular test sequence in a fully automated Build/Test/Report system. After an automated build of our product completes, we have tools and command files that load all appropriate code into the various components of our system, and then we lauch a TestStand sequence that exercises much of the newly imaged system. Since we are running from the command line - and that command line is being monitored by other processes within our Build/Test/Report system, we need to have TestStand stop AND exit, or else the command line just hangs.
So, we really need two things to happen:
1) Get TestStand to stop execution AND exit - and we seem to have this working.
2) Report the results from the test sequence:
   - We have no problem doing this when the Sequnce Editor is launched directly, and the sequence is started from its GUI.
   - However, when we use the command line to launch the sequence via your "TestExec.exe" - there's no report! All of the Report Options settings are the same as for the Sequnce Editor GUI.
So, at a minimum, we need to get the usual report to be generated and saved when we launch from the command line - and the preferred option would be to have any error codes from TestStand (or LabView, since the test sequence uses only LV steps) reported directly to the stdout, in this case the command line.
Hopefully that explains our setup and requirements a little better - and thanks in advance for the assistance.
FYI - TestStand version 4.1.1 running on Windows XP.

Watch the NI-Week 2009 Presentation: Updating the LabVIEW Error Handling Core

The resources for the "Updating the LabVIEW Error Handling Core" NI-Week 2009 Presentation are now online.
See them here: http://lavag.org/topic/10741-updating-the-labview-error-handling-core/
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

I have always gone the latter route when I needed it. I usually use an action engine to keep track of the error messages. Said action engine can be used to combine and suppress errors, as well. I have posted an example below (LabVIEw 7.1). In this case, the error propagation is occurring in a task handler which is processing multiple command/data pairs. The command is set at the beginning of the task and the error handler is sprinkled liberally throughout the task code. In this particular case, the desired behavior is to continue execution on error, but log the errors.
I prefer this type of method because it gives me complete control over the error propagation. It has the down side of requiring more code and effort, but I think it is worth it. I like functionality to be explicit on my block diagrams. It makes long-term maintenance much easier.
This account is no longer active. Contact ShadesOfGray for current posts and information.
Attachments:
ErrorPropagation.llb ‏65 KB

LabVIEW can't find NI-DAQ driver (error 10240).

NI-DAQ is installed, and all the tests in the configuration utility work
fine with the PCI 1200 card. I can see a sine wave from a function
generator, so NI-DAQ works. But no DAQ VIs run, neither the examples
included with LabVIEW nor test programs I've written myself. Error message
10240 is always displayed: "NI-DAQ: LV can't find NI-DAQ driver."
I am working with an older setup, trying to recover an experiment from years
ago. It's a Power Macintosh 7500 with a 100MHz 601 processor and a PCI 1200
DAQ card. LabVIEW 4.0 installed. I've tried downloading several versions
of NI-DAQ from the NI site, but I can't find any support for LabVIEW 4.0.
Currently NI-DAQ 6.6.1 is installed, the version recommen
ded on the site for
Power Macs.
Does this version of NI-DAQ not work with LabVIEW 4.0? If not, what version
of NI-DAQ will work? Is there some way to tell LabVIEW where the NI-DAQ
driver is?
Upgrading LabVIEW or the hardware is a last resort. I just want to get this
experiment running as soon as possible.
My email address is [email protected]

Thanks. But the version of NI-DAQ that was installed when I wrote the email
was NI-DAQ 6.6, and still the error message appeared. I've since pulled the
card and put it into a PC with a more recent version of Lab VIEW and it
works.
"Ryan M" wrote in message
news:[email protected]..
> The latest version of NI-DAQ supporting LabVIEW 4.0 is NI-DAQ 6.6.
> More information regarding this can be found in National Instrument's
> Knowledge Base at:
>
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/d8d43c0b1b
881101862569eb005cda39?OpenDocument
>
> Ryan Mosley
> National Instruments, Applications Engineer
> http://www.ni.com/exchange

LabVIEW error 10899 when testing a virtual channel

I am setting up a virtual analog voltage output channel in the "Measurement and Automation Explorer". I am able to get throught that process and it shows up under "Traditional NI-DAQ Virtual Channels" on the left. When I right
click on the channel and then go to "Test", I get the message "Error - 10899 occured at AO group config".
Sometimes when clicking on test, the MAX crashes and a random window from LabVIEW pops up on the screen. Then I
have to open the MAX again.

Hello bberma01,
I don't like to give you this type of answer, but in this case I think the best think to do is to unistall and reinstall your driver. While we are at it, DAQmx is the newest driver and is very user friendly. I would suggest using it for your data acquisition development.
If you need to download the driver, you can find it Here

Test panel in NI DAQ/ Labview

Hi
I downloaded NI-DAQ and Labview 6i evaluation version to program my DAQ 6020E(BNC) . I clicked on MAX and in the "configuration tree" i see under "devices and interfaces" my DAQ device present, but when i right click on my device i see that the test panel is disabled .My O.S. is Windows Vista. Sometimes i get errors like" NI-Max" files stopped working or "shared" file stopped working etc. What should i do to enable "test panel" on Max? My aim is to program one analog output channel to generate 5.5Volt for which i need test panel. Without the test panel being active, is there an alternate way to do this? The green LED on DAQ board usually is on but occassionally it blinks but finally stabilizes to continuously on state.
Regards

duplicate post. Please don't ask the same question to multiple boards. Your question doesn't seem related to the student edition or Elvis either.

Labview error 2500

Hello all,
I am trying to read a channel from a TDM file and send the data continuously over an analog port. This seems to function when I have only one analog output but when i try to use two channels, it shows an error 2500. This error is not part of the documentation and the exact message at my end is:
Invoke Node in _saveFloat64Channel.vi-
I am using Labview 8.0 with DAQ 8.3.1. The hardware in question is the NI USB 6251.
Please advise.
Regards,
Shailesh.

Things you can improve,
1. Start the AI task probably just before you start the AO task, else if the read from file and genration takes time, you may get buffer overflow error.
2. Change the AO write to N Channel>>Multiple Samples>> 2D Double/ 1D Waveform depending on whether u are using Double or waveform data type.
3. The error that you mentioned in the first post is most likely to come from the TDM write inside the while loop. There may be other errors, but you may be getting only the first one. So it will be a good idea to put a probe on all the three error wires inside the while loop and se if you are getting in in them or not.
4. Inside the while loop after AI Read, the DBL conversion is not required. You can remove it.
5. I am not very sure what you are trying to do in the file read part?You can use array of DBL only if the number of elements that you read from the file and the number of elements from the lookup table are same. Else it is better to use waveform.
Can you try these things and let me know?
"A VI inside a Class is worth hundreds in the bush"
യവന്‍ പുലിയാണു കേട്ടാ!!!

LabView Error Unknown

I am new to LabView and I am getting an error popup when I try to run a particular LabView project. Could someone please list some possible places to look in my project to stop this from coming up? Labview V.6.0.2 and Measurement & Automation V.3.0.2.3005 are my tools.
Thank you,
Chris
Attachments:
LabViewError.jpg ‏296 KB

Hi Chris,
I don't know which DAQ device you are using. Here are few links where you can find for possible reasons
http://forums.ni.com/t5/Signal-Conditioning/error-10007/m-p/541897?requireLogin=False
http://digital.ni.com/public.nsf/allkb/862567530005F09F862569DF006CDFFF
http://digital.ni.com/public.nsf/allkb/474269A422CEF85286256C870006F2B8
Gaurav k
CLD Certified !!!!!
Do not forget to Mark solution and to give Kudo if problem is solved.

NI Daq / Labview error 10243

Similar Messages

Maybe you are looking for