Skip to content

PixEagle v7.0.1 - Operator and Media Recovery

Choose a tag to compare

View all tags
@alireza787b alireza787b released this 28 Jul 10:57
· 32 commits to main since this release
v7.0.1
a918b37

PixEagle v7.0.1

This patch improves operator recovery and media diagnostics on the v7.0.0
stable local/demo software baseline.

Changes

  • Model uploads now distinguish filename collisions, active-store conflicts,
    validation failures, provenance failures, and admission failures without
    replacing an existing artifact.
  • The sidebar uses the confirmed, audited PixEagle restart action. A manual
    restart no longer requires a pending configuration change; active Following
    or Offboard, missing administrator authorization, unavailable safety state,
    and unavailable durable audit remain intentional blockers.
  • A dashboard updated before its backend now explains the one required
    host-side restart instead of showing a generic unavailable-runtime message.
  • Routine tracker and transport badges are quieter and follow the OSD toggle
    without hiding target, recording, error, or fullscreen controls.
  • WebRTC signaling, offer creation, answer generation, ICE connection, and
    first-frame receipt use independent bounded progress deadlines and clearer
    recovery messages.
  • Active QGC guidance now references the focused generic network-JPEG PR
    sequence rather than the retired broad draft. HTTP/WebSocket authentication
    remains a separate future client-security slice.

Verification

  • Maintained non-hardware backend: 3,618 passed, 47 expected optional
    platform/dlib skips, 1 deselected external marker.
  • Phase 0 guardrails: 492 passed.
  • Dashboard: 59 suites / 392 tests, lint, and production build passed.
  • Generated schema: 39 sections / 518 parameters, current.
  • Generated API candidate, Python compile, shell syntax, documentation guards,
    and whitespace checks passed.
  • Exact commit CI:
    https://github.com/alireza787b/PixEagle/actions/runs/30351689942

Acceptance Boundary

Stable means the maintained local/demo installation, configuration, API,
dashboard, tracking-control, command-preview, and lifecycle software contracts
passed their documented non-hardware gates. It does not mean flight
qualification.

This release does not claim Raspberry Pi or Jetson performance, public WebRTC
reachability/TURN configuration, NCNN acceleration, PX4/Pixhawk response,
SIH/SITL/HIL success, real camera/gimbal operation, field safety, aircraft
operation, or regulatory compliance.

Hardware and simulation testers are invited to report exact versions, configs,
commands, sanitized logs, and reproduction steps through GitHub Issues. Use
PixEagle at your own risk and validate every command path in simulation or a
controlled bench before any field test.

Assets 2
Loading