Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Advice for someone doing validation with CompactDAQ?

...the tips and tricks you wish you knew at the beginning? Asking for a friend 🙂

0 Kudos
Message 1 of 6
(666 Views)

What do you mean by "Validation with cDAQ"? What application field are you talking about?

Santhosh
Soliton Technologies

New to the forum? Please read community guidelines and how to ask smart questions

Only two ways to appreciate someone who spent their free time to reply/answer your question - give them Kudos or mark their reply as the answer/solution.

Finding it hard to source NI hardware? Try NI Trading Post
0 Kudos
Message 2 of 6
(599 Views)

Hi Santhosh.  I work with Laura and figure I'll jump in with some thoughts.  Some of the examples I have in mind include:

  • Environmental test - thermal chambers
  • Shock/vibe, NVH
  • Life-cycle / HALT
  • Structural and durability lab tests
  • Performance benchmarking (overlaps with some of the others above)
  • Electrical power and performance test/characterization
  • Software - firmware or embedded control software
  • Logic/protocol/signal validation
  • RF connectivity

Some of these are not applicable for CompactDAQ (or NI DAQ devices in general) - but leaving them there for a more complete view. Always looking to learn, so if you have different thoughts or can further educate me - please do! 🙂 

 

Larua and I are looking to help the community of data acquisition users, so the pro tips from this thread may end up in an NI Connect session, webinar, demo, or white paper. We're looking for the things that would make engineers say "I could save a ton of time if I did that" or "that would get us better data." ...something like that. 

 

thanks! -Brett

0 Kudos
Message 3 of 6
(551 Views)

Validation can mean a lot (or not enough)  ..

 

More general:

What a 17025 specialist assessor would like to see ? (more lab related, I sometimes wear that hat 😉 )

What a quality engineer needs to qualify an EOL tester for 900x <whatever>?

 

What to define for validation tests?

How to document it?

??

 

More specific:

How do I get an idea how reliable is my CompactDAQ TC temperature measurement... really... on the plane?

 

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 4 of 6
(528 Views)

Hi Henrik,

 

Thanks for the reply! I'd like to hear more about your specific experiences doing validation (in whichever role you know best). What's the hardest part? Does NI have the right documentation or videos to help you through the difficulties? Anything you want to share is appreciated. We're trying to understand the information gaps in NI documentation and fill them in hrough white papers, how-to videos, etc.

 

Thanks,

Laura 

0 Kudos
Message 5 of 6
(514 Views)

One obvious requirement is the ability to generate tamper-proof recordings

 

AMS2750 covers pyrometric requirements for thermal processing equipment used for aerospace heat treatment. It covers temperature sensors, instrumentation, thermal processing equipment, system accuracy tests, and temperature uniformity surveys. 

 

Paragraph 3.2.7.1.1 of  AMS2750E states “The system must create electronic records that cannot be altered without detection”.

 

Anybody got any ideas how to do this with the tools NI provides? I suspect many other testing & validation standards will have simmilar requirements.

0 Kudos
Message 6 of 6
(284 Views)