INCA ASAM ASAP3 Interface User`s Guide

INCA ASAM ASAP3 Interface User`s Guide
INCA ASAM ASAP3 Interface
User's Guide
November 2010
Copyright
The data in this document may not be altered or amended without special notification
from ETAS GmbH. ETAS GmbH undertakes no further obligation in relation to this document. The software described in it can only be used if the customer is in possession of a
general license agreement or single license. Using and copying is only allowed in concurrence with the specifications stipulated in the contract.
Under no circumstances may any part of this document be copied, reproduced, transmitted, stored in a retrieval system or translated into another language without the express
written permission of ETAS GmbH.
© Copyright 2010 ETAS GmbH, Stuttgart
The names and designations used in this document are trademarks or brands belonging
to the respective owners.
Document AM010120 R1.26 EN
2
Contents
1
INCA ASAM ASAP3 Interface Overview ................................................................................... 5
1.1
1.2
1.3
1.4
2
Safety Notice .................................................................................................................................. 6
Definition of Terms ......................................................................................................................... 6
Further Information ........................................................................................................................ 7
ASAM ASAP3 Server ........................................................................................................................ 7
1.4.1 Communication .................................................................................................... 7
User Interface...................................................................................................................... 9
2.1
2.2
2.3
2.4
2.5
2.6
ASAM MCD-3MC 4 INCA Interface Window (ASAM-ASAP3 server GUI)................................................ 9
The Toolbar.................................................................................................................................... 9
ASAM-ASAP3 Status Icon in Taskbar ................................................................................................ 9
Communication Options................................................................................................................. 10
Logging in the Interface Window ................................................................................................... 11
Options ........................................................................................................................................ 12
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.6.6
General Options ................................................................................................. 12
Map Editor Options............................................................................................. 13
Online Options ................................................................................................... 14
Recorder Options ............................................................................................... 15
View Options ..................................................................................................... 16
Compatibility Options.......................................................................................... 16
2.7 Usage of ASAP3.INI ...................................................................................................................... 18
2.8 Measurement modes ..................................................................................................................... 18
2.8.1 Old measure mode (Compatibility mode).............................................................. 18
2.8.2 New measure mode ........................................................................................... 19
2.9
2.10
2.11
2.12
3
Search Mechanism for ASAM ASAP3 Variables................................................................................. 20
Realization of ASAM ASAP3 Commands in INCA .............................................................................. 20
Performance considerations ........................................................................................................... 21
FULI – Fast Upper Level Interface (INCA-MCE) ............................................................................... 22
Implementation Notes for Commands .................................................................................. 23
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
Contents
EMERGENCY COMMAND: 1 ............................................................................................................ 23
INIT COMMAND: 2........................................................................................................................ 23
IDENTIFY COMMAND: 20 .............................................................................................................. 23
EXIT COMMAND: 50...................................................................................................................... 24
SELECT DESCRIPTION-FILE AND BINARY FILE COMMAND: 3 ......................................................... 25
DEFINE DESCRIPTION-FILE AND BINARY FILE COMMAND: 30 ........................................................ 27
COPY BINARY FILE COMMAND: 4 .................................................................................................. 30
CHANGE BINARY FILE NAME COMMAND: 5 .................................................................................... 31
SELECT LOOKUP TABLE COMMAND: 6 ........................................................................................... 31
3
3.10
3.11
3.12
3.13
3.14
3.15
3.16
3.17
3.18
3.19
3.20
3.21
3.22
3.23
3.24
3.25
3.26
3.27
3.28
3.29
3.30
3.31
3.32
3.33
3.34
3.35
3.36
3.37
4
PUT LOOKUP TABLE TO AP-S COMMAND: 7 ................................................................................... 32
GET LOOKUP TABLE FROM AP-S COMMAND: 8 ............................................................................... 33
GET LOOKUP TABLE VALUE COMMAND: 9...................................................................................... 34
INCREASE LOOKUP TABLE COMMAND: 10...................................................................................... 35
SET LOOKUP TABLE COMMAND: 11 ............................................................................................... 35
PARAMETER FOR VALUE ACQUISITION COMMAND: 12................................................................... 36
SWITCHING OFFLINE/ONLINE COMMAND: 13 ................................................................................ 37
GET ONLINE VALUE COMMAND: 19 ............................................................................................... 38
GET USER DEFINED VALUE COMMAND: 21 .................................................................................... 38
GET USER DEFINED VALUE LIST COMMAND: 22............................................................................. 39
GET PARAMETER FROM AP-S COMMAND: 14.................................................................................. 40
SET PARAMETER ON AP-S COMMAND: 15 ...................................................................................... 40
DEFINE RECORDER PARAMETERS COMMAND: 41........................................................................... 41
DEFINE TRIGGER CONDITION COMMAND: 42 ................................................................................ 42
ACTIVATE RECORDER COMMAND: 43 ............................................................................................ 43
GET RECORDER STATUS COMMAND: 44 ........................................................................................ 44
GET RECORDER RESULTS HEADER COMMAND: 45 ......................................................................... 44
GET RECORDER RESULTS COMMAND: 46....................................................................................... 45
SAVE RECORDER FILE COMMAND: 47............................................................................................ 46
LOAD RECORDER FILE COMMAND: 48 ........................................................................................... 46
SET GRAPHIC MODE ON AP-S COMMAND: 16................................................................................. 47
RESET DEVICE COMMAND: 17....................................................................................................... 47
SET FORMAT COMMAND: 18 ......................................................................................................... 47
SET CASE SENSITIVE LABELS COMMAND: 61 ................................................................................. 48
EXTENDED QueryAvailableServices COMMAND: 200...................................................................... 48
EXTENDED GetServiceInformation COMMAND: 201....................................................................... 49
EXTENDED ExecuteService COMMAND: 202 ................................................................................. 49
EXTENDED GetWorkingPoint COMMAND: 42001 ........................................................................... 50
Appendix: ASAP3 Error Codes.............................................................................................. 52
4.1 Errors in Log Window without Error Code returned to AuSy ............................................................. 52
4.2 Errors in Log Window with Error Code returned to AuSy .................................................................. 52
5
ETAS Contact Addresses ..................................................................................................... 72
4
Contents
1
INCA ASAM ASAP3 Interface Overview
There are a bunch of ASAM MCD-3MC Interfaces. The following figure gives an overview on
the ASAM MCD-3MC Interfaces.
ASAM MCD-3MC Interfaces
ASAM ASAP3
ASAM MCD-3MC
(Legacy Interface)
(Object Model based Interface)
V2.0
V2.1
V2.1.1
V1.0.0
V1.0.1
V2.1.0
V2.1.1
V1.0.2
V2.2.0
This documents focus
Supported
by INCA
Not
supported by
INCA
This document describes the ETAS implementation of the ASAM ASAP3 interface for INCA.
The term “ASAP3” is alternatively used as abbreviation for “ASAM ASAP3” within this
document.
INCA’s ASAP3 interface implements the ASAP3 V2.1.1 standard but also supports the
previous versions V2.0 and V2.1 covered by this document.
The executable which implements these interfaces is called “ASAP3.EXE” or “ASAM ASAP3
Server”. In fact, ASAP3.EXE implements both, the legacy ASAP3 interface and the new ASAM
MCD-3MC V1.0.1 interface side by side. The selection is done by choosing the MCD3 Version
to use in the INCA GUI. This is mentioned here only for the sake of completeness.
The legacy ASAM ASAP3 interface is no longer a maintained standard. It differs from the
new generation ASAM MCD-3MC Vx.y.z standard fundamentally. Nevertheless it is still used
by a respectable number of systems.
INCA ASAM ASAP3 Interface Overview
5
The following graphic gives an overview on how all the components work together:
Engine,
Transmission,
etc.
ETK
ECU
ETAS
ECU Interface
HW
INCA
RCI2
AuSy
Ethernet / Serial Link
Tool API
ASAM MCD-3MC
Server
INCA - PC
The ASAM ASAP3 interface, illustrated with the general expression ASAM MCD-3MC
Interface, listens at its Ethernet port (or Serial Link (RS232)) for commands sent by the
Automation System (AuSy). These commands are translated into several calls to the Tool
API / RCI2 interface of the INCA core and also logged into the ASAM MCD-3MC interface
window by the ASAM MCD-3MC Server of INCA.
1.1
Safety Notice
DANGER!
Calibration activities influence the behavior of the ECU and the systems controlled by
the ECU. This may result in unexpected behavior of the vehicle and thus can lead to
safety critical situations.
Only well trained personnel should be allowed to perform calibration activities.
1.2
Definition of Terms
LUN:
In INCA, the ASAP3 LUN is a device with a certain associated project and binary data.
Map Number:
The map number is used to identify a certain map that is to be used for further map
access. Despite its name, it is also used for 1D calibration objects (Curves). In INCA,
the Map Number corresponds to a map or curve that is visible (or invisible) in the
INCA Experiment.
MC:
Short for Measurement and Calibration.
6
INCA ASAM ASAP3 Interface Overview
MCS / MC-S:
MC System, in this case INCA is meant.
AP-S:
Other expression for MCS (Application System)
AuSy:
Automation System
ASAM MCD-3MC Interfaces:
They are used to talk about ASAM MC Automation Interfaces in general.
ASAM ASAP3:
ASAM’s legacy Automation Interface taken over by the ASAP standardization
community. By now, ASAM has joined the international ASAM community.
ASAM MCD-3MC Vx.y.z
ASAM’s new generation object model based automation interface. To be precise, this
has always to be mentioned with a version number (Not part of this document).
1.3
Further Information
Information on the ASAM ASAP3 is provided in the INCA online help.
1.4
ASAM ASAP3 Server
The ASAM ASAP3 Server is an additional program (ASAP3.exe) running on the same
computer as INCA. It is started out of the INCA experiment via menu Components|ASAM3MC: Open ASAM-3MC Interface.
1.4.1
Communication
Two different communication types are supported: Serial communication or TCP/IP
communication.
Serial Communication Options:
! Standard: Serial, 9600 Baud (adjustable up to 115200 Baud) 8N1 (8 Data bits, no
parity, one stop bit); the quality of the connection, especially above 9600Baud,
depends on the current system configuration and the quality of the device drivers.
Port and Baud rate can be adjusted by the user.
Network (TCP/IP) Communication Options:
! The implementation uses TCP/IP sockets for communication. ASAP3.EXE works as a
server, it listens at a specific IP address and port number for incoming connection
requests. As soon as a connection is established, the status line shows the IP
addresses of both communicating instances, server and client.
! It is possible to choose to listen at a specific network card installed in the current PC
or at a specific Local Network (IP) address.
! In case Network Card is selected, it is possible to choose among all installed network
cards that are found in the current PC.
! In case Local Network Address is selected, a fixed IP address at which a socket will
listen can be entered, or you can enter “0” (zero) to listen at the default IP address of
the current PC.
! The network port at which ASAM-ASAP3 will listen can also be entered. The default
value is 22222.
! If you choose to use fast socket communication, a specific, faster communication
routine is used. This routine does not support the “Send Acknowledge” option and will
simply ignore that setting.
Both communication types:
! After starting the ASAM-3MC interface, the software tries to setup the last used
communication type along with the last communication options stored in the windows
registry.
INCA ASAM ASAP3 Interface Overview
7
! The communication parameters can be adjusted after breaking the connection. The
connection can be broken explicitly only while there is no active ASAP3 session.
! The ASAM-ASAP3 interface can be adjusted in a way that it does not send an
immediate acknowledge back after each received command. This can be changed
from the “Options/General/Send Acknowledge” settings. Be aware that this option is
not taken into account if you choose Network Communication along with the “Use fast
socket communication” option.
! For serial connections, the reaction on a not completely received command can be
adjusted via the registry. It offers the possibility to set a value for the time-out, after
which an error shall be regarded.
! In addition to the EXIT command, you have the possibility to stop an ASAP3 session in
the ASAM-ASAP3 interface. This releases allocated resources (LUNs, Kf-Nr, ...).
8
INCA ASAM ASAP3 Interface Overview
2
User Interface
The ASAM-MCD-3MC interface implementation displays an own window on the screen. The
last used window positions are saved in the registry.
2.1
ASAM MCD-3MC 4 INCA Interface Window (ASAM-ASAP3 server GUI)
In the status bar, information about the connection is displayed. This comprises information
about the state (Online, Offline), the selected serial port and the selected baud rate. During
receiving or transmitting the data the symbols ‘Rx’ and ‘Tx’ indicate this activity.
The window can be displayed permanently in the topmost position; the option is saved in
the registry.
2.2
The Toolbar
The toolbar on top of the viewer window gives fast access to all essential menu commands
of the ASAM-ASAP3 interface.
2.3
ASAM-ASAP3 Status Icon in Taskbar
In the system tray an ASAM-ASAP3 icon indicating the communication state is shown. The
signs for transmit (Tx) and receive (Rx) are dark grey, as long as the command INIT hasn’t
been sent yet. After this, the signs are displayed in white color. Transmission is shown by
red flushing.
User Interface
9
2.4
Communication Options
The following dialog box is displayed when the opening of a COM port or a network interface
failed. This can happen during the start of the ASAM-ASAP3 interface, when it automatically
tries to setup communication with the saved parameters. It can also happen when reestablishing the connection with other communication parameters.
The following dialog box is used to re-establish the connection (with different
communication parameters) after manually breaking the connection with the menu
command ‘Break Connection’.
10
User Interface
2.5
Logging in the Interface Window
Received commands are displayed in blue color. The answer of a command is displayed in
black color. Error messages are displayed in red. The last 1000 lines are buffered for display
in the window.
It is possible to reset the log window via the menu option File|Clear Window. Furthermore it
is possible to select one or more lines with the mouse or all lines with CTRL+A (Keyboard) or
via the Menu (Edit|Select All). A selection can be copied to the clipboard with CTRL+C
(Keyboard) or via the Menu (Edit|Copy) and then be pasted into any text editor.
Each new command line contains a timestamp with a precision of 1µs.
User Interface
11
2.6
Options
The options can be modified by a tabbed dialog with the following sections.
2.6.1
General Options
Logging
The user can select whether he wants to Disable Logging (for fastest operation), Log only to
screen, Log to screen and file or Log only to file.
The maximum size of the log file can be adjusted with the field Max log file size. The given
amount times 1024 is the maximum log file size in bytes.
If Log to screen and file or Log only to file is selected, the logged data is also written to the
file ASAP3.LOG in the ASAP3 log directory, which is located below the INCA log directory.
The file is created, if not yet existent. Otherwise the new data is appended to the file. The
log file hast to be deleted by the user if not needed anymore. Logging to file will stop
automatically if not more than 1MB free disk space is available.
Logging level
The user can select whether he wants to log Only Errors, only the Commands, or to perform
a Full logging which displays also the parameters of the commands and answers.
Further options
If Update LED Indicators is selected the LED’s in the system tray and the indicators in the
status bar will be updated when sending or receiving a telegram, otherwise not. This option
improves performance if disabled.
12
User Interface
Selecting Send Acknowledge causes the ASAM-ASAP3 interface to send an acknowledge
after each command it received successfully. The acknowledge is defined with the status
code $AAAA.
If Use database names in ‘SELECT / DEFINE DESCRIPTION FILE AND BINARY FILE’ is
selected, parameters in these commands are interpreted as locations within the INCA
database instead of names within the PCs file system.
If Data Download at ‘Select Description and Binary File’ is selected, the data is automatically
downloaded to the ECU.
If Data Download at ‘Select Description and Binary File’ is selected, you can choose the
option Create New DS at download within MCS. If enabled, INCA creates a new data set into
which it imports the hex file. If disabled, INCA overwrites the current data set with the
imported data.
If Labels are case sensitive is set, labels differing only in case are treated as different.
Load differences after switching ignition off/on means that CAN ECUs, which loose their
emulation memory contents during power down, are automatically reinitialized with the PCs
calibration data by INCA after ignition is switched on.
If Include timestamp in recorder results is selected, every call of GET RECORDER RESULTS
(Command 46) will return an additional channel with the label “_time_”, with the timestamp
in ms in float format.
2.6.2
Map Editor Options
The command PUT LOOKUP TABLE TO AP-S contains besides the data for the map also data
for the axes. The user can setup, whether this data for the axes shall be ignored or all the
remaining maps shall be used without interpolation.
User Interface
13
The default is Use axes values without interpolation of remaining maps.
If Show edited values is checked, a view is opened for the selected maps or parameters.
If Use hard bound limitation is checked and a value of a calibration object, which has to be
set, is outside the weak bounds, the weak bounds of the object will be set to the hard
bounds. This option allows using the complete range of the hard bounds. The default is that
this option is not set, which means that the weak bounds will be used for limitation. If in
that case a value outside the weak bounds shall be set, it will be set to the upper or lower
weak bound automatically. Additionally the hard bounds (Min./Max. values) will be returned
when getting the values of a calibration object via ASAM-ASAP3.
2.6.3
Online Options
Going Online
When the command INIT is sent, the ASAM-ASAP3 can modify the online state of INCA in
the following way:
Don’t change online state or Switch MC-S to offline (measurement and ECU calibration
access is stopped) Switch MC-S to online (measurement and ECU calibration access is
started).
Show measured values
If Show measured values is checked, a view is opened for the selected online values.
Working Point Measurements for Characteristics
This option enables or disables the working point functionality which is provided by the
EXTENDED GetWorkingPoint command. In case the functionality is disabled, the EXTENDED
14
User Interface
GetWorkingPoint command will issue an error in case it is executed. If the option is
changed, it has only effect on newly selected characteristics, so it is a good strategy to set
this option before session start.
2.6.4
Recorder Options
By default the results of every recorder measurement are stored in an MDF (=Measure Data
Format) file. With the option Save recorder files additionally in the following format it is
possible to store every measurement in an alternative format. This is always done
additionally to the MDF format, i.e. the MDF file is always written, but if this option is
selected, the measurement is additionally stored in another format of choice.
Background operation of load/save recorder file
!
!
!
!
!
!
ACTIVATE RECORDER
GET RECORDER STATUS
GET RECORDER RESULTS HEADER
GET RECORDERRESULTS
SAVE RECORDER FILE
LOAD RECORDER FILE
The error code returned in this case will be either
“60832 Command not possible because a 'LOAD RECORDER FILE' command is still running in
the background!”
or
User Interface
15
“60833 Command not possible because a 'SAVE RECORDER FILE' command is still running in
the background!”
depending on whether a load or a save operation is in progress.
2.6.5
View Options
With Change Font the user can select the font (-size) used for the output in the log window.
Show ASAM-3MC background logo in output window is helpful for systems with slow graphic
adapters, if the scrolling of the log window is very slow. In this case these options should be
unchecked.
Show Splash window on startup enables the splash window (default).
2.6.6
Compatibility Options
The following options have been added to allow for greatest compatibility with the previous
ASAM-ASAP3 implementations of early INCA versions.
16
User Interface
The option Ignore Protocol Version from IDENTIFY command (allows usage of protocol
version 2.1 commands with protocol version 2.0 and INIT while connection is established)
allows the AuSy to execute protocol version 2.1 commands while identifying itself with
protocol version 2.0.
The option Start generated LUN numbers with 0 will force the SELECT DESCRIPTION FILE
AND BINARY FILE command and the DEFINE DESCRIPTION FILE AND BINARY FILE
command to generate LUN numbers starting with 0 and increased by one. Without this
option set, the LUN numbers are starting with 59 and increased by 29 to simulate “arbitrary”
numbers.
The option Generate ‘Invalid Measurement’ for current value if timestamp of current and last
measure value are equal checks if the current measure value is really a new one, and not
the last one that was send repeatedly because no newer values are available. By default
INCA repeats the latest value until a new one is available. If this checkmark is set, the
system reports ‘Invalid Measurement’ if there is no new measure value.
The option Generate ‘Invalid Measurement during the device re-initialization is off by default,
which means that during a device re-initialization the last valid value is (repeatedly)
returned. If this value is checked, the value for ‘Invalid Measurement’ is returned during
every device re-initialization.
The option Generate ‘Invalid Measurement’ if one of the following is true allows to generate
an invalid measurement if the measurement data isn’t updated for a certain amount of time.
Up that time the last valid value is returned. Basically the option is differs between 2 raster
types:
! Equidistant rasters:
If the delta between the current and the last timestamp exceeds n times the current
raster size an invalid measurement value is returned. Example: The value is wired in a
User Interface
17
50ms raster and the option is set to 5. In this case after a time of 5 x 50ms = 250ms
an invalid measurement is returned.
! Event synchronous rasters:
If the delta between the current and the last timestamp exceeds a certain amount of
time in ms an invalid measurement is returned.
Additionally, it is possible to generate a timeout on the client side with the option Generate
timeout instead of ‘Invalid Measurement’. This option is valid for both raster types.
Attention
All these options are only valid during normal operation. After a measurement was started the
system always waits up to 1000ms for the first data. If after 1000ms no new data is available the
system returns with an INVALID MEASUREMENT error. Once valid data is available, the system will
react as defined with the settings before.
With the option Use old measure mode it is possible to switch back to the measurement
behavior of INCA ASAP3 implementation before INCA 5.3. If this option is switched off, the
client is able to retrieve all available measurement data, as long as he polls fast enough, but
in this case every data has a fixed delay of n+50ms. Please take a look at chapter 2.8 for
more information on measurement modes.
The option Limit number of variables/online window limits the number of measurement
variables that can be displayed in one experiment view. After that number a new view is
opened when adding new measurement variables.
2.7
Usage of ASAP3.INI
With the menu option ‘Extras|Export Current Options…’ you can save the current settings to
an ASAP3.INI file.
The settings in the asap3.ini file can be used with the first start of the ASAM ASAP3 interface
as default settings. To enable this function, the asap3.ini file must be copied into the INCA
data directory (e.g. \ETASData\INCAx.y). At the end of the first run of the ASAM ASAP3
interface, the settings are stored in the registry:
HKEY_CURRENT_USER\Software\ETAS\INCA\x.y\ASAP3
All later runs of ASAM ASAP3 will load and store the settings at this registry location.
This way, every user has its own ASAM-ASAP3 settings.
If the settings later shall be replaced again with an ASAP3.INI file, the ASAM ASAP3 registry
settings have to be deleted (HKEY_CURRENT_USER\Software\ETAS\INCA\x.y\ASAP3 should
not exist anymore). This forces ASAM ASAP3 to reload the settings from ASAP3.INI this
time, but again only once.
2.8
Measurement modes
As already mentioned in section 2.6.6 there are 2 possible measurement modes. The former
one witch has a fixed update rate of 100ms that has been kept for compatibility reasons and
a new one that enables the client to get all available data.
2.8.1
Old measure mode (Compatibility mode)
This measurement mode uses a fixed update rate of 100ms (INCA target server update rate
in default “High bandwidth” mode). If a client polls he always gets the latest available value.
Polling at rates > 10Hz does not really make sense, as in this case only the latest available
value is repeatedly handed to the client. The following overview explains the behavior:
18
User Interface
The data at the client side are delayed, depending on when the client calls GET ONLINE
VALUE. The delay is in the range of 0 - 100ms. Therefore, it is recommended for a client to
call at GET ONLINE VALUE at a fixed rate of 10Hz for best performance. Higher rates will
result in higher workload, but not in more precise results.
Since INCA 5.3 it is possible to switch between 2 operating modes of the target server:
! High bandwidth mode (the default mode, as in all INCA versions < 5.3, internal
update rate: 100ms)
! High performance mode (an alternative mode for INCA 5.3 and above, internal update
rate: xxms)
All things said so far are also valid for the high performance mode, with the only difference
that the 100ms update rate is changed to xxms and all timings will change accordingly.
But even with the high performance mode is not possible to get all available values of a
raster that is faster than the update rate of xxms.
To make it possible to get all values of faster signal a new measure mode was introduced,
which is explained in the following section.
2.8.2
New measure mode
With measurement signals at rates faster than the rate of the selected target server mode
(for all INCA versions < 5.3 this is 100ms), it is necessary to be able to poll at higher rates.
Therefore, a new measurement mode was introduced that allows a client to get the ‘in
between’ data. As the target server delivers the data in 100ms blocks (INCA target server
update rate in default “High bandwidth” mode), the data is buffered in the ASAM ASAP3
server of INCA and then returned to the client depending on ‘when’ it calls GET ONLINE
VALUE. The following overview explains again the behavior:
User Interface
19
If the user wires a 10ms signal and calls at a certain time GET ONLINE VALUE he gets the
value with a fixed delay of 150ms. If he calls GET ONLINE VALUE 10 times in 100ms, i.e.
uses a polling rate of 100Hz, he will get all 10 values that were recorded in that frame.
Since INCA 5.3 it is possible to switch between 2 operating modes of the target server:
! High bandwidth mode (the default mode, as in all INCA versions < 5.3, fixed delay at
internal update rate + 50ms = 100+50ms = 150ms as in the overview)
! High performance mode (an alternative mode for INCA 5.3 and above, fixed delay at
internal update rate + 50ms = xx+50ms = xxms)
Attention
In order to be able to get all values of faster signals it is necessary that the test stand is connected
through Ethernet (serial is too slow) and that the server and client (test stand) PC are fast enough to
handle the higher workload that is caused by higher polling rates.
Note
Everything said about GET ONLINE VALUE is also true for the Command GET USER DEFINED
VALUES.
2.9
Search Mechanism for ASAM ASAP3 Variables
Some ASAM ASAP3 commands need a variable name or a variable name list as parameters.
ASAM ASAP3 gets these variables with the following mechanism:
I. In most cases the user/automation system knows the variable name and the LUN of
the device the variable belongs to. In this case the user takes the LUN and the variable
name as parameters.
II. If the user/AuSy doesn’t know the LUN (in this case he sets the LUN parameter to
$FFFF) the list of all devices is checked, whether one of the devices contains the
variable.
III. If the user/AuSy has different variables with different LUN, every variable should have
the following form: “variable\device”. If in some variables the device name is missing,
it is treated like in case I or II.
2.10
Realization of ASAM ASAP3 Commands in INCA
This chapter describes how ASAM ASAP3 commands are executed in INCA.
In the case of unimplemented commands the error code $5656 is returned.
20
User Interface
Error codes:
There are several categories of errors:
! Errors in the communication between ASAM-ASAP3 server and INCA
! Command specific errors (exceeding of limits, invalid handles (LUN, Map numbers),...)
! INCA specific errors like internal table overflows, declaration errors in description file,
general communication errors between ETAS HW and external devices and so on;
these errors are returned via ASAM ASAP3 with a general description (e.g. command
failed), but are logged in more detail in the INCA monitor window.
Attention:
! INCA can work with 32bit integer values. In ASAM ASAP3, a four-byte float format is
used, which has a precision of 7 - 8 digits. The 32bit integer values have a precision
of 10 digits. Therefore, you will loose precision of data when dealing with 32bit
variables.
Most of the EXTENDED commands of ASAM ASAP3 V2.1.x, which would solve the
previously mentioned problem, are not yet implemented in the current version.
! Invalid measurements will not be indicated to the AuSy with the current
implementation of the tool chain. Only in some cases where the ASAM ASAP3 server
cannot get correct data from INCA, the invalid measurement value will be returned.
! The new behavior of default LUN = 0 is implemented like this: LUN 0 will always
access the first ECU in the current INCA Workspace.
! Download to some K-Line devices fails because they do not support the download of
the full calibration area. Disable download via ASAM ASAP3 and instead do a
differential download directly in the INCA UI in this cases before the ASAP3 session is
started.
! The commands SELECT DESCRIPTION FILE AND BINARY FILE and DEFINE
DESCRIPTION FILE AND BINARY FILE are now able to load a different dataset into
the ECU. Only the description file is used to select the device. If you want to use two
identical ECUs, you cannot distinguish them by the binary file. Therefore you have to
create a copy of the description file with a different name and create a new project
within INCA with this renamed description file. Then you can use this two different
description file names within ASAM ASAP3 to distinguish the two ECUs.
! If a calibration object in INCA will be changed and this object exists also for a second
ECU, it will automatically be changed for both ECUs if Group Device was selected
before. This feature is also available in ASAM ASAP3.
! Switching Online does not automatically start the measurement. The measurement is
started if an ASAM ASAP3 command that requires a running measurement is issued.
Nevertheless, the SWITCHING OFFLINE/ONLINE command must still be issued in
advance, because the access to the ECU must already be provided when starting a
measurement.
The measurement is stopped automatically when a command that requires the
measurement to be stopped is issued. This will not be done in case a flight recorder is
running. In this case, an error message is returned.
! Normally, the IDENTIFY command is required to use ASAM ASAP3 Version 2.1.
Without issuing the IDENTIFY, a MCD system is regarded as a V 2.0 system.
In the INCA ASAM ASAP3 server, this behavior can be changed by an option in the
“Compatibility” settings. The option allows ignoring the protocol version at all and
allowing the V2.1 command even if no IDENTIFY command was sent. Nevertheless,
when using the IDENTIFY command with version 2.0, also version 2.0 is reported
back in the telegram answer.
2.11
Performance considerations
There are several things that should be taken into consideration, to get the maximum
performance when working with INCA’s ASAM ASAP3 server.
! First of all be sure to use the maximum available speed of the serial interface that is
available at the test stand (up to 115200 baud).
! To increase speed when adding new variables with DEFINE RECORDER PARAMETERS
(Command 41) and PARAMETER FOR VALUE ACQUISITION (Command 12) be sure,
User Interface
21
that in the General options dialog (section 2.6.1) the parameter ‘Labels are case
sensitive’ is checked. Uncheck this option only if you really need case insensitive
variable names.
Another possibility to increase speed, especially on slower PCs, is to turn off logging in the
view window in the General options dialog (section 2.6.1). To do this, select the item ‘Only
errors’ in the group ‘Logging’. This will increase the speed especially for repeatedly called
commands like GET ONLINE VALUE (Command 19), GET USER DEFINED VALUE (Command
21) or GET RECORDER RESULTS (Command 46).
In cases where logging cannot be disabled, it can be made faster by switching off the ‘Show
ASAM-3MC background logo in output window’ check in the “View” options tab. The
disabling of the ‘Update LED Indicators’ in the “General” options tab also increases speed.
2.12
FULI – Fast Upper Level Interface (INCA-MCE)
The FULI configuration enables the selection of measurements and calibration for an
alternative data transmission path beside the standard ASAM MCD-3MC interfaces. This is
used to configure the measurements and calibration for the ETAS INCA-MCE product.
For INCA’s ASAM ASAP3 interface a separate LUN for each standard device has to be used
for the transmission via FULI link (see chapter 3.5 and 3.6).
If a measurement value is wired via such a FULI LUN, the label is registered for the FULI
device and will be transported via an alternative data transmission link (i.e. INCA-MCE
EtherCAT/iLinkRT).
New wiring rules apply. (", # = sequence order of execution)
New wiring rules (Add):
A (Norm)
A (FULI)
" measurement
Action
" wire normal
" measurement
# measurement
" wire normal, # enable FULI
# measurement
" measurement
" wire normal, enable FULI
" measurement
" wire normal, enable FULI
A (FULI)
Action
New wiring rules (Remove):
A (Norm)
" measurement
" remove
" measurement
# measurement
# disable FULI, remove
# measurement
" measurement
" disable FULI, # remove
" measurement
" disable FULI, remove
GET ONLINE VALUE returns the values of all wired variables, despite of FULI or not.
Wiring of FULI variables in the recorder is not supported.
Maps and curves of a FULI-LUN are registered for FULI access when the corresponding
SELECT LOOKUP TABLE command is executed. Scalar parameters are registered when they
are actively read the first time with a FULI-LUN. Registration needs to be done before going
online with the ECU, because when the ECU is online, no change of the registration is
possible any more – the configuration is sent to the FULI device just before going online.
The AuSy must be aware of this and must create all map handles and access all scalar
parameters that it wants to be available at the FULI device before it switches online. This, in
addition, means that the FULI device will only receive correct data while INCA is in online
state. In offline State, the INCA configuration and the FULI configuration might be different.
22
User Interface
3
Implementation Notes for Commands
3.1
EMERGENCY
Command:
Answer:
COMMAND: 1
Entry
Data type
Event
WORD
Entry
Data type
No data
-
All connected ECU’s in the current INCA Workspace, which support page switching, are
switched to the Reference Page. Event has to be set to 0.
Note
INIT must be executed before EMERGENCY can be executed.
Error codes:
INCA specific errors
Not yet identified
Only Event 0 allowed
3.2
INIT
Command:
Answer:
COMMAND: 2
Entry
Data type
No data
-
Entry
Data type
No data
-
When an INIT is received although there was already an INIT sent, the ASAM ASAP3 session
is reinitialized. This means, that allocated resources are freed; LUNs, map numbers and
other implicit states are no longer valid; graphic mode and case sensitivity of labels are reset
to the default specified in the options, a running flight recording is cancelled. Objects in the
experiment that have been there already before ASAM ASAP3 was started stay in the
experiment.
If specified in the settings, INCA is put into online state.
Attention: Make sure that INCA is already using the right workspace/project, because with
ASAM ASAP3 it is not possible to change projects.
Error codes:
3.3
INCA specific errors
IDENTIFY
Command:
Answer:
COMMAND: 20
Entry
Data type
Protocol version number
WORD
AuSy name
STRING
Entry
Data type
Protocol version number
WORD
Implementation Notes for Commands
23
MC system name
STRING
The current implementation of the ASAP3 server requires an ASAM ASAP3 V2.x
implementation of the client (test bed). The interface itself works by default according to the
ASAM ASAP3 V2.1.1 specification. Therefore it returns the value 2.1 (→ 513) and the current
version string of INCA (e.g. "INCA V7.0.0 Protocol Version 2.1"}).
The returned version number is 2.1 for all cases where the AuSy identifies itself using
version 2.1 or above. If the AuSy identifies itself using V2.0, the interface adjusts itself to
ASAM ASAP3 V2.0 functionality and returns V2.0. If the interface works in V2.0 mode, all
commands/behavior newly defined in V2.1 are not available to the AuSy and will result in
error messages if requested.
In the case that this command wasn't issued by the client, all following commands, except
for INIT, are answered with the error code ‘This command requires at least Protocol Version
2.1!’.
! EXIT
! DEFINE DESCRIPTION FILE AND BINARY FILE
! GET USER DEFINED VALUE
! GET USER DEFINED VALUE LIST
! QUERY AVAILABLE SERVICES
! GET SERVICE INFO
! EXECUTE SERVICE
The INIT command with LUN equal to 0 is not supported if no IDENTIFY command was
issued.
Error codes:
INCA specific errors
Only Event 0 allowed
Already Identified
Command order error! Need command 2 before!
3.4
EXIT
Command:
Answer:
COMMAND: 50
Entry
Data type
No data
-
Entry
Data type
No data
-
All resources that were used by the AuSy will be released in INCA. That means, that all
inserted online/flight recorder variables and all opened editor windows caused by the AuSy
will be removed/closed.
When flight recorder was used by ASAM ASAP3, just the variables inserted by ASAP3 will be
removed; this command will not restore the previous state before using ASAM ASAP3.
This command works the same as the menu item ‘ASAP3 Stop!’ in the ASAM ASAP3 server
window.
Error codes:
Missing INIT (command 2)
Only Event 0 allowed
24
Implementation Notes for Commands
3.5
SELECT DESCRIPTION-FILE AND BINARY FILE
Command:
Answer:
COMMAND: 3
Entry
Data type
Description file name
STRING
Binary file name
STRING
Destination
WORD
Entry
Data type
Emulator LUN
WORD
Depending on the option Use database names in ‘SELECT / DEFINE DESCRIPTION FILE AND
BINARY FILE’, the parameters in this command are treated differently. If the option is
checked, the names are treated as database names: The description file name is interpreted
as a path and a database item name for the project item in the INCA database, e.g.
DEFAULT\0400. The same holds true for the Binary File Name, but here the path is
interpreted only within the INCA project item, e.g. 0400\0400_1. The following picture
shows how this example looks like in the INCA GUI (left side Description File Name, right
side Binary File Name):
The text further down in this chapter describes the behavior in the case this option is
deselected.
Binary File Name has to reference a valid calibration data file, if the option Data Download at
‘Select Description And Binary File’ is enabled. Either it contains only the filename or it contains
also an absolute, full specified path to the file. The default file extension of “.hex” can be
overridden. In case the mentioned option is not set, the file needs not to exist on the hard
drive, only the INCA database is searched for the name. But the file name must still match
the name of the file, which was used when reading the data file.
Description File Name has to reference a valid ASAP2 file. Either it contains only the filename
or it contains also an absolute, fully specified path to the file. The default file extension of
“.a2l” can be overridden.
Description File Name is only used to select a specific device. Binary File Name can be used
to load a different binary file with this command. The selection algorithm for the device first
compares Description File Name to all installed devices. If no one matches, it repeats the
comparison with only the filename without path of both the required description file and the
Implementation Notes for Commands
25
description file loaded in each device. If this also fails, the same step is done with the base
name (filename without extension) only. If this doesn’t succeed, an error is returned.
If the download option is activated and the binary file contains no fully qualified path name,
the file is searched in the same directory from which the hex file of the current data set was
read. If the hex file cannot be found there, ASAM ASAP3 server searches for the file in the
hex file directory which is specified in the user settings. The “current dataset” in this context
means the dataset that is currently selected in the device; that is, the one that can be
chosen in the menu ‘Dataset|Change Working Data…’.
The value for Destination determines the way an ECU is accessed. The currently supported
values are:
Destination
Code
Destination
0x0
any device (the order the devices are tried is the order in which they are defined in
the Workspace)
0x1
ETK
0x2
CAN (CCP-Protocol)
0x3
K-Line (KWP2000, McMess)
0x8000
AUXIN
0x8001
CAN-Monitoring
0x8002
FlexRay-Monitoring
0x8003
XCP (onCAN, onEthernet, onFlexRay,…)
0x8004
CalcDev
0x8005
LIN-Monitoring
0x8006
ODX-Link
0x8100
any FULI device (the order the devices are tried is the order in which they are
defined in the Workspace)
0x8101
ETK via FULI
0x8102
CAN (CCP-Protocol) via FULI
0x8203
XCP (onCAN, onEthernet, onFlexRay,…) via FULI
The calibration data are loaded and sent to the ECU by this command if the option Data
Download at ‘Select Description And Binary File’ is enabled.
If the option Data Download at ‘Select Description And Binary File’ is enabled, this command
loads the specified calibration data in every case (even if it was already loaded into the PC
before starting ASAM-ASAP3 server). The previously loaded calibration data is not saved
(even if it was modified).
This command cannot be issued a second time after the INIT command, when the resulting
device would be the same; an error message indicates this.
The ECU for this LUN is switched to the Working Page if more than one calibration page is
available in the project used for this ECU.
Error codes:
INCA specific errors
Missing INIT (command 2)
Unable to change the "Load differences after switching ignition
off/on" option.
26
Implementation Notes for Commands
3.6
DEFINE DESCRIPTION-FILE AND BINARY FILE
Command:
Answer:
COMMAND: 30
Entry
Data type
Description file name
STRING
Program code (+Calibration data) file
name
STRING
Calibration data file name
STRING
Destination
WORD
Mode
WORD
Entry
Data type
Emulator LUN
WORD
Description file name
STRING
Program code (+Calibration data) file
name
STRING
Calibration data file name
STRING
Depending on the option Use database names in ‘SELECT / DEFINE DESCRIPTION FILE AND
BINARY FILE’, the parameters in this command are treated differently. If the option is
checked, the names are treated as database names: The description file name is interpreted
as a path and a database item name for the project item in the INCA database, e.g.
DEFAULT\0400. The same holds true for the Binary File Name, but here the path is
interpreted only within the INCA project item, e.g. 0400\0400_1. The following picture
shows how this example looks like in the INCA GUI (left side Description File Name, right
side Binary File Name):
The text further down in this chapter describes the behavior in the case this option is
deselected.
Program code file name and Calibration data file name have to reference a valid program
file/calibration data file, if the option “Data Download at ‘Select Description And Binary File’ “
is enabled. Either they contain only the filename or they contain an absolute, fully specified
path to the file. The default file extension of “.hex” can be overridden. In case the
mentioned option is not set, the files don’t need to exist on the hard drive, only the INCA
Implementation Notes for Commands
27
database is searched for the name. But the file names must still match the names of the
files which were used during data import.
Description File Name has to reference a valid ASAP2 file. Either it contains only the filename
or it contains also an absolute, fully specified path of the file. The default file extension of
“.a2l” can be overridden. The file handling is the same as for the Binary File.
Description File Name is only used to select a specific device. Binary File Name can be used
to load a different binary file with this command. The selection algorithm for the device first
compares Description File Name to all installed devices. If no one matches, it repeats the
comparison with only the filename without path of both the required description file and the
description file loaded in each device. If this also fails, the same step is done with the base
name (filename without extension) only. If this doesn’t succeed, an error is returned.
If a Mode value of 2 is used and the binary file contains no fully qualified path name, the file
is searched in the same directory from which the hex file of the current data set was read. If
the hex file cannot be found there, the ASAM ASAP3 server searches for the file in the hex
file directory which is specified in the user settings. The “current data set” in this context
means the dataset that is currently selected in the device; that is, the one that can be
chosen with the menu ‘Dataset|Change Working Data…’.
The field for Program code file name will be used if Calibration data file name is empty,
otherwise it is ignored.
The field for Calibration data file name can be blank. In this case, the LUN will directly refer
to the first ECU in the INCA Workspace, which matches the description file name. If the
Description file name is empty, too, the first ECU in the Workspace will be used.
The value for Destination determines the way an ECU is accessed. The currently supported
values are:
Destination
Code
Destination
0x0
any device (the order the devices are tried is the order in which they are defined in
the Workspace)
0x1
ETK
0x2
CAN (CCP-Protocol)
0x3
K-Line (KWP2000, McMess)
0x8000
AUXIN
0x8001
CAN-Monitoring
0x8002
FlexRay-Monitoring
0x8003
XCP (onCAN, onEthernet, onFlexRay,…)
0x8004
CalcDev
0x8005
LIN-Monitoring
0x8006
ODX-Link
0x8100
any FULI device (the order the devices are tried is the order in which they are
defined in the Workspace)
0x8101
ETK via FULI
0x8102
CAN (CCP-Protocol) via FULI
0x8203
XCP (onCAN, onEthernet, onFlexRay,…) via FULI
With INCA, mode values of 1 and 3 will not be supported, because the program is not
supported.
With mode equal to 2, the calibration data are loaded and sent to the ECU by this command.
This command loads the specified calibration data in every case (even if it was already
loaded into the PC before starting ASAM ASAP3 server). The previously loaded calibration
data isn’t saved (even if it was modified).
28
Implementation Notes for Commands
This command cannot be issued a second time after the INIT command, if the resulting
device is the same; an error message indicates this.
The returned description and calibration data file name will be the name extracted from the
device. This is the original file name, which was used during import of the project and
calibration data.
The returned file name of calibration file will ALWAYS have an absolute pathname; i.e. it will
contain drive, path and file name.
The ECU for this LUN is switched to the Working Page if more than one calibration page is
available in the project used for this ECU.
Extended support for measurement-only devices, e.g. ADSCAN, CalcDev, CAN-Monitoring,
FlexRay Monitoring
To be able to read in measurement values, the following command will select a specific
measurement device and will provide a LUN for it:
Entry
Data type
Value
Description file name
STRING
“_AUXIN_”
Program code (+Calibration data) file
name
STRING
<device name>
Calibration data file name
STRING
“”
Destination
WORD
0x8000
Mode
WORD
0
Entry
Data type
Value
Emulator LUN
WORD
<dynamic value>
Description file name
STRING
“_AUXIN_”
Program code (+Calibration data) file
name
STRING
<device name>
Calibration data file name
STRING
“”
The answer for this command will be:
Device name refers to the logical device name used within INCA.
This command has to be executed for every single measurement device that shall be
accessed by the AuSy.
The returned LUN can be used with every command that deals with online/recorder
variables.
This mechanism is available in addition to the second way to access measurement values,
where you simply add the measurement device name at the end of a measurement value
name with a LUN which was requested via the standard way.
Error codes:
INCA specific errors
Missing INIT (command 2)
There is already a LUN for the device with this description and
binary file assigned!
Invalid value for 'Mode'!
Invalid value for 'Destination'!
No device with given name found
Only the modes 0 and 2 are supported
Implementation Notes for Commands
29
Unable to change the "Load differences after switching ignition
off/on" option.
Examples
1. To create a LUN for the INCA CalcDev device, use the DEFINE DESCRIPTION AND
BINARY FILE command with the following parameters:
Entry
Data type
Value
Description file name
STRING
“_AUXIN_”
Program code (+Calibration data) file
name
STRING
“CalcDev”
Calibration data file name
STRING
“”
Destination
WORD
0x8000
Mode
WORD
0
2. For CAN Monitoring, use the name of the respective device instead of “CalcDev”, e.g.
“CAN-Monitoring:1”, like in the following command:
Entry
Data type
Value
Description file name
STRING
“_AUXIN_”
Program code (+Calibration data) file
name
STRING
“CAN-Monitoring:1”
Calibration data file name
STRING
“”
Destination
WORD
0x8000
Mode
WORD
0
This method works for all devices that allow at least for measurement.
3.7
COPY BINARY FILE
Command:
Entry
Data type
Target
WORD (see Target/Source Code)
Source
WORD (see Target/Source Code)
Emulator LUN
WORD
Entry
Data type
No data
-
ASAP3 definition:
INCA specific assignment:
1
EPROM
currently not implemented
(we will not read/write
EPROMs/FLASH)
2
FILE
calibration data file (hex)
3
Virtual Emulator Board
PC (INCA database)
4
Physical Emulator Board
emulation memory (e.g. ETK)
Answer:
Target / Source Code:
30
COMMAND: 4
Implementation Notes for Commands
The following transitions are possible:
Transitions:
Action:
3→2
Save binary file
4→2
Receive binary file + Save binary file
4→3
Receive binary file
2→3
Load binary file
3→4
Send binary file
2→4
Load & Send binary file
Load binary file: Loads the specified calibration data in every case (even if it was already
loaded onto the PC before). The previously loaded calibration data is not saved (even if it
was modified).
Save binary file: An existing calibration data file is overwritten without an error message.
Trying to overwrite read-only files causes an error message.
Error codes:
INCA specific errors
Invalid LUN
Invalid number for Source/Destination
3.8
CHANGE BINARY FILE NAME
Command:
Answer:
COMMAND: 5
Entry
Data type
New Binary File Name
STRING
Emulator LUN
WORD
Entry
Data type
No data
-
The new file name is saved at first in a LUN specific memory location in the ASAM ASAP3
interface. With the command COPY BINARY FILE with the transitions 4 → 2 / 3 → 2 the
saved file name is used to store the calibration data. The transitions 2 → 3 / 2 → 4 can be
used to load another calibration data file.
The client (test stand) has to make sure, that the given file name is a valid OS file name; if
directory parts are included, the directories must already exist. Relative pathnames are not
allowed, they must always be absolute. The standard calibration data directory is the
directory where the A2L description file is located. If the calibration file name contains no
path, this standard directory is used as path.
Error codes:
3.9
Invalid LUN
SELECT LOOKUP TABLE
Command:
Answer:
COMMAND: 6
Entry
Data type
Emulator LUN
WORD
Map name
STRING
Entry
Data type
Map number
WORD
y-Dimension (ny)
WORD
Implementation Notes for Commands
31
x-Dimension (nx)
WORD
Address (logging info)
WORD
As map name, the internal item name is expected. Valid map types for this command are
1dim and 2dim maps or arrays respectively matrices. Names of set points are rejected. If the
option “Show edited values” is set or the command SET GRAPHIC MODE ON AP-S was used
before, the map is opened within INCA if it was not yet opened.
With 1dim maps the value for y-Dim is 1. The address field contains the lower 16 bit of the
address read from the description file. The maximal extent for a dimension is 1025. In total
a command must not exceed 65534 bytes!
Note
Together with 1 dim / 2 dim maps the associated online values of their axis are always wired. This is
necessary for the extended command GET WORKING POINT (Command 42001). They have the
same raster priority than values wired with PARAMETER FOR VALUE ACQUISITION (Command 12)
and therefore influence the raster of already wired online values. To avoid this it is necessary to call
the command SELECT LOOKUP TABLE always before the command PARAMETER FOR VALUE
ACQUISITON.
Error codes:
INCA communication errors
Invalid LUN
LUN of AUXIN not allowed
Map name not found
No 1dim or 2dim map
Access of an axis failed
Map dimension has exceeded
3.10
PUT LOOKUP TABLE TO AP-S
Command:
32
COMMAND: 7
Entry
Data type
Map number
WORD
Map length
WORD
Y(1)
REAL
Y(2)
REAL
:
:
Y(ny)
REAL
X(1)
REAL
X(2)
REAL
:
:
X(nx)
REAL
Minimum Z(i,j)
REAL
Maximum Z(i,j)
REAL
Minimum Increment
REAL
Z[X(1),Y(1)]
REAL
Z[X(2),Y(1)]
REAL
Z[X(3),Y(1)]
REAL
Implementation Notes for Commands
Answer:
:
:
Z[X(2),Y(5)]
REAL
:
:
Entry
Data type
No data
-
The values received from the client are adjusted according to the physical conversion of the
description file (not to the value range of the data type, which can be bigger).
In off-line mode, the changes apply only to the data on the PC. They will become effective
for the ECU as soon as the system goes on-line.
There are two levels of dealing with axes: ignoring values for axes and transmitting axes
without interpolation of the remaining maps that are using these axes. The user can decide
between these options in the Extras/Options/Map Editor dialog box. The axes values for
arrays and matrices will be ignored.
The value of Map Length has to be calculated according to the ASAM ASAP3 specification.
Every time, the complete map has to be transmitted; no elements at the end of the data
block are allowed to be omitted.
The values in the fields Minimum, Maximum and Minimum Increment are ignored.
It is also possible to use this command for objects with rescale axes (RES_AXIS) and curve
axes (CURVE_AXIS). In this case only the Z-values will be written, the axes values (X/Y) will
be ignored. The command has to be complete concerning the amount of values - this means
that also the values for the axes have to be there even if they will not be used (but e.g. they
can all be zero). Note: No message will be written into the log window which indicates this
behavior.
If a map or an axis is write-protected the values will not be updated in the MC system and a
message will be written to the log window.
Error codes:
INCA communication errors
Invalid map number
Out of memory
Invalid map length value
Values from the MC system can't be interpreted
Values can't be set in the MC system
Values are out of the limits of the data type
3.11
GET LOOKUP TABLE FROM AP-S
Command:
Answer:
COMMAND: 8
Entry
Data type
Map number
WORD
Entry
Data type
Map length
WORD
Y(1)
REAL
Y(2)
REAL
:
:
Y(ny)
REAL
Implementation Notes for Commands
33
X(1)
REAL
X(2)
REAL
:
:
X(nx)
REAL
Minimum Z(i,j)
REAL
Maximum Z(i,j)
REAL
Minimum Increment
REAL
Z[X(1),Y(1)]
REAL
Z[X(2),Y(1)]
REAL
Z[X(3),Y(1)]
REAL
:
:
Z[X(2),Y(5)]
REAL
:
:
Reads the data being located on the PC. The map length is calculated according the ASAM
ASAP3 specification. Always the whole map is transmitted. The values for Minimum and
Maximum are the limits of the conversion, not of the data type. For example, if RPM is
defined as 0h -> 0.0 and 1FE0H -> 8160.0, the values 0.0 and 8160.0 are returned instead
of 0 and 65535 what would be the range of the data type unsigned int. Minimum Increment
is derived from the conversion.
Error codes:
INCA communication errors
Invalid map number
Access of an axis failed
Values from the MC system can't be interpreted
3.12
GET LOOKUP TABLE VALUE
Command:
Answer:
COMMAND: 9
Entry
Data type
Map number
WORD
Y-Index
WORD
X-Index
WORD
Entry
Data type
Value
REAL
Indices are starting at 1.Y-Index is ignored for 1dim maps.
Returns the value being located on the PC.
Error codes:
INCA communication errors
Invalid map number
Index out of limits
Values from the MC system can't be interpreted
34
Implementation Notes for Commands
3.13
INCREASE LOOKUP TABLE
Command:
Answer:
COMMAND: 10
Entry
Data type
Map Number
WORD
Y-Index
WORD
X-Index
WORD
Y-Delta
WORD
X-Delta
WORD
Offset
REAL
Entry
Data type
No data
-
Indices are starting at 1; delta has to be at least 1. Y-Values are ignored for 1dim maps.
The value for Offset can be either positive or negative.
The map values are calculated accordingly and are subsequently subject to limit checks (if a
value exceeds the range of a physical conversion it is limited accordingly) before the
calibration data is modified.
If a map is write-protected the value(s) will not be updated in the MC system and a message
will be written to the log window.
Error codes:
INCA communication errors
Invalid map number
Range error
Values from the MC system can't be interpreted
Values can't be set in the MC system
Values are out of the limits of the data type
3.14
SET LOOKUP TABLE
Command:
Answer:
COMMAND: 11
Entry
Data type
Map number
WORD
Y-Index
WORD
X-Index
WORD
Y-Delta
WORD
X-Delta
WORD
Value
REAL
Entry
Data type
No data
-
Indices are starting at 1; delta has to be at least 1. Y-Values are ignored with 1dim maps.
The map values are set accordingly as far as they don’t exceed the limits of the limit checks
(if a value exceeds the range of a physical conversion it is limited accordingly).
If a map is write-protected the value(s) will not be updated in the MC system and a message
will be written to the log window.
Implementation Notes for Commands
35
Error codes:
INCA communication errors
Invalid map number
Range error
Values from the MC system can't be interpreted
Values can't be set in the MC system
Values are out of the limits of the data type
3.15
PARAMETER FOR VALUE ACQUISITION
Command:
Entry
Data type
Emulator LUN
WORD
Scanning time (ms)
WORD
Number of values
WORD
Name of 1st value
STRING
Name of 2nd value
STRING
.…
.…
Answer:
COMMAND: 12
Entry
Data type
No data
-
Opens aTool API Measurement window, if none was opened before. Inserts the variables
into the window, if not yet inserted. Already existing values will be rejected.
If the number of elements inserted into the current window exceeds the Maximum number
of elements in one measure window that can be configured in the experiment (see menu:
[Components|ASAM-3MC|Options]), a new window is opened.
With Number of values = 0 all online variables, that were inserted by ASAM ASAP3 are
removed from the experiment. Online variables that have been configured before, stay in
the experiment.
It is also possible to use “variable\device”-name instead of variable names only. This allows
wiring of different values with different devices (LUNs) in one step. This is a deviation of
ASAM ASAP3 that allows faster setup of measurements with variables from many different
devices.
Contrary to ASAM ASAP3 the recording type and scanning time of the latest call for a LUN
does not overwrite all former settings for the variables of the same LUN! (This only happens
in certain cases if a variable is added for recording, see Command 41 DEFINE RECORDER
PARAMETERS for more information).
Single variables used in a measurement must not be defined more than once, otherwise
they will be rejected.
If the time raster for the desired scanning time is already full, the nearest free raster is used
to wire the value. If all rasters are used an error is reported.
36
Implementation Notes for Commands
Attention
If a desired time raster is full, adding of new values lasts longer because every action has to be
retried with the next available raster! In the worst case all rasters are checked until an error is
reported.
Contrary to ASAM ASAP3 it is also possible to wire a variable with a synchronous raster. In this case
the scanning time must be set to 0!
If a variable is already wired as user defined value or recorder value, the rate of that value
will override the currently selected one, i.e. our signal is attached to the already wired value.
Only recorder values have higher ‘timing’ priority and would overwrite the existing raster
with the desired one (See Command: DEFINE RECORDER PARAMETERS for more details).
For CAN-Monitoring and CalcDev (calculated signals) devices the scanning time has no
influence, because variables of these devices are always wired in their default raster. In case
of wiring problems, no fallback rewiring is done, as the signals can only be wired in a
specific raster.
In order to wire measurement values in INCA, it is necessary that the measurement is
stopped while doing that. Therefore, the measurement is stopped and restarted again,
which leads to a short interruption of online data (at least 100ms – see Command 19: GET
ONLINE VALUE).
Error codes:
Communication errors
Missing INIT (Command 2)
Missing IDENTIFY (Command 20)
Invalid LUN
Not offline. SWITCHING OFFLINE/ONLINE (Command 13)
Unknown variable
3.16
SWITCHING OFFLINE/ONLINE
Command:
Answer:
COMMAND: 13
Entry
Data type
Mode
WORD
Entry
Data type
No data
-
This command corresponds to the menu items [Hardware|ECU calibration access (checked)]
in case of mode=1 or [Hardware|ECU calibration access (unchecked)] in case of mode=0.
When going online (mode=1) and the calibration data in the INCA database differs from the
calibration data in the ECU, INCA database data is automatically downloaded to the ECU.
Contrary to the ASAM ASAP3 V2.0 specification, this command can be executed also without
issuing the command PARAMETER FOR VALUE ACQUISITION before to be able to modify
maps offline.
While executing the command INIT, the ASAM ASAP3 interface tries to set the online state
according to the [Exras|Options|Online] “Going Online” options.
If maps and parameters have been modified offline, the calibration data should be sent to
the emulation memory by going online.
Before switching hardware access, ASAM ASAP3 checks if there is at least one ECU in the
workspace which supports at least one calibration page. If this is not the case, hardware
access is not changed.
Error codes:
INCA specific errors
Implementation Notes for Commands
37
Missing INIT (command 2)
Invalid value for online mode
3.17
GET ONLINE VALUE
Command:
Answer:
COMMAND: 19
Entry
Data type
No data
-
Entry
Data type
Number of actual values
WORD
Value of the 1st actual value
REAL
Value of the 2nd actual value
REAL
.…
.…
Returns the values of the selected acquisition variables in the order they got configured. If
the measurement is not running, it is started before.
If the system was offline before or the measurement was not running, the system waits at
least 100ms until it tries to get the values from the INCA target server, otherwise no valid
data would be available.
Attention
Calling GET ONLINE VALUE with rates higher than 10Hz only makes sense if the new measure mode
is activated (See compatibility options for more information on that).
Note for the new measure mode
If the measurement was started, the system waits up to 1000ms for valid data and then – if still no
data is available – returns with an INVALID MEASUREMENT error. This is valid only for the startup
phase. Once valid data was available the system will react as configured in the compatibility options
(see 2.6.6 for more information).
Error codes:
Communication errors
Missing INIT (Command 2)
Missing IDENTIFY (Command 20)
Not online. SWITCHING OFFLINE/ONLINE (Command 13)
No online variables defined
3.18
GET USER DEFINED VALUE
Command:
Answer:
38
COMMAND: 21
Entry
Data type
No data
-
Entry
Data type
Number of actual values
WORD
Value of the 1st actual value
REAL
Value of the 2nd actual value
REAL
Implementation Notes for Commands
.…
.…
If this command (or the command GET USER DEFINED VALUE LIST) is issued, all variables
that were manually defined by the user are returned. If the measurement is not running it is
started before.
If the system was offline before or the measurement was not running, the system waits at
least 100ms until it tries to get the values from the INCA target server, otherwise no valid
data would be available.
Attention
Calling GET USER DEFINED VALUE with rates higher than 10Hz only makes sense if the new
measure mode is activated (See compatibility options for more information on that).
Note for the new measure mode
If the measurement was started the system waits up to 1000ms for valid data and then – if still no
data is available – returns with an INVALID MEASUREMENT error. This is valid only for the startup
phase. Once valid data was available the system will react as configured in the compatibility options
(see 2.6.6 for more information).
Error codes:
Communication errors
Missing INIT (Command 2)
Missing IDENTIFY (Command 20)
Not online. SWITCHING OFFLINE/ONLINE (Command 13)
3.19
GET USER DEFINED VALUE LIST
Command:
Answer:
COMMAND: 22
Entry
Data type
No data
-
Entry
Data type
Number of actual values
WORD
Emulator LUN of 1st value
WORD
Name of 1st value
STRING
Emulator LUN of 2nd value
WORD
Name of 2nd value
STRING
.…
.…
Returns the list of all user defined variables. Always necessary before calling GET USER
DEFINED VALUE (Command 21), if values were manually added or removed since the last
call.
Error codes:
Communication errors
Missing INIT (Command 2)
Missing IDENTIFY (Command 20)
Implementation Notes for Commands
39
3.20
GET PARAMETER FROM AP-S
Command:
Answer:
COMMAND: 14
Entry
Data type
Emulator LUN
WORD
Parameter name
STRING
Entry
Data type
Value
REAL
Minimum value
REAL
Maximum value
REAL
Minimum Increment
REAL
Reads the data located on the PC. The parameter name is the internal name of the
description file.
If the option “Show edited values” is set or the command SET GRAPHIC MODE ON AP-S was
used before, the parameter is opened within INCA if it was not yet opened. For Minimum
value, Maximum value and Minimum Increment see Command 8.
Error codes:
INCA communication errors
Invalid LUN
LUN of AUXIN not allowed
Parameter not found
Object is no parameter
Values from the MC system can't be interpreted
3.21
SET PARAMETER ON AP-S
Command:
Answer:
COMMAND: 15
Entry
Data type
Emulator LUN
WORD
Parameter name
STRING
Value
REAL
Entry
Data type
No data
-
The values received from the client are adjusted according to the physical conversion of the
description file (not to the value range of the data type, which can be bigger).
In off-line mode, the changes only apply to the data on the PC. They will become effective
for the ECU as soon as the system goes on-line.
If the option “Show edited values” is set or the command SET GRAPHIC MODE ON AP-S was
used before, the parameter is opened within INCA if it was not yet opened.
If a parameter is write-protected it will not be updated in the MC system and a message will
be written to the log window.
Error codes:
INCA communication errors
Invalid LUN
40
Implementation Notes for Commands
LUN of AUXIN not allowed
Parameter not found
Object is no parameter
Values from the MC system can't be interpreted
Values can't be set in the MC system
Values are out of the limits of the data type
3.22
DEFINE RECORDER PARAMETERS
Command:
Entry
Data type
Emulator LUN
WORD
Recording type
WORD
Scanning time [ms]
REAL
Divider factor
WORD
Number of values
WORD
Name of 1st value
STRING
Name of 2nd value
STRING
.…
.…
Answer:
COMMAND: 41
Entry
Data type
No data
-
If this command is issued, the current recorder settings are reset. If recording type is set to
synchronous to the system interval time, the scanning time is ignored and should be set to
0.
The field divider factor of the command is ignored and should be set to 0!
Single variables used in a recording must not be defined more than once, otherwise they will
be rejected.
The command can be recalled repeatedly for each LUN. Every LUN can have its own
scanning time.
It is also possible to use “variable\device”-name instead of variable names only. This allows
wiring different values with different devices (LUNs) in one step. This is a deviation of ASAM
ASAP3 that allows faster setup of measurements with variables from many different devices.
Contrary to ASAM ASAP3 the recording type and scanning time of the latest call for a LUN
overwrites only the settings of an already wired variable with the same name and LUN (e.g.
as user defined variable).
Note
If a variable already exists as user defined value or online value, the time raster of that variable is
changed to the current one requested by the recorder setting.
Note
If the time raster for the desired scanning time is already full, an error is reported.
For CAN-Monitoring and CalcDev (calculated signals) devices the scanning time has no
influence, because variables of these devices are always wired in their default raster.
By design all values being wired through ASAM ASAP3 in INCA are recorded and an
additional index file (with the extension ‘.dati’) is created together with every measurement,
Implementation Notes for Commands
41
containing the names of all channels that were wired for recording. This allows all related
commands to return only these variables.
Attention
If the index file is lost somehow, the commands LOAD RECORDER FILE and GET RECORDER
RESULTS will return all values available in the measurement file, i.e. all variables that were wired
with PARAMETER FOR VALUE ACQUISITION and DEFINE RECORDER PARAMETERS at the time the
recording is done.
In order to wire recorder values in INCA, it is necessary that the measurement is stopped
while doing that. Therefore, the measurement is stopped and restarted again witch leads to
a short interruption of online data (at least 100ms – see Command 19: GET ONLINE VALUE).
Error codes:
Communication errors
Missing INIT (Command 2)
Missing IDENTIFY (Command 20)
Invalid LUN
Not offline. SWITCHING OFFLINE/ONLINE (Command 13)
Unknown variable
3.23
DEFINE TRIGGER CONDITION
Command:
Answer:
COMMAND: 42
Entry
Data type
Trigger START
STRING
Trigger STOP
STRING
Max. sample number
INTEGER4
Start delay
INTEGER4
Stop delay
INTEGER4
Entry
Data type
No data
-
If no trigger condition is used, the strings for Trigger START and Trigger STOP must be
empty.
For a manual trigger, the value of Trigger START must be set to “MANUAL”.
As INCA does not support a measurement limited by a max. sample number the command
calculates the recording time in the following way:
recording time = sample rate * max. sample number.
This works only if an equidistant measurement (Recording type = 0) was defined with
DEFINE RECORDER PARAMETERS (Command 20), otherwise the parameter is ignored.
Furthermore, the Trigger START and Trigger STOP strings must be empty.
All variables must contain the device name in the following way: “variable\devicename”.
Example: “ub\ETK-Testdevice:1”
All variables uses in trigger conditions must have been defined before with the commands
PARAMETER FOR VALUE AQUISTITION (Command 12) or DEFINE RECORDER PARAMETERS
(Command 41).
Start delay and Stop delay must be in ms.
42
Implementation Notes for Commands
Note
If a STOP trigger is defined, it is not possible to use a stop delay. In that case the stop delay should
be set to 0.
Attention
There must be blanks before and after all operators in the trigger conditions!
Possible trigger operators are:
"!"
not
"="
equal
"<"
less than
">"
greater than
"<=”
less than or equal
">=”
greater than or equal
"!=”
not equal
"&"
logical and
"|"
logical or
"up"
rising edge and greater
"down”
falling edge and lower
In addition to that, for combining conditions brackets should be always used to be on the
save side (e.g.: (A\ETK > 1) & (A\ETK < 2)).
In order to define a trigger condition in INCA, it is necessary that the measurement is
stopped while doing that. Therefore, the measurement is stopped and restarted again which
leads to a short interruption of online data (at least 100ms – see Command 19: GET ONLINE
VALUE).
Error codes:
Communication errors
Missing INIT (Command 2)
Missing IDENTIFY (Command 20)
Invalid LUN
Not offline. SWITCHING OFFLINE/ONLINE (Command 13)
Unknown variable
3.24
ACTIVATE RECORDER
Command:
Answer:
COMMAND: 43
Entry
Data type
Mode
WORD
Entry
Data type
No data
-
Implementation Notes for Commands
43
When using mode=2, the trigger expression set in DEFINE TRIGGER CONDITION
(Command 41) will not have any effect.
Error codes:
Communication errors
Missing INIT (Command 2)
Missing IDENTIFY (Command 20)
Missing DEFINE RECORDER PARAM. (Command 41)
Missing DEFINE TRIGGER CONDITION (Command 42)
Invalid value for mode.
Not online. SWITCHING OFFLINE/ONLINE (Command 13)
3.25
GET RECORDER STATUS
Command:
Answer:
COMMAND: 44
Entry
Data type
No data
-
Entry
Data type
Recorder Status
WORD
Current Samples
INTEGER4
Stop Condition
WORD
Stop Information
STRING
The value for Current Samples is calculated in the following way:
current samples = recorded time / sample rate
As INCA only provides the recorded time and not the already recorded amount of samples,
the value has to be calculated in that way. After the recording has stopped the exact
number of recorded samples is available.
Note
In very short measurements the sample count showed with GET RECORDER STATUS during and
after a measurement may differ, because there is a little jitter in INCA when starting a recording.
Error codes:
Communication errors
Missing IDENTIFY (Command 20)
Missing ACTIVATE RECORDER (Command 43)
Not online. SWITCHING OFFLINE/ONLINE (Command 13)
3.26
GET RECORDER RESULTS HEADER
Command:
Answer:
44
COMMAND: 45
Entry
Data type
No data
-
Entry
Data type
Start time (Trigger Start) [s]
STRING
Recording type
WORD
Implementation Notes for Commands
Scanning time [ms]
REAL
Divider factor
WORD
Number of samples
INTEGER4
Start delay
INTEGER4
Stop delay
INTEGER4
Lost samples
INTEGER4
Max. Phase Error
INTEGER4
Returns the recorder results of the last recorded measurement. This command can not be
executed while the recorder is running. After the end of recording, the information comes
from a temporary file until it is saved with SAVE RECORDER FILE (Command 47).
If LOAD RECORDER FILE (Command 48) was called prior to this command the data comes
from any file that was saved earlier with SAVE RECORDER FILE (Command 47).
Scanning time will be set to 0 if Recording Type in DEFINE RECORDER PARAMETERS
(Command 41) was set to 1.
Divider Factor will always be set to 1; the values for Start Delay, Stop Delay, Lost Samples
and Max. Phase Error will always be 0.
Note
The recording type ‘1’ (=synchronous to the system interval time) is always reported if one
measurement label of the current recording is wired as ‘Syncro’. Only if all online variables of the
current experiment are not wired as ‘Syncro’, the smallest available raster is reported as selected
scanning time.
Error codes:
Communication errors
Missing IDENTIFY (Command 20)
Recorder is running.
3.27
GET RECORDER RESULTS
Command:
Answer:
COMMAND: 46
Entry
Data type
Data Packet Number n
INTEGER 4
Entry
Data type
Data Packet Number n
INTEGER4
Number of values m
WORD
Value 1 in sample n
REAL
Value 2 in sample n
REAL
Value 3 in sample n
REAL
.…
Value m in sample n
REAL
REAL
The numbering for Data Packet Number starts with 1!
Implementation Notes for Commands
45
If Include timestamp in recorder results is selected in the general options dialog, every call
of GET RECORDER RESULTS returns one additional value with the label “_time_” that
contains the timestamp of the current sample in float format.
LOAD RECORDER FILE normally returns all variables that were stored in the index file that is
saved in parallel to the measurement file and has the extension ‘.dati’. If that index file is
not available, all variables contained in the measurement file are returned (see DEFINE
RECORDER PARAMETERS for more information on index files).
Error codes:
Communication errors
Missing IDENTIFY (Command 20)
Recorder is running.
3.28
SAVE RECORDER FILE
Command:
Answer:
COMMAND: 47
Entry
Data type
Filename
STRING
Entry
Data type
No data
-
Saves the currently open measurement data in a file. If an additional file format was
selected for recording (see Recorder Options for more information on that) that file is
additionally saved a the same location as the one given by filename. Beyond that, also the
index files with the extension ‘.dati’ are stored at that location (see DEFINE RECORDER
PARAMETERS for more information on index files).
Error codes:
Communication errors
Missing IDENTIFY (Command 20)
Recorder is running.
3.29
LOAD RECORDER FILE
Command:
Answer:
COMMAND: 48
Entry
Data type
Filename
STRING
Entry
Data type
Number of values
st
WORD
Name of the 1 value
STRING
Name of the 2nd value
STRING
.…
Loads a recorder file of a recording that was previously saved with SAVE RECORDER FILE
(Command 46). If no path name is given, the ASAM ASAP3 server uses the USERS
measurement files path.
If Include timestamp in recorder results is selected in the general options dialog, LOAD
RECORDER returns one additional value with the label “_time_” that contains the timestamp
of the current sample in float format.
46
Implementation Notes for Commands
LOAD RECORDER FILE normally returns all variables stored in the index file that is saved in
parallel to the measurement file and has the extension ‘.dati’. If that index file is not
available all variables contained in the measurement file are returned (see DEFINE
RECORDER PARAMETERS for more information on index files).
Error codes:
Communication errors
Missing IDENTIFY (Command 20)
Recorder is running.
3.30
SET GRAPHIC MODE ON AP-S
Command:
Answer:
COMMAND: 16
Entry
Data type
Mode
WORD
Entry
Data type
No data
-
This command overrides the options [Extras|Options|Map Editor] “Show edited values” and
[Extras|Option|Online] “Show measured values” for the current ASAM ASAP3 session.
Error codes:
3.31
Missing INIT (COMMAND 2)
RESET DEVICE
Command:
Answer:
COMMAND: 17
Entry
Data type
Emulator LUN
WORD
Entry
Data type
No data
-
The reset command is sent to the device specified in the command SELECT DESCRIPTION
FILE AND BINARY FILE. If this device doesn’t support resetting, then no other device is used
to reset the ECU. The ECU is put into the reset state for a short time and resumes its
previous state afterwards.
This command does nothing for CAN devices/ECUs!
Error codes:
INCA specific errors
Missing INIT (command 2)
invalid LUN
3.32
SET FORMAT
Command:
COMMAND: 18
Entry
Data type
Log. data type
WORD
Model
WORD
Implementation Notes for Commands
47
Answer:
Entry
Data type
No data
-
Coding for log. data type: 0 = all, 1 = maps, 2 = parameters, 3 = online and recorder
values
Coding for model: 0 = physical values, 1 = controller (hex) values
Initially, all data are expected and returned in the physical model.
In INCA, physical conversions as well as string conversions are possible. Because ASAM
ASAP3 commands accept only real values for setting and returning values, variables with
string conversion are always transferred in the controller model, independent of the settings
for model. Whether a returned controller model value is signed or unsigned depends on the
data type of the individual variable.
The value 2 for model is not supported even in ASAM ASAP3 V2.1 mode!
Error codes:
Missing INIT (command 2)
Invalid value for data type
Invalid value for model
3.33
SET CASE SENSITIVE LABELS
Command:
Answer:
COMMAND: 61
Entry
Data type
No data
-
Entry
Data type
No data
-
This command overrides the [Extras|Options|General] “Labels are case sensitive” option for
the current session.
Error codes:
3.34
EXTENDED
QueryAvailableServices
Command:
Answer:
48
Missing INIT (command 2)
COMMAND: 200
Entry
Data type
No data
-
Entry
Data type
Number of services
WORD
Name of the 1st service
STRING
Name of the 2nd service
STRING
:
:
Name of last service
STRING
Implementation Notes for Commands
Only one service is supported. Therefore, number of services is 1. The name of the
supported service is “Switch Emulation Page”.
Error codes:
Missing INIT (command 2)
This command requires at least Protocol Version 2.1
3.35
EXTENDED
GetServiceInformation
Command:
Answer:
COMMAND: 201
Entry
Data type
Service
STRING
Entry
Data type
InfoString
STRING
Only service “Switch Emulation Page” is supported. The returned info specifies the syntax of
the service:
The service "Switch Emulation Page" requires the following parameters:
LUN: <valid LUN number>; PAGE: <valid page number>
The service returns an empty string.
The order of the parameters is significant. The parameter names are not case sensitive. The
colon has to follow immediately after the parameter name without a blank.
Possible values for LUN are the LUN numbers which have been returned with the commands
“SELECT DESCRIPTION FILE AND BINARY FILE” or “DEFINE DESCRIPTION FILE AND
BINARY FILE”.
Valid page numbers are 0 for the working page and 1 for the reference page.
Error codes:
Not yet identified
This command requires at least Protocol Version 2.1!
Unknown service
3.36
EXTENDED
ExecuteService
Command:
Answer:
COMMAND: 202
Entry
Data type
Service
STRING
Service input parameter
STRING
Entry
Data type
Service output parameter
STRING
This command supports only the service “Switch Emulation Page”.
The service input parameters have to follow the syntax described in the command
GetServiceInformation (201).
The behavior of “Switch Emulation Page” is simply to switch to the given emulation page for
the device which is identified by the given LUN.
Implementation Notes for Commands
49
Error codes:
INCA specific errors
Not yet identified
This command requires at least Protocol Version 2.1!
Unknown service
LUN parameter required for this service
Invalid LUN
LUN of AUXIN device not allowed for this function!
PAGE parameter required for this service
Only page numbers 0 (working page) and 1 (reference page) are
supported.
3.37
EXTENDED
GetWorkingPoint
Command:
Answer:
COMMAND: 42001
Entry
Data type
Map number
DWORD
Entry
Data type
Y-Index
WORD
X-Index
WORD
Y-Delta
WORD
X-Delta
WORD
The working point of the specified map will be returned.
Indices within the map are starting at 1. Delta can have one of the values 0, 1 and 2. The
value 1 is returned if the working point is lying exactly on a set point value. The value 2
indicates that the associated online value of an axis is currently between the position defined
by Index and the lower-right neighboring values.
If the working point is not located within the map, the values for the indices will be set to
the lowest or highest value possible according to the map dimension. The values for delta
will be set to 1.
For 2dim maps, each direction is handled independently; that means that if e.g. the working
point is outside the valid range just for the x direction, only these values are set to the
lowest or highest value possible.
There are different map types. These types are:
! Maps without any working point or 2dim maps with only one associated online
variable.
For these maps, 0 will always be returned for all the values.
! Maps with interpolation between neighboring values.
For these maps, if the working point is valid, the delta values will be either 1 or 2!
If the application system is not on-line, the value 0 for all fields will be returned.
Y-Values have to be ignored for 1dim maps.
It is not possible to use this command for arrays and matrices.
To be able to retrieve the working point at any time after a map number was created, the
measurement variables for the working point are already wired during map selection. Since
this costs measurement bandwidth even if the working point is never requested, starting
with INCA 7, a new option allows enabling and disabling the working point feature globally
(refer to chapter 2.6.3 Online Options). In case the working point feature was disabled, an
error is emitted when this command is executed.
50
Implementation Notes for Commands
Error codes:
INCA communication errors
Invalid map number
Access of an axis failed
Values from the MC system can't be interpreted
Values are out of the limits of the data type
The access to the working point data is not possible because the
feature is currently disabled in the ASAP3 options.
Implementation Notes for Commands
51
4
Appendix: ASAP3 Error Codes
4.1
Errors in Log Window without Error Code returned to AuSy
The following errors are displayed in the log window without a separate error code returned
to the AuSy (Automation System).
Error code
Description
20003
(%s error; unexpected end of command)
(replace %s with anyone of: STRING, BYTE, WORD, INTEGER4, REAL)
The command received from the AuSy or the response to be sent to the
AuSy is malformed. This was detected while trying to log the command
or response.
If this happens for a command, either the communication link is not
reliable enough or a programming error on the AuSy side caused the
problem.
If this happens for a response, a programming error within ASAP3.EXE
caused the problem.
20005
Unknown command:
%u(%xh)
(replace %u with a decimal number and %x with a heximal number)
The command with the given number is not recognized by ASAP3.EXE.
This is either one of the unsupported extended commands or an
erroneous telegram sent by the AuSy side.
20014
Environment of was changed interactively
This message is shown if the connection is currently being stopped by
the user and another command is received from the AuSy or if there was
no correct initialization with the INIT command.
20050
Cannot log map because of unknown map number!
This message is displayed during the command PUT LOOK-UP TABLE if
that command asks for a map number which is not known in the current
list of selected maps (via SELECT LOOK-UP TABLE).
4.2
Errors in Log Window with Error Code returned to AuSy
Answers of ASAP3.EXE to the AuSy may be affirmative or negative. The affirmative answers
are given with a status code of 0x0000 or 0x1232. Negative answers have one of the
following states:
Status code
(hex)
Description
0x0000
Success
(ASAP3 spec: Faultless execution of the last command)
0x1232
Success
(ASAP3 spec: Faultless execution of the last command)
52
Appendix: ASAP3 Error Codes
Status code
(hex)
Description
0x2343
Environment of INCA was changed interactively.
(ASAP3 spec: Value $2343 indicates that the last sent telegram was not
processed and that the AuSy must again set up communication, as
interactively major changes have been made to the MC system
configuration predefined by the AuSy. The successful execution of the
‘INIT’ command (Code 2) resets this status (see ‘User command “START”’
in the section on ‘some command sequences’).)
In INCA, this telegram indicates that there was no INIT command before
the last command. This can happen if the ASAP3 server was reset or
restarted or the communication was reestablished without the AuSy’s
knowledge.
0x2344
Measuring data list has changed
(ASAP3 spec: Measuring data list has changed)
This status can occur in the response to the GET USER DEFINED VALUE
in case the user has changed INCAs list of measured values.
0x3454
Success – simulation mode
(ASAP3 spec: A $3454 status informs the AuSy that the MC system is in
simulation mode. The status is interpreted in the subsequent processing
as an ‘0’ or ‘$1232’ status (faultless command execution).)
INCA does not support simulation mode, so this status will never occur.
0x5656
Command not implemented
(ASAP3 spec: This status informs the AuSy of the non-availability of the
function of the last sent command.)
This status occurs if INCA receives the commands EXIT, DEFINE
DESCRIPTION AND BINARY FILE, GET USER DEFINED VALUE, GET USER
DEFINED VALUE LIST and ASAP3 protocol mode is not 2.01 or higher
(e.g. no IDENTIFY command was sent).
This status also occurs if an unknown command or an unimplemented
extended command was received.
0xFFFF
Error
(ASAP3 spec: An error occurred during the processing of the last AuSy
command sent to the MC system. An error number and a detailed error
message in clear text are sent by the MC system to the AuSy.)
INCA shows further error codes and error text in the description part of
the answer telegram. Please see next table for a detailed description of
those error codes
0xAAAA
Command received
(ASAP3 spec: This status is considered as an acknowledgement of the last
command by the AuSy. The final answer of the MC system occurs after
the command has been processed (see telegram above).)
This status is returned if the option “Send Acknowledge” on the General
option tab is checked. It indicates that a command was received from the
AuSy. The command will be executed right after the telegram with status
0xAAAA was sent to the AuSy. The answer telegram for the command will
be sent after the command was executed (or aborted due to an error).
This means, the flow control on the AuSy must depend on the status of
the final answer to the command; the 0xAAAA telegram is only an
interims indicator that INCA is still communicating.
Appendix: ASAP3 Error Codes
53
Status code
(hex)
Description
0xEEEE
Retry command
(ASAP3 spec: In conjunction with command code 0 in the AuSy RETRY
telegram, this status may be considered as a command repeat request
(see telegram above).)
The following errors are displayed in the log window (if logging of at least errors is enabled)
and returned in the response to the AuSy, except where explicitly stated differently. These
errors are contained in answer telegrams that have a status field with the value 0xFFFF.
Error code
(decimal)
Description
60001
Invalid LUN!
The LUN of the command was not provided by the ASAP3 interface since
the last INIT command. If you get this message you should first check
the option “Start generated LUN numbers with 0” in the Compatibility
page of the Options. Normally LUN numbers start from 59. A script that
expects the LUN numbers starting from 59 will cause this error if the
above option is set and vice versa.
PARAMETER FOR VALUE ACQUISITION
DEFINE RECORDER PARAMETERS
SELECT LOOK-UP TABLE
60003
Command order error! Missing INIT (command 2)!
One of the commands IDENTIFY, SELECT DESCRIPTION AND BINARY
FILE or DEFINE DESCRIPTION AND BINARY FILE was sent without a prior
call to the INIT command. This violates the required sequence of setting
up a connection:
INIT
IDENTIFY and then
SELECT DESCRIPTION FILE AND BINARY FILE or
DEFINE DESCRIPTION AND BINARY FILE.
60004
Cannot work with ASAP3 protocol versions different than V2.x!
This error message is shown in case one of the commands
SELECT DESCRIPTION FILE AND BINARY FILE or
DEFINE DESCRIPTION AND BINARY FILE
have been called but no IDENTIFY command was sent before. ASAP3.EXE
supports only ASAP3 protocol versions 2.x. You archive best results, that
is, you get the most features if you identify with version 2.1.
60005
Cannot send calibration data to EPROM!
This error indicates that INCA does not support sending calibration data
to the EPROM via ASAP3 with the command COPY BINARY FILE. The
Target parameter of this command should not be set to 1 (EPROM).
COPY BINARY FILE
60006
Cannot receive calibration data from EPROM!
This error indicates that INCA does not support receiving calibration data
from the EPROM via ASAP3 with the command COPY BINARY FILE. The
Source parameter of this command should not be set to 1 (EPROM).
COPY BINARY FILE
54
Appendix: ASAP3 Error Codes
Error code
(decimal)
Description
60007
Invalid values for source or destination!
The error appears if the command COPY BINARY FILE was used with
invalid parameters for Source and/or Destination. The values for these
parameters must not be zero nor exceed the value of 4.
COPY BINARY FILE
60008
Already identified!
The command IDENTIFY was sent again, after another IDENTIFY
command has been sent already, without an INIT or EXIT command inbetween.
To prevent this error, send an INIT command before the IDENTIFY
command.
IDENTIFY
60009
Need an ASAP3 protocol version V2.x!
The command IDENTIFY was sent with a parameter Protocol version
number set to a version smaller than 2.0 or greater or equal to 3.0. To
prevent this error, use only variants of version 2 (2.xx), because those
are the only ones that are supported.
IDENTIFY
60010
Not yet identified! Missing IDENTIFY (command 20)!
Received a command without the command IDENTIFY being issued
before. IDENTIFY is required to check the protocol version. ASAP3
protocol version 1.0 doesn’t send the command IDENTIFY. It is possible
to suppress this message with the option “Ignore protocol version from
IDENTIFY command…”
With this option set it is possible to use protocol version 2.1 commands
with protocol version 2.0 without the need of calling IDENTIFY.
GET USER DEFINE VALUE LIST
GET USER DEFINED VALUE
PARAMETER FOR VALUE ACQUISITION
GET ONLINE VALUE
DEFINE TRIGGER CONDITION
ACTIVATE RECORDER
GET RECORDER STATUS
GET RECORDER RESULTS HEADER
GET RECORDER RESULTS
SAVE RECORDER FILE
LOAD RECORDER FILE
60012
Out of memory!
There is not enough memory to create the memory representation of a
map. Check the memory in the task manager and quit all applications you
don’t need.
PUT LOOK-UP TABLE
Appendix: ASAP3 Error Codes
55
Error code
(decimal)
Description
60013
Call was canceled; operation wasn't completed by MCS!
INCA did not complete a COM call and the user terminated the
communication by clicking “Abort” on the dialog box COM shows after a
certain timeout was reached while COM waited for INCA. Since this COM
dialogs are disabled, the error should never show up.
60014
Internal error: <individual error text>
This is a general error message for all exceptions that can occur during
operation, mostly exceptions from external applications. The reason for
this error is an unexpected behavior of one of the used subcomponents.
Therefore, there is no general help how to avoid this type of error. Often
a restart of the whole system can help. Otherwise, you should contact the
local support for help.
60016
For 'Event', only 0 is allowed!
This error occurs if the ASAP3 command EMERGENCY is called with the
parameter Event set to a value different from zero. Only the event value
0 is supported by INCA.
EMERGENCY
60017
Invalid map number!
The map number of the command was not provided by ASAP3 since the
last INIT command.
GET LOOK-UP TABLE
PUT LOOK-UP TABLE
GET LOOK-UP TABLE VALUE
SET LOOK-UP TABLE
INCREASE LOOK-UP TABLE
GET WORKING POINT
60020
Invalid structure of received command!
The last received command telegram was analyzed and found to have not
the correct length. Please check on the sending side that the correct
command telegrams are sent. This error can occur for all commands that
contain additional data besides the command code.
60021
There is already LUN %d for the device with this description and
binary file assigned!
The command SELECT DESCRIPTION FILE AND BINARY FILE or DEFINE
DESCRIPTION FILE AND BINARY FILE has been executed with
parameters that lead to a device for which a LUN has already been
assigned. Please check the given description file or device name and the
devices for which a LUN already has been generated.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
60023
Map name not found in description file!
The map name specified in the command SELECT LOOK-UP TABLE
couldn’t be found in the description file currently loaded for the given
LUN.
SELECT LOOK-UP TABLE
56
Appendix: ASAP3 Error Codes
Error code
(decimal)
Description
60024
Name found in description file but it is no 1dim or 2dim map!
The map name specified in the command SELECT LOOK-UP TABLE was
found in the description file currently loaded for the given LUN, but is not
a 1- or 2-dim map. Possibly the name was a parameter, a set point or a
3-dim map.
SELECT LOOK-UP TABLE
60025
Invalid value for data type!
The command SET FORMAT was used with an invalid parameter Log.
data type. The parameter was larger than the maximum value of 3.
Please use a valid value of 0 to 3 instead.
SET FORMAT
60026
Invalid value for model!
The command SET FORMAT was used with an invalid parameter Model.
The parameter was larger than the maximum value of 2. Please use a
valid value of 0 to 2 instead.
SET FORMAT
60027
Answer packet is too long! Data will be clipped!
This message can appear in the log file in the case the answer telegram
would grow beyond its maximum size of 65534 Bytes. In that case, all
additional data is dropped.
The message is shown only in the log file, the client will receive the
telegram with the clipped data.
60028
Map has already been selected!
Received the command SELECT LOOK-UP TABLE with a map that already
has been selected since the last INIT command.
SELECT LOOK-UP TABLE
60030
A map dimension has exceeded the limit of 1025!
Received the command SELECT LOOK-UP TABLE, that resulted in a map
with at least one dimension above 1025 (either x- or y-dimension).
SELECT LOOK-UP TABLE
60031
Invalid value for online mode!
The command SWITCHING ONLINE/OFFLINE was called with an invalid
value for parameter Mode. Please use only values 0 (OFF-LINE) or 1 (ONLINE).
SWITCHING ONLINE/OFFLINE
60033
An unsupported function has been called!
There was a call to a COM object with a function that is not supported in
the COM object (CNotSupportedException). This is either a version
incompatible with INCA or a problem of the installation of INCA. Please
start INCA before you start the ASAP3 session. If the error persists, try to
reinstall INCA.
60034
An unspecified error occurred!
There was a call to a COM object that caused an exception which is not
specified in more detail. The additional error text should give additional
information about the root cause. Most likely the system reached an
unrecoverable error state. Please restart the system.
Appendix: ASAP3 Error Codes
57
Error code
(decimal)
Description
60035
LUN of AUXIN device not allowed for this function!
An AUXIN device does not contain calibration values. Therefore, it is not
possible to use AUXIN device LUN numbers together with calibration
commands.
SELECT LOOK-UP TABLE
GET PARAMETER
SET PARAMETER
60036
Invalid value for 'Mode'!
The mode parameter can only have the values 0 (=Recorder stop), 1
(=Activate Recorder) or 2 (Start Recorder). Every other value will cause
this error.
ACTIVATE RECORDER
60037
Invalid value for 'Destination'!
The command DEFINE DESCRIPTION AND BINARY FILE was called with
an invalid value for parameter Destination. Please use a valid value (see
description of command).
DEFINE DESCRIPTION AND BINARY FILE
60042
Invalid value for 'Recording type'!
The recording type parameter can only have the values 0 (= equidistant
raster) or 1 (= sync. raster). Every other value will cause this error.
DEFINE RECORDER PARAMETERS
60045
ASAP3 command DEFINE RECORDER PARAMETERS has to be
called before!
No recorder parameters were defined so far. Please call DEFINE
RECORDER PARAMETERS before calling the current command.
ACTIVATE RECORDER
DEFINE TRIGGER CONDITION
60047
ASAP3 command DEFINE TRIGGER CONDITION has to be called
before!
No trigger condition was defined so far. Please call DEFINE TRIGGER
CONDITION before calling the current command.
ACTIVATE RECORDER
60048
ASAP3 command ACTIVATE RECORDER has to be called before!
If the recorder was not started with ACTIVATE RECORDER (1 or 2), it is
not possible to stop the recorder with ACTIVATE RECORDER (0) or
retrieve the recorder status with GET RECORDER STATUS.
ACTIVATE RECORDER
GET RECORDER STATUS
60049
Internal error: invalid date/time!
The timestamp within a measurement file was not valid.
GET RECORDER RESULTS HEADER
58
Appendix: ASAP3 Error Codes
Error code
(decimal)
Description
60052
Start delay' must be 0 or negative!
INCA only supports negative start delays (or none) over ASAP3. This is a
limitation of the INCACOM interface.
DEFINE TRIGGER CONDITION
60061
ASAP3 command SWITCHING OFF/ONLINE with Mode=1 has to
be called before!
System must be online for the current command.
GET ONLINE VALUE
GET USER DEFINED VALUE
60200
Error switching to work page.
INCA rejected to switch to the working page. Please see the Monitor
Window for additional information about this problem.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRPITION FILE AND BINARY FILE
EXTENDED ExecuteService
60201
Unable to get database handle from INCA.
There was a problem detected while retrieving a handle to the current
INCA database via COM. Please check if there is a valid database opened
within INCA. If this is the case, please restart INCA and ASAP3.EXE.
This error can only occur during startup of ASAP3.EXE and is displayed in
a message box, it is never returned to the AuSy.
60205
Error could not be specified precisely (<hexadecimal error
code>)
An error (exception) occurred but there was no additional information
about the error available. Only the error code (HRESULT in case of COM)
is returned and given in the brackets as a hexadecimal number. Please
restart INCA and ASAP3.EXE.
60206
Unable to open current opened Experiment
While trying to get a handle of the current opened experiment in INCA,
an error was returned. Please make sure that INCA has an experiment
window open before starting ASAP3.EXE. When starting ASAP3.EXE
regularly via the INCA menu “ASAM-3MC”, this error should never occur.
This error can only occur during startup of ASAP3.EXE and is displayed in
a message box, it is never returned to the AuSy.
60207
No device with given description and binary name found in
current workspace
The command SELECT DESCRIPTION AND BINARY FILE was called with
parameters that did not describe an existing device within INCA. Please
specify a description file that is currently loaded within INCA. Use the
database name or the file name of the description file (A2L file),
according to the setting of the option “Use database names in 'SELECT /
DEFINE DESCRIPTION FILE AND BINARY FILE'” of the ASAP3.EXE tool.
Appendix: ASAP3 Error Codes
59
Error code
(decimal)
Description
60208
Cannot set or create work base to/from file '<filename>' or
cannot download
There was an error while the file with the given name was read into INCA
and set to a (new) work base during execution of the following
commands (probably including the download to the target):
SELECT DESCRIPTION AND BINARY FILE
COPY BINARY FILE
The Monitor window of INCA might show more information about this
error.
60210
Cannot copy binary to file <filename>
During the execution of the COPY BINARY FILE command, an error
occurred. The monitor window of INCA might show more information
about this error. For example, the target file might already exist and be
write-protected or the target path is on a write-protected media or the
free space on the target media is not sufficient for the copy operation.
COPY BINARY FILE
60211
Only the following combinations are supported:
target 2 with source 3 or 4
target 3 with source 4
target 4 with source 3.
The command COPY BINARY FILE was called with invalid parameters for
source and/or target. Only the listed combinations are supported by this
version.
COPY BINARY FILE
60212
No device with given name found
The device name given in the form variable\device is not available. In
INCA it is possible to wire a variable in 2 ways.
First as a combination of LUN and variable name. In this case the LUN
represents the device and the variable must be a valid variable within the
device represented by that LUN.
Alternatively it is possible to use the combination of a variable\device
instead of the variable. In this case the device supersedes the device
addressed by the LUN. If a device with that name doesn’t exist the error
above is reported.
PARAMETER FOR VALUE ACQUISTION
DEFINE RECORDER PARAMETERS
60213
Only the modes 0 and 2 are supported
The command DEFINE DESCRIPTION AND BINARY FILE was sent with
the parameter Mode set to a value of 1 or 3. These values are not
supported, only values 0 and 2 are.
DEFINE DESCRIPTION AND BINARY FILE
60
Appendix: ASAP3 Error Codes
Error code
(decimal)
Description
60214
Unable to switch calibration access on
This error is returned in case INCA is not able to switch the calibration
access on. This may be due to errors in the hardware. Please see the
Monitor window for further error description.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION AND BINARY FILE
INIT
SWITCHING OFFLINE/ONLINE
60215
Unable to start measurement
Some commands need to switch off INCA measurement before they can
perform their main work. For example, to read and download a new
binary file requires INCA to stop the measurement. After the command
has performed its main work, measurement will be switched back on
automatically. In case this switch fails, this error will be returned. A
possible reason can be a hardware problem. Please check the monitor
window for further error description.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
SWITCHING OFFLINE/ONLINE
COPY BINARY FILE
RESET DEVICE
60216
Unable to stop measurement
Some commands need to switch off INCA measurement before they can
perform their main work. For example, to read and download a new
binary file requires INCA to stop the measurement. In case this switch
fails, this error will be returned. A possible reason can be a hardware
problem. Please check the monitor window for further error description.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
SWITCHING OFFLINE/ONLINE
COPY BINARY FILE
RESET DEVICE
60217
Unable to switch calibration access off
This error is returned in case INCA is not able to switch the calibration
access on. This may be due to errors in the hardware. Please check the
Monitor window for further error description.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
INIT
SWITCHING OFFLINE/ONLINE
60218
Cannot reset device
INCA returns an error when trying to reset a device. Please see the
Monitor window for further error description.
RESET DEVICE
Appendix: ASAP3 Error Codes
61
Error code
(decimal)
Description
60219
Received command while processing already command! Please
increase timeout.
ASAP3.EXE received a new command while it was still processing the
previous command. This occurs often when ASAP3.EXE is busy with a
command that lasts very long and the AuSy received a timeout and
therefore repeated the last command. To prevent this, either optimize the
options of ASAP3.EXE for high performance (turn off all logging, turn off
LED indicators) or increase the timeout for the problematic command on
AuSy side.
60220
Internal error (GetOverlappedResult (Read); error code: <error
code>)
An error was reported by the operating system while reading data for the
next command. The error code is given as decimal number in place of the
text <error code> of the above message. The reason for this error is
unclear. If this error occurs repeatedly, you should try to recover by
restarting the whole system.
60221
Could not switch to reference page of at least one device.
While executing the EMERGENCY command, INCA was not able to switch
to the reference page of at least one device. See the monitoring window
for additional error description.
60222
Unable to open current opened Experiment View
ASAP3.EXE was unable to get a handle for the currently opened
Experiment View in INCA. Please make sure that INCA has an experiment
window open before starting ASAP3.EXE. When starting ASAP3.EXE
regularly via the INCA menu “ASAM-3MC”, this error should never occur.
This error can only occur during startup of ASAP3.EXE and is displayed in
a message box, it is never returned to the AuSy.
60223
This command requires at least Protocol Version 2.1
This error occurs if one of the extended commands for services is
executed but the AuSy did not identify with a version number of 2.1 or
higher. To use the extended commands for services, please make sure
that you identify with a protocol version that covers these commands.
EXTENDED QueryAvailableServices
EXTENDED GetServiceInformation
EXTENDED ExecuteService
60224
Unknown service
The service that was requested by the commands EXTENDED
GetServiceInformation or EXTENDED ExecuteService is not supported by
this version of ASAP3.EXE. Please make sure you use the correct version
of ASAP3.EXE and that you only use supported commands (as reported
by EXTENDED QueryAvailableServices). Currently, only the service
“Switch Emulation Page” is supported.
EXTENDED GetServiceInformation
EXTENDED ExecuteService
62
Appendix: ASAP3 Error Codes
Error code
(decimal)
Description
60225
LUN parameter required for this service
The service "Switch Emulation Page" requires the following parameters:
LUN: <valid LUN number>; PAGE: <valid page number>
The service returns an empty string.
If the parameter with the name “LUN” is missing, above error will be
returned.
EXTENDED ExecuteService (Switch Emulation Page)
60226
PAGE parameter required for this service
The service "Switch Emulation Page" requires the following parameters:
LUN: <valid LUN number>; PAGE: <valid page number>
The service returns an empty string.
If the parameter with the name “PAGE” is missing, above error will be
returned.
EXTENDED ExecuteService (Switch Emulation Page)
60227
Error switching to reference page.
INCA returned an error while trying to switch to the reference page. See
the monitor window for further error description.
EXTENDED ExecuteService (Switch Emulation Page)
60228
Only page numbers 0 (working page) and 1 (reference page) are
supported.
The command EXTENDED ExecuteService (Switch Emulation Page)
contains an invalid value for the parameter PAGE. Only 0 and 1 are
allowed.
EXTENDED ExecuteService (Switch Emulation Page)
60231
No device with given destination, description and binary name
found.
ASAP3 was not able to find a device with the given destination,
description file and binary name in the INCA database while executing the
command DEFINE DESCRIPTION FILE AND BINARY FILE. Please check
that the correct names and the destination are given and that the option
“Use database names in 'SELECT / DEFINE DESCRIPTION FILE AND
BINARY FILE'” in the General options dialog is set correctly.
DEFINE DESCRIPTION FILE AND BINARY FILE
Appendix: ASAP3 Error Codes
63
Error code
(decimal)
Description
60233
Unable to switch calibration access on because there is a
running MDA. You should go online before starting MDA.
This error occurs
either in case you execute a SWITCHING OFFLINE/ONLINE command
with parameter Mode equal to 1 (ON-LINE) while there is already a
recorder (Measurement Data Acquisition) running, in order to prepare
online calibration,
or in case you execute a SELECT DESCRIPTION FILE AND BINARY FILE
command while there is already a recorder running and the option “Data
&Download at 'SELECT DESCRIPTION FILE AND BINARY FILE'” was
checked,
or in case you execute a DEFINE DESCRIPTION FILE AND BINARY FILE
command while there is already a recorder running and the Mode
parameter is set to 2.
The SELECT/DEFINE DESCRIPTION FILE AND BINARY FILE commands
try to switch the calibration access on, if this was not yet done with a
preceding SWITCHING OFFLINE/ONLINE command. In case there was
already a recorder started, INCA is not able to switch the calibration
access on.
To circumvent this problem, stop the recorder before executing the
SELECT/DEFINE ESCRIPTION FILE AND BINARY FILE commands.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
SWITCHING OFFLINE/ONLINE
60234
Cannot upload workbase from device!
This error occurs if the command COPY BINARY FILE is executed with the
parameter Target set to 3 (virtual emulator board; PC memory) and the
parameter Source set to 4 (physical emulator board; e.g. ETK) and INCA
is not able to upload the workbase from the physical emulator board into
the PC. See the Monitor window for further error descriptions.
COPY BINARY FILE
60236
Cannot download workbase to device!
This error occurs if the command COPY BINARY FILE is executed with the
parameter Target set to 4 (physical emulator board; e.g. ETK) and the
parameter Source set to 3 (virtual emulator board; PC memory) and INCA
is not able to download the workbase from the PC into the physical
emulator board. See the Monitor window for further error descriptions.
COPY BINARY FILE
64
Appendix: ASAP3 Error Codes
Error code
(decimal)
Description
60237
The command '<command name>' cannot be executed while the
system is online. Please go offline first.
This error can appear when either the command SELECT DESCRIPTION
FILE AND BINARY FILE (3), the command DEFINE DESCRIPTION FILE
AND BINARY FILE (30) or the command COPY BINARY FILE (4) is
executed. In the error message, the text <command name> is replaced
by the according command name.
To execute above commands, INCA needs to perform certain actions that
are not possible while ASAP3 is in the online state. Therefore, the AuSy
has to explicitly switch to off-line mode before executing one of these
commands.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
COPY BINARY FILE
60238
Create Dispatch Error: Cannot connect to the INCA process. This
is probably due to a bad installation of the JAVA runtime. Please
execute msjavax86.exe in the INCA cebra directory.
Original error text: <original error text from the COM
subsystem>
When starting, ASAP3.EXE tries to connect to running instance or to
create a new instance of INCA. If this is not possible, above error
message is shown. The original error text that follows above error
message is emitted by the COM subsystem and can give additional hints
why INCA cannot be connected to or started.
This error occurs only during startup of ASAP3.EXE.
Please check that the JAVA runtime is installed correctly. If not, execute
msjavax86.exe from the subdirectory “cebra” in your INCA program
installation directory.
Note: Starting with INCA 6.0, the Cebra protocol is implemented using
.NET instead of Java. If this error occurs in INCA 6.0 or higher, the
installation of the .NET runtime has to be checked.
60239
Cannot set workbase to the following database entry:
If the attempt to assign a new working data set to a device within INCA
fails, the above error is returned. The error can only occur when the
option “Use database names in 'SELECT / DEFINE DESCRIPTION FILE
AND BINARY FILE'” in the General options dialog is checked. See the
monitor window for more error information.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
60240
No MeasureCal device with given name found
The device given in PARAMETER FOR VALUE ACQUISITION or DEFINE
RECORDER PARAMETERS can not be found. This is an internal error or
may be caused due to a configuration change during an ASAP3 session.
PARAMETER FOR VALUE ACQUISITION
GET USER DEFINED VALUE LIST
DEFINE RECORDER PARAMETERS
Appendix: ASAP3 Error Codes
65
Error code
(decimal)
Description
60241
Cannot download working page "<data set name>" to device.
Please see INCA monitor log for further information.
If the option “Data Download at 'SELECT DESCRIPTION FILE AND
BINARY FILE'” in the General options dialog is checked, ASAP3.EXE tries
to download the working page to the device after the working data set
has been selected within the commands SELECT DESCRIPTION FILE AND
BINARY FILE and DEFINE DESCRIPTION FILE AND BINARY FILE. If this
fails, above error is returned.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
60242
Cannot create a copy of the data set with the new name '<new
data set name>' in project '<project name>'.
In case
the SELECT DESCRIPTION FILE AND BINARY FILE command is executed
while the options “Data Download at 'SELECT DESCRIPTION FILE AND
BINARY FILE'” and “Create New DS at Download within MCS” are
checked, or
the DEFINE DESCRIPTION FILE AND BINARY FILE command is executed
with parameter Mode set to 2 while the option “Create New DS at
Download within MCS” is checked,
ASAP3.EXE tries to create a copy of the selected data set. If INCA is not
able to create a copy, the error message is shown.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
60282
There is already a LUN to the first device in the INCA workspace
assigned!
For protocol version 2.01, ASAP3 allows to access the first device in the
INCA workspace by using the LUN 0. This is possible without the need of
the AuSy to explicitly call the command SELECT DESCRIPTION FILE AND
BINARY FILE or DEFINE DESCRIPTION FILE AND BINARY FILE and is
intended to work as a shortcut. Internally, with the first use of the LUN 0,
almost the same process is executed as with SELECT DESCRIPTION FILE
AND BINARY FILE, which would create a LUN 0 as the first device in the
INCA workspace. In case this process detects that already another
command requested a LUN for the same first device in the INCA
workspace, this error is returned, because it is not allowed to have two
LUNs assigned to the same device.
SELECT LOOK-UP TABLE
GET PARAMETER
SET PARAMETER
COPY BINARY FILE
CHANGE BINARY FILE NAME
RESET DEVICE
EXTENDED ExecuteService (Switch Emulation Page)
PARAMETER FOR VALUE ACQUISITION
DEFINE RECORDER PARAMETERS
66
Appendix: ASAP3 Error Codes
Error code
(decimal)
Description
60283
Loading data into the INCA database is not allowed during online
state to avoid inconsistencies between the ECU and MCD system.
The command COPY BINARY FILE was called with the parameter Target
set to 3 (virtual emulator board; INCA Database) and the parameter
Source set to 2 (File).
Advice: Explicitly switch off-line with command SWITCHING OFFLINE/ON-LINE before issuing the COPY BINARY FILE (Source=2,
Target=3).
COPY BINARY FILE
60284
Internal error: Cannot retrieve the project database path of the
device '<device name>' (INCACOM GetProjectDataBasePath)
When the commands SELECT DESCRIPTION FILE AND BINARY FILE and
DEFINE DESCRIPTION FILE AND BINARY FILE are executed, ASAP3.EXE
has to look for a device within INCA that has the given description file
loaded. In case INCA issues an error when it is asked for the description
file name of a given device, above error is shown; <device name> is
hereby replaced by the current device under investigation.
See the monitor window for more information about the error.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
60285
Internal Error: The project database path of the device '<device
name>' is empty! (INCACOM GetProjectDataBasePath)
When the commands SELECT DESCRIPTION FILE AND BINARY FILE and
DEFINE DESCRIPTION FILE AND BINARY FILE are executed, ASAP3.EXE
has to look for a device within INCA that has the given description file
loaded. In case INCA returns an empty name when it is asked for the
description file name of a given device, above error is shown; <device
name> is hereby replaced by the current device under investigation.
See the monitor window for more information about the error.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
60286
Cannot find data set '<data set name>' in project '<project
database path>'. Please verify project name and data set name.
Be sure to prefix the data set name with the folder name within
project!
If the option “Use database names in 'SELECT / DEFINE DESCRIPTION
FILE AND BINARY FILE'” in the General options dialog is checked and
either of the commands SELECT DESCRIPTION FILE AND BINARY FILE or
DEFINE DESCRIPTION FILE AND BINARY FILE is called with a dataset
name that does not exist within INCA in the given project name, the
above error is returned. Please check that the project specified with the
given project data base path contains a data set that has the same name
as indicated as the data set name.
SELECT DESCRIPTION FILE AND BINARY FILE
DEFINE DESCRIPTION FILE AND BINARY FILE
Appendix: ASAP3 Error Codes
67
Error code
(decimal)
Description
60287
Passover time from receive thread exceeded 1 second: <number
of milliseconds> ms total passover time. Possible reason: system
load too high
ASAP3.EXE uses a separate thread to read commands from the serial line
or from TCP/IP. If a new command is available, the main thread is
notified about this fact. The main thread then tries to read the command
as soon as possible. If the time between notification and current reading
of the command is longer than one second, this warning is logged in the
logging window to inform the user about a possibly too high system load.
Normally, passing a received telegram to the main thread should be a
matter of a few (e.g. 10) milliseconds.
This error is never returned to the AuSy.
60505
The command can't be executed because the index which is used
to have access to the data is out of the possible limits!
SET LOOK-UP TABLE
GET LOOK-UP TABLE VALUE
INCREASE LOOK-UP TABLE
60512
Because of write protection the map values can't be changed!
Possible reason could be that the wrong page is active (reference page)
or that the map is write-protected.
PUT LOOK-UP TABLE
INCREASE LOOK-UP TABLE
SET LOOK-UP TABLE
60513
Because of write protection the x-axis values can't be changed!
Possible reason could be that the wrong page is active (reference page)
or that the map is write-protected.
PUT LOOK-UP TABLE
60514
Because of write protection the y-axis values can't be changed!
Possible reason could be that the wrong page is active (reference page)
or that the map is write-protected.
PUT LOOK-UP TABLE
60515
Because of write protection the parameter value can't be
changed!
Possible reason could be that the wrong page is active (reference page)
or that the map is write-protected.
SET PARAMETER
60517
The access to the working point data is not possible because the
feature is currently disabled in the ASAP3 options.
The option “Enable Working Point functionality for 1D and 2D
characteristics (curves and maps)” in the “Online” option tab is not
checked.
68
Appendix: ASAP3 Error Codes
Error code
(decimal)
Description
60800
The value […] is already wired as Recorder value!
It is not possible to wire a recorder value twice. As the DEFINE
RECORDER PARAMERTERS command is cumulative, please check if you
have wired that value in a prior call of DEFINE RECORDER PARAMETERS.
DEFINE RECORDER PARAMETERS
60801
The value […] is already wired as Online value!
It is not possible to wire an online value twice. As the PARAMETER FOR
VALUE ACQUISTION command is cumulative, please check if you have
wired that value in a prior call of PARAMETER FOR VALUE ACQUISITION.
PARAMETER FOR VALUE ACQUISITION
60808
The value […] is contained twice in the list r the new values!
It is not possible to wire the same value twice. Please check the value list
of the current command, it must contain the same value twice.
PARAMETER FOR VALUE ACQUISITION
DEFINE RECORDER PARAMETERS
60809
Invalid start trigger condition!
Please check your trigger condition for:
- Typing errors
- Missing blanks between variables and operators
- Wrong device names for variables
- Missing quotation marks for variables or variable/device names
that contain blanks
DEFINE TRIGGER CONDITION
60810
Invalid stop trigger condition!
Please check your trigger condition for:
- Typing errors
- Missing blanks between variables and operators
- Wrong device names for variables
- Missing quotation marks for variables or variable/device names
that contain blanks
DEFINE TRIGGER CONDITION
60811
Command […] is not possible while recorder is running. Stop
recorder with the command ACTIVATE RECORDER and Mode=0
first!
The recorder must be stopped for the current command.
PARAMETER FOR VALUE ACQUISTION
GET USER DEFINED VALUE LIST
DEFINE RECORDER PARAMETERS
DEFINE TRIGGER CONDITION
GET RECORDER RESULTS HEADER
GET RECORDER RESULTS
SAVE RECORDER FILE
LOAD RECORDER FILE
Appendix: ASAP3 Error Codes
69
Error code
(decimal)
Description
60812
No recorder data available. Load a recorder file or set up a new
recording first!
A possible reason could also be that the last LOAD RECORDER FILE
operation failed for some reason (e.g. access restrictions, corrupted file
etc).
GET RECORDER RESULTS HEADER
GET RECORDER RESULTS
SAVE RECORDER FILE
60815
1. An error occurred when adding new value(s)!
The following value(s) could not be found: […]
Please check the spelling or case of the values.
PARAMETER FOR VALUE ACQUISITION
DEFINE RECORDER PARAMETERS
Do also check the option “Labels are case sensitive” in the General page
of the Options dialog. In some cases the client uses variable names in
uppercase which will fail if this option is set.
2. An error occurred when adding new value(s)!
Could not add the following value(s) because all raster tables are
full: […]
No further wiring possible. Try to remove variables before adding new
ones.
PARAMETER FOR VALUE ACQUISITION
DEFINE RECORDER PARAMETERS
3. An error occurred when adding new value(s)!
Could not get a Raster for the following variables (Check your
ASAP2 file): […]
The ASAP2 file might contain incorrect raster definitions.
PARAMETER FOR VALUE ACQUISITION
DEFINE RECORDER PARAMETERS
60816
No device found for LUN […]
Please check your script for prior errors. A possible reason could be a
missing or failed SELECT DESCRIPTION FILE AND BINARY FILE or
DEFINE DESCRIPTION FILE AND BINARY FILE.
PARAMETER FOR VALUE ACQUISITION
GET USER DEFINED VALUE LIST
DEFINE RECORDER PARAMETERS
Note: Only devices that support calibration pages can be used with the
SELECT DESCRIPTION FILE AND BINARY FILE command or the standard
syntax of the DEFINE DESCRIPTION FILE AND BINARY FILE command.
See the _AUXIN_ variant of the DEFINE DESCRIPTION FILE AND BINARY
FILE for further information.
70
Appendix: ASAP3 Error Codes
Error code
(decimal)
Description
60819
Start/stop trigger not possible in combination with Nr. of
Samples!
If triggers are defined Nr. of Samples must be set to 0!
INCA does only support start/stop trigger or sample limitation over
ASAP3.
DEFINE TRIGGER CONDITION
60820
The file […] already exists and can not be overwritten because it
is read-only!
Remove the read-only flag from this file to be able to overwrite it. Check
also if the target device (e.g. a removable media) is write-protected.
This error could also be caused by right limitations on a network drive. In
this case you have to contact you network administrator.
SAVE RECORDER FILE
60823
No acquisition rates available for the device with LUN […]!
Perhaps the ASAP2 file does contain incorrect raster definitions for the
device represented by the LUN.
PARAMETER FOR VALUE ACQUISITION
DEFINE RECORDER PARAMETERS
60832
Command not possible because a 'LOAD RECORDER FILE'
command is still running in the background!
ASAP3 performs a LOAD RECORDER FILE in the background, to allow for
a fast response to the LOAD RECORDER FILE command. During the
background execution of this command, no other command that affects
the recorder configuration, is allowed to be executed.
ACTIVATE RECORDER
GET RECORDER STATUS
GET RECORDER RESULTS HEADER
GET RECORDERRESULTS
SAVE RECORDER FILE
LOAD RECORDER FILE
60833
Command not possible because a 'SAVE RECORDER FILE'
command is still running in the background!
ASAP3 performs a LOAD RECORDER FILE in the background to allow for a
fast response to the LOAD RECORDER FILE command. During the
background execution of this command, no other command that affects
the recorder configuration is allowed to be executed.
ACTIVATE RECORDER
GET RECORDER STATUS
GET RECORDER RESULTS HEADER
GET RECORDERRESULTS
SAVE RECORDER FILE
LOAD RECORDER FILE
Appendix: ASAP3 Error Codes
71
5
ETAS Contact Addresses
ETAS HQ
ETAS GmbH
Borsigstraße 14
70469 Stuttgart
Germany
Phone:
Fax:
WWW:
+49 711 89661-0
+49 711 89661-106
www.etas.com
ETAS Subsidiaries and Technical Support
For details of your local sales office as well as your local technical support team and product
hotlines, take a look at the ETAS website:
ETAS subsidiaries
ETAS technical support
72
WWW:
WWW:
www.etas.com/en/contact.php
www.etas.com/en/hotlines.php
ETAS Contact Addresses
73
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising