datalogger

Kingmach dataloggers sit between field sensors and the people who need the data, and the design choices reflect that middle-ground reality. The input side accommodates a range of signal types seen in geotechnical work—vibrating wire, 4–20 mA, RS-485, thermistor, and potenciometric circuits are common, and custom front-end modules can be added for less standard sensors. This flexibility means one logger can often consolidate several standalone readout units, cutting down on the number of boxes bolted to a wall. The analog front ends use 24-bit ADCs with programmable gain, which helps pull clean signals from long cable runs and low-output instruments. Sampling rates and trigger conditions are user-configurable, so you are not forced into a fixed scan interval that doesn’t match the physics of what you are monitoring. Internally, data goes onto industrial-grade flash storage—no spinning disks or battery-backed RAM that fail silently. Depending on the model, storage ranges from a few million to tens of millions of timestamped records, enough for years of autonomous logging at typical hourly intervals. Power consumption is kept low: sleep currents in the microamp range let a modest battery and solar panel combination run indefinitely in all but the darkest locations. When it is time to get data out, options include cellular modem, Ethernet, RS-232, or USB mass-storage mode for a site visit download. Many users push data to an FTP server or a cloud platform; we also offer a desktop utility that handles configuration, live view, and data export without steep licensing fees. Because no two projects are identical, we build loggers to order with the exact channel count, sensor interface, and telemetry method requested. This avoids the common problem of paying for unused channels or missing the one input type you actually need. Our in-house team handles enclosure fabrication, wiring, and testing under one roof, which keeps lead times reasonable and allows us to support legacy sensor types that off-the-shelf loggers ignore. Beyond the hardware, we maintain a support channel that helps customers during commissioning, troubleshooting noise issues, or adjusting sampling logic after initial installation. The goal is to deliver a logging system that doesn’t become a project bottleneck, and we have been doing it long enough to understand that a logger is only as good as the data series it produces. That means paying attention to things like surge protection on each channel, cold-junction compensation for thermocouples, and onboard calculation of derived values such as frequency-based temperature corrections—details that make a difference when you are looking at a year of borehole data trying to spot a trend.