Extensions.BusMonitoring
Jump to navigation
Jump to search
Contents
Classification
| Name | BusMonitoring |
| Short Description | Enable asynchronous collection of communication data (monitoring) at runtime and analysis of monitored data (frames) |
| Class | OTX Extension |
| Base Extension | - |
| Pre-Conditions | - |
| Specified by | ISO 13209-4 |
Introduction
The OTX BusMonitoring Extension is introduced to enable asynchronous collection of communication data (monitoring) at runtime and analysis of monitored data (frames).
The extension is closely related to an ODX/MVCI [ISO 22901] [ISO 22900] based system.
In case of an ODX/MVCI based system it is recommended that the result of MCDMonitorLink::fetchMonitoringFrames is formatted as given in ISO 22900 Annex F. This is related to the terms GetBusFrameAsString, GetBusFrameTimestamp, GetBusFrameAddress, GetBusFrameData and GetBusFrameType.
Actions
| StartBusMonitoring | |
| StopBusMonitoring |
Terms
| Monitor property related terms | |
| BusMonitorEventSource | |
| BusMonitorModeLiteral | |
| BusMonitorModeTerm | |
| BusMonitorModeValue | |
| BusMonitorTerm | |
| BusMonitorValue | |
| FetchBusMonitorBusFrames | |
| IsBusMonitorEvent | |
| Frame property related terms | |
| BusFrameTerm | |
| BusFrameValue | |
| GetBusFrameAddress | |
| GetBusFrameAsString | |
| GetBusFrameData | |
| GetBusFrameTimestamp | |
| GetBusFrameType |
|
Data Types
| BusFrame | |
| BusMonitor | |
| BusMonitorMode |
Exceptions
| BusMonitoringException | |
| NotSupportedException |
Checker rules
| BusMonitoring_Chk001 | Incorrect element types for adresses list in StartBusMonitoring |
