Difference between revisions of "Extensions.Measure"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:OTX '''Measure''' Extension}}[[Category:OTX-Extension]][[Category:Measure]] | {{DISPLAYTITLE:OTX '''Measure''' Extension}}[[Category:OTX-Extension]][[Category:Measure]] | ||
== Classification == | == Classification == | ||
| − | {{ClassificationExtension | Measure | | + | {{ClassificationExtension | Measure | Extends OTX to the requirements of vehicle manufacturing. | [[OtxReference#Extensions|OTX Extension]] | - | - }} |
== Introduction == | == Introduction == | ||
| − | The OTX '''Measure''' extension provides actions, terms and data types for basic measurement and control operations. OTX Measure extension provides a general interface to execute arbitrary so called device services synchronous or asynchronous. Depending on the runtime implementation it can be used to call methods inside a Dynamic Link Library (DLL) or anything else. | + | The OTX '''Measure''' extension provides actions, terms and data types for basic measurement and control operations. Its purpose is to extend OTX to the requirements of vehicle manufacturing. OTX Measure extension provides a general interface to execute arbitrary so called device services synchronous or asynchronous. Depending on the runtime implementation it can be used to call methods inside a Dynamic Link Library (DLL) or anything else. |
| + | |||
| + | {{Note|The Measure extension is not multi-instance capable. This means a device signature can be mapped to only one physical device.}} | ||
== Actions == | == Actions == | ||
| Line 57: | Line 59: | ||
{| {{TableHeader}} | {| {{TableHeader}} | ||
| − | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk001|Measure_Chk001]]| | + | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk001|Measure_Chk001]]|Correct target for ExecuteDeviceService and DeviceEventSource}} |
| − | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk002|Measure_Chk002]]| | + | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk002|Measure_Chk002]]|Executed device service is declarated in device signature}} |
| − | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk003|Measure_Chk003]]| | + | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk003|Measure_Chk003]]|Correct ExecuteDeviceService arguments}} |
| − | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk004|Measure_Chk004]]| | + | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk004|Measure_Chk004]]|ExecuteDeviceService input argument omission}} |
| − | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk005|Measure_Chk005]]| | + | {{TableRowKeyValueList|[[Extensions.Measure.MeasureChk005|Measure_Chk005]]|No Path in ExecuteDeviceService ouput arguments}} |
|} | |} | ||
Latest revision as of 11:34, 18 October 2018
Contents
Classification
| Name | Measure |
| Short Description | Extends OTX to the requirements of vehicle manufacturing. |
| Class | OTX Extension |
| Base Extension | - |
| Pre-Conditions | - |
| Specified by | ISO 13209-3 |
Introduction
The OTX Measure extension provides actions, terms and data types for basic measurement and control operations. Its purpose is to extend OTX to the requirements of vehicle manufacturing. OTX Measure extension provides a general interface to execute arbitrary so called device services synchronous or asynchronous. Depending on the runtime implementation it can be used to call methods inside a Dynamic Link Library (DLL) or anything else.
The Measure extension is not multi-instance capable. This means a device signature can be mapped to only one physical device.
Actions
| ExecuteDeviceService |
Terms
| Measurement related terms | |
| GetMeasurementTimestamp | |
| GetMeasurementStatus | |
| GetMeasurementQuantity | |
| GetMeasurementFloatValue | |
| IsValidMeasurement | |
| Event related terms | |
| DeviceEventSource | |
| IsDeviceEvent | |
| GetDeviceServiceNameFromEvent |
Data Types
| Measurement |
Exceptions
| MeasureException | |
| ConfigurationException | |
| CommunicationException | |
| DeviceException | |
| ServicePreconditionException | |
| InvalidMeasurementException |
Signatures
| DeviceSignature |
Checker rules
| Measure_Chk001 | Correct target for ExecuteDeviceService and DeviceEventSource |
| Measure_Chk002 | Executed device service is declarated in device signature |
| Measure_Chk003 | Correct ExecuteDeviceService arguments |
| Measure_Chk004 | ExecuteDeviceService input argument omission |
| Measure_Chk005 | No Path in ExecuteDeviceService ouput arguments |
