Sorceress · main engine

Live Watch Log

LATEST HOURS

—

READINGS

—

ADDED HERE

—

How to use this log

New reading

Most recent reading in the selected period, against the observed range.

Averagespick a range of engine hours and get the mean of every parameter

From (hours)

To (hours)

Quick range

Charts: pinch or scroll to zoom in on a period · drag to pan · double-tap to reset.

Temperaturescoolant · gearbox · aquadrive (°C)

Oil pressurebar — top-up flagged at 3.8 in the log (5 Dec)

Battery volts

RPM & load

RPM · load · aquadriveshaft speed and load against aquadrive temp

Fuel burnlitres per hour

Boost & fuel pressurebar

Defects & watch notes

Seed data transcribed from the handwritten logbook (Aug 30 – Dec 23, 2025) — best-effort readings. Works offline once loaded; queued readings sync automatically when you're back online.

Auto-flag bandsreadings outside these get an amber gauge and raise an alert note automatically

These are your "normal operating" limits — tighter than the typo checks, looser than a good day. Synced to every device.

Cloud sync off — data stays on this device

One-time setup (~5 min, free) so all devices share the same live database:
1. Go to supabase.com → create a free account → New project (any name, e.g. "engine-log").
2. In the project, open SQL Editor, paste this and press Run:

create table log_items (
  added bigint primary key,
  kind text not null,
  data jsonb not null
);
alter table log_items enable row level security;
create policy "read" on log_items for select using (true);
create policy "insert" on log_items for insert with check (true);

Already set up before this update? Run this once in the SQL Editor to lock the database against wipes:

drop policy if exists "delete" on log_items;

One-time: move the transcribed paper-logbook history (115 readings + 10 notes) into the database so it's backed up, correctable and included in cloud backups:

3. Go to Project Settings → API. Copy the Project URL and the anon public key, paste them here:

Project URL

Anon public key

On first connect, data already saved on this device is uploaded to the shared database. Delete protection: nothing is ever truly erased from the cloud — "deleting" just hides an entry, and the underlying row stays in Supabase where you can recover it. Anyone with the site address can view and add to the shared log — fine for crew, don't post the link publicly. The engineer PIN is a convenience lock, not bank-grade security.