Support Portal / Varta Max

Tier Support

Varta Max Support

Varta Max is the command center tier for UI/API operations, multi-sensor fusion, and tactical mapping.

Setup Requirements

  • Software: Python 3.10+ with .[max].
  • Runtime config: varta_max.yaml (auto-discovered) or explicit --config.
  • Networked deployment: MQTT broker, optional Timescale/PostgreSQL stack, optional Docker services.
  • Browser access for UI operations, or --no-browser for headless startup.
pip install -e ".[max]"
python -m varta_max --config config/lab/max_settings.yaml
python -m varta_max
python -m varta_max --host 0.0.0.0 --port 8081
python -m varta_max --no-browser

Caveats

  • Production safety checks are enforced: default fleet secret is rejected and pairing must remain enabled.
  • Standalone defaults can disable DB retention; validate event retention assumptions against config.
  • MQTT TLS defaults to enabled in standalone settings (mqtt_port: 8883).
  • Lab configs often use insecure/plaintext settings and should not be used as production baselines.

Usage Requirements

  • Set environment: production only after fleet secret, pairing, and network security controls are configured.
  • Verify sensor registration/pairing behavior before live operations.
  • Monitor /health, /health/live, /health/ready, and /metrics during operations.
  • Keep API/UI release aligned with deployed sensor fleet release version.

Deploying Pro Sensors With Max

Placement Rules

  • Mount antennas high with clear line-of-sight and minimal near obstructions.
  • Avoid large nearby reflectors and strongly vibration-prone mounts.
  • Use non-collinear sensor geometry for stronger multi-sensor fusion.
  • For DF-capable deployments, verify array orientation and calibration after final mounting.

TDOA + DF Requirements

  • TDOA requires 3+ contributing sensors with overlapping visibility and in-spec sync.
  • Fallback chain when not eligible: DF intersection, DF+RSSI hybrid, hybrid, then RSSI fallback.
  • DF eligibility requires 2+ bearing-capable sensors and coherent DF clocking.
  • Re-run DF calibration after cable changes, repositioning, or periodic maintenance cycles.

Post-Install Acceptance

  1. Sensor remains online and stable through at least one full monitoring cycle.
  2. No persistent pairing failures, reconnect loops, or recurring fault churn.
  3. Controlled known-signal check appears in Max detections.
  4. For multi-sensor deployments, reported fusion method and position behavior are plausible for current sync/DF state.
  5. Health endpoints and logs are acceptable for baseline operations.