ASAP2 Editor/Viewer 14.0 for Windows XP(SP3) 32 bit / Windows Vista(SP2) 32 bit / Windows 7(SP1) 32/64 bit / Windows 8 32/64 bit
	Creation(Editor) and Visualization of ECU Description Files
	© 1996-2015 Vector Informatik GmbH, Stuttgart

Contents on the DVD
Readme.html	This file
ReleaseNotes.html	Latest information and changes
Setup.exe	ASAP2 Editor/Viewer setup program
Autorun.exe	Start screen
DATA	Start screen files
ISSetupPrerequisites	Required Programs and Libraries to run this application
Vector Drivers	Vector Keyman Driver Setup
Reader	Adobe Acrobat Reader installation program

CD-ROM Installation

PROGRAM INSTALLATION

1. Insert the CD-ROM in your ROM drive.
2. If the Start Screen does not open by itself, start the program "autorun.exe".
3. Select the Option "Install Application" to install ASAP2 Editor/Viewer 14.0.
4. Follow the instructions to complete the software installation.
5. Install the hardware drivers. The current hardware drivers are on the CD supplied with the hardware.
6. To read the ASAP2 Editor/Viewer documentation on screen, select the option "View Documentation"
You will need the Adobe Acrobat Reader to read the documentation. If the Acrobat Reader is not installed on your system, select the option "Install Acrobat Reader". To copy the documentation on your hard drive select the option "Install Documentation"

IMPORTANT INFORMATION

Contents:

1. Latest Information
2. Installation path of Application Data and Configurations
3. Not Implemented Features of ASAP2 1.61
4. Export Format "Report"
5. Contact

1. Latest Information

   
   On Windows 7 64 bit OS installation it is recommended to select a 'C:\Program Files (x86)' subfolder if the application should be
   installed into the general program files folder. Selecting folders like C:\Programs or "C:\Program Files" will cause write protected
   configuration files.
   
   The documentation in pdf format in the directory "doc" of the CD contains the
   latest changes of the program.
   
   Windows 2000 is not supported by ASAP2 Editor/Viewer.
   
   
   

Installation path of Application Data and Configurations

To ensure Windows Vista conformity, the location of the writeable directories will be
moved if the windows program folder was selected as installation path.
The directories of the files are described in the 'Start Installation' page during the installation.
Later on, the directories can be checked via the 'About' dialog.


Not Implemented Features of ASAP2 1.61

The following ASAP2 1.61 keywords are not yet supported. If an ASAP2 file contains such keywords, the information is preserved and can be restored on saving, but it is not possible to display and edit the information in ASAP2 Editor.


• A2ML_VERSION
• HEADER
• MOD_COMMON - DATA_SIZE
• MOD_COMMON - DEPOSIT
• MOD_COMMON - S_REC_LAYOUT
• MOD_PAR - CPU_TYPE
• MOD_PAR - CUSTOMER
• MOD_PAR - CUSTOMER_NO
• MOD_PAR - ECU
• MOD_PAR - NO_OF_INTERFACES
• MOD_PAR - PHONE_NO
• MOD_PAR - SUPPLIERO
• MOD_PAR - USER
• MOD_PAR - VERSION
• USER_RIGHTS - not implemented
• Object types CUBOID, CUBE_4 and CUBE_5 for CHARACTERISTIC
• GUARD_RAILS
• REF_MEMORY_SEGMENT
• COMPARISON_QUANTITY
• MAP_LIST
• MAX_REFRESH
• MAX_GRAD
• ERROR_MASK
• MAX_REFRESH
• CALIBRATION_ACCESS
• UNIT
• MaxDiff (for AXIS_PTS, MEASUREMENT, CHARACTERISTIC)
• Resolution (for MEASUREMENT)
• Accuracy (for MEASUREMENT)
• OFFSET_ and SHIFT_ in record layouts is ignored
  (always the fix axis parameters defined at CHARACTERISTIC are used)

Export format "Report"

The export process is based on templates, which contain macros. All valid macros which are found in a template file are replaced by their values.

The target file always starts with the template file "HEAD.TEMPL" (if available). It may e.g. contain columns titles the macro $HEADER_COMMENT, which will be replaced by the comment.

For each database variable the appropriate template file is determined, the macros are replaced and the result is attached to the end of the target file.

The name of the template file is determined as follows:
If a record layout has been assigned to the variable, the name of the record layout is used as template filename with the file extension ".TEMPL". If no record layout exists for the variable, the name is determined by the variable typ accord to:



Value.TEMPL	scalar parameters
String.TEMPL	ASCII strings
Axis.TEMPL	shared axis
Curve.TEMPL	curves, those x axis points is not stored in the ECU (curves without x axis or with a fixed x axis)
CurveX.TEMPL	curves, those x axis points is stored in the ECU (curves with standard axis or shared axis)
Map.TEMPL	maps, those x- and y-axis points are not stored in the ECU (no x axis or x fixed axis, no y axis or y fixed axis)
MapX.TEMPL	maps, those x- axis points is stored in the ECU and those y- axis points is NOT stored in the ECU ( x standard axis or x shared axis, no y axis or no y fixed axis)
MapY.TEMPL	maps, those x- axis points is NOT stored in the ECU and those those y- axis points is stored in the ECU ( no x axis or no x fixed axis, y standard axis or y fixed axis)
MapXY.TEMPL	maps, those x- and y-axis points are stored in the ECU ( x standard axis or x shared axis, y standard axis or y shared axis)


If the template file for a variable with record layout, according to the name of the record layout could not be found, then a standard template file according to the variable type will be used.

All the template files must be located in the working directory.

The following macros are replaced in the template files:


• File name of the used template files
  $TEMPLATE_NAME$
• Comment entered in the dialog
  $HEADER_COMMENT$
• Name of the database variable
  $NAME$
• Base address of the variable
  $ADDRESS$
• Comment of the variable from the database
  $COMMENT$
• Physical unit of the variable
  $UNIT$
• Physical minimal-value
  $PHYS_MIN$
• Physical maximal-value
  $PHYS_MAX$
• Number of x axis points for axis, curves and maps
  $X_DIMENSION$
• Number of y axis points for axis, curves and maps
  $Y_DIMENSION$
• Data type in C syntax
  $DATATYPE_C$
• Data type in "general formulation" (BYTE,WORD,DWORD,...)
  $DATATYPE$
• Name of the variant for variant coded parameters
  $VARIANT$
• Continous Index
  $INDEX$
• Name of the x axis
  $X_AXIS_NAME$
• Comment of the x axis
  $X_AXIS_COMMENT$
• Physical unit of the x axis
  $X_AXIS_UNIT$
• Physical minimal-value of the x axis
  $X_AXIS_PHYS_MIN$
• Physical maximal-value of the x axis
  $X_AXIS_PHYS_MAX$
• Data type of the x axis in C syntax
  $X_AXIS_DATATYPE_C$
• Data type of the x axis in "general formulation"
  $X_AXIS_DATATYPE$
• Name of the input source for the x axis
  $X_AXIS_SOURCE_NAME$
• Comment of the input source for the x axis
  $X_AXIS_SOURCE_COMMENT$
• Comment of the y axis
  $Y_AXIS_NAME$
• Comment of the y axis
  $Y_AXIS_COMMENT$
• Physical unit of the y axis
  $Y_AXIS_UNIT$
• Physical minimal-value of the y axis
  $Y_AXIS_PHYS_MIN$
• Physical maximal-value of the y axis
  $Y_AXIS_PHYS_MAX$
• Data type of the y axis in C syntax
  $Y_AXIS_DATATYPE_C$
• Data type of the y axis in "general formulation"
  $Y_AXIS_DATATYPE$
• Name of the input source for the y axis
  $Y_AXIS_SOURCE_NAME$
• Comment of the input source for the y axis
  $Y_AXIS_SOURCE_COMMENT$
• If the value of a macro can not be determined, it will not be replaced (e.g.
  $Y_AXIS_NAME$ for a curve).

Contact

Please find the contacts of Vector Informatik GmbH and all subsidiaries worldwide via: http://www.vector.com/vi_addresses_en.html

© 2016 Vector Informatik GmbH