PCAN UDS API Migration from V1.0.0 to V2.1.0

[Shail]

Hello,

We need to migrate PCAN UDS API V2.1.0 latest at the moment from V1.0.0.

1) What are the steps we need to follow to do migration from V1.0.0 to V2.1.0?
2) Is prototype has been change due to feature change from V1.0.0 to V2.1.0 ?
3) What changes in terms of PCAN BASIC, PCAN ISO-TP, PCAN UDS DLL or functionality? We observed PCAN ISO-TP 2016 version available but PCAN UDS API 2013 version available?
4) Which user manual suitable for PCAN UDS V2.1.0?

[PEAK-Support]

Please always check the History Information on our support page to check what exact was changed.

If a new API Specification is not backward compatible, because the ISO specification is not backward compatible, we always keep the API´s itslef backward compatible,
and enhance the APIs with the new specification / new defined functionality. All is well documentes in the PDF / Online Help that comes with the single APIs.

So first use with your existing application the latest API / DLL and test if all works as it did before. After that chek in the Documentation which new functions are available, and which you need for your Application.
To use the APIs you should buy the official specification from the ISO organization - here all changes are described in detail. This document is actually a must read if you want to work with the APIs.

[Shail]

Hello,

In both version of PCAN UDS API UDS_Initialize prototype and return type different.
So Can u explain How it can be called back word compatible ?
Can we use PCAN V2.1.1 API without any change in previous API V1.0.0?

For example,
PCAN V2.1.1 PCAN UDS API
uds_status __stdcall UDS_Initialize_2013(
cantp_handle channel,
cantp_baudrate baudrate,
cantp_hwtype hw_type = 0,
uint32_t io_port = 0,
uint16_t interrupt = 0);

PCAN UDS V1.0.0 PCAN UDS API
TPUDSStatus __stdcall UDS_Initialize(
TPUDSHandle Channel,
TPUDSBaudrate Baudrate,
TPUDSHWType HwType = 0,
DWORD IOPort = 0,
WORD Interrupt = 0);

Thanks and Regards,

[PEAK-Support]

Simply use the old function and it is compatible - if you need the new features - use the new functions - Details are part of our Documentation and ISO Documents.