Construyendo el modelo de competencia
CAPÍTULO 3. EL INSTITUTO MEXICANO DEL PETRÓLEO Y SUS COMPETENCIAS EN EL ÁREA DE NEGOCIOS
3.3 LA COMPETENCIAS DE NEGOCIOS EN EL IMP
Parameterization of the MICROSAR DIAG modules is done with Candelastudio.
> Management of all DTC status bits according to the UDS standard
> Definition of individual snapshots and extended records
> Predefined extended records (e.g. OccurenceCounter)
> Counter and time-based error de-bounce algorithms
> Suppression of low-priority errors when memory is full
> Flexible unlearning (aging) of errors
> Variants handling for diagnostic configuration
> Link time configuration
> Compressed Configuration Data to optimize code size The following AUTOSAR functions are available as options:
> Support of combined errors
> OBDII (ISO 15031 / SAE J1979)
> WWH-OBD (ISO27145)
The DEM base functionality differs a little between ASR 3 and ASR 4.0, except for the interface definitions. That is why Vector offers a migration solution that you can use to easily migrate your ASR 3 compatible SWCs to an ASR 4.0 project.
Diagnostic Communication Manager (DCM) Functions
The DCM implements UDS and OBDII services in the ECU. The ASR 4.0 version of the DCMs offers several extensions compared to the ASR 3 version. The most important of them are:
> Functional Diagnostics. This lets the DCM perform such tasks as directly accessing individual signals of ECU-internal
sender/receiver communication, read or write in the NvM and adapt IoHwAb signals.
> High-performance mode control, which enables execution of diagnostic services via mode dependencies, for example.
The OEM-independent variant of the DCM is available for both ASR 3 and ASR 4.0. For a complete list of supported services, please refer to the table at the end of this datasheet.
The DCM modules for specific OEMs implement the specifications of the particular OEM. Therefore, the lists of supported services vary, e.g. in supplemental support of ResponseOnEvent or LinkControl.
We would be glad to provide you with detailed information on this.
The following functions are available as options:
> Support of OBDII (ISO15031-5)
> WWH-OBD (ISO27145)
In addition, the DCM contains the following extensions as standard features:
> Variant handling for diagnostic configurations
> Multiple Client support
> Seamless collaboration with the Vector Flash Bootloader
> Generation of an application code template for the ECU software
Function Inhibition Manager (FIM) Functions
MICORSAR FIM contains the functional features of ASR 3 and ASR 4.0 as standard.
Contact and Availability
You will find information on the availability of hardware-specific MICROSAR BSW modules at: www.microsar.com/availability/
We would be glad to provide you with information on OEM-specific variants and individual support for your AUTOSAR projects.
Find your contact person at: www.vector.com/contact
Configuration and Parameterization
You adapt the BSW modules from MICROSAR DIAG to your applica-tion’s needs comfortably by configuration with DaVinci Configu-rator Pro. This may be done either with the help of a CANdela or ODX file or by an “ECU Configuration Description”.
For ASR3, diagnostic-specific parameterization of the DCM is performed exclusively via a CANdela file. You can create it quickly and simply or import it from most commonly used ODX dialects with the proven “diagnostic authoring tool” CANdelaStudio.
Scope of Delivery
> Software modules as a library with C header files, optionally as source code
> Command line based generator (for Windows XP/Windows 7)
> BSW module description
> Documentation
> Converters for CANdela diagnostic descriptions
The complete AUTOSAR Solution from Vector
The AUTOSAR solution from Vector consists of the DaVinci tools, MICROSAR-basic software and the MICROSAR RTE.
You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets.
Other Relevant Vector Products
To fulfill specific ISO standards, you can combine MICROSAR DIAG with the following MICROSAR products:
> MICROSAR CAN (ISO 15765-3 oder ISO/DIS 14229-3)
> MICROSAR FR (ISO/DIS 14229-4)
> MICROSAR IP (ISO/DIS 14229-5)
You can use CANdelaStudio to parameterize the CANdela or ODX file for configuration of MICROSAR DIAG. For more information, please refer to the separate datasheet in Vector’s diagnostics catalog.
Parameterization of MICROSAR DIAG is done by CANdelaStudio and DaVinci Configurator Pro
> Creation of a customer-specific diagnostic application
> Integration of diagnostics in your ECU software
The module DCM from MICROSAR DIAG supports …
… by default: UDS diagnostic services
… optional: OBD II Diagnose Services
Diagnostic Service Name
(ISO 14229-1) Service ID
(hex) ASR 3: The SWC
has to … ASR 4.0: The SWC has to … Diagnostic and Communication Management Functional Unit DiagnosticSessionControl 10 … grant service
execution - (handled in DEM configuration)
ECUReset 11 … grant service
execution - (handled in DEM configuration)
SecurityAccess 27 … calculate
seed/key for each security level
… calculate seed/key for each security level CommunicationControl 28 … grant service
execution - (handled in DEM configuration)
TesterPresent 3E - -
ControlDTCSetting 85 - (handled in DEM
module) - (handled in DEM module) Data Transmission Functional Unit
ReadDataByIdentifier 22 … handle data acquisition for each DataId
… handle data acquisition for each DataElement ReadMemoryByAddress 23 via callout via callout ReadDataByPeriodic
Identifier 2A - -
DynamicallyDefineData
Identifier 2C - -
WriteDataByIdentifier 2E …handle data access for each DataId
…handle data access for each DataElement WriteMemoryByAddress 3D via callout via callout
Stored Data Transmission Functional Unit ReadDTCInformation 19 - (handled in DEM
module) - (handled in DEM module) ClearDiagnosticInformation 14 - (handled in DEM
module) - (handled in DEM module) Input/Output Control Functional Unit
InputOutputControlBy
Identifier 2F … control I/O for
each DataId … control I/O for each DataElement Remote Activation Of Routine Functional Unit
RoutineControl 31
… start (stop/request result) for each RoutineId
… start (stop/request result) for each RoutineId
Diagnostic Service Name
(ISO 15031-5) Service
ID The SWC has to … Diagnostic Service Definition for CAN
Request Current Powertrain
Diagnostic Data 01 … handle data acquisition for each PID other than the
"supported ID" and DEM ones Request Powertrain Freeze Frame
Data 02 - (handled in DEM module)
Request Emission-Related
Diagnostic Trouble Codes 03 - (handled in DEM module) Clear/Reset Emission-Related
Diagnostic Information 04 - (handled in DEM module) Request On-Board Monitoring Test
Results for Specific Monitored Systems
06 … handle data acquisition for each TestId of a MonitorId Request Emission-Related
Diagnostic Trouble Codes Detected During Current or Last Completed Driving Cycle
07 - (handled in DEM module)
Request Control of On-Board
System, Test or Component 08 … process each TestId Request Vehicle Information 09
… handle data acquisition for each InfoType ID other than the "supported ID" and DEM ones
Request Emission-Related Diagnostic Trouble Codes with Permanent Status
0A - (handled in DEM module)
V2.5 2012-02
Overview of advantages
> Optimal support of microcontroller peripherals
> Simplified configuration by considering cross-module parameter dependencies in the configurator
> Development accelerated by plausibility and completeness tests in the configurator
> Resource-saving, since functionalities can be deactivated
> Reduced hardware requirements due to optimal utilization of hard-ware buffers
> Gateway developments are supported by efficient auxiliary func-tions
> Available for AUTOSAR 3 and 4.0 (from Q3/2012)
The MICROSAR CAL package contains the drivers for controlling the microcontroller’s peripherals. These drivers are fully compatible with the AUTOSAR specifications of the “Microcontroller Abstrac-tion Layer”. Each MICROSAR CAL driver is optimized controller-specifically.
Application Areas