LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Need to monitor status from VI

I have created a VI to test a pc board we purchase from a vendor.  I would like to have the VI keep track of the number of pc boards that passed each day, the number that failed, and the tests that failed.  Because of suspected quality issues with the vendor (sending us pc boards that fail tests), I would like the VI to keep track of the results and not alert the vendor.  

Is the easiest way to do this to create global variables that are loaded every time the VI is run?   

I am going to require the computer be connected to the internet, and I have created a VI that will send text message to myself.  What other ways could I have it report to me without them knowing?

 

Thank you for your advice.




metzler CLAD
0 Kudos
Message 1 of 16
(3,620 Views)
The most professional way to do all of this is, in my opinion, to write the information to a database. Why on earth would you not want the vendor to know? That is the whole purpose of quality systems used around the world. What are you doing with the boards that fail? Just accept that? You are buying product with the assumption that they work. If they don't then they should be returned to the vendor and be replaced.
Message 2 of 16
(3,617 Views)
Is your test equipment being used by the vendor in their facility?  I'd suggest that you do everything above-board and let them know that you'll be tracking the results. You're not going to fool anyone, especially with the requirement that the computer be connected to the internet.  Failure data is very valuable to their Quality people, too.
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

Message 3 of 16
(3,595 Views)

Why on earth would you not want the vendor to know? 

We have a long history with this vendor.  The quality from them was exceptional the first 3 years of this pcb.  Then they started having problems - we alerted them, and they were corrrected, for 6 months, and came back.  We end up not making shipments because of defective product from the vendor, and they claim they work.  We currently have another vendor we are looking at, and if this vendor is sending us parts that are defective and they know it, we will no longer buy this pc board from them or others.  When some vendors get the notion you may be not be buying from them in the future, they no longer deliver on their promise dates.

 

That is the whole purpose of quality systems used around the world. What are you doing with the boards that fail?   Just accept that? You are buying product with the assumption that they work. If they don't then they should be returned to the vendor and be replaced.

The pc boards that fail are being sent back to the vendor, frequently they cannot find the problem with them, so I end up repairing them - in essence, we are spending the troubleshooting labor to fix their problem. 

 

Is your test equipment being used by the vendor in their facility?

Yes, the pcb is tested at their facility. 

 

You are right, they will know that the test is being monitored because of the requirement of the internet connection. 

 

I have never written information with LabView to a database, only filled in data sheets to Excel.  Is there an example I can use to get me running - this VI is scheduled to be complete this week.

 

Thanks for the advice.




metzler CLAD
0 Kudos
Message 4 of 16
(3,589 Views)
There are a lot of good examples in Help -> Find Examples.  You could write to a CSV file if you don't have a need for related tables or complex queries.  It'd be easier to get done this week, too, seeing how you haven't used databases in LabVIEW before (although it's not difficult, and we'll help).
Message Edited by jcarmody on 04-07-2010 07:32 AM
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

Message 5 of 16
(3,586 Views)

I agree with what the others proposed.  A database is the best solution and it is not that difficult to implement (after having done it at least once 😉 )

 

I hear you with those types of manufacturers..  Seen it often..  Still see it.  Even with full QA systems in place..  And yes, if they suspect you might go away, they'll take care of others first..

We might be dealing with the same manufacturer 😄  LOL!! 😄

Message 6 of 16
(3,576 Views)

I only do LV part time, when my primary job is caught up.  It really stinks, but hopefully some day I will be doing LV full time. 

 

I will look at the examples and see what looks the easiest.

 

Thanks.




metzler CLAD
0 Kudos
Message 7 of 16
(3,564 Views)

I still need the VI to be able to report to me, and I would rather the vendor did not need to do anything. 

 

What is the easiest way for a database to be sent to me from the VI?

 




metzler CLAD
0 Kudos
Message 8 of 16
(3,552 Views)
Depending on the connection to the internet you could send yourself an e-mail on a daily basis. If you have the internet toolkit you will have the necessary VIs to send an e-mail.


Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 9 of 16
(3,549 Views)
SMTP Email Send File VI
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

0 Kudos
Message 10 of 16
(3,547 Views)