Glossary
This chapter collects every term that appears across the PAIO documentation in one place. It covers both AUTOSAR standard terms and PAIO-specific terms, and for each one it records which PAIO screen and which file the term corresponds to.
How to Read This Glossary
- Each table has three columns: term, meaning, and where you see it in PAIO. Follow the link in the third column to reach the document that actually covers the term.
- Bold text in the first column is the headword. Bold text in the meaning and location columns is
an English label that appears in the UI, and it is never translated.
Backticksmark file paths, extensions, key names, enumeration values, and shortcuts. - AUTOSAR element names use the upper-case spelling that appears in ARXML (
ECU-INSTANCE). - Items that appear in the UI but do not actually work are marked as such.
- If this is your first read, start with 19.1; the remaining sections are easier to follow afterwards. Look up 19.2 through 19.7 as you need them.
19.1 PAIO-Specific Terms
Concepts that PAIO defines on its own. They do not exist in the AUTOSAR standard.
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| IO Model | PAIO's primary data model. It is format-neutral, human-readable JSON. ARXML and DBC are conversion layers on top of it, not the original | Every model file under design/ · 01. Product Overview, 04. Workspaces and Projects |
| IO-First | PAIO's design principle that the IO Model, not AUTOSAR, is the source of truth. As a result, information that AUTOSAR cannot express still survives in the model | 01. Product Overview |
| Workspace | The parent folder that holds projects. The application opens one workspace at a time. Each workspace keeps its application data separate and takes a single-instance lock | Project ▸ Open Workspace... (Ctrl+O), sidebar title EXPLORER: <folder name> · 04. Workspaces and Projects |
| Project | One set of design deliverables. It consists of a project metadata file and six fixed folders. A single workspace can hold several projects, and you can edit them at the same time | The project node in the Explorer · 04. Workspaces and Projects |
| Fixed Folder | One of the six folders that are always created with a project and can be neither renamed nor deleted — doc, design, code, workflow, export, import | The child nodes of the project in the Explorer · 04. Workspaces and Projects |
| design tree (model tree) | The way the design folder is presented — not as a file list, but as a semantic tree (System ▸ IVC/VFB/Interface/DataType/Signal, Module ▸ Definition/Configuration) | The design node in the Explorer · 04. Workspaces and Projects |
| edit history (History panel) | A single timeline that manages undo, redo, modified state, and saving for the whole project. Editors do not keep separate undo stacks, so Edit ▸ Undo reverts an edit made in any editor | The History tab in the bottom utility panel · 04.9, 05. UI Layout and Navigation |
| active project scope | The rule that, when several projects are open, undo, redo, Save All, and History apply only to the project that owns the active tab. When the application exits, however, it saves every project | Edit ▸ Undo, Project ▸ Save All · 04. Workspaces and Projects |
| editor tab | The unit that opens one model node or one file. The title has the form <project>:<node>, and at most 20 tabs can be open at once | The top of the editor area · 05. UI Layout and Navigation |
| editor group / split view | A split pane created by dragging a tab to the edge of the editor area | The editor area · 05. UI Layout and Navigation |
| dirty marker (●) | The dot attached to a tab that has unsaved changes. It is derived from entries in the edit history, so a change that leaves no entry is not marked | Next to the tab title · 05. UI Layout and Navigation |
| license lock | The gate that turns write, generate, delete, and export permissions on and off according to license state. Read and import are allowed in every state. The default is locked (read-only), and it opens after sign-in and license validation | The upgrade dialog that appears when an action is blocked · 03. Installation, Login and License |
| ECU Extract / Machine Extract | The feature that produces a partial ARXML containing one node (an ECU or an HPC) and only what that node references. It cleans up the result so that no remaining element holds a dangling reference | Right-click an IVC node ▸ Extract ECU / Extract Machine; the result goes to export/<node name>/ · 13. Import and Export |
| QuickStart workflow | The feature that generates the whole project model step by step with AI, once you pick a domain template (24 templates across 7 domains) and fill in the variables | Project ▸ Quick Start ▸ Template Gallery · 15. AI Assistant |
| PARA Base Set | The bundle that injects the PopcornSAR AP base configuration (service interfaces, data types, platform Adaptive Applications, the PARA composition, and machine content) into a project. It runs through the same merge pipeline as an ARXML import | The PARA Platform button in the Machine Configuration dialog, command palette PARA: Import Platform · 08. VFB Editor |
| CP-SOA | The computation that derives signals, PDUs, and interfaces from service definitions so that SOME/IP service communication can be used on the Classic Platform. The derived result is stored in the model files, and only an origin marker (the SOC badge) is attached separately. Because the badge is only a marker, derived items can also be renamed, edited, and deleted | Command palette Derive Signal (CP-SOA) · 05.6, the ⟳ in SOA DEPLOYMENT of the Interface editor · 09.4.1, the SOC badge in the Signal list · 07.3 |
| DEST catalog | The correspondence table that records which IO Model element the DESTINATION-TYPE of an ECUC Foreign or Instance Reference (an AUTOSAR meta-type string) points to. It sorts 62 meta-types into three grades: candidates provided, name synthesized, and opaque | Entering a reference value in the Module Configuration editor · 12.3 |
| Conflict Resolution | The procedure for choosing, item by item, between Keep Project Version, Use Imported Version, Merge Fields, and Keep Both when an imported element holds a different value from an existing one. Items you leave undecided are overwritten with the imported value | The Conflict Resolution dialog that appears during import · 13.2.5 |
| Import Source Conflicts | A separate screen that appears when several import files selected at once define the same element differently. You pick a reference file and overwrite field by field | The Import Source Conflicts dialog · 13.2 |
paio_* rules | PAIO's own validation rules, which catch practical errors that the AUTOSAR standard constraints do not cover (for example paio_ref_dangling, paio_someip_service_id_unique) | The Constr column of the VALIDATION panel · 14. Validation |
.vfb.layout | A file that holds only the layout information of the VFB canvas (positions, sizes, viewport). It is kept separate from the model data | design/SWC/Layout/<composition>.vfb.layout · 08. VFB Editor |
| IVC | In-Vehicle Communication. PAIO's abbreviation for the in-vehicle communication topology, and also the name of the editor | design ▸ System ▸ IVC · 06. IVC Editor |
19.2 AUTOSAR Common
Terms that appear throughout ARXML, regardless of platform.
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| ARXML | AUTOSAR's XML exchange format. PAIO supports it in both directions, import and export | Right-click the project ▸ Import / Export; the result goes to export/ · 13. Import and Export |
| AR-PACKAGE | The package that holds elements inside an ARXML (the equivalent of a folder). An element's absolute path is built from it. The IO Model has no AR-PACKAGE concept, so PAIO strips packages on import and rebuilds them by rule on export | The exported ARXML · 13.3.5 |
| SHORT-NAME | The identifier of an AUTOSAR element. The first character must be a letter, the rest may be letters, digits, or underscores, and the maximum length is 128 characters. PAIO does not apply a name that breaks the rule to the model (the field only shows an error and keeps the previous value) | The Name field in every editor · 06.12, 12.6.1 |
| DESC | The descriptive text of an element. PAIO's Description field maps to it | The Description field in each editor |
| ADMIN-DATA | The administrative information block attached to an element. PAIO carries an SDG here to record tool-specific information | The exported ARXML |
| SDG (Special Data Group) | The extension slot that AUTOSAR allows. PAIO records ownership relationships that no standard element can express — for example which ECU an ECUC configuration belongs to (IO-ECUC-CONFIG-TO-ECU-MAPPING), and which Machine a composition is mapped to (IO-SWC-TO-MACHINE-MAPPING) | The exported ARXML · 12.5, 13.3.6 |
| ECU-INSTANCE | The electronic control unit element of the Classic Platform. PAIO's ECU node is exported as this | The ECU node on the IVC canvas · 06.1 |
| MACHINE-DESIGN | The element that holds the network side of an Adaptive Platform machine (connectors, addresses, and so on). PAIO's HPC node is exported as this | The HPC node on the IVC canvas · 06.1 |
| SYSTEM | The top-level element that ties the whole system together. It holds FIBEX-ELEMENTS (the list of constituent elements), MAPPINGS, and ROOT-SOFTWARE-COMPOSITIONS | System Information on the System editor · 11. System Editor |
| FibexElement | The collective name for the communication-related elements that the FIBEX-ELEMENTS list of SYSTEM must reference. Clusters, frames, PDUs, signals, ECU-INSTANCEs, and TP configurations all qualify | The exported <Project>_System.arxml · 13.3 |
| CATEGORY | A free-form string that states the kind of an element. For SYSTEM, PAIO writes one of SYSTEM_DESIGN_DESCRIPTION (the whole system), ECU_EXTRACT (an ECU extract), or MACHINE_DESIGN_EXTRACT (a Machine extract) | The ARXML produced by export and by Extract · 13.4 |
| DEST | An attribute on a reference (*-REF) tag that states the element kind of the target | The exported ARXML, and reference editing in ECUC · 12.3 |
| XSD (schema) | The XML schema that defines the structure of ARXML. PAIO bundles R25-11 (AUTOSAR_00054.xsd) and R20-11 (AUTOSAR_00049.xsd) | The exported ARXML · 13. Import and Export |
| R25-11 | The AUTOSAR schema release that PAIO always outputs. Every export uses this namespace | The header of the exported ARXML · 02.5 |
| AUTOSAR feature version | A separate axis handled by the conversion layer, ranging from 4.3 to 4.7 (default 4.7). It is independent of the schema release above | Not exposed in the UI · 02.5 |
| Classic Platform (CP) | The traditional AUTOSAR platform based on ECUs, BSW, and the RTE | The ECU node in IVC, the ECUC editor · 01.5 |
| Adaptive Platform (AP) | The POSIX-based AUTOSAR platform for high-performance computing | The HPC node in IVC, the Machine Configuration dialog · 01.5 |
| constr_xxxx | A constraint number assigned by the AUTOSAR specification. Many PAIO validation rules use the number as-is | The Constr column of the VALIDATION panel · 14.4 |
19.3 Communication
The area covered by the IVC editor and the Signal editor.
Topology
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| Communication Cluster | The logical bus that nodes using the same protocol attach to. There are three kinds: CAN, Ethernet, and LIN | The cluster node on the IVC canvas · 06.4.1 |
| Physical Channel | A physical channel inside a cluster. It holds which connectors are attached, and an Ethernet channel carries a VLAN ID. You edit it in the properties panel, not in the Cluster Configuration dialog | The Physical Channels section of the properties panel when a cluster is selected · 06.8.5 |
| Connector | The attachment point where a node (an ECU or an HPC) joins a channel. There is one kind per protocol — Ethernet, CAN, and LIN — and each connector references one controller | Right-click an IVC node ▸ Add Connector · 06.4.2 |
| Communication Controller | The element that corresponds to a node's communication hardware. There are four kinds: ethernet, can, lin-master, and lin-slave | Right-click an IVC node ▸ Add Controller · 06.4.2 |
| Coupling Element | The element that represents an Ethernet switch, hub, or router. The kinds are switch, hub, and router | Right-click empty IVC canvas ▸ Add Ethernet Switch · 06.4.1 |
| Coupling Port | A port on a switch, or a port owned by an Ethernet controller. Joining two ports corresponds to a physical cable | Right-click a switch ▸ Add CouplingPort · 06.4.3, right-click a port ▸ Connect to Port... · 06.5.4 |
| Network Endpoint | The IP-layer configuration of an Ethernet connector (IPv4/IPv6 address, netmask, gateway, DNS, TTL, and so on) | The Network Endpoint section of the properties panel when a connector is selected · 06.8.2 |
| Application Endpoint | The definition of a single TCP or UDP port. Service instances communicate through this port | The Application Endpoints section of the properties panel, which appears only when an Ethernet connector is selected (it does not appear for a Coupling Port) · 06.8.2 |
| Service Instance | The mapping that ties together which service this node provides (provider) or consumes (consumer) and which port it uses. It references an instance defined in the Interface editor | The Service Instances section of the properties panel when an Ethernet connector is selected · 06.8.2, 09.4.2 |
| PLCA | The physical-layer collision avoidance configuration of 10BASE-T1S Ethernet. It only displays imported values and offers no way to edit them | The PLCA (10BASE-T1S) section of the properties panel when a port-to-port connection line is selected · 06.8.4 |
Frames, PDUs, and Signals
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| Frame | The physical transmission unit that travels on the bus. PAIO models four kinds — CAN, LIN, FlexRay, and Ethernet — but provides only two editing tabs, CAN and LIN | The CAN and LIN tabs of the Signal editor · 07.2 |
| DLC | The data length code of a CAN frame. There are 16 selectable values, from 0 (0 bytes) to 15 (64 bytes); 9 through 15 denote the CAN FD extended lengths (12/16/20/24/32/48/64 bytes) | The DLC field of a CAN frame · 07.7.1 |
| CAN Addressing | standard (an 11-bit ID) and extended (a 29-bit ID) | The Addressing field of a CAN frame · 07.7.1 |
| LIN Frame Type | unconditional, event-triggered, or sporadic. The latter two reference another unconditional frame | The Frame Type field of a LIN frame · 07.7.2 |
| LIN Checksum | classic or enhanced | The Checksum field of a LIN frame · 07.7.2 |
| PDU (Protocol Data Unit) | The protocol data unit carried inside a frame. PAIO distinguishes six kinds | The PDU tab of the Signal editor · 07.5 |
| I-Signal I-PDU | The most common PDU, which carries signals and is sent periodically. It has a length, a cycle time, and signal mappings | PDU tab ▸ + ▸ I-Signal I-PDU · 07.5 |
| Multiplexed I-PDU | A PDU whose internal layout changes according to a selector value. It is split into a STATIC part that is always present and a DYNAMIC part that switches | PDU tab ▸ + ▸ Multiplexed I-PDU · 07.5 |
| NM-PDU | A PDU dedicated to network management. NM nodes reference it as a transmit or receive target | PDU tab ▸ + ▸ NM-PDU · 07.5 |
| N-PDU | The segment-carrying PDU used by the transport protocol layer. A CanTp or LinTp connection references it as a data PDU or a flow control PDU | PDU tab ▸ + ▸ N-PDU · 07.5 |
| DCM-I-PDU | The PDU that carries diagnostic (Dcm) data. The transport protocol layer segments and carries it | PDU tab ▸ + ▸ DCM-I-PDU · 07.5 |
| General Purpose PDU | A general-purpose PDU whose use is distinguished by CATEGORY. The SOME/IP service discovery PDU is one of these | PDU tab ▸ + ▸ General Purpose PDU · 07.5 |
| I-Signal | The communication-layer identity of a signal placed inside a PDU. The Name in the Signal editor is this name | The SIGNAL tab of the Signal editor · 07.7.7 |
| System Signal | The system-layer identity of the same signal. One logical signal is exported with both names, the I-Signal name and the System Signal name. Data mappings reference the System Signal | systemSignalName in the Signal model · 07.7.7, 11.8 |
| Signal Group | A logical bundle of signals that must be handled together. Members are recorded by System Signal name | The GROUP column of the Signals grid · 07.9 |
| Text Table | The enumeration table that ties a signal value to a display label. When this table exists, the initial value field becomes a combo box. In the current version it is read-only and cannot be changed in the editor — entries are created only by an ARXML or DBC import | The Text Table (N entries) section of the Configuration panel · 07.12 |
| Factor / Offset | The coefficients that convert a raw value into a physical value: physical value = raw value × Factor + Offset | The FACTOR and OFFSET columns of the Signals grid · 07.9 |
| Byte Order | The byte order: big-endian (most significant byte first) or little-endian | The BYTE-ORDER column of the Signals grid · 07.9 |
| Update Bit | The position of a separate bit that signals that the signal has been updated | The UPDATE-BIT column of the Signals grid · 07.9 |
| bit layout (Preview) | The picture that shows the bit arrangement inside a PDU or frame in color. Overlapping bits are shown in the error color | The Preview area of the Signal editor · 07.10 |
Network Services
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| NM (Network Management) | The network management that coordinates sleep and wakeup on the bus. PAIO covers CAN NM and UDP NM | Node Configuration ▸ NETWORK MANAGEMENT tab, Cluster Configuration ▸ CAN NM CLUSTER / UDP NM CLUSTER tabs · 06.7.3, 06.7.4 |
| NM Cluster | The set of nodes that share the same NM rules. It holds the cluster-level NM parameters | The NM tabs of Cluster Configuration · 06.7.4 |
| NM Node | The element that attaches one ECU to one NM Cluster | Node Configuration ▸ NETWORK MANAGEMENT tab · 06.7.3 |
| NM Coordinator | The role that coordinates sleep across several NM clusters. Each channel carries ACTIVE, PASSIVE, or NONE | The NM coordinator diagram in Node Configuration · 06.7.3 |
| Transport Protocol (TP) | The layer that splits data too large for a single frame and sends it in pieces. PAIO covers CanTp and LinTp | Cluster Configuration ▸ TRANSPORT PROTOCOL tab · 06.7.4 |
| Addressing Format | The ISO 15765-2 addressing mode of a CanTp connection — STANDARD / EXTENDED / MIXED / MIXED29BIT / NORMALFIXED | The TRANSPORT PROTOCOL tab · 06.7.4 |
| Target Address Type | PHYSICAL (one to one) or FUNCTIONAL (one to many) | The TRANSPORT PROTOCOL tab · 06.7.4 |
| Global Time | Time synchronization between nodes. Ethernet uses IEEE 802.1AS (gPTP); CAN uses an AUTOSAR-specific method | Node Configuration / Cluster Configuration ▸ TIME DOMAIN tab · 06.7.3, 06.7.4 |
| Time Domain | One synchronization domain. It carries master, slave, and gateway roles and a CRC policy | The TIME DOMAIN tab · 06.7.4 |
| SOME/IP | The service-oriented communication protocol of the Adaptive Platform. Its deployment information holds the service ID and an identifier for each event, method, and field | Interface editor ▸ SOME/IP Deployment · 09.3 |
| DDS | Another service-oriented communication middleware. Its deployment information holds the topic name, the service ID, and so on | Interface editor ▸ DDS Deployment · 09.3 |
TSN Ethernet Switch
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| VLAN | The virtual LAN that divides one physical Ethernet logically. Each channel carries a VLAN ID, and each port sets its transmission mode (TAGGED / UNTAGGED / NOT SENT) | Switch Configuration ▸ VLAN Membership panel · 06.7.5 |
| PCP (Priority Code Point) | The priority value from 0 to 7 carried in the VLAN tag | The PRIORITY REGENERATION stage of the port pipeline · 06.7.5 |
| Priority Regeneration | The mapping that rewrites the PCP of a received frame to a different value | The PRIORITY REGENERATION stage of the port pipeline · 06.7.5 |
| Traffic Class | The grade of the transmit queue that a group of PCP values is assigned to | The TRAFFIC CLASS ASSIGNMENT stage of the port pipeline · 06.7.5 |
| FIFO | The transmit queue responsible for one traffic class. You can attach a shaper to it | The FIFO nodes in the EGRESS queue graph · 06.7.5 |
| CBS (Credit-Based Shaper) | The credit-based shaper of IEEE 802.1Qav. It carries idleSlope (the credit increase per second) | Right-click a FIFO ▸ Attach Shaper: CBS · 06.7.5 |
| ETS (Enhanced Transmission Selection) | The bandwidth-allocating shaper and scheduler of IEEE 802.1Qaz. Weights are given as a percentage or as a weight value | Right-click a FIFO ▸ Attach Shaper: ETS, and the ETS scheduler kind · 06.7.5 |
| ATS (Asynchronous Traffic Shaper) | The shaper of IEEE 802.1Qcr. The model and import support it, but you cannot create one from the UI (switch-level TSN settings replace it). Imported values are displayed and preserved | Shown as ATS in the port pipeline · 06.7.5 |
| Frame Preemption | The feature that cuts a long frame short so that an urgent frame goes first. Each traffic class is set to EXPRESS or PREEMPTABLE | The FIFO settings in the EGRESS queue graph · 06.7.5 |
| Scheduler | The element that decides which of several FIFOs is sent first. It is either STRICT PRIORITY or ETS | The scheduler node in the EGRESS queue graph · 06.7.5 |
19.4 Software Structure
The area covered by the VFB editor, the Interface editor, and the System editor.
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| VFB (Virtual Functional Bus) | The abstract layer that deals only with the connections between software components, without regard to hardware placement | design ▸ System ▸ VFB · 08. VFB Editor |
| SWC (Software Component) | A software component. It communicates with the outside only through ports | The nodes on the VFB canvas · 08.2 |
| Composition | A container-type SWC that holds other components. It has ports of its own as well | Right-click empty canvas ▸ ADD COMPOSITION · 08.5.1 |
| Atomic SWC | An SWC that is an indivisible unit of execution. The kinds are Application, Complex Device Driver, Ecu Abstraction, Sensor Actuator, Service (a BSW service), and Adaptive Application. The ADD SWC menu adds Composition to these and so offers seven entries | Right-click a composition ▸ ADD SWC · 08.2 |
| Interface Mapping node | A dedicated node that ties AP service interfaces to the SR and CS elements of CP. It is not an SWC kind but a separate node kind | Right-click empty canvas at root level ▸ ADD INTERFACE MAPPING · 08.5.1 |
| Prototype | An instance of an SWC type actually placed inside a composition. You can place the same type several times as several prototypes | Right-click a composition ▸ ATTACH SWC · 08.5.2, the AS PROTOTYPE column on the System editor · 11.4.1 |
| drill-down | Entering a composition to edit its contents. The breadcrumb at the top of the screen shows your current location | Double-click a composition · 08.4 |
| Port | The point at which an SWC exchanges data with the outside. There are three directions: PPort (provided), RPort (required), and PRPort (both) | Right-click a node ▸ ADD Port · 08.5 |
| Port Interface | The contract for what a port exchanges. A port references one interface | The Interface editor · 09. Interface Editor |
| Sender-Receiver (SR) | The interface that sends and receives data elements in one direction | The Sender-Receiver tab of the Interface editor · 09.3.2 |
| Client-Server (CS) | The interface that calls operations and receives results. Arguments carry an IN, OUT, or INOUT direction | The Client-Server tab of the Interface editor · 09.3.3 |
| Mode-Switch | The interface that announces a mode change. It holds a ModeDeclarationGroup name, an initial mode, and a list of mode declarations | The Mode-Switch tab of the Interface editor · 09.3.4 |
| Service Interface | The service interface of AP. It holds events, methods, and fields, together with a C++ namespace and a version | The Service tab of the Interface editor · 09.3.1 |
| Data Element | One piece of data carried by a Sender-Receiver interface. It has a name and a data type | The Sender-Receiver tab · 09.3.2 |
| Operation | One call offered by a Client-Server interface | The Client-Server tab · 09.3.3 |
| ComSpec | The communication properties of a port. The kind depends on direction and on whether a queue is used, and it holds an initial value, a timeout, a transmission mode, and so on | The ComSpec section of the properties panel when a port is selected · 08.7 |
| Internal Behavior | The definition of an Atomic SWC's internal behavior. It holds Runnables, RTE events, and Inter-Runnable Variables | The SWC Internal Behavior dialog · 08.8 |
| Runnable (Runnable Entity) | The unit of execution that the RTE calls. It holds symbol (the C function name in the generated code), a minimum start interval, and so on | The canvas nodes of the SWC Internal Behavior dialog · 08.8 |
| RTE Event | The trigger that wakes a Runnable. The menu offers seven kinds — TimingEvent, BackgroundEvent, DataReceivedEvent, OperationInvokedEvent, SwcModeSwitchEvent, InitEvent, and InternalTriggeredEvent (the AUTOSAR name is InternalTriggerOccurredEvent) | The RTE Events add menu of the SWC Internal Behavior dialog · 08.8 |
| Access Point | The point at which a Runnable accesses a port or a variable. There are nine kinds — DataSendPoint, DataReceivedPoint, SyncServerCallPoint, DataWriteAccess, DataReadAccess, WrittenLocalVariable, ReadLocalVariable, ModeSwitchPoint, ModeAccessPoint | The Access Points add menu of the SWC Internal Behavior dialog · 08.8 |
| InternalTriggeringPoint | The origin of a trigger that wakes another Runnable from inside an SWC. It belongs to the owning Runnable. It sits in the Access Points menu, but it is stored as a separate element rather than as a VARIABLE-ACCESS | The tenth entry of the Access Points add menu of the SWC Internal Behavior dialog · 08.8 |
| Inter-Runnable Variable (IRV) | A variable shared by the Runnables inside one SWC | SWC Internal Behavior dialog ▸ right-click the SWC body ▸ ADD IRV · 08.8 |
| SWC-to-ECU mapping | The relationship that decides which composition is placed on which ECU or HPC. You can edit it on three screens, and they stay synchronized in real time | The MAPPED ECU column on the System editor · 11.4.5, IVC Map Composition · 06.6, VFB Map to ECU/HPC · 08.5.3 |
| Data Mapping | The mapping that ties a port's data element to a communication signal (or signal group). It is recorded in the System model | The Data Mapping section that appears in the properties panel when you select a composition boundary port in VFB · 08.7, 11.8 |
| InterfaceMapping | The definition that maps the events, methods, and fields of an AP service interface onto the data elements and operations of CP. It is stored in the VFB model, not in the Interface model | The Mapping tab of the Interface editor · 09.3.7, the InterfaceMapping node in VFB · 08.7 |
| Root Composition | The top-level composition of the system. The SYSTEM element references it | The row with the System badge in the SWC Hierarchy of the System editor · 11.4.4 |
19.5 Data Types
The area covered by the DataType editor.
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| Application Data Type | A data type defined in terms of physical meaning (unit and range). On export it becomes APPLICATION-PRIMITIVE-DATA-TYPE and the like | The DataType editor · 10. DataType Editor |
| Implementation Data Type | A data type defined in terms of the implementation (the C language). It is exported as IMPLEMENTATION-DATA-TYPE | The exported <Project>_DataType.arxml · 10.7 |
| StdCpp Implementation Data Type | An implementation data type defined in terms of C++. It is exported as STD-CPP-IMPLEMENTATION-DATA-TYPE, and primitives are rewritten into C++ spelling (uint8_t and so on) only here | The exported <Project>_DataType.arxml · 10.7 |
| SW-BASE-TYPE | The base type that holds the bit size, the encoding, and the native C declaration | The BaseTypes package of the exported <Project>_DataType.arxml · 13.3.5 |
| CompuMethod | The conversion rule that ties a raw value to a physical value (or to text). PAIO generates it automatically — as TEXTTABLE for an ENUMERATION and as LINEAR for an ALIAS — and names it CM_<type name> | The exported <Project>_DataType.arxml · 13.3 |
| Unit | A physical unit. It holds a display name and an SI conversion factor and offset. 33 default units are included | The Unit tab of the DataType editor · 10.8 |
| DataConstr | A value range constraint. It is generated automatically as DC_<type name> only when an ALIAS type has a minimum or a maximum | The exported <Project>_DataType.arxml · 13.3 |
| DataTypeMappingSet | The set that pairs Application types with implementation types. PAIO creates two automatically, DataTypeMappingsCP (for C) and DataTypeMappingsAP (for C++) | The exported <Project>_DataType.arxml · 10.7 |
| Category | The kind of a data type. There are nine — PRIMITIVE, ALIAS, STRUCTURE, UNION, ENUMERATION, FIXED_ARRAY, DYNAMIC_ARRAY, STRING, MAP | The Category field of the DataType editor · 10.2 |
| built-in primitives | The 11 base types PAIO reserves — boolean, float32, float64, sint8/16/32/64, uint8/16/32/64. They are injected into memory automatically when a project opens and are not stored in the model files | The top of the DataType editor list · 10.7 |
| ALIAS | An alias for another type. Factor, Offset, Min, Max, and Unit are specified only here | The ALIAS details of the DataType editor · 10.2 |
| Init Value | The initial value of an element. PAIO uses one shared widget on every initial value screen, and the input form is determined automatically from the structure of the target type | The INIT VALUE column and the initial value section of the Signal editor · 07.11, the port ComSpec section · 08.7 |
| ValueSpecification | The AUTOSAR structure that expresses initial values in structure, array, and map form as well as single values. A form PAIO does not recognize is preserved verbatim and shown in a read-only viewer | The initial value editing area · 07.11 |
19.6 Adaptive Platform
The area covered by the AA Internal Behavior and Machine Configuration dialogs of the VFB editor and by the Adaptive tab of the Interface editor.
Basic Concepts
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| HPC | High-Performance Computer. In PAIO it denotes an Adaptive Platform node, and it is exported as MACHINE-DESIGN | Right-click empty IVC canvas ▸ Add HPC · 06.4.1 |
| Machine | One AP execution environment. It holds processors and cores, the OS, Function Groups, and platform module instances | Click the HPC icon of a composition ▸ the Machine Configuration dialog · 08.10 |
| Function Group | The group that bundles and defines the operating states of a machine. Each group has a state machine (mode declarations plus transitions) | Machine Configuration ▸ FUNCTION GROUP tab · 08.10 |
| MachineFG | The default Function Group that every machine must have. The default state machine is named MachineState, the initial mode is Off, and the declared states are Off / Startup / Shutdown / Restart / Verify | Machine Configuration ▸ FUNCTION GROUP tab · 08.10 |
| Mode Declaration | One state of a state machine | The state diagram of the FUNCTION GROUP tab · 08.10 |
| Adaptive Application (AA) | The application SWC of AP. It holds both Executable and Process settings | Double-click on the VFB canvas ▸ the AA Internal Behavior dialog · 08.9 |
| Executable | One build artifact. It holds a version, a category, a build type (BUILD-TYPE-DEBUG / BUILD-TYPE-RELEASE), the root SWC prototype, and the minimum timer resolution | AA Internal Behavior ▸ PROPERTIES tab · 08.9 |
| Process | The process that actually runs an Executable. It holds start conditions (Function Group states), execution dependencies, log settings, and core affinity | AA Internal Behavior ▸ EXECUTION tab, Machine Configuration ▸ PROCESSES tab · 08.9 |
| Execution Dependency | The condition that starts a process only while another process is in a given state (Idle / Starting / Running / Terminated) | AA Internal Behavior ▸ EXECUTION tab · 08.9 |
| Module Instantiation | A platform module instance placed on a machine. Each module kind has its own configuration screen | Machine Configuration ▸ MODULE tab · 08.10 |
| Error Domain | The domain that groups AP application error codes | The Error Domain tab of the Interface editor · 09.3.6 |
Functional Clusters
In PAIO you create the port interfaces for each functional cluster on the Adaptive tab of the Interface editor, and you configure the machine side on the MODULE tab of the Machine Configuration dialog. The two screens cover different ranges. The Adaptive tab has 9 clusters (CM and UCM have no dedicated port interface), while the MODULE tab has 10 modules (RDS has no corresponding module). The table below lists both together.
| Cluster | Meaning | Where you see it in PAIO |
|---|---|---|
| ara::log (LOG, Log and Trace) | Logging and tracing. It covers the DLT application ID, the log mode (CONSOLE/FILE/NETWORK), and the log level (OFF through VERBOSE) | Interface ▸ Adaptive ▸ ara::log ▸ LogAndTrace, Machine ▸ MODULE ▸ LOG · 09.3.5, 08.10 |
| CM (Communication Management) | Service-oriented communication management | Machine ▸ MODULE ▸ CM · 08.10 |
| ara::sm (SM, State Management) | State management. There are four interface kinds: StateClient, DiagTrigger, EmError, and PhmError | Interface ▸ Adaptive ▸ ara::sm, Machine ▸ MODULE ▸ SM (state machines, actions, requests and notifications, and the wiring diagram) · 09.3.5, 08.10 |
| ara::phm (PHM, Platform Health Management) | Platform health monitoring. There are two interfaces: PhmSupervisedEntity and PhmRecoveryNotification | Interface ▸ Adaptive ▸ ara::phm, Machine ▸ MODULE ▸ PHM (checkpoints, the transition diagram, and Global Supervision) · 09.3.5, 08.10 |
| ara::nm (NM, Network Management) | The network management of AP. There is one interface, NetworkManagement, and the machine side deals with NetworkHandle | Interface ▸ Adaptive ▸ ara::nm, Machine ▸ MODULE ▸ NM · 09.3.5, 08.10 |
| ara::tsync (TS, Time Synchronization) | Time synchronization. There are two interfaces: SynchronizedTimeBaseConsumer and SynchronizedTimeBaseProvider | Interface ▸ Adaptive ▸ ara::tsync, Machine ▸ MODULE ▸ TS · 09.3.5, 08.10 |
| ara::crypto (CRY, Cryptography) | Cryptography. There are five interfaces: CryptoKeySlot, CryptoKeySlotClient, CryptoCertificate, CryptoCertificateGroup, and CryptoProvider | Interface ▸ Adaptive ▸ ara::crypto, Machine ▸ MODULE ▸ CRY · 09.3.5, 08.10 |
| ara::per (PER, Persistency) | Persistent storage. There are two interfaces, PersistencyKeyValueStorage and PersistencyFileStorage, and the machine owns the actual storage | Interface ▸ Adaptive ▸ ara::per, Machine ▸ MODULE ▸ PER · 09.3.5, 08.10 |
| ara::rds (Raw Data Stream) | Raw data streams. There are four interfaces: RawDataStreamClient, RawDataStreamServer, Ieee1722RawDataStreamConsumer, and Ieee1722RawDataStreamProducer. The MODULE tab has no corresponding module, so this is handled through mappings on the AA side | Interface ▸ Adaptive ▸ ara::rds, the AA Internal Behavior dialog · 09.3.5, 08.9 |
| ara::idsm (IDS, Intrusion Detection) | Intrusion detection. There are five interfaces: SecurityEventReport, IdsmTimestampProvider, IdsmContextProvider, IdsmReportingModeProvider, and IdsmQualifiedEventReceiver | Interface ▸ Adaptive ▸ ara::idsm, Machine ▸ MODULE ▸ IDS, the exported <Project>_IDS.arxml · 09.3.5, 08.10 |
| ara::ucm (UCM, Update and Configuration Management) | Update and configuration management. There is no dedicated port interface; it is handled only through machine module settings (Master / Subordinate) | Machine ▸ MODULE ▸ UCM · 08.10 |
| DLT | Diagnostic Log and Trace. A log transport specification that classifies logs by application ID and context ID | The DLT application table in Machine ▸ MODULE ▸ LOG, and AA Internal Behavior ▸ EXECUTION tab · 08.9, 08.10 |
Adaptive Interface Badges
These are the badges that follow an interface name in the Adaptive tab list of the Interface editor (09.3.5).
| Badge | Interface |
|---|---|
SC / DT / EM / PHM | StateClient / DiagTrigger / EmError / PhmError |
PHM/SE / PHM/RN | PhmSupervisedEntity / PhmRecoveryNotification |
NM | NetworkManagement |
TS/C / TS/P | SynchronizedTimeBaseConsumer / Provider |
CR/KS / CR/KSC / CR/CERT / CR/CG / CR/PRV | CryptoKeySlot / KeySlotClient / Certificate / CertificateGroup / Provider |
RDS/C / RDS/S / RDS/1722C / RDS/1722P | The four RawDataStream interfaces |
PER/KV / PER/FS | PersistencyKeyValueStorage / FileStorage |
IDSM/SEV / IDSM/TS / IDSM/CTX / IDSM/RM / IDSM/QEV | The five IDSM interfaces |
LnT | LogAndTrace |
19.7 ECUC
The area that covers Classic Platform BSW module configuration. Two editors work as a pair.
| Term | Meaning | Where you see it in PAIO |
|---|---|---|
| ECUC (ECU Configuration) | The configuration system for BSW modules. It separates "which parameters exist" (the definition) from "what their values are" (the configuration) | design ▸ Module · 12. ECUC |
Module Definition (.def) | The document that declares the structure of containers, parameters, and references a module can have. It holds no values | The Module Definition editor · 12.1 |
Module Configuration (.conf) | The document that fills in actual values according to a definition. It always references a definition and is kept per ECU | The Module Configuration editor · 12.2 |
| Container | The bundle that holds parameters and references. A definition has two kinds, ParamDef (ordinary) and Choice (either-or) | Right-click the DEFINITION tree ▸ Add Container · 12.1 |
| Container Instance | One actual instance of a defined container, created in a configuration. You can name it and duplicate it | The container tree ▸ + (Add Container) · 12.2 |
| Parameter | An item that holds a value. A definition offers nine kinds — Integer, Float, Boolean, Enumeration, String, Function Name, Linker Symbol, Multiline String, Add Info | Right-click the DEFINITION tree ▸ Add Parameter · 12.1 |
| Reference | An item that points to another container instance. The definition screen can create four kinds (the four rows below) | Right-click the DEFINITION tree ▸ Add Reference · 12.1 |
| Reference (simple) | Points to one instance that matches the container definition path written in destination | The candidate dropdown of the CONFIGURATION panel · 12.3 |
| Choice Reference | Holds several destination entries. PAIO resolves each one separately and shows the combined candidates | The combined dropdown of the CONFIGURATION panel · 12.3 |
| Foreign Reference | Points to an AUTOSAR element outside ECUC by DESTINATION-TYPE (a meta-type name) | A candidate dropdown if the DEST catalog knows the type, free text entry if it does not · 12.3 |
| Instance Reference | Points to an outside element together with a context chain. DESTINATION-CONTEXT lists the element kinds it passes through, separated by spaces | Editing the two fields DEST and VALUE in the CONFIGURATION panel · 12.3 |
| Symbolic Name Reference | An old reference kind removed in AUTOSAR 4.4.0. Only import is supported, and it does not appear in the Add Reference menu of the definition editor. On export it becomes an ordinary Reference | Only inside an imported module definition · 12.1 |
| destination | The path of the target a reference points to. Inside PAIO it has the form <module>/<container>[/<child>...], without an AR-PACKAGE | The destination field of the PROPERTIES panel · 12.3 |
| DESTINATION-TYPE | The AUTOSAR meta-type name a Foreign or Instance Reference points to (for example RUNNABLE-ENTITY). PAIO connects it to an IO Model element through the DEST catalog | The PROPERTIES panel and the CONFIGURATION panel · 12.3 |
| DESTINATION-CONTEXT | The chain of element kinds an Instance Reference passes through on the way to its target | The PROPERTIES panel · 12.1 |
| Multiplicity | How many of an item may exist. It is written as a lower and an upper bound, and an unlimited upper bound is inf | The multiplicity fields of the PROPERTIES panel · 12.1 |
| Origin | A string that records who created the definition item (for example a standard name or a vendor name) | The Origin field of the PROPERTIES panel · 12.1 |
| Config Class | The grade that states when a value must be fixed — PRE-COMPILE, LINK, POST-BUILD, PUBLISHED-INFORMATION. It is recorded paired with a variant | The Value and Multiplicity Config Class lists of the PROPERTIES panel, and the badges (display only) of the CONFIGURATION panel · 12.1, 12.2 |
| Config Variant | The configuration approach that determines when a setting is fixed — VARIANT-PRE-COMPILE, VARIANT-LINK-TIME, VARIANT-POST-BUILD, PRECONFIGURED-CONFIGURATION, RECOMMENDED-CONFIGURATION | Definition: Supported Config Variants / configuration: Implementation Config Variant · 12.1, 12.2 |
| Post-Build Variant Used | Whether this configuration uses a post-build variant. It has three states — unset, true, and false — and unset is never changed to false on its own | The module-level Variant area of Module Configuration · 12.2 |
| ECUC generation | The feature that produces BSW module configurations from the IVC and Signal models. The target modules are Can, CanIf, Com, EcuC, and PduR | Select an ECU in IVC ▸ properties panel ECUC GENERATION ▸ Generate ECUC · 12.4 |
EcucDefinitionCollection | The element that bundles module definitions on export | The exported <Project>_EcucModuleDef.arxml · 12.5 |