Collaboration and Productivity

Collaboration and productivity - Key functions for AUTOSAR authoring tools

ETAS ISOLAR-A’s user-friendly interface: this example shows the mapping of software components to ECUs.

When developing AUTOSAR-compatible systems, application software developers benefit from having various editors as well as automated functions and scripts.

ETAS ISOLAR-A’s editors support standard work processes for generating AUTOSAR systems and software, as well as the AUTOSAR concepts of “Variant Handling” and “Splitable.”

Automated ISOLAR-A functions support a high number of work processes and help increase productivity and avoid error-prone manual work:

  • Generation, import of legacy formats (DBC, FIBEX, LDF, ODX), and any number of AUTOSAR files (including system, ECU, and diagnostic extracts), diff/merg, and validation of software artifacts
  • Integration of AUTOSAR systems and application software
  • Generation of system and ECU extracts for single and multi-core ECUs
  • Configuration of run-time environments (RTE)

Developers have additional access to the AUTOSAR data model and can modify it using scripts. Examples of where this can be useful include modifications (refactoring), recurring tasks, and customer-specific tasks.

A growing number of functions can also be used via command line, including signal-data mapping, validations, ECU extract generation, and much more.

With ISOLAR-A ECU EXTRACT, there is now a software product available that focuses on the generation of ECU extracts via command line.

Table-based Composition Editor supports Variation points, Splitable, and Auto Connection.

ISOLAR-A’s BCT add-on (Basic Software Configuration Tool) facilitates ECU configuration for AUTOSAR-compatible basic software.

The BCT add-on is highly flexible thanks to its configurability and expandability. Simultaneously, BCT supports customized generation of basic software configurations through features such as import of network descriptions, automation of configurations, generation of reports and customer documentation, as well as basic software code generation (e.g. based on ETAS RTA-BSW V2.0).

The System Editor supports to configure, e.g., networks, frames, protocol data units (pdu’s) and signals

There are editors available for basic software configuration. Recurring work processes benefit from integrated update and merge functions. Depending on the basic software in use, more abstract editors are available that support features such as the configuration of COM stack and diagnostic modules. Tasks like ECU configuration, automated validation, and data logging are also available via command line.