RTA-BSW v2.1.1 User Guide

RTA-BSW v2.1.1 User Guide

Copyright The data in this document may not be altered or amended without special notification from ETAS GmbH. ETAS GmbH undertakes no further obligation in relation to this document. The software described in it can only be used if the customer is in possession of a general license agreement or single license. Using and copying is only allowed in concurrence with the specifications stipulated in the contract. Under no circumstances may any part of this document be copied, reproduced, transmitted, stored in a retrieval system or translated into another language without the express written permission of ETAS GmbH. Copyright 2018 ETAS GmbH, Stuttgart The names and designations used in this document are trademarks or brands belonging to the respective owners. Document RTA-BSW User Guide V2.1.1 R01 EN 01.2018 2

Contents Contents... 3 1 Introduction... 4 1.1. Applicable Versions... 4 1.2. Safety Notice... 4 1.3. Definitions and Abbreviations... 4 1.4. Bibliography... 6 1.5. Conventions... 7 2 How to use this User Guide... 8 3 AUTOSAR... 9 3.1. Motivation... 9 3.2. Architecture... 10 3.3. Methodology... 15 3.4. Interfaces... 18 3.5. Multi-core... 20 4 RTA-BSW Architecture and Workflow... 22 4.1. Installation... 22 4.2. Integration with ISOLAR-A... 22 4.3. Activities and Outputs... 22 4.4. Creating a System Template and Software Component Template... 23 4.5. BSW Configuration Generation... 24 4.6. BSW Code Generation... 94 5 ETAS Contact Addresses... 96 5.1. ETAS HQ... 96 5.2. ETAS Subsidiaries and Technical Support... 96 Index... 97 RTA-BSW v2.1.1 User Guide 3

1 Introduction The RTA-BSW User Guide describes how to work with the RTA-BSW product on electronic control units. The guide also includes generic description of AUTOSAR BSW and the interactions between the components that make up the BSW. RTA-BSW includes multiple stacks that aggregate related BSW modules: RTA-BASE System Services supporting ECU and BSW initialization RTA-COM for vehicle network communication RTA-MEM supports persistent data storage RTA-DIAG supports ASW/BSW diagnostics and logging RTA-J1939 supports diagnostics using J1939 protocol RTA-SAFE supports functional safety including watchdog RTA-CAN for CAN-based communication RTA-XCP supports extended Calibration Protocol RTA-LIN for LIN-based communication RTA-HWD[CAN] supports CAN hardware access RTA-OS an SC1-4 AUTOSAR Operating System RTA-RTE AUTOSAR Run-time Environment generator RTA-BSW is provided as a plug-in to ETAS s AUTOSAR Authoring Tool, ISOLAR-A. 1.1. Applicable Versions This document applies to RTA-BSW v2.1.1. This is compatible with: ISOLAR-A v9.3 RTA-RTE v5.10 RTA-OS v5.5 As far as is possible the configuration of RTA-BSW and RTA-RTE uses standard ARXML and therefore the configuration aspects described in this User Guide are also applicable to later versions of the software. 1.2. Safety Notice CAUTION! Any configuration(s) this User Guide describes are an example only and users must be review and adapt them for specific project requirements before use. 1.3. Definitions and Abbreviations ARXML ASW AUTOSAR XML used to describe SWCs, Systems and ECU configurations. AUTOSAR Application Software. In AUTOSAR the application consists of multiple communicating SWCs including service, application and complex device driver SWCs. RTA-BSW v2.1.1 User Guide 4

BSW BSWMD AUTOSAR Basic Software module. AUTOSAR defines a comprehensive BSW architecture consisting of OS, RTE, service, interface and driver BSW modules that provide a device independent ECU abstraction to ASW and thus promote SWC reuse and relocation. See Section 1 for a list of AUTOSAR BSW modules. BSW Module Description an ARXML file modelling a BSW module including the schedulable and callable entities and the triggering BSW events. BSWMD files are generated by the RTA-BSW Code Generation process for modules that present an AUTOSAR interface to the RTE. BSW Stack CAN CDD A slice through the AUTOSAR Layered SW Architecture that comprises functionally related BSW modules from the OS, RTE, Service, ECU Abstraction and Microcontroller Abstraction layers. Controller Area Network peer-to-peer message protocol designed for automotive use. Complex Device Driver a custom BSW module for accessing hardware for which AUTOSAR defines no standardized access. The form of the upper interface of a CDD is standardized ports and therefore accessible to ASW using the Rte. However, the functionality provided by the CDD, for example how it accesses hardware, is implementation specific. Communication Cluster A set of ECUs linked by a communication medium using one or more Physical Channels. The communication can have arbitrary topology (bus, star, ring, etc.). All nodes within the cluster use the same communication protocol. Communication Controller DTC ECU E/E FlexRay EEPROM I-PDU IOC A dedicated hardware device, e.g. a CAN Controller, through which frames and send and received from a network. Diagnostic Trouble Code. Electronic Control Unit. In the context of AUTOSAR, an ECU comprises one microcontroller/peripherals and associated ASW and AUTOSAR configuration. In particular, AUTOSAR does not consider the mechanical design in the definition of an ECU and thus if a single housing contains multiple microcontrollers each requires its own AUTOSAR configuration and BSW stack. Electrical and Electronic. Automotive bus supporting high data rate communication with a static, time-sliced, segment providing real-time messages and a dynamic segment for event-triggered communication. Electronically Erasable Programmable Read-only memory. Interaction Layer PDU. Inter-OsApplication Communication Os API for sending and receiving data between OsApplications. RTA-BSW v2.1.1 User Guide 5

MCAL ODX OSEK PDU Microcontroller Abstraction Layer the lowest software layer of the Basic Software within the AUTOSAR SW architecture. The MCAL contains internal drivers (BSW with direct access to the microcontroller and its internal peripherals) and serves to make higher layers independent or the microcontroller. Open Diagnostic Data Exchange non-autosar format for configuring diagnostic software. Offene Systeme und deren Schnittstellen für die Elektronik im Kraftfahrzeug (Open Systems and their Interfaces for the Electronics in Motor Vehicles). OSEK include the specification of OSEK-OS and OSEK-COM which were use as the basis for the AUTOSAR Os and Com BSW modules Protocol Data Unit a set of messages sent/received over a network as a coherent entity. Physical Channel PIM Schema SPI SWC TP UDS VFB Communication medium, e.g. a CAN Bus, used to send and receive information between ECUs. A CAN or LIN Cluster consists of exactly one Physical Channel whereas a FlexRay cluster may have multiple Physical Channels to provide redundancy. Per-Instance Memory provides instance-specific state accessed through an Rte generated API. A XML file that describes the permitted structure and content type of another XML file including data types, available elements and their permitted order as well as more specialized rules such as multiplicity constraints. An ARXML file is defined using an AUTOSAR supplied schema. Serial Peripheral Interface synchronous serial interface using a master-slave architecture and widely used in automotive embedded systems. AUTOSAR Software Component A functional unit within ASW. An AUTOSAR application consists of multiple SWCs. Transmission Protocol A transport mechanism used to transmit and receive I-PDUs larger than a single bus frame. Unified Diagnostic Services A standardized set of diagnostic services defined by ISO 15765 and supported by the AUTOSAR Dcm module. AUTOSAR Virtual Function Bus. The VFB is an abstract composition of the ASW including all SWCs in the system their connections but not the mapping to particular ECUs. The VFB enables integration of ASW to occur early in the development phase and permits verification of the consistency of the communication relationship between SWCs. 1.4. Bibliography [1] AUTOSAR Motivation and Goals, AUTOSAR http:/www.autosar.org/about/basics/motivation-goals/ RTA-BSW v2.1.1 User Guide 6

[2] RTA-RTE User Guide, v5.11, ETAS GmbH [3] RTA-OS User Guide, v5.5, ETAS GmbH [4] RTA-BSW Installation and Getting Started Guide, v2.1.1, ETAS GmbH [5] ISOLAR-A V9.3 Getting Started Guide, ETAS GmbH [6] RTA-OS Getting Started, v5.5, ETAS GmbH [7] RTA-RTE Getting Started Guide, v5.11, ETAS GmbH 1.5. Conventions The following typographical conventions are used in this document: Mod AUTOSAR BSW Module OCI_CANTxMessage msg0 = Code snippets are presented on a gray background and in the Courier font. Choose File Open. Click [OK]. Press <ENTER>. The "Open File" dialog box is displayed. Select the file setup.exe A distribution is always a onedimensional table of sample points. Meaning and usage of each command are explained by means of comments. The comments are enclosed by the usual syntax for comments. Menu commands are shown in boldface with connecting arrow showing sub-menu / commands. GUI Buttons, e.g. those on dialog boxes, are shown in boldface with square brackets. Keyboard commands are shown in angled brackets. Names of program windows, dialog boxes, fields, etc. are shown in quotation marks. Text in drop-down lists on the screen, program code, as well as path- and file names are shown in the Courier font. General emphasis and new terms are set in boldface. RTA-BSW v2.1.1 User Guide 7

2 How to use this User Guide The RTA-BSW User Guide describes how to work with RTA-BSW within a development process for AUTOSAR-based ECUs. Section 3 provides an introduction to AUTOSAR BSW and the three key concepts: Architecture, Methodology and Interfaces. Readers already familiar with AUTOSAR development can skip this section. Section 4 describes how to use RTA-BSW based on an exemplar workflow and how the ConfGen and CodeGen elements of RTA-BSW derive the BSW configuration from the System Description and generate the BSW source core. RTA-BSW v2.1.1 User Guide 8

3 AUTOSAR This chapter introduces the AUTOSAR initiative and explores the key AUTOSAR concepts of architecture, methodology and interfaces that together contextualize RTA-BSW. 3.1. Motivation The AUTOSAR initiative arose from a recognition that the complexity of automotive software was ever increasing and that this complexity was likely to prove overwhelming as the amount of software in a vehicle increased exponentially. The principal motivations of AUTOSAR [1] directly address the increasing complexity: Management of E/E complexity associated with growth in functional scope. Scalability of solutions within and across product lines. Improved quality and reliability of E/E systems. AUTOSAR aims to meet these goals through the definition of a modular development approach with an emphasis on configuration that permits the integration of solutions from multiple suppliers using well-defined roles and responsibilities. The AUTOSAR approach relies on three key concepts: Architecture Definition of an automotive SW architecture (including a comprehensive BSW stack) providing progressive degrees of abstraction that promote application and basic software re-use and re-locatability. Methodology Definition of a systematic method of working between suppliers and OEMs that permits seamless interactions with a common configuration language. Interfaces Definition of the syntax and semantics of interactions including the interfaces between modules in the architecture and between suppliers and OEMs when exchanging solutions. SW Layers Services ECU Abstraction MCAL Architecture Methodology How supplier and OEM interact Common configuration language Syntax and semantics System Description SWC Description Interfaces Figure 1: AUTOSAR Key Concepts RTA-BSW v2.1.1 User Guide 9

3.2. Architecture AUTOSAR focuses on embedded automotive ECUs and therefore the AUTOSAR SW architecture exhibits certain key properties: Strong Hardware Interaction Automotive application software (ASW) makes extensive use of sensors and actuators in the ECU hardware. High Network Interaction a vehicle contains multiple networks and each ECU connects to at least one of the networks. Limited Computational Resources the microcontrollers used have limited resources both computing power and memory. Real-time Automotive application SW must respond to stimuli within a certain time limit. The complexity of automotive software has increased rapidly in recent years. AUTOSAR aims to provide a mechanism to control that complexity while retaining the properties above. 3.2.1 AUTOSAR Layered SW Architecture The AUTOSAR Layered SW Architecture is the key to how AUTOSAR provides a mechanism to manage the complexity of automotive software. The AUTOSAR architecture structures ECU software as a hierarchy of application software (ASW, consisting of multiple SWCs) and basic software (BSW) modules. Within the architecture description, AUTOSAR defines a mapping of the ASW/BSW to architectural layers, the responsibilities of each layer and the relationship between BSW modules. Application Software AUTOSAR Run-time Environment (RTE) Service Layer ECU Abstraction Layer Complex Drivers Microcontroller Abstraction Layer (MCAL) Microcontroller Hardware Figure 2: Layers within the AUTOSAR SW Architecture Figure 2 shows the layers within the AUTOSAR Layered SW Architecture. Each layer encapsulates and abstracts the functionality and behavior of the layer below: Application Software AUTOSAR models application software as collection of loosely coupled and highly cohesive SWCs. This design enables modular application development and independent implementation/test of individual SWCs (modules). A loosely coupled architecture implies limited dependencies between SWCs and is RTA-BSW v2.1.1 User Guide 10

desirable to permit the relocation of SWCs on different ECUs without changing the system design. Likewise, a highly cohesive architecture limits the individual responsibilities of a module an individual SWC will typically perform a small set of tasks. When combined with a loosely coupled architecture, a highly cohesive set of SWCs enables the development of robust systems of reusable components. AUTOSAR Run-Time Environment (RTE) provides communication and scheduling services to application software. The Rte module s purpose is to make application software independent of a mapping to a specific ECU and thus permits SWCs reuse or relocation between ECUs in the vehicle. Service Layer Modules that provide basic services for applications, RTE and BSW modules. a ECU Abstraction Layer Provides an API for access to peripherals and devices regardless of their location (microcontroller internal/external) and their connection to the microcontroller (port pins, type of interface). The ECU Abstraction provides an interface to the Services layer that is microcontroller and ECU independent. Microcontroller Abstraction Layer (MCAL) The lowest software layer of the AUTOSAR Basic Software containing drivers for internal devices, such as Fls and Eep, and memory-mapped external devices. These drivers have direct access to the internal hardware. Microcontroller Hardware Contains internal devices located inside the microcontroller, e.g. internal EEPROM or CAN controllers. Driver for internal devices are located in the Microcontroller Abstraction Layer The aim of the AUTOSAR Layered SW Architecture is to increase the re-usability of the application software by providing an abstract, uniform and standardized interface between the application SW and the hardware in the form of the BSW. By increasing re-usability the overall complexity of automotive software is also reduced as repeated work. Each layer of the AUTOSAR SW architecture encapsulates some dependency: The Service Layer offers abstracted services to both ASW (through the Run-time Environment) and other BSW modules. The facilities offered by the abstracted services are available on any AUTOSAR ECU promoting the portability and re-use of ASW. The ECU Abstraction Layer contains interface modules that provides an abstraction of the MCAL to the Service Layer than encapsulates information on MCU hardware layout, e.g. number and type of CAN controllers, by providing an AUTOSAR defined device abstraction. The abstraction provided ensures that the service layer can provide its abstraction without regard to the particular characteristics of individual ECU hardware. The Microcontroller Abstraction Layer (MCAL) contains the drivers for internal MCU hardware devices and encapsulates hardware specific characteristics of the MCU. This encapsulation provides to the ECU Abstraction Layer an AUTOSAR defined interface that makes it independent of the MCU hardware. 3.2.2 BSW Module Classification As well as their assignment to layers within the AUTOSAR SW architecture, BSW modules can be further classified as belonging to one of a number of module types. Each type has particular characteristics and responsibilities: Interface A BSW module providing a functional abstraction of the associated Driver module through the provision of a generic API that is independent of the characteristics of the device. RTA-BSW v2.1.1 User Guide 11

An Interface module does not change data before passing to the Driver. Typically, Interface modules are located in the ECU Abstraction Layer. Handler A BSW module that is an Interface module that also supports concurrent access and/or asynchronous access by multiple clients. A Handler will typically perform buffering and arbitration and, as it is a form of Interface, does not change data. AUTOSAR includes few specific Handler modules since the functionality is usually combined within an Interface or Driver module. Manager A BSW module that offers specific services to multiple clients simultaneously. A manager extends that Handler use-case to support abstraction for multiple clients where this is not possible for a pure handler. However, unlike a handler a manager can change and/or adapt the data before passing to the Interface. A Manager is typically located in the Service Layer. Driver A BSW module that controls a specific HW device. A driver can control either internal or external devices. Drivers for internal devices and memory-mapped external devices are in located in the Microcontroller Abstraction Layer since they access the microcontroller directly. Drivers for external devices are located in the in ECU Abstraction Layer. Complex Device Driver (CDD) A BSW module that spans the architecture having both a direct interface to microcontroller hardware as well as providing an AUTOSAR interface for access by ASW. The functionality of a CDD is not standardized by AUTOSAR however, the upper interface is configured using ports and therefore accessible by ASW through the Rte. Note: Use of a CDD by ASW implies a dependency on specific hardware capabilities of the ECU and therefore a reduction in the portability of the ASW. Library a collection of related utility functions accessible by all BSW modules and the Rte. A library function is reentrant (can be invoked by multiple BSW modules simultaneously), stateless and executes in the context of the caller. AUTOSAR specifies libraries for bit handling, interpolation, cryptography, etc. 3.2.3 BSW Stack A BSW stack defines a slice through the AUTOSAR Layered SW Architecture that comprises modules from the Service, ECU Abstraction and Microcontroller Abstraction layers. At a high-level, the functionality offered by the layers within the AUTOSAR Architecture is described by the functional blocks as shown in Figure 3. The functional blocks form the basis for the BSW stacks that collectively comprise RTA-BSW. RTA-BSW v2.1.1 User Guide 12

Application Software AUTOSAR Run-time Environment (RTE) Key Service Layer System Services Onboard Device Abstraction Memory Services Memory HW Abstraction Comm. Services Comm. HW Abstraction IO HW Abstraction Complex Drivers ECU Abstraction Layer MCAL Microcontroller Drivers Memory DriveRs Comm Drivers IO Drivers Microcontroller Hardware Figure 3: AUTOSAR Layered SW Architecture High Level Structure. A BSW stack is typically defined on a functional level and consists of modules that cooperate to provide functionally related services to the application layer. The following stacks are considered in this User Guide: RTA-BASE : ECU and BSW initialization and state management RTA-COM : Vehicle network communication using Com, PduR and bus-specific modules. RTA-MEM : Persistent (across driving cycles) storage using non-volatile memory. RTA-DIAG : Event logging and interaction with post-driving cycle diagnostic and service. 3.2.4 BSW Interactions AUTOSAR defines how and when BSW modules within the Layered SW Architecture can interact. System Services Onboard Device Abstraction Application Software AUTOSAR Run-time Environment (RTE) Memory Services Memory HW Abstraction Comm. Services Comm. HW Abstraction IO HW Abstraction Complex Drivers Key Permitted Discouraged Forbidden Microcontroller Drivers Memory DriveRs Comm Drivers IO Drivers Microcontroller Hardware Figure 4: BSW Interactions within the AUTOSAR Layered SW Architecture RTA-BSW v2.1.1 User Guide 13

Within the Services Layer, AUTOSAR permits horizontal interactions between modules, e.g. the Dem module saves fault data using the NVRAM manager both of which are service modules. Likewise, AUTOSAR permits horizontal interactions between modules in the ECU Abstraction Layer. However, horizontal interactions are not allowed between modules in the Microcontroller Abstraction Layer. AUTOSAR makes an exception for complex drivers; these are permitted to use horizontal interfaces to any BSW module. A vertical interaction occurs when one SW Layer accesses interfaces of the SW layer above or below. Single vertical interactions, e.g. from Service Layer to ECU Abstraction Layer, are clearly permitted since they define the interfaces that connect stacks together. In addition, a BSW module may access a lower layer module of another layer group, e.g. SPI for external hardware. The bypassing of one software layer i.e. a vertical interaction that skips a layer should be avoided and is discouraged within AUTOSAR and not used by the standardized BSW. AUTOSAR does not permit the bypassing of two or more software layers. To avoid dependencies on hardware, AUTOSAR does not permit the bypassing of the MCAL by modules within the Service and ECU Abstraction Layers. Finally, any BSW module in any layer may interact with system services. This exception is important for services provided by the Operating Systems since it means that a single mechanism for data consistency and scheduling can be applied to the BSW. RTA-BSW v2.1.1 User Guide 14

Figure 5 shows the AUTOSAR defined permitted interaction matrix for modules within the BSW. The figure is intended to be read row-wise and indicates access via a call-back only. Uses System Services Memory Services Comm. Services Complex Drivers I/O HW Abstraction Onboard Device Abstraction Memory HW Abstraction Comm. HW Abstraction Microcontroller Drivers Memory Drivers Comm. Drivers I/O Drivers SWC/RTE System Services Memory Services Communication Services Complex Driver Figure 5: AUTOSAR Layered SW Architecture Interaction Matrix A Complex Device Driver (CDD) has unique characteristics in the AUTOSAR architecture; it provides a standardized mechanism for accessing non-standard microcontroller hardware directly and providing an AUTOSAR interface accessible by ASW through the Rte. Due to its position within the layered architecture it has restricted access to BSW modules based on the following rules: Restricted Access I/O HW Abstraction On-board Device Abstraction Memory HW Abstraction Comm. HW Abstraction Microcontroller Drivers Memory Drivers Comm. Drivers I/O Drivers When accessed by a BSW module the module must offer a configurable interface that can adapt to the requirements of the CDD. When accessing a BSW module not only must the BSW s interface be configurable (e.g. names of call-back routines) but the interface must be re-entrant as parallel access from upper-layers and the CDD may occur. In addition no manager BSW module must exist since otherwise incoherent changes in the module s state by the manager and the CDD might occur. 3.3. Methodology The AUTOSAR Methodology defines how ECU software is developed by dividing the development process into a number of separable actions that cover all aspects of ECU SW RTA-BSW v2.1.1 User Guide 15

Bus development from the creation of a system-level description through to generation of each ECU s executable. System Configuration Input System Configuration (ARXML) ECU 1 SWC 1 SWC 2 ECU 2 SWC 1 System Design SWC 1 ECU Extract (ARXML) SWC 2 ECU Configuration ECU Value Collection (ARXML) SWC 1 SWC 2 RTE BSW Microcontroller RTA-BSW, OS and RTE Generation RTA-BSW (inc. OS/RTE) Source files (.c/.h) Figure 6: AUTOSAR Methodology The AUTOSAR methodology works in conjunction with the AUTOSAR Interfaces that standardize the data exchange formats used within the development process. RTA-BSW v2.1.1 User Guide 16

3.3.1 System Design The System Design phase defines the abstract application architecture, network topology and mapping of application to ECUs and communication to network signals. Application architecture is described using the concepts of the AUTOSAR Virtual Function Bus (VFB). The VFB comprises an abstract view of ASW and their interconnections and thus enables integration of ASW to occur early in the development phase. The network topology what signals are present and on to which networks they are mapped, what buses are present in the vehicle and how they are connected to ECU instances. The software mapping of ASW to ECUs. The result of the System Design phase is an AUTOSAR System Description consisting of one or more ARXML files. The System Description describes the entire vehicle architecture and can therefore grow to a significant size. In addition as it contains all information about the vehicle some of which will be proprietary and therefore not distributable from OEM to supplier. The AUTOSAR methodology defines a sub-process within System Design to derive either a System Extract (information pertaining to one functional sub-system) or an ECU Extract (information for a single ECU) from the complete system description. Figure 7 shows the hierarchy formed from System Description, System Extract and ECU extract. System Description System Extract System Extract ECU Extract ECU Extract ECU Extract Swc A ECU 1 RTE BSW Swc B Swc C ECU 2 RTE BSW Swc D Swc E ECU 3 RTE BSW Swc F Communication Bus Figure 7: AUTOSAR System Description, System Extract and ECU Extract hierarchy 3.3.2 ECU Configuration The ECU Extract contains sufficient information for configuration/generation of the BSW modules and the RTE for a single ECU. For example, the ECUC Value Collection for an ECU Extract will define the signals (frames) that are sent/received by that ECU and no others. The ECU extract is derived from the System Description by removing elements on other ECUs this process is automated by ISOLAR-A. RTA-BSW v2.1.1 User Guide 17

3.3.3 BSW and RTE Generation RTA-BSW ConfGen processes the system description to derive a default ECU Configuration Description. The integrator then applies any desired manual updates to the default ECU Configuration (using ISOLAR-A) before the RTA-BSW CodeGen process generates the BSW. 3.3.4 Application Development The ASW Development process is largely independent of System Design. The latter requires only a limited set of information about each SWC, e.g. the ports used to communicate, and therefore ASW development can proceed in parallel with System Design. The AUTOSAR methodology thus permits the independent implementation and testing of SWCs. By separating the implementation and test of different SWCs AUTOSAR promotes re-use of the SWC within a new ECU and simplifies integration by the OEM. 3.4. Interfaces The AUTOSAR Interfaces defines when and how participants within the AUTOSAR Methodology, such as OEM and supplier, exchange information. 3.4.1 Data Exchange Formats AUTOSAR defines several standardized data formats for exchanging information related to SWC, Systems and ECU configuration descriptions. SWC Description ARXML describing the interfaces, dynamic behavior and resource requirements of the SWC. The syntax and semantics of the SWC Description are described by the AUTOSAR Software Component Template and is typically created by the supplier and provided to the OEM along with the relevant source or object-code implementation files. BSW Module Description ARXML describing the interfaces, dynamic behavior and resource requirements of a BSW module. The syntax and semantics of the BSW Module Description are described by the AUTOSAR BSW Module Description Template and is typically created by the BSW generation process for BSW modules that present an AUTOSAR interface to the RTE. System Description ARXML description of vehicle E/E architecture including network topology and signals, ECU topology and SWC mapping to ECUs. The AUTOSAR System Template defines the syntax and semantics of a System Description. ECU Extract ARXML description for an ECU provided by the OEM to the ECU supplier. The ECU Extract, in conjunction with the ECUC Description, permits configuration and generation of the BSW and RTE for the ECU. The AUTOSAR System Template defines the syntax and semantics of an ECU Extract (this is the same AUTOSAR configuration syntax used for the System Description). ECUC Description ARXML description of BSW configuration parameters and derived from the ECU Extract and BSW Module Descriptions. RTA-BSW v2.1.1 User Guide 18

The ECUC Description uses a system of containers that group the corresponding parameters and, optionally, sub-containers. The parameters configure the specific parts of BSW, e.g. a top-level Com container contains the entire configuration for the module. The Com container will include multiple sub-containers (that in turn may contain additional sub-containers) that configure different aspects of the module including the ComSignals, etc. Com Container ComGeneral Parameters ComSignal Parameters ComIPdu Parameters ComSignalGroup Parameters ComGroupSignal Parameters ComGroupSignal Parameters The system of containers and parameters that form the ECUC Description is defined by an AUTOSAR-supplied ECU Configuration Parameter Definition file. This ARXML file defines the available containers and parameters for every standardized BSW module. The approach is both flexible and extensible vendor specific parameters can also be modelled through additional ARXML description file that describes how and when the parameters should be defined. All AUTOSAR data exchange formats use XML consistent with a schema defined by AUTOSAR. Since both supplier and OEM use the same schema, a common interpretation of the exchange is possible. The AUTOSAR schema is updated with each release of AUTOSAR to reflect new and modified features. 3.4.2 Interfaces in the Layered SW Architecture Within the Layered SW Architecture, AUTOSAR distinguishes between three different API forms: AUTOSAR Interface AUTOSAR define the syntax using the Software Component Template. The SWC implementer defines the semantics, e.g. the data items transmitted or received using the interface. Standardized AUTOSAR Interface AUTOSAR defines both the syntax and semantics. The Software Component Template defines the syntax. The respective AUTOSAR specification defines the interface semantics, i.e. what ports, data items and operations are included in the interface. Standardized Interface both the syntax and semantics defined by AUTOSAR and consisting of C functions. Figure 8 shows the interface forms used within the AUTOSAR Architecture. RTA-BSW v2.1.1 User Guide 19

A Service Layer BSW module can present either a Standardized AUTOSAR interface or a Standardized Interface to the upper layer RTE as AUTOSAR define both the syntax (interface form) and semantics (behavior of the module) to ensure portability of ASW. In contrast, ASW use AUTOSAR Interfaces since AUTOSAR defines only the syntax of data exchange format, the Software Component Template. The user defines the semantics of the interface embodied within the application functionality. Application SWC AUTOSAR Interface Actuator SWC AUTOSAR Interface ASW Sensor SWC AUTOSAR Interface Application SWC AUTOSAR Interface RTE Standardized Interface Standardized AUTOSAR Interface Standardized Interface AUTOSAR Interface AUTOSAR Interface Services Communication ECU Abstraction Operating System Standardized Interface BSW Standardized Interface Microcontroller Abstraction Complex Device Driver Microcontroller Hardware Figure 8: Interfaces in the AUTOSAR Layered SW Architecture 3.5. Multi-core RTA-BSW supports AUTOSAR R4.0 and therefore does not, in general, support the distribution of BSW across multiple ECU Partitions (microcontroller cores). The following constraints therefore apply when using a multi-core ECU: All BSW modules must be mapped to a single ECU partition The ECU partition containing the BSW must set the ECUC parameter Ecuc- PartitionBswModuleExecution to true. No other ECU partition must also set the ECUC parameter EcucPartitionBswModule- Execution to true. The Os module (RTA-OS) supports multi-core applications and the EcuM module can be configured to start the OS on each applicable core. The Rte (RTA-RTE) supports multi-core applications with elements of the ASW mapped to multiple ECU partitions. The Rte uses the Os s IOC API for communication between SWCs in different partitions and this mechanism does not support access to BSW which uses a C function based API to interface with the Rte. Consequently, Rte and BSW interactions must occur within the same ECU partition. RTA-BSW v2.1.1 User Guide 20

All ASW that need to access BSW must be mapped to the same ECU partition as the BSW. For example, ASW access to NvM for non-volatile memory use or Com for inter-ecu communication. It is not always possible to map the ASW SWCs that access BSW to the same ECU partition as the BSW, e.g. different partitions may have software with different safety integrity levels. If this is the case, then a proxy SWC within the BSW partition forwards access to the BSW from ASW in a different partition. Figure 9 illustrates a system where BSW access by SwcB is forwarded using Rte generated inter-partition communication to SWC Proxy in the same partition as the BSW. Asw/Bsw Partition 1 Asw Partition 2 Asw Partition 3 Key SwcA Proxy SwcB SwcD Inter- Partition Comms. BSW SwcC SwcE Intra- Partition Comms. Figure 9: Multi-core access to BSW using proxy SWC RTA-BSW v2.1.1 User Guide 21

4 RTA-BSW Architecture and Workflow RTA-BSW is an implementation of the AUTOSAR BSW and includes multiple module bundles that aggregate AUTOSAR functionality into coherent packages: RTA-BASE ECU and BSW mode management RTA-COM network-independent communication components RTA-MEM persistent/non-volatile data storage for ASW and BSW RTA-DIAG ASW/BSW diagnostics and logging RTA-SAFE components for safety management RTA-CAN CAN-specific network components RTA-XCP supports XCP protocol RTA-LIN LIN-specific network components RTA-J1939 supports diagnostics using J1939 protocol (with ISOBUS extensions) RTA-HWD[CAN] support for external CAN transceivers RTA-OS real-time operating system RTA-RTE RTE generator 4.1. Installation RTA-BSW is provided as a plug-in to ISOLAR-A; please consult the separate RTA-BSW Installation and Getting Started Guide [4] for detailed installation instructions. RTA-OS and RTA-RTE both use a different installation approach to the other RTA-BSW stacks. Refer to RTA-OS Getting Started [6] and RTE Getting Started Guide [7] respectively for installation instructions for these. 4.2. Integration with ISOLAR-A RTA-BSW is a plug-in for the ISOLAR-A AUTOSAR Authoring Tool. The RTA-BSW plug-in comprises two tools, ConfGen and CodeGen, used to create configuration and code for services and ECU abstraction modules. ConfGen traverses the AUTOSAR System Template (EcuInstance, SystemSignal, etc.) and create an equivalent configuration in EcucValueDescription format, which allows specific parameterization and is the input for BSW code generation tools. CodeGen an AUTOSAR BSW code generation tool, consuming configuration in EcucValueDescription format to create source code equivalent in.c/.h format using the RTA-BSW generator. See below for the use of ConfGen and CodeGen in a typical workflow. The following sections provide information on using these two tools focusing on the different options that they present. 4.3. Activities and Outputs Figure 10 illustrates the activities and generated outputs present in the intended workflow for the RTA-BSW plug-in. RTA-BSW v2.1.1 User Guide 22

The workflow shown in Figure 10 contains some key steps: The AUTOSAR System Description ARXML file(s) are created entirely using an AUTOSAR Authoring Tool, such as ISOLAR-A, or by importing information from legacy files, such as DBC, LDF or ODX. The user augments the System Description with additional ASW configuration, i.e. SWCs and compositions, using the AUTOSAR Software Component Template ARXML to define the VFB Configuration. RTA-BSW ConfGen uses the System Description and ASW Configuration(s) to create a default BSW Configuration using ECUC Value Collection ARXML. If required, the default BSW Configuration can be adaption to a specific user-case prior to final BSW generation. RTA-BSW CodeGen creates the BSW implementation this includes C source code and, for modules that present an AUTOSAR interface to the RTE, one or more BSWMD files for inclusion with the RTE generator s configuration. ASW Configuration Software Component Template ASW Description (ARXML) EcucValue Adaption for specific use-case Import Existing Information (Optional) ISOLAR-A Import System Description (ARXML) ConfGen BSW Configuration (ARXML) CodeGen DBC / LDF / etc. System Template ECUC Value Collection RTA-BSW Implementation Figure 10: RTA-BSW Activities and Outputs 4.4. Creating a System Template and Software Component Template As shown in Figure 10, RTA-BSW operates on an AUTOSAR System Template and upon Software Component Templates to generate the BSW Configuration. The ISOLAR-A v9.3 Getting Started Guide [5] describes how both types of template are prepared. The RTA- RTE Getting Started Guide [7] also provides configuration advice, for example data mappings for complex data types. The use of legacy file imports provides a route to quickly populating the system template with some information that ConfGen can use to generate BSW configuration automatically. 4.4.1 Legacy File Import ISOLAR-A supports the import of a number of different legacy file formats to perform the initial population of the AUTOSAR System Description. RTA-BSW ConfGen (described in 4.5) uses imported legacy files to generate configuration for specific BSW modules as shown in below: File format DBC Modules configured automatically RTA-CAN (CanIf, CanNM, CanSM) RTA-COM (Com, ComM, IpduM, Nm, PduR) RTA-BSW v2.1.1 User Guide 23

ODX (must feature both UDS and J1939 configuration) LDF RTA-DIAG (Dcm, Dem), RTA-J1939 (J1939Tp, J1939Dcm, J1939Rm, J1939Rm) RTA-LIN (LinIf, LinSM) Using ISOLAR-A to import legacy file formats is described in Section 5.3 ( Creating an AUTOSAR System Template in ISOLAR-A ) of the ISOLAR-A v9.3 Getting Started Guide [5]. 4.5. BSW Configuration Generation The RTA-BSW ConfGen tool generates BSW configuration information using data from the System Template and from Application Software Component Templates. To start ConfGen, click on the toolbar icon with the AUTOSAR System Template project selected. symbol (Screenshot 1) with an The selected project should contain at least the System Template Description (i.e. the SWCs, their mapping to ECUs, network information including mapping data communicated by SWCs to network signals). and, to make full use of this tool it is recommended that the complete Virtual Functional Bus (VFB) configuration is present. Screenshot 1: RTA-BSW Toolbar The first step is to select the RTA-BSW version to run (Screenshot 2): Screenshot 2: RTA-BSW Version Selection Dialog RTA-BSW v2.1.1 User Guide 24

Next, select the ECU Instance for which you wish to generate the EcucValueDescription values (Screenshot 3): Screenshot 3: RTA-BSW ECU Instance Selection Dialog After clicking [OK] the ConfGen process will begin, reporting results to the console (Screenshot 4): Screenshot 4: RTA-BSW Import result log (example) After completion of ConfGen the project will contain EcucValueDescription ARXML files and Parameter definitions which will allow you to customize and generate AUTOSAR BSW. RTA-BSW v2.1.1 User Guide 25

4.5.1 Repeating Configuration Generation If a BSW configuration already exists, then BSW Import ( button) deletes the following files before re-creating them with the replacement configuration: Project_EcucValues.arxml ECU configuration values for all modules (apart from CAN). Can_EcucValues.arxml ECU configuration values for CAN. Repeating RTA-BSW configuration generation deletes and then recreates the Project_EcucValues.arxml and Can_EcucValues.arxml files. Hence, the process will also delete any changes made by the user that are contained in the files. The AUTOSAR splitable mechanism provides a means to ensure that additions to the default configurations are not lost when regenerating the configuration. To exploit the splitable mechanism, define additional Ecuc parameters and reference values in separate ARXML files using the same ARPackage and EcucContainer structure as the default values. ISOLAR-A presents split items as a single entity when viewing using ARExplorer and Show Abstraction Groups is selected. Alternatively, the ISOLAR-A Splitable Explorer presents a combined view of all split items and can be used to create new split items. The RTA-BSW generation tools RTA-OS, RTA-RTE and RTA-BSW will then ensure that the split items in different Ecuc containers are combined to form a single item. El1 pkga El2 pkga root El1 pkgb merge El2 root pkgb El3 pkgb merge El1 El2 El1 El2 El3 El4 El4 root El1 El1 pkgc pkgc El2 El2 4.5.2 ConfgGen Parameters It is possible to change the default value used by ConfGen for the parameters. Adding a rule to the Settings/algo.properties file found in the System project will override the default value used by ConfGen if the user cannot otherwise change the value by configuring the system template. If the system template can configure the value then it is not possible to change the default in the algo.properties file. Rules in the algo.properties file take the form of a comma-separated list of defaults: manprop_{module}_{specifier} = {parameter}:{default_value}, module o specifier o The name of the module that contains the parameter. ALL to apply to all instances of the module. RTA-BSW v2.1.1 User Guide 26

o parameter o o The SHORT-NAME of the instance to apply the parameter. The name parameter to set. If there is a naming collision in the module, it is necessary to use the full path of the parameter. default_value o The new default value to use. CanConfigSet CanConfigSet//CanController//CanBusoffProcessing The default value is POLLING. CanConfigSet//CanController//CanControllerActivation The default value is TRUE. CanConfigSet//CanController//CanControllerBaseAddress CanConfigSet//CanController//CanControllerBaudrateConfig//CanContr ollerbaudrate The default value/s are ['500']. CanConfigSet//CanController//CanControllerBaudrateConfig//CanContr ollerpropseg CanConfigSet//CanController//CanControllerBaudrateConfig//CanContr ollerseg1 CanConfigSet//CanController//CanControllerBaudrateConfig//CanContr ollerseg2 CanConfigSet//CanController//CanControllerBaudrateConfig//CanContr ollersyncjumpwidth CanConfigSet//CanController//CanControllerId CanConfigSet//CanController//CanFilterMask//CanFilterMaskValue CanConfigSet//CanController//CanRxProcessing RTA-BSW v2.1.1 User Guide 27

CanConfigSet//CanController//CanRxProcessing The default value is POLLING. CanConfigSet//CanController//CanTxProcessing The default value is POLLING. CanConfigSet//CanController//CanWakeupProcessing The default value is POLLING. CanConfigSet//CanHardwareObject CanConfigSet//CanHardwareObject//CanHandleType CanConfigSet//CanHardwareObject//CanIdType CanConfigSet//CanHardwareObject//CanObjectId CanConfigSet//CanHardwareObject//CanObjectType CanConfigSet//CanHardwareObject//CanTTHardwareObjectTrigger//CanTT HardwareObjectBaseCycle CanConfigSet//CanHardwareObject//CanTTHardwareObjectTrigger//CanTT HardwareObjectCycleRepetition The default value is 1. CanConfigSet//CanHardwareObject//CanTTHardwareObjectTrigger//CanTT HardwareObjectTimeMark CanConfigSet//CanHardwareObject//CanTTHardwareObjectTrigger//CanTT HardwareObjectTriggerId RTA-BSW v2.1.1 User Guide 28

CanGeneral CanGeneral//CanCpuType The default value is OTHERS. CanGeneral//CanDevErrorDetection The default value is TRUE. CanGeneral//CanHardwareCancellation CanGeneral//CanIdenticalIdCancellation CanGeneral//CanIndex CanGeneral//CanMultiplexedTransmission CanGeneral//CanVersionInfoApi RTA-BSW v2.1.1 User Guide 29

CanIf CanIf//CanIfCtrlDrvCfg//CanIfCtrlCfg//CanIfCtrlId CanIf//CanIfCtrlDrvCfg//CanIfCtrlDrvRxIndication The default value is TRUE. CanIf//CanIfCtrlDrvCfg//CanIfCtrlDrvTxCancellation CanIf//CanIfDispatchCfg//CanIfDispatchUserCtrlBusOffUL The default value is CAN_SM. CanIf//CanIfDispatchCfg//CanIfDispatchUserCtrlModeIndicationUL The default value is CAN_SM. CanIf//CanIfInitCfg//CanIfInitCfgSet CanIf//CanIfInitCfg//CanIfInitHohCfg//CanIfHrhCfg//CanIfHrhListCfg //CanIfHrhListCanId CanIf//CanIfInitCfg//CanIfInitHohCfg//CanIfHrhCfg//CanIfHrhRangeCf g//canifhrhrangebaseid CanIf//CanIfInitCfg//CanIfInitHohCfg//CanIfHrhCfg//CanIfHrhRangeCf g//canifhrhrangemask CanIf//CanIfInitCfg//CanIfInitHohCfg//CanIfHrhCfg//CanIfHrhRangeCf g//canifhrhrangerxpdulowercanid CanIf//CanIfInitCfg//CanIfInitHohCfg//CanIfHrhCfg//CanIfHrhRangeCf g//canifhrhrangerxpdurangecanidtype CanIf//CanIfInitCfg//CanIfInitHohCfg//CanIfHrhCfg//CanIfHrhRangeCf g//canifhrhrangerxpduuppercanid CanIf//CanIfInitCfg//CanIfInitHohCfg//CanIfHrhCfg//CanIfHrhSoftwar efilter RTA-BSW v2.1.1 User Guide 30

CanIf//CanIfInitCfg//CanIfInitHohCfg//CanIfHthCfg The default value is TRUE. CanIf//CanIfInitCfg//CanIfRxPduCfg//CanIfRxPduCanId CanIf//CanIfInitCfg//CanIfRxPduCfg//CanIfRxPduCanIdMask CanIf//CanIfInitCfg//CanIfRxPduCfg//CanIfRxPduCanIdRange//CanIfRxP ducanidrangelowercanid CanIf//CanIfInitCfg//CanIfRxPduCfg//CanIfRxPduCanIdRange//CanIfRxP ducanidrangeuppercanid CanIf//CanIfInitCfg//CanIfRxPduCfg//CanIfRxPduCanIdType CanIf//CanIfInitCfg//CanIfRxPduCfg//CanIfRxPduDlc The default value is 1. CanIf//CanIfInitCfg//CanIfRxPduCfg//CanIfRxPduId CanIf//CanIfInitCfg//CanIfRxPduCfg//CanIfRxPduReadData CanIf//CanIfInitCfg//CanIfRxPduCfg//CanIfRxPduUserRxIndicationName CanIf//CanIfInitCfg//CanIfTxPduCfg//CanIfTxPduCanId CanIf//CanIfInitCfg//CanIfTxPduCfg//CanIfTxPduCanIdMask CanIf//CanIfInitCfg//CanIfTxPduCfg//CanIfTxPduCanIdType CanIf//CanIfInitCfg//CanIfTxPduCfg//CanIfTxPduDlc CanIf//CanIfInitCfg//CanIfTxPduCfg//CanIfTxPduId CanIf//CanIfInitCfg//CanIfTxPduCfg//CanIfTxPduReadNotifyStatus CanIf//CanIfPublicCfg//CanIfAddressTranslationTableSupport RTA-BSW v2.1.1 User Guide 31

CanIf//CanIfPublicCfg//CanIfMetaDataSupport CanIf//CanIfPublicCfg//CanIfPublicCancelTransmitSupport CanIf//CanIfPublicCfg//CanIfPublicChangeBaudrateSupport CanIf//CanIfPublicCfg//CanIfPublicDevErrorDetect CanIf//CanIfPublicCfg//CanIfPublicMultipleDrvSupport CanIf//CanIfPublicCfg//CanIfPublicNumberOfCanHwUnits The default value is 1. CanIf//CanIfPublicCfg//CanIfPublicReadRxPduDataApi CanIf//CanIfPublicCfg//CanIfPublicReadRxPduNotifyStatusApi The default value is TRUE. CanIf//CanIfPublicCfg//CanIfPublicReadTxPduNotifyStatusApi The default value is TRUE. CanIf//CanIfPublicCfg//CanIfPublicSetDynamicTxIdApi CanIf//CanIfPublicCfg//CanIfPublicTxBuffering CanIf//CanIfPublicCfg//CanIfPublicTxConfirmPollingSupport RTA-BSW v2.1.1 User Guide 32

CanIf//CanIfPublicCfg//CanIfPublicVersionInfoApi CanIf//CanIfPublicCfg//CanIfPublicWakeupCheckValidApi RTA-BSW v2.1.1 User Guide 33

CanNm CanNm//CanNmGlobalConfig CanNm//CanNmGlobalConfig//CanNmBusLoadReductionEnabled CanNm//CanNmGlobalConfig//CanNmBusSynchronizationEnabled CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmBusLoadReductio nactive CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmComMNetworkHand leref CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmImmediateNmCycl etime CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmImmediateNmTran smissions CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmMsgCycleOffset CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmMsgCycleTime CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmMsgReducedTime CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmMsgTimeoutTime CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmNodeId CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmPduCbvPosition CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmPduNidPosition CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmRemoteSleepIndT ime CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmRepeatMessageTi me CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmTimeoutTime CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmUserDataLength RTA-BSW v2.1.1 User Guide 34

CanNm//CanNmGlobalConfig//CanNmChannelConfig//CanNmWaitBusSleepTim e CanNm//CanNmGlobalConfig//CanNmComControlEnabled CanNm//CanNmGlobalConfig//CanNmComUserDataSupport CanNm//CanNmGlobalConfig//CanNmDevErrorDetect CanNm//CanNmGlobalConfig//CanNmImmediateRestartEnabled CanNm//CanNmGlobalConfig//CanNmImmediateTxconfEnabled CanNm//CanNmGlobalConfig//CanNmMainFunctionPeriod CanNm//CanNmGlobalConfig//CanNmNodeDetectionEnabled CanNm//CanNmGlobalConfig//CanNmNumberOfChannels CanNm//CanNmGlobalConfig//CanNmPassiveModeEnabled CanNm//CanNmGlobalConfig//CanNmPduRxIndicationEnabled CanNm//CanNmGlobalConfig//CanNmRemoteSleepIndEnabled CanNm//CanNmGlobalConfig//CanNmRepeatMsgIndEnabled CanNm//CanNmGlobalConfig//CanNmStateChangeIndEnabled CanNm//CanNmGlobalConfig//CanNmUserDataEnabled RTA-BSW v2.1.1 User Guide 35

CanSM CanSM//CanSMConfiguration//CanSMManagerNetwork//CanSMBorCounterL1T ol2 CanSM//CanSMConfiguration//CanSMManagerNetwork//CanSMBorTxConfirma tionpolling CanSM//CanSMConfiguration//CanSMManagerNetwork//CanSMComMNetworkHa ndleref CanSM//CanSMConfiguration//CanSMManagerNetwork//CanSMNetworkIndex CanSM//CanSMConfiguration//CanSMModeRequestRepetitionMax The default value is 5. CanSM//CanSMGeneral//CanSMDevErrorDetect CanSM//CanSMGeneral//CanSMVersionInfoApi RTA-BSW v2.1.1 User Guide 36

CanTp CanTp//CanTpConfig//CanTpChannel//CanTpChannelMode The default value is CANTP_MODE_HALF_DUPLEX. CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpBs CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpNAe CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpNAe//CanTpNAe CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpNSa CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpNSa//CanTpNSa CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpNTa CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpNTa//CanTpNTa CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpNar CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpNbr CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpNcr CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpRxAddressingFo rmat CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpRxNPdu//CanTpR xnpduid CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpRxNSduFCActiva tion CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpRxPaddingActiv ation CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpRxPaddingValue CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpRxTaType RTA-BSW v2.1.1 User Guide 37

CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpTxFcNPdu//CanT ptxfcnpduconfirmationpduid CanTp//CanTpConfig//CanTpChannel//CanTpRxNSdu//CanTpTxFcNPdu//CanT ptxfcnpduref CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpNAe CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpNAe//CanTpNAe CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpNSa CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpNSa//CanTpNSa CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpNTa CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpNTa//CanTpNTa CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpNas CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpNbs CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpNcs CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpRxFcNPdu//CanT prxfcnpduref CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpTc CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpTxAddressingFo rmat CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpTxNPdu//CanTpT xnpduconfirmationpduid CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpTxNPdu//CanTpT xnpduref CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpTxNSduFCActiva tion CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpTxNSduId RTA-BSW v2.1.1 User Guide 38

CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpTxPaddingActiv ation CanTp//CanTpConfig//CanTpChannel//CanTpTxNSdu//CanTpTxTaType CanTp//CanTpConfig//CanTpGeneral//CanTpChangeParameterRequestApi CanTp//CanTpConfig//CanTpGeneral//CanTpChannelMode The default value is CANTP_MODE_HALF_DUPLEX. CanTp//CanTpConfig//CanTpGeneral//CanTpDevErrorDetect CanTp//CanTpConfig//CanTpGeneral//CanTpFCHandling The default value is CANTP_FC_ADAPTABLE. CanTp//CanTpConfig//CanTpGeneral//CanTpMainFunctionPeriod CanTp//CanTpConfig//CanTpGeneral//CanTpStrictDlcCheck CanTp//CanTpConfig//CanTpGeneral//CanTpTransmitFromRxind The default value is CANTP_OFF. CanTp//CanTpConfig//CanTpGeneral//CanTpTxBurstMode The default value is CANTP_OFF. CanTp//CanTpConfig//CanTpGeneral//CanTpUnexptdPduHandling The default value is CANTP_IGNORE. CanTp//CanTpConfig//CanTpGeneral//CanTpVersionInfoApi The default value is TRUE. RTA-BSW v2.1.1 User Guide 39

Com Com//ComConfig//ComConfigurationId Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//combitposition Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comfilter//comfilteralgorithm Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comfilter//comfiltermask Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comfilter//comfiltermax Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comfilter//comfiltermin Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comfilter//comfilteroffset Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comfilter//comfilterperiod Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comfilter//comfilterx Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comsignalendianness Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comtransferproperty Com//ComConfig//ComGwMapping//ComGwDestination//ComGwDestinationDe scription//comupdatebitposition Com//ComConfig//ComGwMapping//ComGwSource//ComGwSourceDescription/ /ComBitPosition Com//ComConfig//ComGwMapping//ComGwSource//ComGwSourceDescription/ /ComBitSize Com//ComConfig//ComGwMapping//ComGwSource//ComGwSourceDescription/ /ComSignalEndianness RTA-BSW v2.1.1 User Guide 40

Com//ComConfig//ComGwMapping//ComGwSource//ComGwSourceDescription/ /ComSignalLength Com//ComConfig//ComGwMapping//ComGwSource//ComGwSourceDescription/ /ComSignalType Com//ComConfig//ComGwMapping//ComGwSource//ComGwSourceDescription/ /ComUpdateBitPosition Com//ComConfig//ComIPdu//ComIPduDirection Com//ComConfig//ComIPdu//ComIPduHandleId Com//ComConfig//ComIPdu//ComIPduType Com//ComConfig//ComIPdu//ComTimeout Com//ComConfig//ComIPdu//ComTxIPdu//ComMetaDataDefault Com//ComConfig//ComIPdu//ComTxIPdu//ComMetaDataDefault Com//ComConfig//ComIPdu//ComTxIPdu//ComMinimumDelayTime Com//ComConfig//ComIPdu//ComTxIPdu//ComTxIPduUnusedAreasDefault Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeFalse//ComTxMode//Com TxModeMode Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeFalse//ComTxMode//Com TxModeNumberOfRepetitions Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeFalse//ComTxMode//Com TxModeRepetitionPeriod Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeFalse//ComTxMode//Com TxModeTimeOffset Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeFalse//ComTxMode//Com TxModeTimePeriod Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeTrue//ComTxMode//ComT xmodemode RTA-BSW v2.1.1 User Guide 41

Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeTrue//ComTxMode//ComT xmodenumberofrepetitions Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeTrue//ComTxMode//ComT xmoderepetitionperiod Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeTrue//ComTxMode//ComT xmodetimeoffset Com//ComConfig//ComIPdu//ComTxIPdu//ComTxModeTrue//ComTxMode//ComT xmodetimeperiod Com//ComConfig//ComIPduGroup//ComIPduGroupHandleId Com//ComConfig//ComSignal//ComBitPosition Com//ComConfig//ComSignal//ComBitSize Com//ComConfig//ComSignal//ComFilter//ComFilterAlgorithm Com//ComConfig//ComSignal//ComFilter//ComFilterMask Com//ComConfig//ComSignal//ComFilter//ComFilterMax Com//ComConfig//ComSignal//ComFilter//ComFilterMin Com//ComConfig//ComSignal//ComFilter//ComFilterOffset Com//ComConfig//ComSignal//ComFilter//ComFilterPeriod Com//ComConfig//ComSignal//ComFilter//ComFilterX Com//ComConfig//ComSignal//ComHandleId Com//ComConfig//ComSignal//ComNotification Com//ComConfig//ComSignal//ComSignalDataInvalidValue Com//ComConfig//ComSignal//ComSignalEndianness RTA-BSW v2.1.1 User Guide 42

Com//ComConfig//ComSignal//ComSignalLength Com//ComConfig//ComSignal//ComSignalType Com//ComConfig//ComSignal//ComTimeout Com//ComConfig//ComSignal//ComTimeoutNotification Com//ComConfig//ComSignal//ComTransferProperty Com//ComConfig//ComSignal//ComUpdateBitPosition Com//ComConfig//ComSignalGroup//ComGroupSignal//ComBitPosition Com//ComConfig//ComSignalGroup//ComGroupSignal//ComBitSize Com//ComConfig//ComSignalGroup//ComGroupSignal//ComFilter//ComFilt eralgorithm Com//ComConfig//ComSignalGroup//ComGroupSignal//ComFilter//ComFilt ermask Com//ComConfig//ComSignalGroup//ComGroupSignal//ComFilter//ComFilt ermax Com//ComConfig//ComSignalGroup//ComGroupSignal//ComFilter//ComFilt ermin Com//ComConfig//ComSignalGroup//ComGroupSignal//ComFilter//ComFilt eroffset Com//ComConfig//ComSignalGroup//ComGroupSignal//ComFilter//ComFilt erperiod Com//ComConfig//ComSignalGroup//ComGroupSignal//ComFilter//ComFilt erx Com//ComConfig//ComSignalGroup//ComGroupSignal//ComHandleId Com//ComConfig//ComSignalGroup//ComGroupSignal//ComSignalDataInval idvalue Com//ComConfig//ComSignalGroup//ComGroupSignal//ComSignalEndiannes s RTA-BSW v2.1.1 User Guide 43

Com//ComConfig//ComSignalGroup//ComGroupSignal//ComSignalLength Com//ComConfig//ComSignalGroup//ComGroupSignal//ComSignalType Com//ComConfig//ComSignalGroup//ComGroupSignal//ComTransferPropert y Com//ComConfig//ComSignalGroup//ComHandleId Com//ComConfig//ComSignalGroup//ComNotification Com//ComConfig//ComSignalGroup//ComTimeout Com//ComConfig//ComSignalGroup//ComTimeoutNotification Com//ComConfig//ComSignalGroup//ComTransferProperty Com//ComConfig//ComSignalGroup//ComUpdateBitPosition Com//ComConfig//ComTimeBase//ComGwTimeBase Com//ComConfig//ComTimeBase//ComRxTimeBase 01. Com//ComConfig//ComTimeBase//ComTxTimeBase 01. Com//ComGeneral//ComConfigurationUseDet The default value is TRUE. Com//ComGeneral//ComMetaDataSupport RTA-BSW v2.1.1 User Guide 44

ComM ComM//ComMChannel//ComMBusType The default value/s are ['COMM_BUS_TYPE_INTERNAL']. ComM//ComMChannel//ComMChannelId ComM//ComMChannel//ComMFullCommRequestNotificationEnabled ComM//ComMChannel//ComMNetworkManagement//ComMNmLightTimeout The default value is 10. ComM//ComMChannel//ComMNetworkManagement//ComMNmVariant The default value/s are ['NONE']. ComM//ComMChannel//ComMNoCom The default value is TRUE. ComM//ComMChannel//ComMUserPerChannel//ComMUserChannel ComM//ComMGeneral//ComMDevErrorDetect ComM//ComMGeneral//ComMEcuGroupClassification ComM//ComMGeneral//ComMModeLimitationEnabled ComM//ComMGeneral//ComMPncGatewayEnabled ComM//ComMGeneral//ComMPncSupport ComM//ComMGeneral//ComMSynchronousWakeUp RTA-BSW v2.1.1 User Guide 45

ComM//ComMGeneral//ComMVersionInfoApi ComM//ComMGeneral//ComMWakeupInhibitionEnabled ComM//ComMUser//ComMUserIdentifier RTA-BSW v2.1.1 User Guide 46

Dcm Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabfnc Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabfnc Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabscheduler Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabscheduler Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabserviceid The default value is 16. Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabserviceid Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabsessionlevelref Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabsidinitfunction Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabsidinitfunction Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabsubfuncavail Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsidtabsubfuncavail Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsubservice Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsubservice//dcmdsdsubserviceid Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsubservice//dcmdsdsubservicesecuritylevelref RTA-BSW v2.1.1 User Guide 47

Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdService//DcmD sdsubservice//dcmdsdsubservicesessionlevelref Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdSidTabId Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//DcmDsdSidTabId Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//NRCForService Dcm//DcmConfigSet//DcmDsd//DcmDsdServiceTable//NRCForService Dcm//DcmConfigSet//DcmDsl//DcmDslBuffer//DcmDslBufferSize Dcm//DcmConfigSet//DcmDsl//DcmDslDiagResp//DcmDslDiagRespMaxNumRes ppend Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslperiodictranmissionconre f Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslprotocolrx//dcmdslprotoc olrxaddrtype Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslprotocolrx//dcmdslprotoc olrxaddrtype Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslprotocolrx//dcmdslprotoc olrxpduid Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslprotocolrx//dcmdslprotoc olrxpduid Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslprotocolrx//dcmdslprotoc olrxpduref Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslprotocolrx//dcmdslprotoc olrxtestersourceaddr RTA-BSW v2.1.1 User Guide 48

Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslprotocolrxtestersourcead dr Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslprotocoltx//dcmdslprotoc oltxpduref Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslmainconnection//dcmdslprotocoltx//dcmdsltxconf irmationpduid Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slconnection//dcmdslperiodictransmission//dcmdslperiodicconnection //DcmDslPeriodicTxPduRef Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slprotocolid Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slprotocolisparallelexecutab Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slprotocolnrc21onpriorityassessmentreject Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slprotocolpriority Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slprotocolsidtable Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slprotocolsidtable Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmD slprotocoltranstype Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmS endresppendontranstoboot Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmT imstrp2serveradjust Dcm//DcmConfigSet//DcmDsl//DcmDslProtocol//DcmDslProtocolRow//DcmT imstrp2starserveradjust RTA-BSW v2.1.1 User Guide 49

Dcm//DcmConfigSet//DcmDsp//DcmDspComControl//DcmDspComControlAllCh annel//dcmdspallcommchannelref Dcm//DcmConfigSet//DcmDsp//DcmDspControlDTCSetting//DcmDspControlD TCSettingReEnableModeRuleRef Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataFreezeCurrentStat efnc Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataInfoRef Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataReadFnc The default value is A_UINT32. Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataResetToDefaultFnc Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataReturnControlToEc ufnc Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataShortTermAdjustme ntfnc Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataSize Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataType Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataUsePort Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDataWriteFnc Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDiagnosisScaling Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDiagnosisScaling//Dcm DspAlternativeDataProps//DcmDspLinearScale//DcmDspDiagnosisReprese ntationdatalowerrange Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDiagnosisScaling//Dcm DspAlternativeDataProps//DcmDspLinearScale//DcmDspDiagnosisReprese ntationdataoffset Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDiagnosisScaling//Dcm DspAlternativeDataProps//DcmDspLinearScale//DcmDspDiagnosisReprese ntationdataresolution RTA-BSW v2.1.1 User Guide 50

Dcm//DcmConfigSet//DcmDsp//DcmDspData//DcmDspDiagnosisScaling//Dcm DspAlternativeDataProps//DcmDspLinearScale//DcmDspDiagnosisReprese ntationdataupperrange Dcm//DcmConfigSet//DcmDsp//DcmDspDataInfo//DcmDspDataFixedLength The default value is TRUE. Dcm//DcmConfigSet//DcmDsp//DcmDspDid//DcmDspDidIdentifier Dcm//DcmConfigSet//DcmDsp//DcmDspDid//DcmDspDidInfoRef Dcm//DcmConfigSet//DcmDsp//DcmDspDid//DcmDspDidMaxNumberOfRecords/ /DcmDspDidMaxNumRecords Dcm//DcmConfigSet//DcmDsp//DcmDspDid//DcmDspDidSignal//DcmDspDidDa tapos Dcm//DcmConfigSet//DcmDsp//DcmDspDid//DcmDspDidSignal//DcmDspDidDa taref Dcm//DcmConfigSet//DcmDsp//DcmDspDid//DcmDspDidUsed Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idcontrol//dcmdspdidcontrolsecuritylevelref Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idcontrol//dcmdspdidfreezecurrentstate Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idcontrol//dcmdspdidresettodefault Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idcontrol//dcmdspdidreturncontroltoecu Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idcontrol//dcmdspdidshorttermadjustment Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idread Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idread//dcmdspdidreadsecuritylevelref Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idread//dcmdspdidreadsessionref RTA-BSW v2.1.1 User Guide 51

Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idwrite Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idwrite//dcmdspdidwritesecuritylevelref Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidAccess//DcmDspD idwrite//dcmdspdidwritesessionref Dcm//DcmConfigSet//DcmDsp//DcmDspDidInfo//DcmDspDidDynamicallyDefi ned The default value is TRUE. Dcm//DcmConfigSet//DcmDsp//DcmDspMaxDidToRead Dcm//DcmConfigSet//DcmDsp//DcmDspMaxPeriodicDidToRead Dcm//DcmConfigSet//DcmDsp//DcmDspMemory//DcmDspMemoryIdInfo//DcmDs pmemoryidvalue Dcm//DcmConfigSet//DcmDsp//DcmDspMemory//DcmDspMemoryIdInfo//DcmDs preadmemoryrangeinfo//dcmdspreadmemoryrangehigh Dcm//DcmConfigSet//DcmDsp//DcmDspMemory//DcmDspMemoryIdInfo//DcmDs preadmemoryrangeinfo//dcmdspreadmemoryrangehighrb Dcm//DcmConfigSet//DcmDsp//DcmDspMemory//DcmDspMemoryIdInfo//DcmDs preadmemoryrangeinfo//dcmdspreadmemoryrangelow Dcm//DcmConfigSet//DcmDsp//DcmDspMemory//DcmDspMemoryIdInfo//DcmDs preadmemoryrangeinfo//dcmdspreadmemoryrangelowrb Dcm//DcmConfigSet//DcmDsp//DcmDspMemory//DcmDspUseMemoryId Dcm//DcmConfigSet//DcmDsp//DcmDspPeriodicDidTransmission//DcmDspMa xperiodicdidscheduler Dcm//DcmConfigSet//DcmDsp//DcmDspPeriodicTransmission//DcmDspPerio dictransmissionfastrate Dcm//DcmConfigSet//DcmDsp//DcmDspPeriodicTransmission//DcmDspPerio dictransmissionmediumrate RTA-BSW v2.1.1 User Guide 52

Dcm//DcmConfigSet//DcmDsp//DcmDspPeriodicTransmission//DcmDspPerio dictransmissionslowrate Dcm//DcmConfigSet//DcmDsp//DcmDspReadDTC//DcmDspReadDTCRow//DcmDsp DTCInfoSubFuncLevel Dcm//DcmConfigSet//DcmDsp//DcmDspReadDTC//DcmDspReadDTCRow//DcmDsp DTCSubFuncServHandler Dcm//DcmConfigSet//DcmDsp//DcmDspRoutine//DcmDspRequestResultsRout inefnc Dcm//DcmConfigSet//DcmDsp//DcmDspRoutine//DcmDspRequestResultsRout inesupported Dcm//DcmConfigSet//DcmDsp//DcmDspRoutine//DcmDspRoutineFixedLength Dcm//DcmConfigSet//DcmDsp//DcmDspRoutine//DcmDspRoutineIdentifier Dcm//DcmConfigSet//DcmDsp//DcmDspRoutine//DcmDspRoutineInfoRef Dcm//DcmConfigSet//DcmDsp//DcmDspRoutine//DcmDspRoutineUsePort Dcm//DcmConfigSet//DcmDsp//DcmDspRoutine//DcmDspStartRoutineFnc Dcm//DcmConfigSet//DcmDsp//DcmDspRoutine//DcmDspStopRoutineFnc Dcm//DcmConfigSet//DcmDsp//DcmDspRoutine//DcmDspStopRoutineSupport ed Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineAuthori zation//dcmdsproutinesecuritylevelref Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineRequest ResIn//DcmDspRoutineRequestResInSignal//DcmDspRoutineSignalLength Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineRequest ResIn//DcmDspRoutineRequestResInSignal//DcmDspRoutineSignalPos Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineRequest ResIn//DcmDspRoutineRequestResInSignal//DcmDspRoutineSignalType Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineRequest ResOut//DcmDspRoutineRequestResOutSignal//DcmDspRoutineSignalLengt h RTA-BSW v2.1.1 User Guide 53

Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineRequest ResOut//DcmDspRoutineRequestResOutSignal//DcmDspRoutineSignalPos Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineRequest ResOut//DcmDspRoutineRequestResOutSignal//DcmDspRoutineSignalType Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineStopIn/ /DcmDspRoutineStopInSignal//DcmDspRoutineSignalLength Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineStopIn/ /DcmDspRoutineStopInSignal//DcmDspRoutineSignalPos Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineStopIn/ /DcmDspRoutineStopInSignal//DcmDspRoutineSignalType Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineStopOut //DcmDspRoutineStopOutSignal//DcmDspRoutineSignalLength Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineStopOut //DcmDspRoutineStopOutSignal//DcmDspRoutineSignalPos Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspRoutineStopOut //DcmDspRoutineStopOutSignal//DcmDspRoutineSignalType Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspStartRoutineIn //DcmDspStartRoutineInSignal//DcmDspRoutineSignalLength Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspStartRoutineIn //DcmDspStartRoutineInSignal//DcmDspRoutineSignalPos Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspStartRoutineIn //DcmDspStartRoutineInSignal//DcmDspRoutineSignalType Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspStartRoutineOu t//dcmdspstartroutineoutsignal//dcmdsproutinesignallength Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspStartRoutineOu t//dcmdspstartroutineoutsignal//dcmdsproutinesignalpos Dcm//DcmConfigSet//DcmDsp//DcmDspRoutineInfo//DcmDspStartRoutineOu t//dcmdspstartroutineoutsignal//dcmdsproutinesignaltype Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityDelayTime rmonitor RTA-BSW v2.1.1 User Guide 54

Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityNRCExceed NoOfAttempt Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritycomparekeyfnc Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritydelaytime Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritydelaytimeonboot Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritygetseedfnc Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritykeysize The default value is 1. Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritykeysize Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritylevel The default value is 1. Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritylevel Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritynumattdelay The default value is 1. Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritynumattdelay Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritynumattlock RTA-BSW v2.1.1 User Guide 55

Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritynumattlock Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecurityseedsize The default value is 1. Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecurityseedsize Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecuritysessionref Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityRow//DcmD spsecurityuseport Dcm//DcmConfigSet//DcmDsp//DcmDspSecurity//DcmDspSecurityStoreSeed Dcm//DcmConfigSet//DcmDsp//DcmDspSesSecUsedInProtocol Dcm//DcmConfigSet//DcmDsp//DcmDspSession//DcmDspSessionRow//DcmDsp SessionForBoot Dcm//DcmConfigSet//DcmDsp//DcmDspSession//DcmDspSessionRow//DcmDsp SessionLevel The default value is 1. Dcm//DcmConfigSet//DcmDsp//DcmDspSession//DcmDspSessionRow//DcmDsp SessionLevel Dcm//DcmConfigSet//DcmDsp//DcmDspSession//DcmDspSessionRow//DcmDsp SessionP2ServerMax Dcm//DcmConfigSet//DcmDsp//DcmDspSession//DcmDspSessionRow//DcmDsp SessionP2ServerMax Dcm//DcmConfigSet//DcmDsp//DcmDspSession//DcmDspSessionRow//DcmDsp SessionP2StarServerMax Dcm//DcmConfigSet//DcmDsp//DcmDspSession//DcmDspSessionRow//DcmDsp SessionP2StarServerMax The default value is 5. RTA-BSW v2.1.1 User Guide 56

Dcm//DcmConfigSet//DcmGeneral//DcmDevErrorDetect Dcm//DcmConfigSet//DcmGeneral//DcmDslP2maxthresholdtime Dcm//DcmConfigSet//DcmGeneral//DcmDspDataDefaultEndianness Dcm//DcmConfigSet//DcmGeneral//DcmOSCounterMacro Dcm//DcmConfigSet//DcmGeneral//DcmOSTimerUse Dcm//DcmConfigSet//DcmGeneral//DcmOSTimerUse Dcm//DcmConfigSet//DcmGeneral//DcmRTEInterface Dcm//DcmConfigSet//DcmGeneral//DcmRTEsupport Dcm//DcmConfigSet//DcmGeneral//DcmRequestManufacturerNotificationE nabled Dcm//DcmConfigSet//DcmGeneral//DcmRequestSupplierNotificationEnabl ed Dcm//DcmConfigSet//DcmGeneral//DcmRespondAllRequest Dcm//DcmConfigSet//DcmGeneral//DcmTaskTime The default value is 10. Dcm//DcmConfigSet//DcmGeneral//DcmTaskTime Dcm//DcmConfigSet//DcmGeneral//DcmVersionInfoApi Dcm//DcmConfigSet//DcmPageBufferCfg//DcmPagedBufferEnabled Dcm//DcmConfigSet//DcmPageBufferCfg//DcmPagedBufferEnabled Dcm//DcmConfigSet//DcmProcessingConditions//DcmModeCondition//DcmC onditiontype RTA-BSW v2.1.1 User Guide 57

Dem Dem//DemGeneral//DemDataElementClass//DemExternalCSDataElementClas s//demdataelementdatasize Dem//DemGeneral//DemDataElementClass//DemExternalCSDataElementClas s//demdataelementreadfnc Dem//DemGeneral//DemDataElementClass//DemExternalCSDataElementClas s//demdataelementuseport Dem//DemGeneral//DemDataElementClass//DemExternalSRDataElementClas s//demdataelementdatasize Dem//DemGeneral//DemDataElementClass//DemInternalDataElementClass/ /DemDataElementDataSize RTA-BSW v2.1.1 User Guide 58

EcuC EcuC//EcucPduCollection//Pdu//MetaDataLength The default value is 4. EcuC//EcucPduCollection//Pdu//PduLength RTA-BSW v2.1.1 User Guide 59

Fee Fee//FeeBlockConfiguration//FeeBlockNumber Fee//FeeBlockConfiguration//FeeBlockSize Fee//FeeBlockConfiguration//FeeDeviceIndex Fee//FeeBlockConfiguration//FeeImmediateData Fee//FeeBlockConfiguration//FeeNumberOfWriteCycles The default value is 1. Fee//FeeGeneral//FeeDevErrorDetect Fee//FeeGeneral//FeeIndex Fee//FeeGeneral//FeePollingMode The default value is TRUE. Fee//FeeGeneral//FeeSetModeSupported The default value is TRUE. Fee//FeeGeneral//FeeVersionInfoApi Fee//FeePublishedInformation//FeeBlockOverhead The default value is 17. Fee//FeePublishedInformation//FeeMaximumBlockingTime The default value is 10. Fee//FeePublishedInformation//FeePageOverhead The default value is 1. RTA-BSW v2.1.1 User Guide 60

Fls Fls//FlsGeneral//FlsAcLoadOnJobStart Fls//FlsGeneral//FlsBaseAddress Fls//FlsGeneral//FlsCancelApi Fls//FlsGeneral//FlsCompareApi Fls//FlsGeneral//FlsDevErrorDetect Fls//FlsGeneral//FlsDriverIndex Fls//FlsGeneral//FlsGetJobResultApi Fls//FlsGeneral//FlsGetStatusApi Fls//FlsGeneral//FlsSetModeApi The default value is TRUE. Fls//FlsGeneral//FlsTotalSize RTA-BSW v2.1.1 User Guide 61

IpduM IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMByteOr der IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMRxDyna micpart//ipdumoutgoingdynamicpduref IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMRxDyna micpart//ipdumrxselectorvalue IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMRxDyna micpart//ipdumsegment//ipdumsegmentlength IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMRxDyna micpart//ipdumsegment//ipdumsegmentposition IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMRxHand leid IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMRxIndi cationpduref IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMRxStat icpart//ipdumoutgoingstaticpduref IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMRxStat icpart//ipdumsegment//ipdumsegmentlength IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMRxStat icpart//ipdumsegment//ipdumsegmentposition IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMSelect orfieldposition IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMSelect orfieldposition//ipdumselectorfieldlength IpduM//IpduMConfig//IpduMRxPathway//IpduMRxIndication//IpduMSelect orfieldposition//ipdumselectorfieldposition IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMByteOrder IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMIPduUnuse dareasdefault RTA-BSW v2.1.1 User Guide 62

IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMInitialDy namicpart IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMOutgoingP duref IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMSelectorF ieldposition IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMSelectorF ieldposition//ipdumselectorfieldlength IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMSelectorF ieldposition//ipdumselectorfieldposition IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMSize IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxConfirm ationpduid IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxConfirm ationtimeout The default value is 1. IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxDynamic Part//IpduMJitUpdate IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxDynamic Part//IpduMSegment//IpduMSegmentLength IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxDynamic Part//IpduMSegment//IpduMSegmentPosition IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxDynamic Part//IpduMTxDynamicConfirmation The default value is TRUE. IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxDynamic Part//IpduMTxDynamicHandleId IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxDynamic Part//IpduMTxDynamicPduRef RTA-BSW v2.1.1 User Guide 63

IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxStaticP art//ipdumjitupdate IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxStaticP art//ipdumsegment//ipdumsegmentlength IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxStaticP art//ipdumsegment//ipdumsegmentposition IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxStaticP art//ipdumtxstaticconfirmation The default value is TRUE. IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxStaticP art//ipdumtxstatichandleid IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxStaticP art//ipdumtxstaticpduref IpduM//IpduMConfig//IpduMTxPathway//IpduMTxRequest//IpduMTxTrigger Mode IpduM//IpduMGeneral//IpduMDevErrorDetect IpduM//IpduMGeneral//IpduMStaticPartExists IpduM//IpduMGeneral//IpduMTimerConfig//IpduMOsTimerUse The default value is CyclicCount. IpduM//IpduMPublishedInformation//IpduMRxDirectComInvocation RTA-BSW v2.1.1 User Guide 64

J1939Dcm J1939Dcm//J1939DcmConfigSet//J1939DcmChannel//J1939DcmBusType J1939Dcm//J1939DcmConfigSet//J1939DcmChannel//J1939DcmBusType The default value is J1939DCM_J1939_NETWORK_1. J1939Dcm//J1939DcmConfigSet//J1939DcmChannel//J1939DcmComMChannelR ef J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmDiagnosticMessa gesupport//j1939dcmdiagnosticmessagesupportchannelref J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmDiagnosticMessa gesupport//j1939dcmdmxsupport J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmDiagnosticMessa gesupport//j1939dcmdmxsupport The default value is "J1939DCM_+name+""_SUPPORT""". J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmDiagnosticMessa gesupport//j1939dcmrxpdu//j1939dcmrxpduid J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmDiagnosticMessa gesupport//j1939dcmrxpdu//j1939dcmrxpduid J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmDiagnosticMessa gesupport//j1939dcmtxpdu//j1939dcmtxpduid J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmDiagnosticMessa gesupport//j1939dcmtxpdu//j1939dcmtxpduid J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmDiagnosticMessa gesupport//j1939dcmtxpdu//j1939dcmtxpduref J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmNmNodeRef J1939Dcm//J1939DcmConfigSet//J1939DcmNode//J1939DcmNodeRmUserRef RTA-BSW v2.1.1 User Guide 65

J1939Dcm//J1939DcmGeneral//J1939DcmCommonBufferSize The default value is 82. The maximum value for this parameter is 1785. J1939/21_201603 - Section 5.10.1.1 - Individual message packets are assigned a sequence number of 1 to 255. This yields a maximum message size of (255 packets * 7 bytes/packet =) 1785 bytes. J1939Dcm//J1939DcmGeneral//J1939DcmDM1BufferSize The default value is 82. J1939Dcm//J1939DcmGeneral//J1939DcmDM1MaxDTCs The default value is 20. J1939Dcm//J1939DcmGeneral//J1939DcmDevErrorDetect J1939Dcm//J1939DcmGeneral//J1939DcmMaxDTCsPerMainFunction The default value is 10. J1939Dcm//J1939DcmGeneral//J1939DcmMaxFreezeFramesPerMainFunction The default value is 10. RTA-BSW v2.1.1 User Guide 66

J1939Nm J1939Nm//J1939NmConfigSet//J1939NmChannel//J1939NmCAMRxPdu//J1939N mcamrxpduid J1939Nm//J1939NmConfigSet//J1939NmChannel//J1939NmCAMTxPdu//J1939N mcamtxpduid J1939Nm//J1939NmConfigSet//J1939NmChannel//J1939NmComMNetworkHandl eref J1939Nm//J1939NmConfigSet//J1939NmChannel//J1939NmNMRxPdu//J1939Nm NMRxPduId J1939Nm//J1939NmConfigSet//J1939NmChannel//J1939NmNMTxPdu//J1939Nm NMTxPduId J1939Nm//J1939NmConfigSet//J1939NmChannel//J1939NmRxPdu//J1939NmRx PduId J1939Nm//J1939NmConfigSet//J1939NmChannel//J1939NmTxPdu//J1939NmTx PduId J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNameManagemenManufa cturercodeallow J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNameManagementECUIn sallow J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNameManagementFunct ionallow J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNameManagementFunct ioninsallow J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNameManagementIdent itynumberallow RTA-BSW v2.1.1 User Guide 67

J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNameManagementIndus trygroupallow J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNameManagementSelfC onfigaddrallow J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNameManagementVehic lesystemallow J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNameManagementVehic lesysteminsallow J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeAddressChangeAl low J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeId J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeId J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeIsExternal J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeIsExternal J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeNameArbitraryAd dresscapable J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeNameECUInstance J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeNameFunction J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeNameFunctionIns tance J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeNameIdentityNum ber J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeNameIndustryGro up J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeNameManufacture rcode J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeNameVehicleSyst em RTA-BSW v2.1.1 User Guide 68

J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeNameVehicleSyst eminstance J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodePreferredAddres s J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeStartUpDelay J1939Nm//J1939NmConfigSet//J1939NmNode//J1939NmNodeVirtualAddress J1939Nm//J1939NmGeneral//J1939NmCAMSupport J1939Nm//J1939NmGeneral//J1939NmClaimedAddressStoringNvMSupport J1939Nm//J1939NmGeneral//J1939NmDevErrorDetect J1939Nm//J1939NmGeneral//J1939NmGeneralNumberofUnknownNameNodes The default value is 10. J1939Nm//J1939NmGeneral//J1939NmNameManagementSupport RTA-BSW v2.1.1 User Guide 69

J1939Rm J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmAckQueueSize J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmAckmRxPdu//J1939 RmAckmRxPduId J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmAckmRxPdu//J1939 RmAckmRxPduId J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmAckmRxPdu//J1939 RmAckmRxPduRef J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmAckmTxPdu//J1939 RmAckmTxPduId J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmAckmTxPdu//J1939 RmAckmTxPduRef J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmComMNetworkHandl eref J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmRequestQueueSize J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmRequestTimeoutMo nitors J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmRqstRxPdu//J1939 RmRqstRxPduId J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmRqstRxPdu//J1939 RmRqstRxPduRef J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmRqstTxPdu//J1939 RmRqstTxPduId J1939Rm//J1939RmConfigSet//J1939RmChannel//J1939RmRqstTxPdu//J1939 RmRqstTxPduRef J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmNmNodeRef J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmNodeChannelRef RTA-BSW v2.1.1 User Guide 70

J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmComIPd u//j1939rmcomipdupgn J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserAc kindication J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserAc kindication J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserAc kpgn J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserId J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserId J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserPG N J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserRe questindication J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserRe questindication J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserSe ndack J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserSe ndack J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserSe ndrequest J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserSe ndrequest J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserTi meoutsupervision J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserTi meoutsupervision J1939Rm//J1939RmConfigSet//J1939RmNode//J1939RmUser//J1939RmUserTy pe RTA-BSW v2.1.1 User Guide 71

J1939Rm//J1939RmGeneral J1939Rm//J1939RmGeneral//J1939RmSupportAckIndication J1939Rm//J1939RmGeneral//J1939RmSupportAckTransmission J1939Rm//J1939RmGeneral//J1939RmSupportRequestIndication J1939Rm//J1939RmGeneral//J1939RmSupportRequestTransmission J1939Rm//J1939RmGeneral//J1939RmSupportTimeoutSupervision J1939Rm//J1939RmGeneral//J1939RmVersionInfoApi RTA-BSW v2.1.1 User Guide 72

J1939Tp J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpETPRxCmNPd u//j1939tpetprxcmnpduid J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpETPRxDtNPd u//j1939tpetprxdtnpduid J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpETPTxFcNPd u//j1939tpetptxfcnpdutxconfid J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxCmNPdu// J1939TpRxCmNPduId J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxCmNPdu// J1939TpRxCmNPduRef J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxDtNPdu// J1939TpRxDtNPduId J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxDtNPdu// J1939TpRxDtNPduRef J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxPg//J193 9TpRxDirectNPdu//J1939TpRxDirectNPduId J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxPg//J193 9TpRxDirectNPdu//J1939TpRxDirectNPduRef J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxPg//J193 9TpRxNSdu//J1939TpRxNSduRef J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxPg//J193 9TpRxPgDynLength J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxPg//J193 9TpRxPgPGN J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxProtocol Type RTA-BSW v2.1.1 User Guide 73

J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpRxSa J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpTxFcNPdu// J1939TpTxFcNPduRef J1939Tp//J1939TpConfiguration//J1939TpRxChannel//J1939TpTxFcNPdu// J1939TpTxFcNPduTxConfId J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpETPRxFcNPd u//j1939tpetprxfcnpduid J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpETPRxFcNPd u//j1939tpetprxfcnpduid J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpETPTxCmNPd u//j1939tpetptxcmnpdutxconfid J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpETPTxCmNPd u//j1939tpetptxcmnpdutxconfid J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpETPTxDtNPd u//j1939tpetptxdtnpdutxconfid J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpRxFcNPdu// J1939TpRxFcNPduId J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpRxFcNPdu// J1939TpRxFcNPduRef J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxCmNPdu// J1939TpTxCmNPduTxConfId J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxDa J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxDtNPdu// J1939TpTxDtNPduRef RTA-BSW v2.1.1 User Guide 74

J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxDtNPdu// J1939TpTxDtNPduTxConfId J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxPg//J193 9TpTxDirectNPdu//J1939TpTxDirectNPduRef J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxPg//J193 9TpTxDirectNPdu//J1939TpTxDirectNPduTxConfId J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxPg//J193 9TpTxNSdu//J1939TpTxNSduId J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxPg//J193 9TpTxNSdu//J1939TpTxNSduRef J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxPg//J193 9TpTxPgDynLength J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxPg//J193 9TpTxPgPGN J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxProtocol Type The default value is "". J1939Tp//J1939TpConfiguration//J1939TpTxChannel//J1939TpTxSa J1939Tp//J1939TpGeneral//J1939TpDevErrorDetect J1939Tp//J1939TpGeneral//J1939TpETPSupport J1939Tp//J1939TpGeneral//J1939TpMaxPacketsPerBlock J1939Tp//J1939TpGeneral//J1939TpPacketsPerBlock RTA-BSW v2.1.1 User Guide 75

Lin Lin//LinGeneral//LinDevErrorDetect Lin//LinGeneral//LinIndex Lin//LinGeneral//LinVersionInfoApi Lin//LinGlobalConfig//LinChannel//LinChannelBaudRate Lin//LinGlobalConfig//LinChannel//LinChannelId Lin//LinGlobalConfig//LinChannel//LinChannelWakeupSupport RTA-BSW v2.1.1 User Guide 76

LinIf LinIf//LinIfGeneral//LinIfCancelTransmitSupported LinIf//LinIfGeneral//LinIfDevErrorDetect LinIf//LinIfGeneral//LinIfMultipleDriversSupported LinIf//LinIfGeneral//LinIfMultipleTrcvDriverSupported LinIf//LinIfGeneral//LinIfNcOptionalRequestSupported LinIf//LinIfGeneral//LinIfTpSupported LinIf//LinIfGeneral//LinIfTrcvDriverSupported LinIf//LinIfGeneral//LinIfVersionInfoApi LinIf//LinIfGlobalConfig//LinIfChannel//LinIfChannelId LinIf//LinIfGlobalConfig//LinIfChannel//LinIfFrame//LinIfChecksumT ype LinIf//LinIfGlobalConfig//LinIfChannel//LinIfFrame//LinIfFrameType LinIf//LinIfGlobalConfig//LinIfChannel//LinIfFrame//LinIfLength LinIf//LinIfGlobalConfig//LinIfChannel//LinIfFrame//LinIfPduDirect ion//linifrxpdu//linifuserrxindicationul LinIf//LinIfGlobalConfig//LinIfChannel//LinIfFrame//LinIfPduDirect ion//liniftxpdu//liniftxpduid LinIf//LinIfGlobalConfig//LinIfChannel//LinIfFrame//LinIfPduDirect ion//liniftxpdu//linifusertxul RTA-BSW v2.1.1 User Guide 77

LinIf//LinIfGlobalConfig//LinIfChannel//LinIfFrame//LinIfPid LinIf//LinIfGlobalConfig//LinIfChannel//LinIfGotoSleepConfirmation UL The default value is LIN_SM. LinIf//LinIfGlobalConfig//LinIfChannel//LinIfMaster//LinIfClusterT imebase LinIf//LinIfGlobalConfig//LinIfChannel//LinIfMaster//LinIfJitter LinIf//LinIfGlobalConfig//LinIfChannel//LinIfScheduleRequestConfir mationul The default value is LIN_SM. LinIf//LinIfGlobalConfig//LinIfChannel//LinIfScheduleTable//LinIfE ntry//linifdelay LinIf//LinIfGlobalConfig//LinIfChannel//LinIfScheduleTable//LinIfE ntry//linifentryindex LinIf//LinIfGlobalConfig//LinIfChannel//LinIfScheduleTable//LinIfR esumeposition LinIf//LinIfGlobalConfig//LinIfChannel//LinIfScheduleTable//LinIfR unmode LinIf//LinIfGlobalConfig//LinIfChannel//LinIfScheduleTable//LinIfS cheduletableindex LinIf//LinIfGlobalConfig//LinIfChannel//LinIfSlave//LinIfConfigure dnad LinIf//LinIfGlobalConfig//LinIfChannel//LinIfSlave//LinIfFunctionI d LinIf//LinIfGlobalConfig//LinIfChannel//LinIfSlave//LinIfProtocolV ersion LinIf//LinIfGlobalConfig//LinIfChannel//LinIfSlave//LinIfSupplierI d LinIf//LinIfGlobalConfig//LinIfChannel//LinIfSlave//LinIfVariant RTA-BSW v2.1.1 User Guide 78

LinIf//LinIfGlobalConfig//LinIfChannel//LinIfStartupState The default value is NORMAL. LinIf//LinIfGlobalConfig//LinIfChannel//LinIfTransceiverDrvConfig/ /LinIfTrcvWakeupNotification LinIf//LinIfGlobalConfig//LinIfChannel//LinIfWakeupConfirmationUL The default value is LIN_SM. LinIf//LinIfGlobalConfig//LinIfChannel//LinSleepFrameDelay 01. LinIf//LinIfGlobalConfig//LinIfChannel//LinTpScheduleChangeDiag RTA-BSW v2.1.1 User Guide 79

LinSM LinSM//LinSMChannel//LinSMSchedule//LinSMScheduleIndex LinSM//LinSMChannel//LinSMSleepSupport LinSM//LinSMChannel//LinSMTransceiverPassiveMode LinSM//LinSMChannel//LinSmNetworkIndex LinSM//LinSMGeneral//LinSMDevErrorDetect LinSM//LinSMGeneral//LinSMVersionInfoApi RTA-BSW v2.1.1 User Guide 80

MemIf MemIf//MemIfGeneral//MemIfDevErrorDetect MemIf//MemIfGeneral//MemIfNumberOfDevices The default value is 1. MemIf//MemIfGeneral//MemIfRbFeeUsed The default value is TRUE. RTA-BSW v2.1.1 User Guide 81

Nm Nm//NmChannelConfig The default value is PASSIVE. Nm//NmChannelConfig//NmBusType//NmStandardBusNmConfig//NmStandardB ustype Nm//NmChannelConfig//NmChannelId Nm//NmChannelConfig//NmChannelSleepMaster Nm//NmChannelConfig//NmComMChannelRef Nm//NmChannelConfig//NmShutdownDelayTimer The default value is 600. Nm//NmChannelConfig//NmStateReportEnabled Nm//NmChannelConfig//NmSynchronizingNetwork Nm//NmGlobalConfig//NmGlobalConstants//NmMultipleChannelsEnabled Nm//NmGlobalConfig//NmGlobalConstants//NmNumberOfChannels Nm//NmGlobalConfig//NmGlobalConstants//NmRemoteSleepCancelCallback Nm//NmGlobalConfig//NmGlobalConstants//NmRemoteSleepIndCallback Nm//NmGlobalConfig//NmGlobalConstants//NmRxCallbackHeader The default value is "". Nm//NmGlobalConfig//NmGlobalConstants//NmRxIndicationCallback The default value is "". Nm//NmGlobalConfig//NmGlobalConstants//NmStateChangeIndCallback The default value is "". Nm//NmGlobalConfig//NmGlobalFeatures//NmBusSynchronizationEnabled RTA-BSW v2.1.1 User Guide 82

Nm//NmGlobalConfig//NmGlobalFeatures//NmComControlEnabled Nm//NmGlobalConfig//NmGlobalFeatures//NmComUserDataSupport Nm//NmGlobalConfig//NmGlobalFeatures//NmCoordinatorSupportEnabled Nm//NmGlobalConfig//NmGlobalFeatures//NmNodeDetectionEnabled Nm//NmGlobalConfig//NmGlobalFeatures//NmNodeIdEnabled Nm//NmGlobalConfig//NmGlobalFeatures//NmPassiveModeEnabled Nm//NmGlobalConfig//NmGlobalFeatures//NmPduRxIndicationEnabled Nm//NmGlobalConfig//NmGlobalFeatures//NmRemoteSleepIndEnabled Nm//NmGlobalConfig//NmGlobalFeatures//NmRepeatMsgIndEnabled Nm//NmGlobalConfig//NmGlobalFeatures//NmStateChangeIndEnabled Nm//NmGlobalConfig//NmGlobalFeatures//NmUserDataEnabled Nm//NmGlobalConfig//NmGlobalProperties//NmCycletimeMainFunction Nm//NmGlobalConfig//NmGlobalProperties//NmDevErrorDetect RTA-BSW v2.1.1 User Guide 83

NvM NvM//NvMBlockDescriptor//NvMBlockCrcType The default value is NVM_CRC16. NvM//NvMBlockDescriptor//NvMBlockJobPriority NvM//NvMBlockDescriptor//NvMBlockJobPriority The default value is 1. NvM//NvMBlockDescriptor//NvMBlockJobPriority The default value is 1. NvM//NvMBlockDescriptor//NvMBlockManagementType The default value is NVM_BLOCK_NATIVE. NvM//NvMBlockDescriptor//NvMBlockUseCrc The default value is TRUE. NvM//NvMBlockDescriptor//NvMBlockUseSyncMechanism NvM//NvMBlockDescriptor//NvMBlockWriteProt NvM//NvMBlockDescriptor//NvMBlockWriteProt NvM//NvMBlockDescriptor//NvMCalcRamBlockCrc NvM//NvMBlockDescriptor//NvMInitBlockCallback The default value is NULL_PTR. NvM//NvMBlockDescriptor//NvMMaxNumOfReadRetries NvM//NvMBlockDescriptor//NvMMaxNumOfWriteRetries RTA-BSW v2.1.1 User Guide 84

NvM//NvMBlockDescriptor//NvMNvBlockLength NvM//NvMBlockDescriptor//NvMNvBlockLength The default value is 1. NvM//NvMBlockDescriptor//NvMNvBlockNum The default value is 1. NvM//NvMBlockDescriptor//NvMNvramDeviceId NvM//NvMBlockDescriptor//NvMRamBlockDataAddress NvM//NvMBlockDescriptor//NvMRamBlockDataAddress The default value is null. NvM//NvMBlockDescriptor//NvMRbBlockPersistentId The default value is null. NvM//NvMBlockDescriptor//NvMRbGenRteAdminPort The default value is null. NvM//NvMBlockDescriptor//NvMRbGenRteServicePort The default value is null. NvM//NvMBlockDescriptor//NvMRbResistantToLayoutRemoval The default value is null. NvM//NvMBlockDescriptor//NvMReadRamBlockFromNvCallback The default value is null. NvM//NvMBlockDescriptor//NvMResistantToChangedSw NvM//NvMBlockDescriptor//NvMResistantToChangedSw RTA-BSW v2.1.1 User Guide 85

The default value is null. NvM//NvMBlockDescriptor//NvMResistantToChangedSw NvM//NvMBlockDescriptor//NvMRomBlockDataAddress The default value is null. NvM//NvMBlockDescriptor//NvMRomBlockNum NvM//NvMBlockDescriptor//NvMSelectBlockForReadAll NvM//NvMBlockDescriptor//NvMSelectBlockForReadAll The default value is null. NvM//NvMBlockDescriptor//NvMSelectBlockForWriteAll NvM//NvMBlockDescriptor//NvMSelectBlockForWriteAll The default value is TRUE. NvM//NvMBlockDescriptor//NvMSingleBlockCallback The default value is null. NvM//NvMBlockDescriptor//NvMStaticBlockIDCheck NvM//NvMBlockDescriptor//NvMWriteBlockOnce NvM//NvMBlockDescriptor//NvMWriteBlockOnce NvM//NvMBlockDescriptor//NvMWriteVerification NvM//NvMBlockDescriptor//NvMWriteVerification RTA-BSW v2.1.1 User Guide 86

NvM//NvMBlockDescriptor//NvMWriteVerificationDataSize NvM//NvMCommon//NvMApiConfigClass The default value is NVM_API_CONFIG_CLASS_3. NvM//NvMCommon//NvMBswMMultiBlockJobStatusInformation The default value is TRUE. NvM//NvMCommon//NvMCompiledConfigId NvM//NvMCommon//NvMCrcNumOfBytes The default value is 1. NvM//NvMCommon//NvMDevErrorDetect The default value is TRUE. NvM//NvMCommon//NvMDrvModeSwitch NvM//NvMCommon//NvMDynamicConfiguration NvM//NvMCommon//NvMJobPrioritization NvM//NvMCommon//NvMMultiBlockCallback The default value is NULL_PTR. NvM//NvMCommon//NvMPollingMode The default value is TRUE. RTA-BSW v2.1.1 User Guide 87

NvM//NvMCommon//NvMSetRamBlockStatusApi The default value is TRUE. NvM//NvMCommon//NvMSizeStandardJobQueue The default value is 1. RTA-BSW v2.1.1 User Guide 88

Options Options//CanIfFormat RTA-BSW v2.1.1 User Guide 89

PduR PduR//PduRBswModules//PduRBswModuleRef PduR//PduRBswModules//PduRCancelReceive PduR//PduRBswModules//PduRCancelTransmit PduR//PduRBswModules//PduRChangeParameterRequestApi PduR//PduRBswModules//PduRCommunicationInterface PduR//PduRBswModules//PduRLowerModule PduR//PduRBswModules//PduRRetransmission PduR//PduRBswModules//PduRTransportProtocol PduR//PduRBswModules//PduRTriggertransmit PduR//PduRBswModules//PduRTxConfirmation PduR//PduRBswModules//PduRUpperModule PduR//PduRBswModules//PduRUseTag PduR//PduRGeneral//PduRCanTpChangeParameterRequestApi PduR//PduRGeneral//PduRDevErrorDetect The default value is TRUE. PduR//PduRGeneral//PduRFifoTxBufferSupport PduR//PduRGeneral//PduRIFGatewayOperation PduR//PduRGeneral//PduRMemorySize RTA-BSW v2.1.1 User Guide 90

PduR//PduRGeneral//PduRMinimumRoutingLoRxPduId PduR//PduRGeneral//PduRMinimumRoutingLoTxPduId PduR//PduRGeneral//PduRMinimumRoutingUpRxPduId PduR//PduRGeneral//PduRMinimumRoutingUpTxPduId PduR//PduRGeneral//PduRMulticastFromIfSupport PduR//PduRGeneral//PduRMulticastToIfSupport PduR//PduRGeneral//PduRMulticastToTpSupport PduR//PduRGeneral//PduRSbTxBufferSupport PduR//PduRGeneral//PduRTPGatewayOperation PduR//PduRGeneral//PduRVersionInfoApi PduR//PduRGeneral//PduRZeroCostOperation RTA-BSW v2.1.1 User Guide 91

PduR//PduRRoutingTables//PduRConfigurationId PduR//PduRRoutingTables//PduRRoutingTable//PduRRoutingPath//PduRDe stpdu//pdurdefaultvalue PduR//PduRRoutingTables//PduRRoutingTable//PduRRoutingPath//PduRDe stpdu//pdurdestpduhandleid PduR//PduRRoutingTables//PduRRoutingTable//PduRRoutingPath//PduRDe stpdu//pdurdesttxbufferref PduR//PduRRoutingTables//PduRRoutingTable//PduRRoutingPath//PduRDe stpdu//pdurtransmissionconfirmation PduR//PduRRoutingTables//PduRRoutingTable//PduRRoutingPath//PduRSr cpdu//pdursourcepduhandleid RTA-BSW v2.1.1 User Guide 92

4.5.3 Can Mailbox Mapping Some hardware requires that the Can Mailboxes are presented in a particular order. This can be supported by setting a mailbox mapping rule in the algo.properties file. If specified the mailboxes will be ordered alphabetically according to the following rule with a comma-separated list of sorting criteria: MbSortingPref=criteria1, criteria2, The criteria can be one of: canhandletype canaddressingmode direction controllername mask The ordering for a criteria will be reversed by appending the optional ~rev the desired criteria. For example: MbSortingPref=direction,controllerName~rev,canHandleType Note: if a criteria is specified to be sorted both forwards and reversed then the behavior is undefined. 4.5.4 Can Controller Mailbox Assignment The number of mailboxes assigned to a Can Controller may be configured in the algo.properties file using the following rule: NumberofMB_{SHORT-NAME}={max_mailboxes} Where SHORT-NAME is the short name of the Can Controller being configured. If this rule is not specified then there is no limit to the number of mailboxes that can be assigned to a controller. One mailbox will be assigned for each frame if possible. Should there be more frames than the mailbox limit then the following steps will be performed in order until the limit is no longer exceeded. o o o All Standard RX messages are combined into one Mailbox, all Extended RX messages are combined into one Mailbox, all Tx messages with a period less than property PduTimingLimit will get a dedicated Mailbox If either the remaining number of Standard or Extended messages are smaller than ½ the remaining mailboxes then these are assigned one Mailbox each and the other messages packed. If there are more Standard and Extended messages than ½ of the remaining Mailboxes then the Standard Mailboxes are packed into ½ the remaining Mailboxes and the Extended in the remaining half. RTA-BSW v2.1.1 User Guide 93

4.6. BSW Code Generation CodeGen, the RTA-BSW Code Generation tool takes a BSW configuration and generates source code from it. There are two ways to activate CodeGen: Clicking the toolbar icon,, which will run an existing configuration, or create a default if one cannot be found. Creating a new run configuration (see Screenshot 5). This gives you the ability to configure the code generation process. In the second case, click the arrow next to the play button and select RUN CONFIGURATIONS Screenshot 5: RTA-BSW Run Configuration menu This will open the run configuration menu (Screenshot 6), the sections of this GUI are as follows (numbers marked in red on Screenshot 6): 1. List of run configuration instances: each item listed here is a configuration; you could have a run configuration per project, or create custom configurations for different use cases. (e.g. Validate only and only run the Com module) 2. Select RTA-BSW: presents a list of installed RTA-BSW versions and prompts for a selection, this will control the available modules (5) as long as a valid project is selected. 3. Select Project: prompts for a selection of a workspace project. If this is a valid AUTOSAR project and an RTA-BSW version has been selected, then the list of modules (5) will be populated with available modules. 4. Select Output Path: by default the path will be set to {ProjectPath}/src/BSW/Gen, but can be set to any directory, the process will then organise the generated files by module in the selected directory 5. Module List: this contains the list of available modules for generation/validation. This is populated by seeing which modules have been configured in the selected project and comparing that to the available modules in the selected RTA-BSW. You can then turn a module or stack on/off by clicking the check button. Note: unlicensed stacks will be greyed out. 6. Miscellaneous Options: contains other options for controlling the process such as turning code generation off (validate only) or instruct the process to not produce SWCD ARXML (to avoid overwriting manual configuration) RTA-BSW v2.1.1 User Guide 94

Screenshot 6: Run Configuration options As CodeGen runs, it places the source code (.c/.h) implementation of the AUTOSAR BSW system configured by the above process into the specified output directory. RTA-BSW v2.1.1 User Guide 95