Sensor data workflows
Turn raw sensor readings into useful engineering data.
DaqSense keeps capture, parsing, formula columns, diagnostics, charts, and export in one local desktop workflow. The source remains available when a result needs to be checked.
What changes with DaqSense
The goal is a dependable test record, not another software project to maintain.
Named columns
Turn delimited or prefixed rows into tables with field names and units that make sense during the run.
Calculated values
Add validated formula columns for scaling, calibration, unit conversion, and derived checks.
Two useful records
Keep the unchanged source stream and a clean structured output for analysis.
Common signs the current workflow is costing time
- Raw ADC counts or sensor codes are hard to judge while the test is running.
- Calibration formulas are applied manually after every run.
- Debug messages and malformed lines break otherwise useful CSV output.
- Different message types are mixed in one serial stream.
- The cleaned spreadsheet no longer makes it clear what the device originally sent.
A simpler workflow
- 1
Inspect representative rows
Identify the delimiter, prefixes, headers, and message families the device actually emits.
- 2
Create clear tables
Map supported rows into named columns and keep non-matching input visible in diagnostics and raw capture.
- 3
Add formula columns
Calculate engineering values on the workstation without changing the device firmware for every adjustment.
- 4
Export for analysis
Write clean CSV files and export recorded sessions to spreadsheet files for the next stage of work.
Example workflow
Calibrated thermistor stream
Input
A board prints timestamp and resistance values as comma-separated rows.
In DaqSense
DaqSense names the columns, applies a temperature formula, displays the calculated value, and records diagnostics.
Output
The session contains original resistance readings and structured temperature data for review in CSV or Excel.
A good fit when
- ✓ The input is line-oriented text with stable, supported patterns.
- ✓ The team needs both raw readings and calculated values.
- ✓ Formulas change more often than the embedded firmware should.
- ✓ CSV or spreadsheet output fits the downstream analysis process.
Use another approach when
- — The data requires an unsupported binary decoder, protocol stack, or custom script.
- — The calculation needs complex stateful processing or domain-specific validation.
- — The device should perform the authoritative calibration inside certified firmware.
Continue exploring
Related product details and practical guides.
Thermistor calculator
Calculate Steinhart-Hart coefficients from three calibration points.
Serial parsing guide
Learn how delimiters, prefixes, and engineering-unit conversions fit together.
Serial data logger
See how parsing fits into the complete recording workflow.
Prepared by the DaqSense R&D team from current product capabilities and customer-discovery work. Product limitations are stated so teams can evaluate the preview on their own hardware.