Aviya’s vCLB models aircraft interfaces and components in software before controller hardware exists. Compatible scripts migrate to CLB controller-hardware testing, with real-time plant models, parameter overrides and configuration-controlled test execution. Supplier-described open-loop factory and repair/overhaul testing provides another use. Modelled interfaces do not specify physical interface cards, and advertised simulation steps do not establish end-to-end latency.
Technical detail
Core features
Software models of ARINC429, CANBus, AFDX, sensors, valves and LRUs
Compatible vCLB/CLB GUI and configuration-controlled scripts
PC real-time simulation using MATLAB/Simulink and proprietary models converted to C
Runtime interaction and open-loop factory/repair testing
Real-time simulation
Hardware-in-the-loop
Reusable test scripts
Use & integration
Recorded applications
Pre-hardware software verification
Controller hardware integration testing
Factory and repair test development
These describe the reviewed application scope, not confirmed deployments, released requirements or procurement eligibility.
Evidence of maturity
Currently advertised CLB/vCLB methods with historical supplier-reported shipping and unnamed Level A customer use. Current accepted model/configuration and quantified performance are unverified.
Commercial availability
Custom test-platform enquiries through Aviya; physical I/O, model fidelity, qualification responsibility and acceptance criteria need a scoped specification.
Integration and verification
Readiness
A technology readiness level is not established by the reviewed public sources.
Reviewed connections
No reviewed Mission area or released Defence need connection is currently published.
Original sources 3 linked records
These records support this capability and its published Mission area and Defence need connections. A source count is not a count of independent confirmations.
CLB uses a PC real-time simulator with MATLAB/Simulink and proprietary models converted to C, configuration-controlled scripts and runtime parameter interaction. The supplier claims FPGA simulation steps below10ns; this is not end-to-end I/O latency or independently validated accuracy. Open-loop factory and repair/overhaul testing is also described.
Supports: Capability · defence applications
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · maturity
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · technical tags
CLB uses a PC real-time simulator with MATLAB/Simulink and proprietary models converted to C, configuration-controlled scripts and runtime parameter interaction. The supplier claims FPGA simulation steps below10ns; this is not end-to-end I/O latency or independently validated accuracy. Open-loop factory and repair/overhaul testing is also described.
Supports: Capability · summary
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · capability type
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · core features
CLB uses a PC real-time simulator with MATLAB/Simulink and proprietary models converted to C, configuration-controlled scripts and runtime parameter interaction. The supplier claims FPGA simulation steps below10ns; this is not end-to-end I/O latency or independently validated accuracy. Open-loop factory and repair/overhaul testing is also described.
Supports: Capability · core features
CLB uses a PC real-time simulator with MATLAB/Simulink and proprietary models converted to C, configuration-controlled scripts and runtime parameter interaction. The supplier claims FPGA simulation steps below10ns; this is not end-to-end I/O latency or independently validated accuracy. Open-loop factory and repair/overhaul testing is also described.
Supports: Capability · commercial availability
CLB uses a PC real-time simulator with MATLAB/Simulink and proprietary models converted to C, configuration-controlled scripts and runtime parameter interaction. The supplier claims FPGA simulation steps below10ns; this is not end-to-end I/O latency or independently validated accuracy. Open-loop factory and repair/overhaul testing is also described.
Supports: Capability · commercial availability
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · technicaldomainslugs
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · catalogue teaser
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · core features
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · name
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · catalogue teaser
CLB uses a PC real-time simulator with MATLAB/Simulink and proprietary models converted to C, configuration-controlled scripts and runtime parameter interaction. The supplier claims FPGA simulation steps below10ns; this is not end-to-end I/O latency or independently validated accuracy. Open-loop factory and repair/overhaul testing is also described.
Supports: Capability · technical tags
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · technology readiness level
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · core features
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · summary
CLB uses a PC real-time simulator with MATLAB/Simulink and proprietary models converted to C, configuration-controlled scripts and runtime parameter interaction. The supplier claims FPGA simulation steps below10ns; this is not end-to-end I/O latency or independently validated accuracy. Open-loop factory and repair/overhaul testing is also described.
Supports: Capability · slug
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · display lead
vCLB models ARINC429, CANBus, AFDX, sensors, valves and LRUs in software before controller hardware exists. It shares a GUI and compatible scripts with CLB, allowing script migration to later controller-hardware tests. MATLAB/SCADE autocode integration and PC-resource scaling are supplier-described; modelled interfaces do not specify physical CLB interface cards.
Supports: Capability · defence applications
CLB uses a PC real-time simulator with MATLAB/Simulink and proprietary models converted to C, configuration-controlled scripts and runtime parameter interaction. The supplier claims FPGA simulation steps below10ns; this is not end-to-end I/O latency or independently validated accuracy. Open-loop factory and repair/overhaul testing is also described.
The supplier historical case says an unnamed aerospace customer used CLB extensively for DO-178B LevelA V&V, interfacing controller hardware with proprietary sensor/effector simulation. vCLB enabled software exercise before hardware and reused GUI scripts on CLB later. No named customer, aircraft, certificate, acceptance record or quantified saving is supplied.
Supports: Capability · technical tags
The supplier historical case says an unnamed aerospace customer used CLB extensively for DO-178B LevelA V&V, interfacing controller hardware with proprietary sensor/effector simulation. vCLB enabled software exercise before hardware and reused GUI scripts on CLB later. No named customer, aircraft, certificate, acceptance record or quantified saving is supplied.
The5December2012 CLB release advertises development and DO-178B/DO-254 LevelA test support, fault/flight parameter overrides and shipping at that release date. The linked products.php brochure is now404; historical shipping does not prove current stock or accepted configuration.
Public sources cited · Facts and assessments kept separate · Human review
The supplier historical case says an unnamed aerospace customer used CLB extensively for DO-178B LevelA V&V, interfacing controller hardware with proprietary sensor/effector simulation. vCLB enabled software exercise before hardware and reused GUI scripts on CLB later. No named customer, aircraft, certificate, acceptance record or quantified saving is supplied.
