PCAN Explorer and GPRS Link

[rampinia]

Hello,
I have a PEAK GPRS Link module with firmware completly rewritten by myself. I have LOG activity within this module. Is it possibile to have the file format of the *.trc made by PCAN explorer so to use the same format within GPRS Link? doing this I can use PCAN Explorer symbol file to open and export data recorded within GPRS link.

Regards,

Andrea

[PEAK-Support]

Sample of a standard TRACE File (no symbolic Information - RAW CAN):

Trace File (ASCII)

trace-sample.jpg (77.97 KiB) Viewed 4756 times

The Header:
; is a REMARK for comments, except a $ is follow (STARTTIME/FILEVERSION)
FILEVERSION: please use 1.1 to be compatible with PCAN-Explorer 4/5
STARTTIME: Date and time are handled as a "floating point" value. The integral part of the value is the number of days that have passed since December 30, 1899. The fractional part is fraction of a 24 hour day that has elapsed.
Example
39414.8339742292

39414 indicates the days passed from 30 December 1899, without execute a calculation, it is enough to check with Excel spreadsheet: 28.11.2007

Time calculation 1

time1.jpg (15.13 KiB) Viewed 4756 times

0.8339742292 represents the fraction of the elapsed day expressed in 24 hours.
When 24 hours are elapsed, the integer part increments of 1 unit.
In one day there are 24 hours, 1440 minutes, 86.400 seconds, 86.400.000 ms.

Time calculation 2

time2.jpg (19.96 KiB) Viewed 4756 times

Columns description:
* Message Number is a simple Counter
* Time Offset is the Offset in ms from Frame to Start of Trace (see header)
* Type is the Message Type - could be

• -Rx for received Frames
  -Tx for send Frames - if you like to store this also
  If a RTR is send or Received, in the Data Byte field a RTR is written. Sample:
  2) 7468.9 Tx 0000 8 RTR

* ID is the CAN ID (HEX)
* Data Length Code is the counter of the used the Data Bytes in this frame
* Data could be 0 to 8 single Bytes in HEX


The Trace file is a ASCII Textfile (8Bit character - no unicode).
The Linebreak is a CR (0x0D) and a LF (0x0A)
We do not use Tab - only Space (0x20)

Trace File - view in HEX Editor

trace-sample2.jpg (180.71 KiB) Viewed 4756 times