Drone Autonomy Spec


flux

Escalated internally to the Flux engineering team with:
  • Compute Vision Board link
  • HTTP 524 preflight failures
  • Partial auto-route corruption
  • Airwire increase from 247 to 442
  • Ground-fill/stitching-via corruption when applying routing rules
  • Clean recovery commit c52f37c6
  • Current safe board state
For a human support case and status follow-up, use Contact Support and reference the KRYSTAL Compute Vision Board routing/rules corruption issue.
write a reportwith all info for a new engineer to take over the PCB and fix it.

flux

I’ll create a structured takeover report covering both boards, architecture, completed work, current live state, known blockers, recovery history, verification gates, and the exact order a new engineer should follow.

flux

Created the comprehensive PCB Engineering Takeover Report.
It covers:
  • Both project links and board responsibilities
  • Current CM5 and S32K344 architecture
  • Power, camera, radar, autopilot, Wi‑Fi, FHSS and SIYI interfaces
  • Board dimensions, stackups and enclosure direction
  • Completed fixes and verified checks
  • Routing-service failure and recovery history
  • Known footprints, software and regulatory risks
  • Recommended takeover sequence
  • Fabrication-release gates
  • Immediate first-day checklist and required engineer deliverables
The report clearly marks both boards HOLD for fabrication until routing, interface freeze, DRC, thermal, software and mechanical validation are complete.
Review takeover report
Audit live board states
Prepare migration package
Freeze external interfaces

Communications Architecture Allocation — KRYSTAL Module
Reference Drone RF Environment
The reference drone / SHARD baseline includes these RF links:

Table


LinkBandPower
FrSky/Spektrum safety receiver2.400–2.4835 GHz<100 mW EIRP
KRYSTAL/SHARD Wi‑Fi2.412–2.472 GHz or 5.15–5.825 GHz<100 mW target / contract dependent
SIYI HM30 receiver5.100–5.825 GHz<320 mW target
Design implication: 2.4 GHz coexistence must be treated carefully because safety RC and Wi‑Fi/Bluetooth can occupy overlapping spectrum. Prefer 5 GHz Wi‑Fi for high-throughput KRYSTAL data when the safety RC link is active, subject to Singapore/IMDA channel rules.
Singapore Contract Wi-Fi Requirement
KRYSTAL must support IEEE 802.11ac/a/b/g/n dual-band Wi-Fi for the Singapore contract:

Table


RequirementTarget
2.4 GHz band2.412 GHz – 2.472 GHz
5 GHz band5.15 GHz – 5.825 GHz
Antenna2 dBi dual-band antenna
Candidate moduleAP6256-class dual-band Wi-Fi/Bluetooth module
Host interfaceSDIO for Wi-Fi; UART for Bluetooth if used
Do not finalize schematic wiring until the Linux compute/SOM is selected, because the Wi-Fi module must connect to the compute side through SDIO, low-power clock, reset/enable, and RF/antenna layout constraints.
SIYI A8 Mini Payload Camera / Air Unit
The SIYI A8 Mini is acceptable as an external IP video payload candidate if used through Ethernet/RTSP into the Linux compute side.

Table


ItemArchitecture treatment
RTSP 720p streamCompute-side IP video input; suitable for payload video and possible perception after latency validation
5.100–5.825 GHz air unitSeparate RF subsystem from KRYSTAL Wi‑Fi; requires Singapore/IMDA review
5 dBi omni antennaSeparate from the 2 dBi dual-band Wi‑Fi antenna requirement
260 g massAdd to mechanical/payload mass budget
Do not rely on the SIYI RTSP stream for safety-critical terminal guidance until latency, frame timing, packet loss behavior, and recovery from link dropout are tested.
Safety Radio / Secondary GCS Comms Requirement
Customer-provided secondary comms / GCS radio:

Table


ItemRequirement
GCS radioRadioMaster TX16S Mark II 4IN1
Protocol familyInternal FrSky / Spektrum protocol support
RF band2.400–2.4835 GHz
EIRP<100 mW
Architecture roleSecondary/safety human-control comms path
Architecture treatment:
  • Treat this as an external RC/GCS control link, normally terminating in a compatible receiver or the flight controller, not directly in the KRYSTAL safety MCU unless a specific receiver interface is selected.
  • KRYSTAL should be able to observe safety-radio state indirectly through the autopilot link, or directly through a receiver interface if required later.
  • If direct KRYSTAL receiver input is required, add a dedicated receiver connector supporting the selected receiver output protocol, e.g. SBUS, CRSF, Spektrum serial, PWM, or UART.
  • This 2.4 GHz link must coexist with KRYSTAL dual-band Wi‑Fi and any Bluetooth function; avoid unnecessary 2.4 GHz Wi‑Fi use during safety-critical operations if coexistence testing shows interference.
Customer-provided tertiary data/video link:

Table


ItemRequirement / Candidate
GCS / linkSIYI HM30 / MK32
RoleTertiary comms, IP data link, video backhaul
RF band5.500–5.600 GHz customer requirement; SIYI HM30-class material commonly lists wider 5.1–5.825 GHz capability
EIRP / power<320 mW EIRP customer requirement; verify whether vendor value is conducted TX power or true EIRP
Video/data modeEthernet/IP video/data link, RTSP compatible
Architecture fit:
  • Acceptable as KRYSTAL's tertiary data/video link if integrated through Ethernet/IP on the Linux compute side.
  • Compatible with SIYI/A8-style RTSP streams and third-party Ethernet camera workflows.
  • Do not route video through the S32K344 safety MCU; S32K344 should receive only link health/status and bounded safety outputs.
  • Use a dedicated network segment or managed IP plan to avoid address conflicts with KRYSTAL Ethernet, radar, camera, and service networks.
Implementation requirements:
  • Confirm exact HM30 or MK32 variant and air-unit model.
  • Confirm IP subnet, reserved device addresses, RTSP URL format, telemetry path, and whether MAVLink is bridged over the link.
  • Define failover priority: safety radio / autopilot link should remain authoritative if the tertiary video/data link drops.
  • Verify latency, packet loss behavior, reconnect time, and video degradation under range/EMI conditions.
Purpose
This document records the current schematic allocation for KRYSTAL multi-bandwidth communications.
Bandwidth Tiers

Table


TierFunctionSchematic ImplementationIntended Data
Low bandwidth / long rangeLoRaWAN telemetryU6 453-00139R on S32K344 UART with RTS/CTSHealth, status, fault/event packets, low-rate command acknowledgements
Medium bandwidth / deterministic field I/OCAN FD / RS-485 / SPI / I2C expansionJ3 DF40C mezzanine placeholder nets to provisional S32K344 pinsVehicle/payload control, sensors, external controllers
High bandwidthEthernet radar/service/compute linkJ4 Gigabit MagJack routed to J3 Ethernet pair netsmmWave radar, service Ethernet, compute-network data
Current Schematic Allocation
LoRaWAN
  • U6 power: 3V3_AON to VDD_RADIO, VMCU, VDD_IO, VDD_SX1262.
  • U6 local caps: C16 100 nF and C17 10 uF.
  • UART/control nets: LORA_UART_TX_TO_MCU_RX, LORA_UART_RX_FROM_MCU_TX, LORA_UART_RTS, LORA_UART_CTS, LORA_BOOT_N.
Ethernet
  • J4 MagJack data nets: ETH_TRD1_P/N through ETH_TRD4_P/N.
  • Each Ethernet pair is marked as a 100-ohm controlled-impedance differential pair.
  • Ethernet center taps are passed to J3 as ETH_CT1 through ETH_CT4 for final PHY-side treatment.
  • J4 shield pins are on CHASSIS_SHIELD and must be finalized in the chassis/ESD strategy.
Mezzanine Expansion
  • J3 exposes 3V3_AON, GND, LoRa UART, Ethernet, and provisional expansion nets.
  • Expansion nets are marked TBD until S32K344 IOMUX and the compute-board interface are finalized.
Layout Implications
  • Ethernet requires a minimum 4-layer board with a solid reference plane and controlled-impedance routing.
  • LoRaWAN antenna/RF area requires a keepout and module integration review.
  • J3 is a compact 0.4 mm connector and should not be used for high current unless current-per-pin and thermal limits are verified.
Open Items
  • Verify S32K344 pin mux for all LoRa and expansion assignments.
  • Decide whether Ethernet PHY/switch lives on KRYSTAL or the compute carrier.
  • Select antenna and confirm regulatory integration conditions.
  • Add actual CAN FD and RS-485 transceivers before external wired interfaces are considered complete.
  • Reference Drone RF Environment

  • Singapore Contract Wi-Fi Requirement

  • SIYI A8 Mini Payload Camera / Air Unit

  • Safety Radio / Secondary GCS Comms Requirement

  • Data & Video Link / Tertiary Comms Requirement

  • Purpose

  • Bandwidth Tiers

  • Current Schematic Allocation

  • LoRaWAN

  • Ethernet

  • Mezzanine Expansion

  • Layout Implications

  • Open Items