SCARI GT (SCA v2.2.2 Compliant)
The SCA Core Framework is the central piece of the Component Based Development (CBD) infrastructure. It provides the overall software management functions of the embedded system. Residing on the target platform, it coordinates the deployment and configuration of the software components, ensuring that each one is loaded on the proper processor and connected to the other components as per the application mapping, wherever they may reside on the platform.
The SCARI-GT Core Framework is the most advanced SCA Core Framework available on the market. Tested for compliance against the SCA v2.2.2, it was used by the US Department of Defence JTRS Test and Evaluation Lab (JTEL) as part of their test bed to validate and improve the accuracy of its conformance tool (JTAP).
Deployed in thousands of high-performance radio systems around the world, the SCARI Core Framework (CF) is the commercial off-the-shelf (COTS) runtime environment of choice for platform providers and radio manufacturers, supporting the largest combination of operating systems, object request brokers, and processors.
VIAVI research team has been key contributor to the evolution of the specification and since the implementation of SCA v0.3 in the year 2000, while still at the Communications Research Centre Canada (CRC). Since then, the VIAVI team has implemented every new release of the SCA specification.
The VIAVI SCARI-GT Core Framework implements a number of task and static deployment optimizations which results in a smaller and faster Core Framework allowing reduced boot times.
The VIAVI SCARI-GT Core Framework adds support for the optional ResourceFactory as well as a number of unique features.
VIAVI SCARI GT: What's In The Box?
- Core Framework Components:
DomainManager, ApplicationFactory, Application, DeviceManager, FileManager, FileSystem, and File
- Node Components:
Log service, AudioDevice, ExecutableDevice and optional MHALDevice, USRPDevice
- Sample Applications:
Voice audio effect, performance analysis, log producer and optional AM, FM and P25 applications
VIAVI SCARI Next (SCA 4.X)
- VIAVI engineers are participating in the development of SCA Next (SCA v4.x), and have contributed a number of change proposals.
- VIAVI’s implementation of SCARI-Next CF will become available once the SCA v4.x specification gains international acceptance and becomes a requirement on national procurement programs.
VIAVI SCARI RT (SCA 2.2.2/4.X)
- Currently under R&D, VIAVI SCARI-RT CF will provide deterministic behavior for the deployment of standard SCA applications, which is essential for specific domains that require deterministic behavior.
- VIAVI SCARI-RT CF is expected to require smaller footprints and provide faster boot up times than VIAVI SCARI-GT CF.
If you have any questions about our products and services please contact us at +1-819-307-0333 or email us at email@example.com
Most comprehensive support for Operating Environments (OEs)
- SCARI GT has been ported to even more platforms: Wind River VxWorks [both RTP and kernel modes], GHS INTEGRITY, Lynx Software Technologies LynxOS, BlackBerry QNX, Linux, MontaVista and other embedded Linux flavors.
- Has been used on a large variety of PowerPC processors, ARM and XScale processors, and x86 processors. It has also been integrated on System-On-a-Chip (SoC) solutions such as the TI DaVinci processors, the Xilinx FPGAs with PPC cores, and more.
- Supports the most popular ORBs: ORBexpress is the defacto standard for SDR applications thanks to its great real-time performance. Also support TAO for research projects.
Ultra fast XML parsing
- Uses a hand crafted XML parser instead of a COTS DOM parser
- Performs in 13 to 21% of the runtime memory required for DOM parsing
- Performs in 8 to 20% of the time required for DOM parsing
Faster file access
- Reduces time that a Core Framework waits while files are copied
- Avoids copying files in the same file system (source and destination)
- Substantial reduction of app deployment time on embedded systems
File caching system for deployed components
- Uses cache to avoid copying previously deployed implementations
- Significantly reduces boot time (platforms that run the same applications)
Optimized registration from DeviceManagers
- Registration of Devices and Services using digested information
- Without this feature, each Device requires a minimum of 19 CORBA calls
- Speeds up node registration and reduces boot up time
Standalone remote Devices
- Devices can be started manually and report to a remote DeviceManager
- Provides footprint savings as not all nodes need to have a DeviceManager
- Can be used as a solution for the lack of SCA support for DeviceFactory
- Can run several Devices in a single address space
- Provides footprint optimizations
- Much higher speed of communication between Devices
Collocated Domain and Device Managers
- Use a single address space for both managers
- Reduces ORB-related footprint of managers by close to 50%
- Core Framework converts indirect connections into direct connections
- Requires much less CORBA interactions
- Uses a caching system to find components/ports involved in connections
- Significant gains for components/ports involved in several connections