Independent maintenance tool — not affiliated with VideoRay or Greensea IQ
Defender Doctor
Launch Tool

Defender Doctor

Offline diagnostic analyzer for Mission Specialist Defender ROV telemetry

0bytes of your data uploaded
44fault-signature rules
7thrusters monitored per vehicle
How It Works Data Safety ►  Launch Tool

How It Works

Take the dive recording the topside Greensea Workspace already wrote, drop that one file into the tool, and read a ranked fault report: what tripped, when, the likely cause, and the fix — plus an engineer bundle ready for a support ticket.

1

Grab the recording

The operational workspace records every dive automatically to gss_logs — nothing to set up. Take the newest .gssbin for the dive that went wrong. That single file is the whole input.

Not the Playback workspace: it replays an old log and is not connected to the vehicle, so it records nothing.

2

Drop the file

Move it to this computer using your approved transfer process, open the tool, and drop it in — the recording, a folder, or individual files. Analysis runs instantly, on this device.

3

Read the report

Findings are ranked worst-first with evidence charts, a plain-language verdict, and a concrete fix per fault. Download the report and the engineer bundle to pass along.

A Coverage section names any signal the recording did not carry and the exact channels to export if you need them. Collect one file; the report tells you when it needs more.

Then it asks for what no log can hold — the insulation reading, the power source, the tether run, the hull number — picking the questions from the faults it actually found.

If the report asks for more: the CSV export
1 · Open the Logging tab (under the map view)
2 · In the Convert-to-CSV panel, click Choose Log File
3 · Select the .gssbin recording of the dive
4 · Shift-select ALL channels in the list
5 · Click Convert to CSV
6 · One .csv per channel lands in gss_logs — drop those into the tool

37 of the 44 rules run here. The remaining seven diagnose the topside console itself — drive space against the space it needs to boot, whether the operating system sees the tether interface, whether the comms module answers — and read a diagnostic sweep of the console rather than a telemetry file, so they run from the command-line field kit instead. That kit is also what to reach for when the vehicle will not boot at all and there is no recording to analyze.

Schematic recreation for instruction — not vendor software imagery. Official procedure: VideoRay Greensea Import/Export Guide.

Data Safety

The analysis engine runs entirely inside your browser tab. Your telemetry never leaves this device.

No upload pathThe server hosts only this page. There is no endpoint that receives files — nothing to breach, nothing retained, no server-side record of your data.
Enforced by policyThe tool page ships a Content-Security-Policy with connect-src 'none': the browser itself blocks every network request after the page loads. Verify it in DevTools → Network while you run an analysis.
Encrypted deliveryThe page arrives over TLS (HTTPS, HSTS) and sits behind access credentials. Reports are generated locally as downloads on your machine.

Run the Diagnostics

You will be asked for the access credentials provided with this link.

Open Diagnostic Tool

Government systems: move files off a Navy console only via command-approved removable media and process. This page does not change which devices may hold your data.