PEAK-Converter Version History

2017-09-07 - Version 2.1.2

Improvements:

  • Added support for ASC files with CAN-FD information (ASC version 8.1 and greater)
  • Remarks:
    • CAN-FD supported only as "Source/input" file
    • Conversion from TRC (PCAN-Trace) to ASC can only be achieved for standard CAN
    • Target version is automatically set to ASC 7.0 when converting from TRC to ASC
    • Opening the results folder now explicitly calls the process using its name, "Windows Explorer". This avoids problems on some computers where the process call could be interpreted in a wrong way

Bug fixes:

  • Loading a corrupted or empty BTR file was causing the converter to hang-up


2017-06-29 - Version 2.1.1

Bug fixes:

  • The size of resulting *.BTRC trace files was calculated wrong
  • Timestamps in *.BTRC files had rounding problems and were losing some microseconds
  • Some records belonging to the BTRC format were not being included in some scenarios
  • Canceling a conversion operation was causing the tool to hang


2017-05-29 - Version 2.1.0

Improvements:

  • Added support for the new PEAK Binary format (*.BTRC), version 1 (PCAN-Diag FD)
  • General code enhancements

Bug fix:

  • When using the command line, the resulting trace was always empty if the target version was not specified


2016-10-21 - Version 2.0.3

Bug fix:

  • Conversions from PEAK CAN Trace File (any version) to ASC or BTR failed due to a wrong target version check


2016-10-14 - Version 2.0.2

Improvement:

  • Added support for PEAK CAN Trace File format version 2.1 (PCAN-Explorer 6)

Bug fix:

  • The start time information ($STARTTIME) of the first session in a PCAN-Router binary file (BTR) with multiple sessions was being used as start time for all other sessions


2015-09-04 - Version 2.0.1

Improvements:

  • Writing FD messages within a CSV-File is now avoided. It must be a kind of new version for CSV with FD data in the future
  • CSV-File outputs all kind of messages (FD too) now. The output format was lightly modified to be similar to the PCAN-Trace version 2.0
  • The output trace 'CSV' was adjusted to support the new messages types used for CAN-FD data

Change:

  • The message output of the PCAN-Trace format 1.2 was not aligned with the header

Bug fixes:

  • PCAN message trace 2.0 adapted to avoid writing of messages with a length > 8, when there are no FD (J1939 is not allowed)
  • PCAN-Trace message counter was not correlative. It was counting also messages not being written
  • Timestamps of PCAN-Trace messages were erroneously converted to seconds instead of in milliseconds, when saving them in CSV format
  • Conversion PCAN-Trace -> BTR Trace failed if the data to be converted had an unknown format (FD for example), or a length code greater than 8
  • Wrong formatted data was created in traces of the type 'PCAN-Trace 2.0', when the trace file to be converted contained J1939 data
  • Converting to the PCAN-Binary format (BTR) failed, if the source trace contained CAN FD data (PCAN-Trace 2.0)
  • The resolution of timestamps in CSV format was erroneously set to 1 second instead of to 1 millisecond


2015-08-14 - Version 2.0.0

  • New easy to use Wizard user interface
  • Improved conversion process and performance
  • Improved command line usage and options
  • Support for the new PCAN trace format for CAN FD data frames
  • Integrated application help


2013-09-16 - Version 1.9.9

Bug fixes:

  • Some properties of an ASC trace session were not recognized correctly
  • Newer ASC trace versions couldn’t be converted due to some format incompatibilities
  • It was not possible to start a new conversion process after having one canceled, without re-starting the PEAK-Converter

Enhancements:

  • Internal minor changes


2013-02-07 - Version 1.9.8

Bug fix:

  • An "access denied" error was being triggered after converting a file into the trace format
    PCAN-Trace v. 1.1


2012-12-12 - Version 1.9.7

Bug fixes:

  • An exception was being triggered, when a conversion process was cancelled
  • The PEAK-Converter was erroneously reading decimal coded data from ASC files as hexadecimal values


2012-10-17 - Version 1.9.6

Bug fix:

  • An exception was being triggered while interpreting a new binary trace file feature

Enhancement:

  • Binary trace files generated by a PCAN-Router Pro with a wrong or not set Date/Time are now tolerated and can be converted


2012-06-26 - Version 1.9.5

Bug fixes:

  • The variable $FILEVERSION of a PCAN trace file was being ignored when the variable $STARTTIME had a wrong format
  • While converting a LIN-trace to ASC-Trace, the timestamp of the messages was being saved as microseconds instead of seconds
  • An exception occurred while converting a LIN file, when any LIN message had a timestamp with a value bigger than 4 bytes
  • While loading messages from PCAN trace files, extended messages were not always recognized
  • The extended flag of ASC messages was being ignored, causing wrong formatting of extended messages in some scenarios


2012-06-11 - Version 1.9.3

  • Bug fix: A bug when converting BTR files with multi-sessions was fixed. When the option "Include Date and Time" was not checked, only the last session of the BTR file was converted


2012-02-24 - Version 1.9.2

  • Bug fix: A problem determining the beginning of a circular trace session on a BTR (binary trace) file was fixed


2011-11-28 - Version 1.9.1

Improvements:

  • The command OUT (command-line), can now also be used to set the Type of a conversion
  • Using the command-line with at least the command IN starts the conversion process automatically
  • The command AUTO (command-line) has changed its behavior. Now AUTO means, "auto-close" and it is used to close the PEAK-Converter automatically when a conversion process ends successfully
  • New help-document for the command-line. It can be accessed from the Help menu of the PEAK-Converter

Bug fixes:

  • The PEAK-Converter crashed when the command-line has a wrong format
  • The extension of the converted file was wrongly set to ASC, when converting from BTR to CSV
  • When the destination folder for a conversion was set to a root (C:\, D:\ etc.) an extra path character ("\") was wrongly added to the destination path


2011-10-12 - Version 1.9.0

Improvements:

  • Support for conversion to Character Separated Values format (CSV). This conversion is also supported through command line
  • The conversion range for PCAN-Router Pro trace files was augmented. Now it can be converted to ASC and CSV, instead of only to the PCAN-Trace format
  • Support for the new enhanced PCAN-Router Pro trace that can store more than 16 trace sessions per file

Bug fixes:

  • The conversion process of a PCAN-Router Pro trace (*.btr) to a PCAN-Trace file (*.trc) couldn’t be canceled
  • The parsing of Error/Status frames was done wrong
  • Several changes to avoid a crash while parsing Error/Status frames


2011-08-08 - Version 1.8.9

Bug fix:

  • The conversion of PCAN-Router Pro traces (*.btr) had a problem calculating the amount of data to be read from a trace file, resulting in a Out-Of-Memory error


2011-08-04 - Version 1.8.8

Bug fix:

  • The conversion of PCAN-Router Pro traces (*.btr) had a problem calculating some time values within the stored trace sessions, resulting in wrong (jumps) timestamp for several blocks of CAN frames


2011-05-31 - Version 1.8.7

Bug fix:

  • PCAN-LIN trace file conversions were showing negative timestamps


2011-05-30 - Version 1.8.6

Improvement:

  • Support for conversion from PCAN-LIN View Pro trace files (*.ltrc) to PCAN-Trace format. Remark: This conversion is intended just for debug purposes and doesn’t handle all LIN information contained in the *.ltrc file


2011-04-12 - Version 1.8.5

Improvements:

  • A new option was added to include Data-Time information into the target file of a conversion process
  • Code enhancements for a better performance

Bug fix:

  • Slightly wrong Date-Time format used for the target file name was corrected


2011-03-18 - Version 1.8.4

Improvements:

  • Support for conversion from Vector Ascii Trace format (ASC) to PCAN-Trace format
  • The PCAN-Trace Converter can now be controlled using the command line

Bug fix:

  • Several changes to avoid an application crash due to a wrong message format


2010-12-20 - Version 1.7.3

Improvement:

  • Status and Error frames within PCAN-Trace files are now supported

Bug fix:

  • Concerning crash when converting trace files with status and/or error frames


2010-12-15 - Version 1.7.2

Improvements:

  • Enhanced user interface
  • A conversion process can now be canceled


2010-10-25 - Version 1.7.1

Bug fix:

  • Corrections due to application crashes


2010-07-20 - Version 1.7.0

Improvement:

  • Support for conversion to Vector Ascii Trace format (ASC)
  • First official release


...