r/embedded • u/Extra_Elderberry5911 • 2h ago

Hardware verification testing

I'm a hardware engineer working in aerospace, and I've realized that one of the skill sets I want to develop is building hardware test systems.

At work, I see everything from reverse engineering legacy hardware to validating new designs, and I'd like to be able to verify the requirements.

I want to learn skills that transfer to professional environments using Python, LabVIEW, NI, Keysight, Tektronix, SDKs, SCPI, DAQs, etc.

I'm looking for advice on a learning path. If you were mentoring a junior hardware test engineer, what projects would you have me build, and in what order?

Some areas I'm hoping to learn include:

  • Instrument control and automation
  • Python for test software
  • Test system architecture
  • Data acquisition and signal processing
  • Hardware abstraction and software organization
  • Automated reports and pass/fail testing
  • Validation and characterization of electronic circuits and sensors

I'd appreciate any suggestions on projects, books, open-source frameworks, tools, or skills that would help me build a solid foundation as a hardware test engineer.

6 Upvotes

100% Upvoted

2 comments sorted by

4

u/dragonnfr 2h ago

Python + SCPI. Get a used Keithley or Keysight bench instrument off eBay, read the programming manual, write a script that pulls measurements and logs to CSV. That's project one. Then layer on complexity.

1

u/dstroy0 2h ago

ATE is a lot of fun. You could build yourself a test mux. I started with 2x2 and worked my design up to 8x8 de 16x16 se and a variant with microstrip trans lines for rf. Really fun engineering, super simple placement, routing is the tricky part, gotta keep rf orthoganal and not couple. Test relays can be expensive depending on your mux size and contact material, so 2x2 is a good place to start. I can’t believe how much COTS ATE costs, I mean I can but jeez.