Unit conversion is one of the most common operations in automation workflows. Whether you're processing sensor data, normalizing IoT readings, transforming API payloads, or preparing values for downstream systems, you need conversions that are fast, predictable, and mathematically correct.
Nodlyn's new Unit connector brings a complete suite of high‑precision transformations directly into your workflows — without external services, without cloud dependencies, and without custom code. Everything runs locally, inside the same execution engine that powers the rest of Nodlyn.
Why Local Unit Conversion Matters
Most automation platforms rely on cloud APIs or third‑party libraries for unit conversion. This introduces latency, privacy concerns, and dependency chains that break offline workflows.
Nodlyn takes a different approach: all conversions happen inside the runtime. No network calls, no external math engines, no hidden dependencies. This ensures:
- Zero latency — conversions run in microseconds
- Full offline support — ideal for IoT, factories, and edge devices
- Deterministic results — identical outputs across all environments
- High precision — configurable decimal rounding
The Unit Connector: Six Capabilities, One Purpose
The connector exposes six transformation nodes, each designed for a specific domain:
- convertTemperature — Celsius, Fahrenheit, Kelvin
- convertPressure — bar, psi, kPa
- convertWeight — kg, g, lb
- convertLength — m, cm, mm, inch, feet
- convertVolume — L, mL, gallon, m³
- convertGeneric — custom math formula using
x
Each capability is schema‑driven, meaning the inspector UI is generated automatically. No custom React components are required.
Unified Settings: Consistent and Predictable
All conversion nodes share a common structure:
- Value — the numeric input
- From — source unit
- To — target unit
- Precision — decimal rounding (default: 6)
This makes it easy to swap one conversion for another without changing workflow logic. The convertGeneric node adds a powerful twist: you can define any formula using x as the input variable.
x * 3.28084 x / 1000 (x - 32) * 5/9 (x * 9/5) + 32These formulas are parsed and evaluated locally using a safe, deterministic math engine.
Dry-Run Support: Safe Testing for All Transformations
Every Unit executor implements Nodlyn's dry-run mode:
- No formulas are executed
- No conversions are applied
- The node returns the input value unchanged
This allows you to validate workflow structure without affecting downstream logic.
Precision and Determinism
All conversions use IEEE‑754 double precision internally, followed by configurable rounding. This ensures:
- Stable results across platforms
- No floating‑point drift
- Consistent outputs in cloud and on-prem
For example, converting meters to feet uses the exact factor 0.3048, and temperature conversions follow the official Kelvin and Fahrenheit formulas.
Performance Characteristics
Because all operations run inside Nodlyn's runtime, conversions are extremely fast:
- Temperature — microseconds
- Pressure — microseconds
- Length — microseconds
- Generic formulas — microseconds
There is no cloud round-trip, no API throttling, and no external dependencies. Your automation runs at the speed of your hardware.
Cloud-Compatible, Local-First
All Unit capabilities are marked CloudCompatible. Workflows behave identically whether running on your machine or inside Nodlyn Cloud.
But the philosophy remains unchanged: your data stays local unless you choose otherwise.
The Bottom Line
The Unit connector brings high‑precision, domain‑specific, and fully offline transformations to Nodlyn workflows. Whether you're normalizing sensor data, converting API payloads, or applying custom formulas, the Unit connector delivers fast, reliable, and predictable results.
Combined with Nodlyn's local-first execution model, you get an automation stack that is accurate, private, and built for real-world engineering.