Hardware-in-the-Loop Testing

The Pragmatic Embedded Podcast · 21 Sept 2021 · 34m

What this episode covers

Hosts Jeff Gable and Luca Enjani discuss hardware-in-the-loop (HIL) testing, contrasting high-fidelity aerospace systems with simpler, agile approaches for startups. They highlight the risk of 'horse-sized rabbits' where complex test rigs cost over $100,000 but provide little value, advocating instead for rudimentary setups using tools like Raspberry Pi or Python scripts. The conversation emphasizes that even a simple smoke test providing physical feedback is superior to pure software simulation, especially for catching race conditions and validating real-world interactions in medical devices and robotics.

Most relevant to

early-stage companies and companies scaling up

Topics

Mentioned

Chips
Raspberry Pi
Tools
LabVIEW, Python
Also
CAN bus, MIL-STD-1553, ARINC 429

Other shows on the same ground, closest first.

  • Embedded.fm · 1h 22m

    508: Descartes' Demon

    William Griffin, co-founder of Spark Embedded, explains the distinction between hardware-in-the-loop (HIL) and model-in-the-loop (MIL) testing, emphasizing that HIL involves a closed loop where the controller's output affects the simulated plant model. He discusses the value of model-based system design (MBSD) using tools like Simulink for off-highway vehicles and robotics, noting the trade-offs between high-fidelity simulation and cost. Griffin also shares insights on learning complex topics through repetition and creating safe environments for engineering teams to experiment and fail.

  • Embedded.fm · 1h 07m

    500: Nerding Out About the Ducks

    Komathi Sundaram, a principal test engineer at Cruise, discusses her career transition from software development to embedded testing and her philosophy on automation. She details the architecture of hardware-in-the-loop (HIL) test benches, explaining how to orchestrate real-world scenarios like NFC taps and audio loops for devices under test. Sundaram emphasizes the importance of continuous integration, using Docker for environment consistency, and designing 'brick test beds' to safely allow developers to break systems during innovation.

  • Coredump Sessions · 1h 01m

    #021: Hardware at Software Speed: How BootLoop Is Bringing AI to the Bench for Firmware Teams

    Noah Pasek-Nelson and Chris Markus, co-founders of BootLoop, explain how their AI platform accelerates the firmware lifecycle by combining deep hardware context with automated hardware-in-the-loop testing. They discuss how ingesting schematics and data sheets eliminates hallucinations, allowing the system to generate, flash, and validate code on physical devices like oscilloscopes and logic analyzers. The founders also cover BootLoop's security posture, pricing model, and its 'Sentinel' product for automated field debugging.

  • Embedded.fm · 1h 13m

    182: Sorry Little Diodes

    Hosts Elecia White and Chris Svec discuss a variety of embedded systems topics, including the use of the RTL-SDR dongle for software-defined radio and the challenges of low-quality Chinese Ham radios. They analyze the industry's need to 'grow up' regarding security and ethics, citing the ESA Schiaparelli lander failure as an example of integration testing gaps. The conversation also covers the utility of Compiler Explorer (Godbolt.org) for comparing assembly output and addresses the prevalence of imposter syndrome among engineers.

  • The Amp Hour · 1h 44m

    Pedantic or Andrantic

    Chris Gammell, a developer advocate at Hologram and founder of Contextual Electronics, joins Elecia and Chris White of Embedded.fm to discuss hardware prototyping, learning strategies, and industry tools. The conversation covers the challenges of cellular IoT connectivity, the utility of the HackRF software-defined radio, and debugging techniques using the J-Trace Pro. They also explore pedagogical concepts like the Dreyfus model for learning programming and hardware, emphasizing the importance of iteration and mental health in engineering careers.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by The Pragmatic Embedded Podcast. The episode itself belongs to its publisher.