An open-source hardware data logger that records serial data to microSD cards up to 64GB.
OpenLog is an open-source hardware data logger that captures serial data from devices like microcontrollers and saves it to a microSD card. It solves the problem of reliably recording sensor data, debug outputs, or any serial stream in embedded projects without needing a computer attached. The device supports cards up to 64GB and offers configurable baud rates and power-saving features.
Embedded systems engineers, hobbyists, and researchers who need to log serial data from microcontrollers, sensors, or other hardware in field deployments or prototyping.
Developers choose OpenLog for its simplicity, reliability, and open-source hardware design, which allows for customization and transparency. It provides a dedicated, low-power logging solution that works independently of a computer, unlike software-based serial monitors.
Open Source Hardware Datalogger
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
OpenLog provides a dedicated, plug-and-play device for logging serial data without complex software setup, as emphasized in its philosophy of simplicity and reliability.
Supports microSD cards up to 64GB using FAT32, allowing for extensive data collection in long-term deployments, as noted in the key features.
Offers adjustable baud rates from 4800 to 115200 bps and power-saving modes consuming ~2mA average, making it versatile for various embedded applications.
Includes commands for file and directory operations with wildcard support, enabling easy data management directly from the serial interface, as highlighted in the features.
Maximum baud rate of 115200 bps may be insufficient for high-speed data acquisition, and performance improvements in v4 were needed to handle higher speeds, indicating inherent limitations.
Only supports FAT32 filesystem, which can be a barrier if compatibility with modern formats like exFAT or larger cards beyond 64GB is required.
Requires purchasing physical hardware, adding cost and setup complexity compared to software-based logging solutions that leverage existing microcontrollers or computers.
As per the version history, earlier versions like v2 are described as 'buggy', and v1 has limited storage, leading to potential stability and compatibility issues across deployments.