Contents I

Table of Contents
Part I D-PDU API Release Notes 2
1 D-PDU API Version
...................................................................................................................................
1.7.2 2
2 D-PDU API Version
...................................................................................................................................
1.7.2.1 2
3 D-PDU API Version
...................................................................................................................................
1.7.2.2 2
4 D-PDU API Version
...................................................................................................................................
1.7.2.3 3
5 D-PDU API Version
...................................................................................................................................
1.7.2.4 4
6 D-PDU API Version
...................................................................................................................................
1.7.2.5 5
7 D-PDU API Version
...................................................................................................................................
1.7.3 5
8 D-PDU API Version
...................................................................................................................................
1.8.0 8
9 D-PDU API Version
...................................................................................................................................
1.8.1 8
10 D-PDU API Version
...................................................................................................................................
1.8.2 9
11 D-PDU API Version
...................................................................................................................................
1.8.3 9
12 D-PDU API Version
...................................................................................................................................
1.8.4 10
13 D-PDU API Version
...................................................................................................................................
1.8.5 10
14 D-PDU API Version
...................................................................................................................................
1.8.6 11
15 D-PDU API Version
...................................................................................................................................
1.8.7 13
16 D-PDU API Version
...................................................................................................................................
1.8.8 13
17 D-PDU API Version
...................................................................................................................................
1.8.9 14

Index 0

KPIT Infosystems GmbH, 2013

I
 2 D-PDU API Handbuch

1 D-PDU API Release Notes

1.1 D-PDU API Version 1.7.2

First official In2Soft D-PDU API delivery version.

1.2 D-PDU API Version 1.7.2.1

Changes in D-PDU API DLL

Bugfix: Roll of log files

Problem:
In the previous D-PDU API version sometimes the automatic roll of the log files didn't
work. As a result it was always logged in the same file which means that the log file
wasn't limitted in size. Additionally the performance of the D-PDU API was much slower.
State: fixed

1.3 D-PDU API Version 1.7.2.2

Changes in D-PDU API DLL

Bugfix (ID#592): pin order for link creation

Problem:
In the previous D-PDU API version the order of pin information given on a call of
PDUCreateComLogicalLink was relevant for resource selection instead of only checking
the pin type.
State: fixed

KPIT Infosystems GmbH, 2013

 D-PDU API Release Notes 3

1.4 D-PDU API Version 1.7.2.3

Changes in D-PDU API DLL

Bugfix (ID#593): duplicate CoP handles

Problem:
For standard and internal ComPrimitives it was (theoretically) possible that the same
CoP handle was assigned several times. This led to incorrect behaviour on reception of
events from the firmware.
State: fixed

Bugfix (ID#575): spaces within simulation filename

Problem:
If the simulation filename or path in the option string included spaces, the D-PDU API
wasn't able to open the simulation file.
State: fixed

Bugfix (ID#586): CAN-API resources in MDF dependent on number of

controllers
Problem:
Up to the last version, there was only one entry in the MDF for all types of dSPACE
CAN-API devices. So the MDF showed resources for controllers that are not available on
a device if it has only one controller.
Solution:
Now, there are two types of CAN-API modules, identified by the module type IDs 11 (1
CAN controller) and 12 (2 CAN controllers). Accordingly there are also two entries for the
device types within the MDF file.
State: fixed

Bugfix (ID#587): Number of modules for dSPACE calibration hub CAN-API

device
Problem:
If CAN-API device calibration hub is used, for each can controller a module instance is
returned by the D-PDU API.
Solution:
Several controllers in a CAN-API device are now combined to one module instance.

KPIT Infosystems GmbH, 2013

 4 D-PDU API Handbuch

State: fixed

Bugfix (ID#612): Simulation file lines with more than 4096 bytes
Problem:
The simulation module supports no simulation file lines with more than 4096 bytes. So a
full UDS request or response can't be declared.
State: fixed

Changes in In2Soft eCOM Firmware

Bugfix (ID#576): timer initialization

Problem:
The variable used for timer calculation wasn't initialized properly.
State: fixed

Changes in dSPACE CAN-API PduProtocolLayer

Bugfix (ID#605): dSPACE CAN-API: wrong baudrate is used if link s opened

a 2nd time
Problem:
If a link was reopend again a wrong baudrate was may set to the CAN-API device, as
the initilization wasn't done properly.
State: fixed

1.5 D-PDU API Version 1.7.2.4

Changes in D-PDU API DLL

Bugfix (ID#605): dSPACE CAN-API: wrong baudrate is used if link s opened

a 2nd time
Problem:
The D-PDU API DLL didn't realize that a ComParam was changed if it is set to the same

KPIT Infosystems GmbH, 2013

 D-PDU API Release Notes 5

value like the 1st link has.

State: fixed

Changes in Firmware (PduProtocolLayer)

Bugfix (ID#580): Buffer overflow in i2sCommLib

Problem:
A buffer overflow occured if many parallel links operated on full capacity. This led to an
error in the PduProtocolLayer.
State: fixed

1.6 D-PDU API Version 1.7.2.5

Changes in D-PDU API DLL

Change (ID#690): dSPACE CAN-API: I/O control for update of available

devices
Problem:
The list of available dSpace CAN-API devicese was only created on a PDUConstruct
call. Now the list of available CAN-API devices can be updated by calling the I/O control
"PDU_IOCTL_UPDATE_DEVICES".

1.7 D-PDU API Version 1.7.3

Changes in D-PDU API DLL

New Funtions
Monitoring support for CAN and K-Line
dSpace K-Line Support
Logging without deletion of logfiles; creation of timestamped log files instead

KPIT Infosystems GmbH, 2013

6 D-PDU API Handbuch

Bugfix: handling of invalid mapping tables

State: fixed

Bugfix: Callback function sporadically isn't executed

State: fixed

Bugfix (ID#944): In2Soft eCOM reconnect after connection loss not possible
State: fixed

Bugfix: K-Line Resources limited to one resource for KWP2000 and

KWP2000LP per controller
State: fixed

Bugfix: connection loss of shared devices if UPDATE_DEVICES i/o control

is executed
State: fixed

Bugfix: Callback function sporadically isn't executed

State: fixed

Bugfix: I2SX reconnect after connection loss

State: fixed

Bugfix: iso14230 k-line synchronisation

State: fixed

Bugfix (Bug #850): PPL KLine not deinitialized at PduApi kill

State: fixed

Changes in In2Soft eCOM Firmware

Bugfix: handling for protocols KWP2000 and KWP2000LP on K-Line

The handling of ComParam and URID address parameters is now conforme to D-PDU

KPIT Infosystems GmbH, 2013

 D-PDU API Release Notes 7

API specification.

Bugfix (ID #620): K-Line: tester present response is returned instead of

request response
The PduProtocolLayer sometimes returned the tester present response instead of the
ECU request response.
State: fixed

Bugfix (ID #706): TP20 ComParam CP_VWTP_BlockSize isn't evaluated

correctly
The PduProtocolLayer always sends blocks with a size of CP_VWTP_BlockSize+1 CAN
frames if CP_VWTP_BockSize is not zero.
State: fixed

New Function (ID #713): K-Line pullup resistor

The optional ComParam CP_K_LinePullup is supported now. Additionally, the
ComParam can be overwritten using the D-PDU API INI file.

The ComParam CP_K_LinePullup supports the following values:

0: No pullup
1: 12V pullup (500 Ohm)
2: 24V pullup (1000 Ohm)
The In2Soft D-PDU API internally supports the additional value:
3: AUTO DETECTION

The initial value for CP_K_LinePullup in the In2Soft D-PDU API is '3: AUTO
DETECTION'. So, if no client application sets the ComParam, the PduProtocolLayer
measures the current VBat. If the measured voltage is greater 18V, the 24V pullup will
be used, otherwise the 12V pullup.

Additionally, the In2Soft D-PDU API offers the possibility to set the pullup mode in the INI
config file. In the section 'SETTINGS' the parameter KLinePullup can have the following
values:

'NO' (0): no pullup

'12V' (1): 12V system (500 Ohm)

KPIT Infosystems GmbH, 2013

 8 D-PDU API Handbuch

'24V' (2): 24V system (1000 Ohm)

'AUTO' (3): auto detection
'OFF' (4): use ComParam value CP_K_LinePullup (default)

If one of these values is set (except OFF) any given CP_K_LinePullup ComParam value
will be overwritten. Note that this setting is used by any K-Line link on any module device
(if the device supports K-line and especially to set the pullup; currently just In2Soft
eCOM is supported)

Bugfix: K-Line synchronization

The iso14230 kernel driver sporadically blocked during K-Line communication.
State: fixed

Bugfix (Bug #544): PDU_INFO_MODULE_LIST_CHG event is not generated

A reconnect of a lost eCOM VCI is now detected.
Dependent on the INI setting AutoScanCycleTimeMS (default 5000) the broadcast is
send cyclic. If new modules are detected, they are added to the module list. If a
reconnected module is detected, it gets available again.
A MODULE_LIST_CHANGE event is also fired if the BUSY/FREE state of a module did
change.
State: fixed

1.8 D-PDU API Version 1.8.0

Changes in D-PDU API DLL

- Performance improvement

1.9 D-PDU API Version 1.8.1

Changes in Firmware (PduProtocolLayer)

Bugfix: Timestamps for K-Line monitoring
Problem:
The timestamps for K-Line messages during K-Line monitoring weren't set properly.
State: fixed

KPIT Infosystems GmbH, 2013

 D-PDU API Release Notes 9

Bugfix: Access violation error on K-Line FastInit

Problem:
On Execution of an empty FastInit message, in some UseCases an access violation
error could occur.
State: fixed

1.10 D-PDU API Version 1.8.2

Changes in D-PDU API DLL

New Function
Logging of D-PDU-API Software Version and D-PDU-API Software Date during
PDUConstruct

Changes in In2Soft eCOM Firmware

New Function
Enabling of Lowspeed-CAN for 2nd CAN-Controller

1.11 D-PDU API Version 1.8.3

Changes in D-PDU API DLL

Bugfix: Correcture of P2Max default value for protocol ISO 14230-3

Problem: P2Max default value was set to 100ms instead of 50ms
State: fixed

Changes in Firmware

Bugfix: Handling of negative responses with code 0x78 for DCI-Kline

(dSpace)
Problem: positive responses from ECU were ignored in case of a preceeding
negative response with NRC 0x78
State: fixed

KPIT Infosystems GmbH, 2013

 10 D-PDU API Handbuch

Bugfix: CAN-Monitoring for IXXAT devices

Problem: direction for monitoring frames was always Tx (expected: Rx)
State: fixed

Bugfix: Controller-handling for IXXAT devices

Problem: only first CAN controller was used
State: fixed

1.12 D-PDU API Version 1.8.4

Changes in D-PDU API DLL

Bugfix: D-PDU API crash

Problem: D-PDU API crashed when an UPDATE_DEVICES-Ioctl was sent
immediately up to an UPDATEPARAM-ComPrimitive
State: fixed

1.13 D-PDU API Version 1.8.5

Changes in D-PDU API DLL

Change: Logging
- number of logfiles is limited to value specified in .ini-file
- oldest logfile will be removed if maximum number is reached
- reduced log-output

Change: PDUAPI_IN2SOFT.ini configuration

- number of logfiles set to 5
- logfile size set to 10 MB
- AutoScanDevices set to 0 (disabled)
- CheckURIDTable set to 1 (CAN-IDs in URIDTable must be unique for a certain
logical link)
- DefaultTargetIP set to 172.29.127.129 for In2Soft VCI detection

Bugfix: Lost messages from firmware

Problem: Reception error will occur if firmware sends two messages in a row and the

KPIT Infosystems GmbH, 2013

 D-PDU API Release Notes 11

first message exceeds MTU of TCP

State: fixed

Changes in Firmware

Bugfix: missing PDU_COPST_FINISHED event

Problem: no PDU_COPST_FINISHED was created when a
PDU_ERR_EVT_PROT_ERR occured
State: fixed

Bugfix: missing responses in functional addressing mode

Problem: responses from some ECUs were not returned as result items
State: fixed

1.14 D-PDU API Version 1.8.6

Changes in D-PDU API DLL

Bugfix: Logging
Problem: Logfile names with two or more timestamps were created if all logfiles were
removed after a PDUDestruct call without unloading the DLL.
State: fixed

Bugfix (ID#1049): Deadlock in PDUModuleDisconnect when eCom was

powered off before
Problem: If PDUModuleDisconnect is executed after eCom is switched off (with open
LogicalLinks), a deadlock in PDU API-Dll will cause the higher-level application to
hang up
State: fixed

Change: Use of std library instead of boost for D-PDU-API Linux version
- class shared_ptr is taken from std library

Change: Order of writing ComParam sets to firmware

- URID table is written ahead of all other ComParam sets

KPIT Infosystems GmbH, 2013

12 D-PDU API Handbuch

Change: enhanced error reporting

- more detailed information on errors by means of ExtraErrorInfoId (see Module
Description File)

Change: use of MS Windows environment variables in LogFilename of

PDUAPI_IN2SOFT.ini
- use of environment variables enabled in LogFilename. Variable must be
surrounded by two percent signs. Example:
LogFilename=%HOMEPATH%\logs\PDUAPI.LOG

Change: automatic log directory creation for MS Windows

- automatically creation of directory for logging in case of nonexistent log paths

Changes in Firmware

Bugfix: missing PDU_COPST_FINISHED event

Problem: no PDU_COPST_FINISHED was created when a
PDU_ERR_EVT_TX_ERROR occured for functional addressing
State: fixed

Bugfix (ID#1028): Time between flow control from ECU and next
consecutive frame
Problem: Value of CP_Cs is used as minimum time span between reception of flow
control and transmission of next consecutive frame. Correctly, the STMin value
reported by the vehicle should be used.
State: fixed

Bugfix (ID#714): PDU_ERR_EVT_RX_TIMEOUT after expiration of

CP_CyclicRespTimeout
Problem: If CP_CyclicRespTimeout for cyclic receive ComPrimitives
(numRecvCycles = -1) expires, a PDU_ERR_EVT_RX_TIMEOUT is generated, but
the ComPrimitive's state should change immediately to PDU_COPST_FINISHED.
State: fixed

Bugfix (ID#1025): PDU_ERR_EVT_RX_TIMEOUT for functional SendRecv-

ComPrimitives with multiple responses
Problem: For functional SendRecv-ComPrimitives with multiple responses
(numRecvCycles = -2), a PDU_ERR_EVT_RX_TIMEOUT is always generated.
Correctly, the ComPrimitive's state should change immediately to
PDU_COPST_FINISHED without error events, if at least one valid response is

KPIT Infosystems GmbH, 2013

 D-PDU API Release Notes 13

received.
State: fixed

1.15 D-PDU API Version 1.8.7

Changes in D-PDU API DLL

BugFix: Version check mask

Problem: D-PDU API may crash if firmware version does not match D-PDU API
version. From now on, D-PDU API and firmware have to agree in first three numbers
of version.
State: fixed

BugFix: Logging
Problem: Each time a PDUConstruct is executed, D-PDU API creates a new logfile if
LogFilename in PDUAPI_IN2SOFT.ini contains slashes and backslashes. Leads to
violation of maximum number of logfiles.
State: fixed

New Function for dSpace CAN-API devices

I/O control PDU_IOCTL_GET_CTRL_ID introduced to determine controller index of
module to be used for specified resource id (passed as input parameter of type
PDU_IT_IO_UNUM32)

1.16 D-PDU API Version 1.8.8

Changes in Firmware

Bugfix: PDU_ERR_EVT_NOERROR instead of PDU_ERR_EVT_TX_ERROR

(eCom only)
Problem: If eCom is used for K-Line communication with wrong pull-up resistor value,
an error event of type PDU_ERR_EVT_NOERROR is generated instead of
PDU_ERR_EVT_TX_ERROR.
State: fixed

KPIT Infosystems GmbH, 2013

 14 D-PDU API Handbuch

1.17 D-PDU API Version 1.8.9

Changes in D-PDU API DLL

BugFix (ID#1146): incorrect LogFilename in PDUAPI_IN2SOFT.ini

Problem: Segmentation fault during PDUConstruct if LogFilename property in
PDUAPI_IN2SOFT.ini is not set properly
State: fixed

BugFix (ID#1146): incorrect LogLevel in PDUAPI_IN2SOFT.ini

Problem: Segmentation fault during PDUConstruct if LogLevel property in
PDUAPI_IN2SOFT.ini is not set properly
State: fixed

BugFix: incorrect behaviour in case of EnableVirtualDevices = 0 (dSpace)

Problem: Although EnableVirtualDevices is disabled, it is not possible to use all of the
six supported controllers of "real" devices
State: fixed

KPIT Infosystems GmbH, 2013