Table-Driven Translation
A lookup table maps source protocol and message type to target protocol, message type and data transform. New weapons added by configuration alone.
12-bit → 32-bit · field-configurable
Flagship programme
WIU
Sovereign Weapon Integration
Mate any domestic munition to any foreign platform.
Frontline fighters lock out home-grown armaments behind inaccessible OEM flight software. The Weapon Interface Unit sits silently on the weapon bus and presents your munition as a recognised OEM store — no source code, no OEM cooperation, no aircraft modification.
◎ MIL-STD-1553B · Bus Monitor 1 Mbit/s
● RT 15
“The supreme art of war is to subdue the enemy without fighting — and to hold one’s own arms in one’s own hand.”
≤10ms
Bus latency
≤1ms
A→B switch
0
Uncommanded
0%
Indigenous
The Problem · OEM Dependency
A single foreign vendor holds the key to your firepower.
Every frontline platform — Rafale, Su-30MKI, Mirage 2000, Jaguar — is configured by its OEM to recognise only OEM-certified stores. Integrating a domestic munition means surrendering sensitive weapon data to a foreign manufacturer. Source code is withheld, fees are prohibitive, and timelines stretch into years: combat readiness gated by another government’s commercial and political decisions.
YEARS
Integration lead time
OEM-led store integration measured in years, per weapon, per platform.
0%
Flight-software visibility
The operational flight program remains entirely inaccessible to the operator.
∞
Leverage exposure
Indefinite dependence on foreign approval for every new capability fielded.
1
Single point of failure
One withheld update can ground an entire weapon programme.
The System · Non-Intrusive Integration
It speaks the aircraft’s language — as the weapon it expects.
Installed inline between the pylon umbilical and the munition, the unit emulates a known OEM store while its protocol translator converts every message to and from your weapon’s native format — in hard real time.
Host platform
Aircraft SMS & bus
Sees only an emulated OEM weapon at the expected address. No modification, no recertification.
MIL-STD-1760
Weapon Interface Unit
Emulate · Translate · Interlock
Hardware-paced bus control presents the OEM identity; a table-driven translator maps protocols, bit-widths and timing.
Domestic munition
Your store
Smart bombs, LGBs, A2A & cruise missiles — via a field-replaceable connector module.
Native protocol
✓ No source code
✓ No OEM cooperation
✓ No airframe modification
✓ Electrically & logically transparent
Capabilities
Built to a certifiable engineering baseline.
Every function is carried through architecture, test and CEMILAC certification evidence as a traceable whole.
Hard Real-Time Determinism
Dedicated silicon handles the time-critical bus function while the RTOS preempts all non-critical work. Bounded latency, guaranteed maximum jitter.
≤ 10 ms end-to-end · watchdog enforced
Dual-Channel Release Interlock
A hardware consent line and a digital command word must both confirm before release. The safe-arm logic lives in hardware — not overridable by software.
zero single-point uncommanded release
Health Monitoring & Test
Continuous monitoring across pylon, weapon and internal watchdog channels. Built-in test reports per-block status; anomalies drop to a safe mode.
≤ 50 ms recovery to weapons-safe
Deterministic Logging
Every bus message, translation, fault and interlock change is timestamped to non-volatile flash with atomic writes. Full mission replay on the ground.
certification-traceable · power-fail safe
Multi-Weapon · Multi-Platform
Many weapon profiles held in flash, selectable pre-flight. Re-target across MIL-STD-1553B, GOST R 52070-2003 or DIGIBUS via platform profiles.
new platform = new profile, not new core
Architecture
Two domains. One certifiable chain.
The 1553B bus is half-duplex and time-division multiplexed — its timing cannot be guaranteed on a general-purpose processor. The FPGA owns the bus; the processor owns everything else. Safety lives in hardware, where software cannot reach it.
▣
FPGA · Hard real-time
- ·Bus RT core
- ·Message scheduler
- ·Bus A/B manager
- ·Safe-arm machine
- ·Interlock monitor
▤
Processor · RTOS
- ·Translation engine
- ·Logging daemon
- ·Tablet interface
- ·Maintenance port
- ·Firmware updates
FIG 1 · Signal chain · DWG WIU-SCH-001 · REV C
SCALE NTS · SCOMET-CONTROLLED
Operational Workflow
Ground to release to log retrieval.
Five defined phases from pre-flight configuration through employment. The critical phase is gated by dual-channel confirmation.
- IPre-flight
Ground Configuration
Unit mated, munition attached, weapon profile selected; built-in test declares mission-ready.
TEST PASS · STANDBY
- IIPower-up
Address Enumeration
Configured address loads, interlock asserts, the unit answers with the emulated OEM identity.
RT 15 ONLINE
- IIIIn-flight
Initialisation & Config
Commands answered per profile; the translator forwards parameters to the munition.
TRANSLATOR ACTIVE
- IVEmployment
Weapon Employment
Safety block verifies both the hardware consent line and the digital command word independently.
DUAL-CH ARMED
- VPost-flight
Log Retrieval
Final state written through hold-up capacitor; the full mission log retrieved for certification.
LOG COMPLETE
Development Roadmap
From lab capture to fleet capability.
A staged path with explicit exit criteria, converging on CEMILAC type approval and long-term obsolescence-managed support.
01Current
Bus Analysis
Capture & decode the OEM weapon profile across its full lifecycle.
02Planned
HW Prototype
First board on a bench bus simulator; power & bus core.
03Planned
Ground Trial
Full weapon lifecycle on a live aircraft, powered, on the ground.
04Planned
Captive Carry
Airborne with an inert store; EMI, brownout, vibration, thermal.
05Planned
Live Fire
Authorised-range release; dual-channel interlock validated.
06Planned
Certification
CEMILAC compliance; independent V&V; type approval.
07Planned
Initial Capability
Field to first squadrons; maintenance training; feedback loop.
08Planned
Full Capability
Fleet-wide deployment; long-term support programme active.
Proven Precedent
Emulation-based integration is battle-proven.
This approach formalises what air forces under pressure have already fielded successfully — including India’s own.
UBAS on F-16
Under sanctions and locked out of the flight software, Türkiye fielded a tablet-based system to integrate indigenous weapons on its F-16 fleet at will.
Bypass · OEM lockout
HARM on Su-27
Soviet-era airframes, fundamentally incompatible with the US AGM-88, made to employ HARM via an emulated stores-management layer.
Cross-OEM · A2G
Astra Mk1 as R-77-1
The indigenous Astra Mk1 presents itself to the Su-30MKI weapon computer as an R-77-1, reusing the existing digital logic — the core principle, already flying.
Domestic · A2A
R-73 on Mirage 2000
A Russian R-73 mated to a French Dassault platform with neither OEM consulted — independence from OEM leverage, demonstrated.
Cross-OEM · A2A
MIL-STD-1553BMIL-STD-1760MIL-STD-704
MIL-STD-810MIL-STD-461DO-178C
DO-254CEMILACSCOMET
Atmanirbhar Bharat · Buy Indian — IDDM
Put your weapons on your terms.
Request a technical briefing on the Weapon Interface Unit programme.
“The supreme art is to make the weapon serve the hand that holds it, not the hand that sold it.”