MAKING MODERN LIVING POSSIBLE
User Manual
Danfoss Telematics Solutions
Logging Data
powersolutions.danfoss.com
User Manual |
Danfoss Telematics Solution Logging Data |
|
|
Revision history |
Table of revisions |
|
|
|
|
|
|
|
Date |
Changed |
Rev |
|
|
|
|
|
October 2015 |
Danfoss layout |
0100 |
|
|
|
|
|
July 2015 |
Review |
0001 |
|
|
|
|
|
February 2015 |
First edition |
0000 |
|
|
|
|
2 |
BC00000348 en-US • Rev 0100 • October 2015 |
User Manual |
Danfoss Telematics Solution Logging Data |
|
Contents |
|
|
About this Manual |
|
|
|
General................................................................................................................................................................................................. |
5 |
Creating object dictionary groups and objects |
|
|
|
Rename entry..................................................................................................................................................................................... |
7 |
|
Modifying the logging configuration....................................................................................................................................... |
7 |
|
Configuring the device for Data Logging................................................................................................................................ |
7 |
|
Logging CAN messages and sending them to DTS portal................................................................................................ |
8 |
|
Receiving the J1939 message...................................................................................................................................................... |
9 |
|
Creating a PGN 61444................................................................................................................................................................ |
9 |
|
Receive Message Communication Parameters.............................................................................................................. |
10 |
|
Timeout and Conditions........................................................................................................................................................ |
11 |
|
Logging of all data bytes every 60 seconds.................................................................................................................... |
11 |
|
Logging................................................................................................................................................................................... |
11 |
|
Log specific bytes under certain conditions or every 10 minutes.......................................................................... |
13 |
|
Variables................................................................................................................................................................................. |
13 |
|
Logging................................................................................................................................................................................... |
14 |
|
Mapping....................................................................................................................................................................................... |
15 |
|
Active Conditions................................................................................................................................................................ |
15 |
|
Data Link................................................................................................................................................................................. |
16 |
|
Jobs................................................................................................................................................................................................ |
17 |
|
Job 1......................................................................................................................................................................................... |
17 |
|
Job 2......................................................................................................................................................................................... |
19 |
|
Saving CAN messages to microSD memory cards............................................................................................................. |
20 |
|
Logging GNSS positions.............................................................................................................................................................. |
20 |
|
Logging internal variables.......................................................................................................................................................... |
21 |
Configure Logged Data View |
|
|
|
Data view.......................................................................................................................................................................................... |
24 |
|
Adapt the configuration to the web portal.......................................................................................................................... |
24 |
|
Elements of the xml file............................................................................................................................................................... |
25 |
|
XML Header...................................................................................................................................................................................... |
25 |
|
Message definition........................................................................................................................................................................ |
25 |
|
Global dictionary............................................................................................................................................................................ |
26 |
|
Transformer...................................................................................................................................................................................... |
26 |
|
Units.................................................................................................................................................................................................... |
26 |
|
Value definitions............................................................................................................................................................................. |
27 |
|
Parsing definition .......................................................................................................................................................................... |
28 |
|
View definition ............................................................................................................................................................................... |
29 |
Appendix |
|
|
|
CLF file................................................................................................................................................................................................ |
32 |
|
File header................................................................................................................................................................................... |
32 |
|
File payload................................................................................................................................................................................. |
32 |
|
Message Payload Definitions............................................................................................................................................... |
33 |
|
Timestamp Value Definitions............................................................................................................................................... |
35 |
|
Message tail...................................................................................................................................................................................... |
35 |
|
Bitmask.............................................................................................................................................................................................. |
36 |
|
Examples........................................................................................................................................................................................... |
36 |
|
Example 1.................................................................................................................................................................................... |
36 |
|
Section 1, “File Header” [3].................................................................................................................................................... |
36 |
|
Section 2, “File Payload” [3]................................................................................................................................................... |
36 |
|
Message Type 0 - 11 bit CAN Message - Node 1........................................................................................................... |
36 |
|
Message Type 1 - 29 bit CAN Message - Node 1........................................................................................................... |
36 |
|
Message Type 2 - 11 bit CAN Message - Node 2........................................................................................................... |
37 |
|
Message Type 3 - 29 bit CAN Message - Node 2........................................................................................................... |
37 |
|
Message Type 16 - GPS Location Data (J1939 Format)............................................................................................... |
37 |
|
Message Type 17 - GPS Movement Data (J1939 Format).......................................................................................... |
37 |
|
Timestamp Type 00 = No Time Stamp.............................................................................................................................. |
37 |
|
Timestamp Type 01 = UNIX Time Stamp......................................................................................................................... |
37 |
|
Section 3, “Message Tail” [11]............................................................................................................................................... |
37 |
BC00000348 en-US • Rev 0100 • October 2015 |
3 |
User Manual |
Danfoss Telematics Solution Logging Data |
|
|
Contents
Example 2.................................................................................................................................................................................... |
37 |
4 |
BC00000348 en-US • Rev 0100 • October 2015 |
User Manual |
Danfoss Telematics Solution Logging Data |
|
|
This document is part of the Danfoss Telematics Solutions portal and provides important information on the intended use, and operation of the portal described below.
The device is delivered with a basic configuration. Customize the configuration to your purposes by defining the CAN messages to be logged and by using the WS Configurator tool to update the device configuration (via CAN bus or remotely).
BC00000348 en-US • Rev 0100 • October 2015 |
5 |
User Manual |
Danfoss Telematics Solution Logging Data |
|
|
Configure the device with WS Configurator. You can find the basic instructions for this in WS 403 Remote Solution Installation Guide - L1419125.
You can create, rename, or remove object dictionary groups or objects in the tree structure.
Below is an explanation of how to create object dictionary groups and objects. In the example, the object RECEIVE MESSAGE PDO is created.
In order to create the object Receive Message PDO, you need the object dictionary group CUSTOM CAN COMMUNICATION and then the object dictionary group Receive CAN Messages (PDOs).
1.Open the WSxxx_DanfossDefault.DOD configuration file
2.Right-click on the top entry in the tree structure to open the context menu.
3.In the context menu, click on New Object Dictionary Group > Custom CAN Communication. This creates the object dictionary group Custom CAN Communication.
4.Right-click on the object dictionary group Custom CAN Communication.
5.In the context menu, click on New Object Dictionary Group > Recieve CAN Messages (PDOs). This creates the object dictionary group Receive CAN Messages (PDOs).
6. Right-click on the object dictionary group Recieve CAN Messages (PDOs).
6 |
BC00000348 en-US • Rev 0100 • October 2015 |
User Manual Danfoss Telematics Solution Logging Data
Creating object dictionary groups and objects
7. In the context menu, click on New Object Dictionary Entry > Recieve Message PDO.
This opens the window Number of new Objects and their Version.
8.Under Number of new Objects, enter the number of objects (received messages) you want to create. In this example: 1.
9.Click on the OK button.
The object Receive Message PDO is created.
Rename an entry in the tree structure;
1.Click on the corresponding entry to select it.
2.Click on the entry again to rename it.
In logging mode, the device logs CAN messages, GNSS data, and internal variables. All logged data is saved to an internal, nonvolatile memory and sent to the DTS portal.
Alternatively, you can also save the data to an inserted microSD memory card. You can read off the data saved on the microSD memory card using the USB interface.
The internal nonvolatile memory has a capacity of 32 MB and can save a maximum of 5000 files.
When the memory is full, each new file saved is overwritten over the oldest file. Here you will find an explanation of how to configure the device, using some concrete examples.
You must define basic variables in order to correctly link up the device with an existing CAN network.
BC00000348 en-US • Rev 0100 • October 2015 |
7 |
User Manual |
Danfoss Telematics Solution Logging Data |
|
|
Creating object dictionary groups and objects
1.In the object dictionary group Device Variables, click on the variable Device Application MasterMode.
2. Enter the value 0 to enable Data Logging/File Transfer Mode.
You must configure at least the following variables to enable CAN communication (the variables belong to the object dictionary group Device Variables > CAN Basic Settings):
•CANopen NMT Startup
•CAN1 Device CANopen Node ID
•CAN1 Device Baud Rate
•CAN2 Device CANopen Node ID
•CAN2 Device Baud Rate
Variable |
Value |
Function |
|
|
|
CANopen NMT Startup |
0 |
Automatically sets the device to CANopen mode |
|
|
Operational. |
|
|
|
CAN1: Device CANopen |
1 … 127 (default 37) |
The CANopen node address / device ID number (can be |
Node ID |
|
left at standard value). |
|
|
|
CAN1: Device Baud Rate |
min. 50 kbit/s |
The bit rate at which the CAN bus operates |
|
max. 1 Mbit/s |
|
|
(default: 250 kBit/s) |
|
|
|
|
8 |
BC00000348 en-US • Rev 0100 • October 2015 |
User Manual |
Danfoss Telematics Solution Logging Data |
|
|
|
|
|
|
Creating object dictionary groups and objects |
|
|
|
|
|
|
|
|
Variable |
Value |
Function |
|
|
|
|
|
CAN2: Device CANopen |
1 … 127 (default 37) |
The CANopen node address / device ID number (can be |
|
Node ID |
|
left at standard value). |
|
|
|
|
|
CAN2: Device Baud Rate |
min. 50 kbit/s |
The bit rate at which the CAN bus operates |
|
|
max. 1 Mbit/s |
|
|
|
(default: 250 kBit/s) |
|
|
|
|
|
For the logfiles, you must configure further variables (These variables belong to the object dictionary group Device Variables > Logging):
•Logging – File Upload Period
•Logging – File Header Text
•Logging – Send File Command
Variable |
Function |
|
|
Logging – File Upload |
Period in which the logfile is completed and sent to the DTS Portal. 0 = data is sent |
Period |
when the size of the logfile reaches 1 kB. |
|
|
Logging – File Header |
Information text in the head of each logfile. Can contain for instance version |
Text |
information (max. 32 characters). |
|
|
Logging – Send File |
Assign any value to the variable during operation in order to close and send the |
Command |
existing logfile. |
|
|
The logfile is sent to the DTS Portal when its size reaches 1 kB, irrespective of the time set.
Using the example of the receipt of the J1939 message (with PGN 61444 Electronic Engine Controller 1), we will explain the general procedure for configuring CAN messages received. The procedure can also be applied to other CAN messages from other CAN protocols.
You require an object Receive Message PDO in the object dictionary group Custom CAN
Communication > Receive CAN Messages (PDOs).
1.Create the object dictionary group Custom CAN Communication > Receive CAN Messages (PDOs) , if it does not already exist.
See Creating object dictionary groups and objects on page 6.
2.Create the object Recieve Message PDO in the object dictionary group Receive CAN Messages (PDOs).
BC00000348 en-US • Rev 0100 • October 2015 |
9 |
User Manual |
Danfoss Telematics Solution Logging Data |
|
|
Creating object dictionary groups and objects
3.Rename the object.
In this example in PGN 61444.
1. Click on the Communication tab and make the following settings:
Description |
Selection |
Result |
|
|
|
CAN Protocol |
None |
The receive CAN message is a single message (Layer 2). |
|
|
|
Valid on CAN Interface |
Set |
Activates the configuration, sets the reception channel |
|
|
(if several are available). |
|
|
|
2. Click on the Standard Channel tab in the Communication tab and make the following settings:
Description |
Selection |
Result |
|
|
|
Full CAN Message Object |
Set |
Assigns the receive message to a controller channel. |
|
|
|
ID-Length |
29-bit ID |
ID length of the CAN message to be received. |
|
|
|
DOWN-SAMPLE |
Set (100) |
Receive message max. every 100 ms (not every 10ms as |
|
|
transmitted) |
|
|
|
10 |
BC00000348 en-US • Rev 0100 • October 2015 |
User Manual |
Danfoss Telematics Solution Logging Data |
|
||
|
|
|
||
Creating object dictionary groups and objects |
|
|
||
|
|
|
|
|
|
|
Description |
Selection |
Result |
|
|
|
|
|
|
|
Cob-ID |
Fix |
Fixed identifier of the receive message (J1939 PGN |
|
|
|
(00F00400) |
61444). |
|
|
|
|
|
|
|
Mask |
Fix |
This mask determines that bits 8 … 24 of the identifier |
|
|
|
(00FFFF00) |
fixed in Cob-ID must not vary in the identifier of the |
|
|
|
|
receive message. In the J1939 protocol, this is the PGN |
|
|
|
|
area. The first bits of the identifier define the priority |
|
|
|
|
and the last bits of the identifier define the source |
|
|
|
|
address. That is why these bits of the identifier in the |
|
|
|
|
J1939 protocol can be different and are not evaluated |
|
|
|
|
on reception in this example. |
|
|
|
|
|
1. Click on the Timeout and conditions tab in the Communication tab
2. Make the following settings:
Description |
Selection |
Result |
|
|
|
Always active |
Set |
The CAN message is received irrespective of events or |
|
|
conditions. |
|
|
|
Example 1
Simple cyclical logging without checking additional conditions.
The example is based on the settings in the chapter Receiving the J1939 message on page 9.
1. Click on the Logging tab.
BC00000348 en-US • Rev 0100 • October 2015 |
11 |
User Manual |
Danfoss Telematics Solution Logging Data |
|
|
Creating object dictionary groups and objects
2. In the Logging tab, click on the Conditions tab.
3. Make the following settings
Description |
Selection |
Result |
|
|
|
Logging enabled |
Set |
Logging enabled |
|
|
|
Log message on |
AND |
The data is only logged when timeout is reached AND |
|
|
the condition is met. |
|
|
|
Logging period |
Use a fix |
Duration of the logging interval in milliseconds. |
|
value |
|
|
(60000) |
|
|
|
|
Condition / Always true |
Set |
Logging takes place without prior checking of |
|
|
conditions. |
|
|
|
1. In the Logging tab, click on the Payload tab.
2. |
Make the following settings: |
|
|
|
|
|
|
|
Description |
Selection |
Result |
|
|
|
|
|
Log received CAN message |
Set |
Log the data of the receive CAN message. |
|
|
|
|
|
Bytes to log |
All |
Log all data bytes. |
3. |
|
|
|
Save the configuration file and load the configuration to the device as described in Configuring the |
|||
|
device for Data Logging on page 7. |
|
|
12 |
BC00000348 en-US • Rev 0100 • October 2015 |