LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Automated testing

Then add a text box to your front panel and write whatever you want to it. A shift register with a concantanate strings will work.

 

A lot of what you are asking is pretty basic stuff. Have you seen the available LabVIEW  tutorials and taken the time to go through them?

0 Kudos
Message 11 of 30
(1,097 Views)
I have not gone through the tutorials but I have been playing around with Labview, Im under a time constraint and I have my program pretty much done besides adding this text in, so I figured coming on here would be the fastest way to finish up without going through those long training courses, I will refer to these in the future tho
0 Kudos
Message 12 of 30
(1,095 Views)
Can I use the error out indicator and just place that on my front panel and connect it to the error out of the DAQ assistant ???
0 Kudos
Message 13 of 30
(1,077 Views)
This is what it looks like..if you check like frame 3 and 5 of the case structure I connected an error out to the DAQ assistant that checks IGNITION COLD...except when there should be an error its not displaying anything, is this not the right way to do this???
0 Kudos
Message 14 of 30
(1,076 Views)
0 Kudos
Message 15 of 30
(1,075 Views)
No it's not because as soon as you go to the next state, you will clear the error because you have nothing wired to it and it will use the default which is no error. What does this have to do with your previous question of getting a status message?
0 Kudos
Message 16 of 30
(1,071 Views)
I set up my VI using the setup that VT suggested which works fine if a test fails at the very end the result button says FAILED. What I want though is that at the end when it says FAILED that it would also say somewhere what failed...such as Ignition Cold, etc...
0 Kudos
Message 17 of 30
(1,068 Views)

Then do as I suggested with a string indicator. The error indicator has nothing at all to do whether the test passes or not or the kind of message you want to display.

 

Actually, I should modify my second sentence. If you get an error, you could also set the fail Boolean and text. It's when you don't get an error (and you shouldn't unless the DAQ hardware fails), that the error cluster is not at all related to pass/fail status.

0 Kudos
Message 18 of 30
(1,057 Views)
I would think it would also be pretty obvious that you could build a string array just like the Boolean status array is being built. In each case where a test is done, you just need to create separate strings for pass/fail conditions.
0 Kudos
Message 19 of 30
(1,051 Views)
Can you post a quick pic of what you are saying...it helps in my situation
0 Kudos
Message 20 of 30
(1,047 Views)