write a reportwith all info for a new engineer to take over the PCB and fix it.
Thought for 9 sec
flux
86 days ago
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.
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.
The reference drone / SHARD baseline includes these RF links:
Table
Link
Band
Power
FrSky/Spektrum safety receiver
2.400–2.4835 GHz
<100 mW EIRP
KRYSTAL/SHARD Wi‑Fi
2.412–2.472 GHz or 5.15–5.825 GHz
<100 mW target / contract dependent
SIYI HM30 receiver
5.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
Requirement
Target
2.4 GHz band
2.412 GHz – 2.472 GHz
5 GHz band
5.15 GHz – 5.825 GHz
Antenna
2 dBi dual-band antenna
Candidate module
AP6256-class dual-band Wi-Fi/Bluetooth module
Host interface
SDIO 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
Item
Architecture treatment
RTSP 720p stream
Compute-side IP video input; suitable for payload video and possible perception after latency validation
5.100–5.825 GHz air unit
Separate RF subsystem from KRYSTAL Wi‑Fi; requires Singapore/IMDA review
5 dBi omni antenna
Separate from the 2 dBi dual-band Wi‑Fi antenna requirement
260 g mass
Add 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
Item
Requirement
GCS radio
RadioMaster TX16S Mark II 4IN1
Protocol family
Internal FrSky / Spektrum protocol support
RF band
2.400–2.4835 GHz
EIRP
<100 mW
Architecture role
Secondary/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.