Simple Case suite is made up of numerous applications and frameworks that can simplify system development, specifically, systems that rely on message based communication between their components. But even in this relatively small niche, there are various technologies and development environments. We would like to help you understand exactly which of our products can assist you in your upcoming development needs and have therefore compiled this section to help you do that by suggesting product combinations based on technologies and needs.
The Data Distribution Service for Real-Time Systems (DDS) is a standard that aims to enable scalable, real-time, dependable, high-performance and interoperable data exchanges between publishers and subscribers. SimpleDDS is a solution for easy development of components and applications that use DDS as the base for data interactions which is based on RTI’s Connext DDS. Adi’s solution leverages their implementation to assist you in the efficient use of DDS technology with minimal DDS skills. If you are developing (or are intending to) a system that relies on DDS for communication, these are the products that will most likely answer your needs:
| What You Want to Do | The Solution |
|---|---|
| Eliminate multiple (and possibly conflicting) definitions in long and complicated text/XML files. | Use ICD tool to define and manage topics and their types (i.e. data dictionary). Access and work on the same data by different teams and levels. |
| Define what data items specific components of the system publish or subscribe to. | Use ICD tool to model the information. |
| Connect DDS publisher and subscriber specification to actual implementation. | Use ICD tool to automatically generate code that only needs one function call to create a domain participant with its subscriptions and publications ready to work. |
| Use simple generic participant-level API, free from need to access complex specific DDS participant hierarchy. | Using DDS Framework you do not need to access readers and writers directly. For example, use readAllTopics() of the participant object to get all inbound data for it. |
| Let developers concentrate on the “what” instead of the “how”. | DDS Framework takes care of how information is received or transmitted, you only need to what to do with it. |
| Develop a sophisticated framework for handling DDS. | Build it on top of Adi’s DDS Framework (currently available in C# and C++). |
| Mix DDS with technologies such as TCP, UDP, RS, MuxBus. | Use ICD tool to define participants and data of all interfaces regardless of technology. Determine specific output only at code generation stage. Use appropriate framework (see below) for each technology or develop your own. |
STANAG 4586 is a NATO Standard Interface of the Unmanned Control System (UCS) Unmanned Aerial Vehicle (UAV) interoperability. It includes data link, command and control, and human/computer interfaces. A Vehicle Specific Module (VSM) is the functional unit responsible for enabling control of a legacy UAV, which is not compliant with STANAG 4586, through the standard Data Link Interface (DLI). Over the past 10 years, Adi Mainly Software has specialized in developing VSM units for numerous UAV systems with a myriad of payloads and capabilities. To streamline the development process, we have built a very comprehensive set of tools that drastically reduces the effort needed and shortens time to market for these (and similar) systems. If you need to develop a VSM unit to enable control of a UAV through a STANAG 4586 compliant Ground Station, we have the following products for you:
For less specific systems that use message passing as their means of communication, we have the following solutions:
