For automatically deploying Chrona components to specific platforms you need the Chrona VisualDistributor tool. With the Chrona VisualDistributor you specify the platform where the components should be deployed, or you load an already defined platform. Then you specify for each component on which node it should execute—with a straight-forward drag-and-drop operation. Finally, you let the Chrona VisualDistributor generate the code automatically, so that you can execute the Chrona components on your specific platform.
- Platform specification. In case of a single node system you only define which kind of hardware and operating system you use. The hardware could, for example, be a dSpace MicroAutoBox for prototyping. The operating system could be your proprietary OS. In the automotive context it could, for example, be OSEK or AUTOSAR-OS. In case of a distributed system you have to specify which communication infrastructure is used. This could be, for example, FlexRay or Time-Triggered Ethernet. With the Chrona VisualDistributor you can specify platforms with arbitrary complexity, such as ones consisting of hundreds of nodes with multiple bus systems and gateways between them.
- Supported platforms. We support common embedded platforms and constantly add platforms to that list; please contact us to check whether your platform is already supported. Otherwise we implement the Chrona VisualDistributor plugin according to your specific requirements. The Chrona VisualDistributor is shipped with all the plugins required for a customer's specific platform.
- Fully automatic code and schedule generation. You literally have to press a single button to automatically generate the executable code, platform-specific configuration files, and in case of a distributed system the communication schedule(s). You can change the topology and/or how Chrona components should be mapped to the computing nodes at any time. Simply generate the code and schedules again. If the computing platform does not offer sufficient resources, the Chrona VisualDistributor stops the code generation. If the code generation succeeds the behavior of the TDL components on a particular platform is guaranteed to be always identical to their TDL specification provided by means of the Chrona VisualCreator tool.
- Static communication schedule analysis. In case of a distributed platform, the Chrona VisualDistributor automatically generates a static communication schedule. You can view the generated schedule and export it as Fibex file.
- Incremental communication scheduling. The Chrona VisualDistributor can also consider an already defined communication schedule and incrementally extend that schedule. Currently we support the Fibex format for importing communication schedules.
- Run-time environment. The Chrona TDL:Compiler, which is part of the Chrona VisualDistributor tool, generates timing code for each Chrona component. The socalled Chrona TDL:Machine executes the timing code on each node of the platform. The Chrona VisualDistributor is shipped with the Chrona TDL:Machine(s) required for a customer's specific platform.
