LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem about data in "real time"

Hi steve,

 

Sorry, I wasn't working the last days. 

 

I tried to put a structure around the "write to measurement file" as you told me in your last message. But it doesn't work. Something is strange, I got 0 error but the file isn't created. 

 

To be more specific, if in the "write to measurement files" settings, I tick "ask the users to choose a file", i will have the answer and the file is created after, but I can't choose when exactly. So it's a problem. And in addition, I still got the same data in all lanes, as before. 

 

But when I don't tick this option, and chose just "save in a file" the file isn't created at all... 

 

 

0 Kudos
Message 51 of 58
(1,236 Views)

About the error "5", I don't understand too...

 

I tried to change the location of the file, the name, etc. And nothing works. I never seen this error before, and finally I did a lot of test and saved lot's of file before this part of the code. So I don't understand why now, I got this error, cause I got exactly the same settings than before. 

0 Kudos
Message 52 of 58
(1,235 Views)

If you zip up a copy like you did before, I will look at it.

 

steve

----------------------------------------------------------------------------------------------------------------
Founding (and only) member of AUITA - the Anti UI Thread Association.
----------------------------------------------------------------------------------------------------------------
0 Kudos
Message 53 of 58
(1,230 Views)

I hope that I'll send everything :s

 

I hope that you will understand what's wrong with it ...

 

Thank you, again.

 

Maxime

0 Kudos
Message 54 of 58
(1,226 Views)

It looks like your vi has been drinking Smiley Wink

 

The first thing I see is you used a while loop instead of a case structure around the Express vi.

The little true/false constant should be wire to the case selector. (Use to turn on/off logging)

You wont need the second stop button.

 

I'll do some more checking.

----------------------------------------------------------------------------------------------------------------
Founding (and only) member of AUITA - the Anti UI Thread Association.
----------------------------------------------------------------------------------------------------------------
Message 55 of 58
(1,222 Views)

Oh, there is an enable input on the Express vi.

There is no need for any extra structure.

Just a true/false connected to the enable input.

(The second one down on the left side.)

 

----------------------------------------------------------------------------------------------------------------
Founding (and only) member of AUITA - the Anti UI Thread Association.
----------------------------------------------------------------------------------------------------------------
Message 56 of 58
(1,219 Views)

When you are talking about the "express vi" I don't understand what is this 😮 

 

This is the VI multi task ? :s 

 

Cause, I thought that's the block measure file, then I deleted the loop while and I put a loop condition. I don't know if you would say that... but I did it, and I got the error 5, again... 

 

Now about the second message, I don't find the enable input >< 

 

I got this  : ex multi tasks.PNG

 

But I don't know if it's what you want >< 

 

0 Kudos
Message 57 of 58
(1,212 Views)

Yes, I was talking about the "DAQmx Multi tasks" vi.

 

When I removed the while loop you added, and reset the target file,

the vi runs OK including saving the data to a file.

I am, however, using simulated hardware.

Actually I did get an error 5 once - I did have the file open, so it was expected.

 

Your implementation of the case structure should work. (Set a false to disable logging)

Although there is a simpler method available.

Here is the context help for the "Write to Measurement File" express vi.

write to meas file.png

----------------------------------------------------------------------------------------------------------------
Founding (and only) member of AUITA - the Anti UI Thread Association.
----------------------------------------------------------------------------------------------------------------
0 Kudos
Message 58 of 58
(1,173 Views)