Undergraduate Research

Ballistocardiogram (BCG) Data-Acquisition PCB

A mixed-signal hardware platform developed to acquire the small sensor signals used in ballistocardiography research, with an emphasis on PCB design, reliable hardware bring-up, measurement, troubleshooting, and scalable deployment.

Mixed-Signal PCB DesignData AcquisitionKiCadDigilent Analog Discovery 3Hardware Validation
Three-dimensional render of the ballistocardiogram mixed-signal data-acquisition PCB

Project Area

Biomedical Instrumentation

Hardware

Mixed-Signal PCB

My Role

Undergraduate Research Assistant

Focus

Design, Bring-Up, and Validation

What Is BCG?

Measuring the body’s mechanical response to each heartbeat

A ballistocardiogram, abbreviated BCG, records the subtle motion of the body associated with cardiac contraction and the ejection and movement of blood. Unlike an electrocardiogram, which measures the heart’s electrical activity, ballistocardiography focuses on a mechanical response.

These motions are small, so the acquisition electronics must handle low-level sensor signals while preserving useful physiological information. That requirement makes board layout, grounding, power, component selection, signal integrity, and repeatable validation central engineering concerns.

This project focused on the data-acquisition hardware used in a university research platform. The PCB work supports signal capture and experimentation; it is not presented here as a medical device or diagnostic product.

My Contribution

From board design through laboratory validation

As an undergraduate research assistant at Texas State University, I helped relaunch and improve a faculty-developed ballistocardiogram data-acquisition platform. My work covered the complete board-level engineering loop rather than ending when the PCB layout was complete.

  • Designed and simulated custom mixed-signal printed circuit boards.
  • Supported PCB assembly and first-power-on hardware bring-up.
  • Measured and evaluated signals with oscilloscopes and logic analyzers.
  • Troubleshot board-level functional and signal-integrity issues.
  • Created the project bill of materials (BOM) to organize component selection, quantities, sourcing, and cost information.
  • Improved component sourcing, manufacturability, cost, and deployment scalability.
  • Transferred design information, test data, and lessons learned to the next group of research students to support the project’s long-term continuity.

Development Workflow

An iterative design, test, and improvement cycle

01

Understand the System

Review the research platform’s sensing, acquisition, interface, power, and mechanical needs before beginning the board design.

02

Design the PCB

Develop the schematic and physical layout while separating sensitive mixed-signal paths and accommodating the required connectors and devices.

03

Bring Up Hardware

Assemble and inspect the board, verify power and reference points, and test interfaces in a controlled sequence.

04

Measure and Refine

Use laboratory instruments to evaluate behavior, isolate faults, validate revisions, and feed findings back into the next design iteration.

Hardware Development

Board revisions shaped by integration and test results

The available board designs show the evolution of the acquisition electronics, component placement, connectors, test points, and mechanical outline. Three-dimensional PCB renders were used to review layout and integration before fabrication and assembly. KiCad was used for schematic capture, PCB layout, and three-dimensional board review throughout the design process.

Bring-Up and Validation

Turning a fabricated board into a verified system

Hardware bring-up used staged checks so that power, references, interfaces, and signal paths could be evaluated before complete system operation. A Digilent Analog Discovery 3 provided oscilloscope and logic-analyzer measurements, giving direct evidence of circuit behavior and helping isolate board-level faults.

The results informed subsequent revisions and practical improvements to component availability, cost, manufacturability, and deployment. This work connected schematic and layout decisions with measured performance on physical hardware.

I also created the project bill of materials to organize component and sourcing information. To help the research continue beyond my involvement, I shared the accumulated design information, test data, and troubleshooting knowledge with the next group of research students.

Continue Exploring

Return to the engineering project portfolio