Getting the MAX30100 Pulse Oximeter Working in Proteus: A Guide to Downloading and Fixing Library Issues

The MAX30100 is an integrated pulse oximetry and heart-rate monitor sensor module. It is a favorite among biomedical engineering students and hobbyists for designing health monitoring systems. However, when moving from the physical world to simulation in Proteus ISIS, users frequently encounter "Library Not Found" errors or simulation failures.

This article explores why the MAX30100 library often fails in Proteus and provides a step-by-step guide to downloading the correct files and applying the necessary fixes to get your simulation running.

Creating a functional substitute (when no Proteus model exists)

If you can’t get a reliable MAX30100 model, simulate the sensor behavior using:

• A photodiode + LED pair model: use LED sources and photodiode SPICE models to approximate the sensor optical chain.
• A current/voltage source feeding an ADC input model that mimics the sensor’s I2C/analog output timing.
• A microcontroller model running the same I2C driver code; feed it a scripted I2C slave behavioral model that returns expected registers and data patterns from the MAX30100.

Practical steps:

1. Build a small Proteus subcircuit that models the MAX30100 register set: implement I2C slave address and respond with prerecorded measurement bytes.
2. For realistic pulsatile data, generate a CSV file with sample SpO2/Pulse waveform values and have the slave return those values cyclically.
3. Use that slave to test microcontroller firmware and UI without hardware.

Step 4: Code Compatibility

Ensure the code running on your Arduino (in Proteus) matches the library model.

1. In your Arduino IDE, install the SparkFun MAX3010x Pulse and Proximity Sensor Library.
2. Upload the Example1_Basic_Readings.ino sketch.
3. In Proteus, double-click the Arduino and point the "Program File (HEX)" to the compiled sketch output (usually in AppData\Local\Temp).

Step 4: Wiring the Simulation Correctly

If the library is installed and the HEX file is linked, but the simulation hangs or shows an error (like "Real-time simulation failed"), the issue is likely the wiring setup. The MAX30100 communicates via I

Step 3: The Circuit "Fix" (Simulation Hanging)

This is the most common oversight. The MAX30100 communicates via I2C. In the real world, the sensor module usually has built-in pull-up resistors. In Proteus, the simulation model often requires you to add them manually, or the logic lines float, causing the microcontroller to wait forever.

How to fix the freeze:

1. Open the Terminals mode in Proteus.
2. Place two Pull-Up Resistors (typically 4.7kΩ or 10kΩ).
3. Connect one resistor between VCC and SCL.
4. Connect the second resistor between VCC and SDA.
5. If using an Arduino:
   • Connect SCL to Pin A5.
   • Connect SDA to Pin A4.
   • Connect INT (Interrupt) to Pin D2 (optional, but needed for some code examples).

Step-by-step: Importing a third-party MAX30100 library into Proteus

1. Obtain a compatible Proteus library (.LBR) or a GitHub repo containing Proteus files. Prefer repos with examples.
2. Backup your Proteus libraries folder (typically C:\ProgramData\Labcenter Electronics\Proteus XXXX\LIBRARY).
3. Close Proteus.
4. Copy the .LBR file into the Proteus LIBRARY folder.
5. Start Proteus, open Library → Use Library, search the MAX30100 symbol.
6. If the part appears but the footprint is missing, open Library Manager → Edit part → map to correct PCB footprint manually.
7. If the behavioral model is missing, attach a testbench input (see “Simulating sensor output” below).

Step 2: Manual Injection (The Reliable Way)

If you can't find a verified library, create a working model in under 5 minutes:

• Grab the official datasheet – Note the I2C address (0x57) and register map.
• Use Proteus’s "I2C Debugger" + "Voltage Generators" – Simulate the MAX30100 as a slave device that returns pre-recorded photodiode waveforms. (Yes, this is how pros test firmware without real hardware.)
• Convert an existing "MLX90614" library – Surprisingly, the temperature sensor shares 90% of the I2C structure. Rename pins, swap registers, and you have a functional MAX30100.

Fix #3: Delay in Firmware

The HEX model needs time to initialize. In your Arduino simulation code (or any MCU code), add a delay(2000); in setup() before you initialize the MAX30100. This gives the virtual sensor time to start its internal oscillator.