Office 0049-(0)40 - 866 298 75
Mobil 0049-(0)171-28 52 405

The PMS AutoSAR Configurator 

Configuration of all diagnostic and DTC features of your PMS StandOS operating system

 

The PMS Diagnostic Configurator

With the PMS ConfiguratorDiagnose you can

interactively configure and generate real time code for all diagnostic and error memory tasks as defined in the automotive UDS standard. PMS ConfiguratorDiagnose can be applied for all popular microcontrollers.

Controlling the remote StandOS

PMS ConfiguratorDiagnose configures and generates code for all diagnostic and DTC settings for a specific project. When the menu or the button „Generate Code“ is activated, is the PMS ConfiguratorDiagnose generating C source and header files, which control the diagnostic and DTC configuration in the respective remote StandOS operating system.

Configuration of the diagnostic properties

PMS ConfiguratorDiagnose offers you the import of requirement specifications from for example PTC Integrity.

Supported Services

In this table you can determine, which diagnostic services are supported and which not. In some diagnostic sessions some services are not allowed by the UDS standard. This is shown by the white background color. Only when the background color is green, services are allowed by the UDS standard. You can enable or disable the green services by clicking with the mouse on the proper field.

Standard Jobs

In the form „Standard Jobs“ all standard UDS jobs can be enabled or disabled. Essential jobs are prescribed by the UDS standard and should all be available and checked. All optional jobs and coding jobs are not necessarily available, so some may be unchecked.

Read & Write Data by Identifier (0x22, 0x2E)

The Read and Write Data By Identifier services allows the diagnostic tool to read and write information from/to the ECU at an internal location specified by the provided data identifier. This diagnostic control as well as the IO and Routine control diagnoses can read and write one or more signals in the ECU. The signals are listed up in a separate window. All requirements of the UDS standard are implemented without restrictions.

General DTC settings 

Input & Output Control By Identifier (0x2F)

The purpose of the IO control diagnosis is to force input data, internal data and output data to certain values. The data modified by the Read Data By Identifier and Write Data By Identifier diagnosis commands are only valid as long as the input drivers or the application not are changing that value. When the IO Control diagnosis has forced ECU variables, StandOS will prevent the input drivers and the application to override the forced values.

Remote Routine Control (0x31)

The Remote Routine Control services allows the diagnostic tool to start and stop routines and read ECU data related to the remote routines. Remote routine control services are identified by a unique data identifier (DID).

Each remote routine service has the following properties:

Control Type

01 : Start Routine - positive response required.

02 : Stop Routine - positive response required

03 : Request Routine Results - positive resp.

0x81 : Start Routine - no positive resp.required

0x82 : Stop Routine - no positive response req

Run Options

1 : Run routine once - The routine is started immediately and will only run once.

2 : Run routine continuesly - The routine is repetedly called in certain intervals.

Configuration of the DTC properties

The Diagnostic Trouble Codes (DTC) are configured in specific user friendly windows. In the “General” form are the number of primary and secondary DTCs determined, and also the bits of the event status mask. By clicking the bottom “Calculate” the minimum prescribed number of DTC entries can be calculated for you. The minimum number of freeze frames is two (the first and the last)

Descriptor table and environment data

In the form „Descriptors“ all DTCs are configured, especially the group, the origin, the severity, the trigger events for the diagnostic master, the settings for healing.

Each DTC can have several environment data. They are configured  in a separate window. When the memory space in the environment table is exceeded, the PMS Configurator Diagnose will deny the superfluous data and give a warning in the output window.

Freeze Frames and „Extended Frames

In the forms „Freeze Frames“ and „Extended Frames“ the respective DTC data are configured. The prescribed data in the freeze frame and the extended data are predefined by the PMS Configurator Diagnose as fixed in the UDS standard.

Storing data in an EEPROM

To save energy, controllers are regularly going in a sleep state. Before the sleep state is entered and after a wake up, StandOS retains all important process data to/from a non volatile memory. In the NVRAM window you can configure EEPROM blocks of variable length.

Tracking the development history

To be able to track the development history the forms „Authors“ and „History“ are featured. Each new input and each modification are entered here.