SD Cards, Server History and Same-Condition Comparison

Logging, Replay and Polar Performance

The suite does not just steer the boat. It also records what happened, what the conditions were, and whether a change actually made the boat calmer, faster or worse in comparable conditions.

Suite Overview Safety + Prevention

Onboard SD Logging

Critical runtime data is kept locally on board so the evidence stays with the boat even when there is no internet.
Event traces, alarm states, control transitions and performance-related samples can be written to SD for later replay and tuning.
That makes it possible to review a rough maneuver or a steering change immediately instead of waiting for shore sync.
The practical question after any change is simple: was this actually better or worse than before?

Server-Side Passage History

The SailingKSF server keeps the wider voyage story: position, heading, weather, sea-state context, route state and long-range history.
Boat-side logs and server-side logs complement each other instead of competing.
The boat keeps the fast local truth source, while the server keeps the longer tactical and historical view.
That gives a stronger basis for debrief, support and careful tuning over many passages.

Same-Condition Better Or Worse

Performance review only makes sense when you compare like with like.
The system can group runs by wind strength, wind angle and measured boat response, so a fresh run can be compared against older runs from roughly the same conditions.
That is how small gains or regressions show up after controller changes, sail-trim changes or hardware changes.
It is less about chasing one perfect top-speed number and more about honest before/after evidence under similar load.

Polar Graph On iPad And Server

The iPad is a practical place to review the latest performance graph straight after a watch, trial run or trim change.
The server keeps the larger history and a cleaner owner-performance polar for later review.
That polar is based on stored sailing data, not brochure targets.
The result is a more honest picture of how the boat is actually performing offshore in real use.

How The Logging Layers Fit Together

Blackbox logging answers what happened around a specific event.
Track and passage logging answer where, when and in what weather it happened.
Polar/performance logging shows whether the boat is improving or regressing in comparable conditions.
Together, they turn tuning changes and offshore incidents into evidence instead of guesswork.

**Recent Event Timeline**
Blackbox-style event logging used to inspect what happened around a maneuver or anomaly.

Related across the suite

Current page focus: SD-card logging, passage history and owner-performance polar review.

Blackbox evidence for specific events.

Track and passage history for where and when things happened.

Owner-performance polar review on iPad and server.

Same-condition better/worse comparison after changes.

Weather, position and boat-status history.

Exportable local data for debrief and support.

Feedback And Comments

This project is still in progress, and I would genuinely like feedback on what is missing, what feels unclear, and what would be most useful offshore. The first sea trial is planned for the 2026 sailing season, and every comment is reviewed by me before it appears publicly.

No public comments yet. You can be the first to add feedback.

Built For Singlehanded Offshore Reality

These public pages focus on what the suite actually delivers offshore: steadier steering, fail-safe automation, and practical offshore support that reduces workload without taking control away from the skipper.