01-16-2006 04:24 AM
Error Code: -50150
DAQmx Create Channel (AI-Voltage-Basic).vi<append>
<B>Task Name: </B>_unnamedTask<0>
Can anyone shed some light on this problem?
Cheers.
01-17-2006 05:49 AM
Hi Neilelph,
What version of DAQmx are you using?
Emma R
NIUK & Ireland
01-17-2006 05:54 AM
Version 7.5
Thanks.
Neil.
01-17-2006 09:02 AM
Hi Neil,
Do you have access to the code? If so can you Post the relevent section - containing AI-Voltage-Basic.vi?
You say that the error 50150 occurs occasionally, can you get it to error on purpose? how? does it error when you enter a certain value or perform a particular task?
Thanks
Emma R
NIUK & Ireland
01-17-2006 09:18 AM
Hi.
I can't replicate the problem or force the error at all. I only see the error code in the database where the results are saved, and an email is also automatically sent to me with the entire error message.
I've attached the code for yo to have a look at (minus a couple of sub VI's)
Cheers.
Neil.
01-24-2006 04:02 AM
01-24-2006 08:00 AM
Apologies. Didn't notice a sub vi was missing.
All the missing Sub vi does, is returns the time and date.
The code you posted is not quite the same as what I am doing - I only run the code you posted once, then quit the application, then do the same at regular intervals. This is controlled using the PC Task manager. Your code will just cycle until the stop button is pressed.
Perhaps you can try your testing on the code attached using your PC Task Manager to run it every 30 seconds, for example (you may have to build the code into an executable first). I'll try tesing with the code you posted to see if the error can be produced without quitting the app at the end.
Just curious, but does the error code -50150 not mean anything?
Incidentally, the VI's that I removed from the code, just send an email out if an error occurs - the DAQmx code is run before any other Sub VI's and so the error can't be emanating from them (given that the app is killed, and then re-started afresh for the next cycle)
Thanks.
Neil.
01-25-2006 10:58 AM
01-26-2006 03:08 AM
11-15-2012 03:34 AM - edited 11-15-2012 03:37 AM
Hi fellas,
I have a really similar problem to the one Neilelph had, but I can´t see how to solve it from your answers. I attached a picture of my main .VI.
It´s basically a photodiode measurment system working as follows:
1. First the moving stages for the system get ready (X-Y moving stages for the Photodiode and Z stage for the Laser). That´s the CONFIG subVI in the left.
2. Then there is a For Loop, that repeats N times depending on the Initial Z, final Z and step values. So in this .VI the laser moving stage is the only one changing.
3. In each loop, the stages go to the X,Y,Z(t) posiition (MOV subVI), wait for the movement (WAIT subVI) and read the position. After that, the DAQmx acquistion part starts. I just sample the output DC voltage coming from the Photodiode (Dev1/ao1), 1000 samples in 1 second, and then I make an average of all of them with the Basic DC/rms block. So at the end I have 1 position of Z and one DC value. And it worked perfectly. At least for small number of iterations I have no problems.
The problem comes with small steps and a great number of iterations. For example last night I ran a measurement. 10000 iterations, the whole range of Z, and today i checked it. It worked fine until 5000 give or take, the half of the range. From that point, the DC ouput recorded in the .lvm file is just 0.00000. It´s the second time it happens, so I´m wondering what´s wrong because I´m affraid to make more long measurments and obtain the same results.
The error message I obtained is the same than in the thread title: -50150 DAQmx Create Channel (AI-Voltage-Basic).vi:6<append> <B>Task Name: </B>_unnamedTask<53BC>
Maybe it would be useful to mention that, sometimes, there is no error and I have some DC Output Voltage value, for random Z potitions, but since the first error message, that barely happens. The output is almost always 0.
Sorry for my writting skills in English. I hope you can understand my situation.
Thank you in advance.
Kind regards,
frilance.