Nex / SSTV · GW3JEH · Commissioning snapshot

Station

Checking stationMode: loadingTX locked
↗

Execution boundary

Transmitter safety unavailable

The console cannot verify transmitter state. No transmit capability is inferred.
Unavailable
Selected policyNot reportedExecutorNot reportedStation profileNot reportedArm stateNot reportedAuthorizationNot reportedArm expiryNot reportedResource leaseNot reportedFenceNot reportedWatchdogNot reportedPTTNot reportedPower ceilingNot reportedPlayback audioNot reported
Interlocks
  • Station Status Unavailable

Status only — there is no browser arming or PTT control. Auto RX and Auto TX remain shadow/planned until a separately commissioned executor exposes bounded authority.

Operator runbook

Use the status panels to observe; do not infer commissioning from a saved mode

This guide is static help, not live telemetry. Follow the linked page for the current service evidence before making any operational decision. A healthy web page, an image, a saved schedule, or a configured device never grants transmit authority.

  1. Monitor — receive and archive only.

    Confirm fresh receiver and decoder evidence on Monitoring. A received or partial image is reception evidence only; it is not a contact and it does not create a reply.

  2. Auto RX — shadow planning only.

    On Automatic QSO, plans may be reviewed, but the deployed shadow path cannot register a reply worker, key a radio, or send an image. Treat every proposed reply as non-transmitted until a separately commissioned transport reports a durable result.

  3. Auto TX — disabled.

    Schedules and preview plans are not an executor. The current deployment has no automatic RF authority: do not expect a schedule to transmit, and do not use the console as a substitute for supervised station commissioning.

  4. Log only a proved reciprocal contact.

    Only confirmed_qso is logbook eligible. It requires a confirmed local transmission leg and a distinct, later matching acknowledgement. Image-only, failed, timed-out, replayed, or uncertain exchanges remain visible as activity but must not be exported or counted as QSOs.

  5. Production Pi — local preflight before activation.

    The target is semlohnhoj1234.plus.com on the Raspberry Pi, not the WSL development bench. Use the administrator deployment review below, bootstrap a Pi-local MFA administrator, then run the documented Pi-local preflight. The current web view never SSHes to the Pi or changes DNS, router, listener, service, or station state.

  6. Incident recovery — fail closed and inspect first.

    If a receiver, USB/IP attachment, service, or webpage is unavailable, keep Auto RX/Auto TX disabled. Check the read-only station and monitoring status, then follow the recovery guidance in docs/installation.md, docs/native-ft710-usbip.md, and docs/rx888-receive.md. Do not force-bind, detach, reflash, or restart an ambiguous device from this page.

What is not commissioned here: automatic reply transport, automatic transmit, scheduler execution, provider email delivery, logging-provider upload, remote SDR transport, and RX-888 first-open commissioning. These remain separate, explicit operational decisions.

Administrator evidence matrix

Commissioning requires observable facts, not a dashboard setting

Loading read-only commissioning evidence…

Administrator architecture evidence

Equal first-wave host profile

Checking inert SSTV, WSPR, FT4 and FT8 host registration…

Administrator deployment review

Production Pi deployment status

Loading the safe Pi deployment checklist…

Hardware & interfaces

Station

Configure rig control, audio routing and PTT intent without arming the transmitter.
Read-only configurationChecking your station session…