Specification of Function Inhibition Manager , No.82, 2021-11
AUTOSAR R21-11記事一覧はこちら。
AUTOSAR 21-11, 200文書読んだ。2022年5月に全部到達。
AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成
用語(terms)
| Term | Description |
|---|---|
| Activity state | The activity state is the status of a software component being executed. The activity state results from the permission state as a precondition and physical enable condition, too. It is not calculated by the FiM and not available as a status variable. It can only be derived from |
| local information within a software component. For further details, see chapter 7.2.1.6. | |
| API | Application Programming Interface |
| BSW | Basic Software |
| Dem | Diagnostic Event Manager |
| ECU | Electronic Control Unit |
| FID | Function Identifier |
| FiM | Function Inhibition Manager |
| Functionality | Functionality comprises User-visible and User-non-visible functional aspects of a system (AUTOSAR_Glossary.pdf [2]). In addition to that - in the FiM context - a functionality can be built up of the contents of one, several or parts of runnable entities with the same set of permission / inhibit conditions. By means of the FiM, the inhibition of these functionalities can be configured and even modified by calibration. Each functionality is represented by a unique FunctionId. A functionality is characterized by a specific set of inhibit condition in contrast to runnable entities having specific scheduling conditions. |
| HW | Hardware |
| ID | Identification/Identifier |
| Inhibition Condition | The relation between one FID, an inhibition mask and the status of a Dem event/component. (see FiMInhibitionConfiguration) |
| ISO | International Standardization Organization |
| MIL | Malfunction Indication Light |
| Monitoring function | • Part of the Software Component. • Mechanism to monitor and finally to detect a fault of a certain sensor, actuator or could be a plausibility check • Reports states about events from internal processing of a SW-C or from further processing of return values of other basic software modules. • See also AUTOSAR_SWS_DiagnosticEventManager [3] |
| NVRAM | Non volatile Memory |
| OBD | On-board Diagnostics |
| OBDII | Emission-related On-board Diagnostics |
| OEM | Original Equipment Manufacturer |
| OS | Operating System |
| Permission state | The permission state contains the information whether a functionality, represented by its FID, can be executed or whether it shall not run. The state is controlled by the FiM based on reported events. For further details, see chapter 7.2.1.6. |
| RAM | Random Access Memory |
| ROM | Read-only Memory |
| RTE | Runtime Environment |
| Runnable entity | A Runnable Entity is a part of an Atomic Software-Component, which can be executed and scheduled independently from the other Runnable Entities of this Atomic Software-Component. It is described by a sequence of instructions that can be started by the RTE. Each runnable entity is associated with exactly one EntryPoint. |
| SW-C | Software Component |
| UDS | Unified Diagnostic Services |
| WP | Autosar Work Package |
| Xxx_ | Placeholder for an API provider |
英日単語帳
日本語は仮訳
T.B.D.
参考(reference)
[1] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral
[2] Glossary
AUTOSAR_TR_Glossary
[3] Specification of Diagnostic Event Manager
AUTOSAR_SWS_DiagnosticEventManager
[4] Requirements on Function Inhibition Manager
AUTOSAR_SRS_FunctionInhibitionManager
[5] Virtual Functional Bus
AUTOSAR_EXP_VFB
[6] Software Component Template
AUTOSAR_TPS_SoftwareComponentTemplate