Skip to content

Adapt radio-frequency and communication requirements #99

Description

@caudri-loki

Background

The existing radio-frequency wording is considered outdated. Most teams use 2.4 GHz equipment, while the organization primarily needs enough information to detect conflicts before the event. The preferred direction is to simplify or remove prescriptive frequency wording and collect communication details during registration.

Proposed direction

  • remove or simplify obsolete frequency restrictions;
  • collect each team's radio and communication technologies during registration;
  • perform conflict and safety checks before the event;
  • keep RC-mode safety requirements separate from general frequency allocation;
  • ensure the new wording remains compatible with telemetry rules.

Decisions required

  • determine which frequency restrictions are legally or operationally necessary;
  • define the information teams must submit;
  • define the warning or resolution process for conflicts;
  • identify any technologies that remain prohibited or restricted.

Acceptance criteria

  • Obsolete frequency wording has been identified.
  • Required registration fields are defined.
  • Conflict-check and warning procedures are documented.
  • RC-mode and telemetry rules remain internally consistent.

Related but not duplicate: #85 — Restructure of the RC-mode sections reorganized RC-mode wording but did not cover the 2027 frequency-registration concept.

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussionNeeds broader discussion before proceeding

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions