Some operating limits are fixed; others only make sense in relation to another measurement. An acceptable engine temperature, for example, may change across the RPM range. BoatKit can evaluate a supported measurement against an adjustable multi-point curve rather than reducing every condition to one threshold.
The resulting normal, warning, or critical state follows the value into gauges and dashboards. An operator sees the measurement, its source, and the evaluated state in the place where the data is already being used. That same categorized value can also feed history, rules, and configurable alarms, keeping the threshold logic consistent across the interface.
Engine RPM monitoring also filters momentary zero readings by default. While an engine is running, BoatKit holds its last RPM through zeros for up to one second, helping keep gauges and trip logs steady. Sustained zero readings still take effect, and the option can be disabled in the RPM sensor settings.
Available measurements and sensible limits come from the equipment and the vessel’s operating guidance. BoatKit supplies the monitoring model; the installer or operator remains responsible for configuring limits appropriate to the machinery and sensors aboard.