LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW in Industry

Solved!
Go to solution

I'll add that LabVIEW isn't only used for test and measurement, but also to control real systems. My company builds high performance motor drives, solar panel inverters, energy storage systems, hybrid-electric vehicle emulators, aerospace flight controls, and many other products that require deterministic and high fidelity control systems. With LabVIEW we can write code that executes every second (PC), every millisecond (real-time), or every microsecond (FPGA) without worrying so much about low-level compiler optimizations, HDL timing constraints, and many other problems that come up with non-LabVIEW embedded systems.

0 Kudos
Message 11 of 17
(1,616 Views)

Hoovah,

 

A few abbreviations you used I'm not familiar with.  What are you referring to with DV, PV, and ED testing?

0 Kudos
Message 12 of 17
(1,612 Views)

Here at Alpha Technologies and at our subsidiary Outback Power, we use LabVIEW in production test, qualification, and R&D.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 13 of 17
(1,607 Views)

@RavensFan wrote:

Hoovah,

 

A few abbreviations you used I'm not familiar with.  What are you referring to with DV, PV, and ED testing?


Danm those TLAs. Three letter aconims. Worse,are those XTLA (extended three letter acronyms) and DXTLAs (double extended TLAs) Abbriviated TLAs are "AT"s

 

Design Verification 

 

Production Verification 

 

Engineering design? (Soft front panels)


"Should be" isn't "Is" -Jay
Message 14 of 17
(1,590 Views)

Thanks.

 

But technically they are tLA.  two Letter Acronyms.  (never heard of that one before, but since two and three both begin with a "t" .....    Smiley LOL

0 Kudos
Message 15 of 17
(1,588 Views)

ED - Engineering Development

Before any real testing is done, mostly debug level, troubleshooting tests to make sure the basics of it are working.  Tested with hand built parts, usually using similar components as the end product but nothing is set in stone on the design.  Usually no report generation is done other than a traveler piece of paper, on the UUT stating it works.

 

DV - Design Verification (and/or Validation)

Hand built parts with what is expected to be a product that is the same dimensions and using the same components as the final product.  The product is basically the same as the final ones, but the process of building them isn't refined.  The testing can be quite through and takes several months to a year to complete.

 

PV - Product (Production or Process) Validation

Parts built using the final real process.  Usually involving robots, or finalized work instructions specifying every thing about the build including screw torque amounts.  The majority of the testing DV did isn't done here because the design shouldn't change from DV to PV, but the process has so other tests might be added.

 

Usually there are multiple DVs depending on how much the design changes.  Some DVs are to cut cost and are expected, assuming the savings is worth the time and effort to perform another validation.  Some re-testing isn't required based on what was changed too.  There is hopefully only one PV, but if something major changes like the entire line moves buildings, or tooling changes take place, then multiple PVs maybe required.  For instance if a relay is replaced with a cheaper version you shouldn't need to perform leak testing again which is usually part of a DV.  But if the sealant between covers is changed a leak check will probably be necessary.

Message 16 of 17
(1,584 Views)

Those are Abbriviated TLAs just call them ATs 


"Should be" isn't "Is" -Jay
0 Kudos
Message 17 of 17
(1,555 Views)