System architecture
Inside SIGNAL³
A passive RF platform designed for field deployment, built around independent sensing paths, local processing, operator visibility and continuous system monitoring.
System level
Current engineering architecture
Sensing architecture
Three independent RF receivers and processing paths operate concurrently.
Local compute
All primary sensing and detection processing occurs on the field unit.
Connectivity
Local Wi-Fi access supports operator use and field provisioning.
Positioning
Integrated GNSS architecture with automatic self-location under validation and manual fallback.
Data
Detection events and configuration are stored locally.
Operation
Core detection works without cloud connectivity or an external API.
Monitoring
System and sensor health are continuously reported through the operator interface.
Deployment envelope under validation
Outdoor enclosure, production power architecture, environmental limits, dimensions, weight, range and certifications remain under engineering validation. Validated values will be published when available.
What three means
Three sensing paths. One platform.
Each sensing path operates independently, allowing SIGNAL³ to observe different classes of drone-related RF activity simultaneously.
Detect. Correlate. Confirm.
The SIGNAL³ architecture is being developed toward correlation of independent observations into confidence-scored aircraft tracks, allowing multiple sensing paths to reinforce a single detection rather than simply producing separate alerts.
Operator interface
Built as a field appliance, not just an RF receiver.
SIGNAL³ combines sensing, system health, diagnostics and local configuration through a purpose-built operator interface running directly on the unit.
Sensor status
Live state of each RF sensing subsystem.
RF activity
Real-time 5.8 GHz spectrum and detection information.
System health
CPU, memory, storage, uptime and thermal monitoring.
Device health
Sensor faults and recovery status surfaced directly to the operator.
Local positioning
GNSS-based unit positioning architecture with manual fallback.
Wi-Fi management
Local network scan, connection and field provisioning.
Event history
Local detection and event records without a required cloud service.
Self-monitoring
A detector that monitors itself.
A drone detector is only useful if the operator knows when part of it stops working. SIGNAL³ continuously monitors its sensing hardware and system state, attempts recovery from selected failures, and surfaces actionable fault information through the operator interface.
Self-monitoring with automated first-line recovery.
Local by design
The detection system does not need the cloud.
Core SIGNAL³ sensing and detection processing runs locally on the unit. No cloud service, external API or licensing server is required for the three sensing paths to operate. Detection records remain local to the system.
- Local RF processing
- Local operator interface
- Local detection records
- No required cloud telemetry
- No required internet connection for core sensing
Online map tiles require internet access unless map data has been cached locally.
Designed for secure deployment.
SIGNAL³ is being engineered toward authenticated local access, encrypted communications, signed software updates and hardened field deployment.
Production hardening roadmap
- + Authenticated operator access
- + Role-based controls
- + Encrypted local communications
- + Signed update packages
- + Rollback protection
- + Protected configuration
- + Auditable software versions
Multi-node architecture
The SIGNAL³ architecture is being developed toward multi-node deployments in which geographically distributed sensors contribute to a common operating picture.
Wider-area RF geolocation remains a longer-term research and development direction.
See SIGNAL³ in operation.
Request a technical demonstration of the sensing platform, operator interface and current detection capabilities.
Request a demoDiscuss field evaluation