Sei sulla pagina 1di 21

Compact CAN Integration Overview

Version 28.3 Page 1 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

Compact CAN Integration Overview


Version: 28.3 Updated: 27/Apr/09

CONFIDENTIAL This document contains proprietary information that is the sole property of Pointer Telocation Ltd. The document is submitted to the recipient for his use only. By receiving this document, the recipient undertakes not to duplicate or to disclose, in part or the whole, any of the information contained herein; to any third party; without a-priory written permission from Pointer Telocation Ltd.

Compact CAN Integration Overview


Version 28.3 Page 2 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

TABLE OF CONTENTS 1 2 TRACEABILITY TABLE .......................................................................................................... 3 INTRODUCTION ..................................................................................................................... 4 2.1 About this Document ........................................................................................................ 4 2.2 General ............................................................................................................................ 4 2.2.1 High level Features....................................................................................................... 4 2.2.2 Device Architecture ...................................................................................................... 4 2.3 Used Abbreviations .......................................................................................................... 5 2.4 Related Documents .......................................................................................................... 5 3 GENERAL DESCRIPTION ...................................................................................................... 6 3.1 CAN General Overview .................................................................................................... 6 3.1.1 Specification Versions .................................................................................................. 6 3.2 ISO11898 ......................................................................................................................... 6 3.3 J1939/FMS ....................................................................................................................... 7 4 INTEGRATION PRINCIPLES .................................................................................................. 9 4.1 The CAN Harvester .......................................................................................................... 9 4.2 The Sensors Array ......................................................................................................... 10 4.3 The Sensor Triggers ....................................................................................................... 10 4.4 CAN Data Delivery ......................................................................................................... 10 4.4.1 Can Status Interrogation ............................................................................................. 10 4.4.2 An active CAN Message ............................................................................................. 11 4.5 Available Trigger Types .................................................................................................. 13 4.5.1 Threshold Trigger ....................................................................................................... 13 4.5.2 Delta Trigger............................................................................................................... 13 4.5.3 Periodic Trigger .......................................................................................................... 13 4.5.4 Complex Trigger ......................................................................................................... 13 4.6 Reporting CAN Speed and Odometer in Position Messages (Msg. Type 0) ................... 15 5 CONFIGURATION ................................................................................................................. 16 5.1 5.2 5.3 5.4 5.5 Data on CAN (J1939 example) ....................................................................................... 16 Selecting Sensors .......................................................................................................... 17 Setting Templates for a Trigger ...................................................................................... 17 Assigning Simple Triggers .............................................................................................. 19 Assigning Complex Triggers ........................................................................................... 20

Compact CAN Integration Overview


Version 28.3 Page 3 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

1
Version 28.1 28.2

Traceability Table
Date 4/02/09 8/02/09 Description Original version The name of the document modified Device architecture chart added Minor modifications and fixes after review

28.3

27/4/09

Minor description mistakes are fixed Complex trigger generation description updated

Compact CAN Integration Overview


Version 28.3 Page 4 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

2
2.1

Introduction
About this Document

This document is intended to provide a clear understanding of the integration of the Cellocator unit with the vehicles CAN bus, its operational logic, CAN bus event reporting options, and accompanying debugging and configuration tools.

2.2
2.2.1

General
High level Features
To monitor up to 25 parameters, reported over the vehicles CAN bus from the CCC, by polling or periodical auto-updates. To generate active messages to the CCC carrying CAN data, triggered by pre-defined logical conditions.

Using the provided interface the customer will be able:

2.2.2

Device Architecture

The following illustration provides an overview of the Cellocator device.

Compact CAN Integration Overview


Version 28.3 Page 5 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

2.3
ACK CAG CCC PDU SMS DB OTA

Used Abbreviations
Definition Acknowledge Controller Area Network Command and Control Center Protocol Description Unit (Common name for data SMS) Short Message Service (GSM) Database Over the air

Abbreviation

2.4
No. 1 2 3 4

Related Documents
Document Name SAE j 1939-71 FMS document Ver 01.00 FW28 Release Notes Appendix - Modular Message type 9 v28_1 1.00 1 Version Date December 2004 January 2, 2007 January 14, 209 February 2, 2009 Remark Or newer

Compact CAN Integration Overview


Version 28.3 Page 6 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

3
3.1

General Description
CAN General Overview

The Controller Area Network (CAN) was created by Robert Bosch in Germany in March, 1985. The Bosch Company designed it to replace automotive wiring.

3.1.1

Specification Versions

In early versions of the specification (version 1.2, Part A), CAN messages contained an 11 bit identifier providing the capability to address 2047 identifiers. In 1992, CAN specification 2.0, (Part B), extended the identifier size to 29 bits providing up to 56 million unique identifiers. The goal was to make automobiles more reliable, safe and fuel-efficient while decreasing wiring harness weight and complexity. Since its inception, the CAN protocol has gained widespread popularity in industrial automation and automotive/truck applications.

3.2

ISO11898

The Cellocator unit is compliant with the ISO1189 standard, as described below. The CAN protocol defines the Data Link Layer and part of the Physical Layer in the OSI model.

Cellocator Unit

The CAN bus is a balanced (differential) 2-wire interface running over either a shielded twisted pair (STP), un-shielded twisted pair (UTP), or a ribbon cable. A transceiver is able to drive a 40m bus at

Compact CAN Integration Overview


Version 28.3 Page 7 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

1 Mb/s. A longer bus length can be achieved by slowing the data rate. The specification also requires 120 (nominal) terminating resistors at each end of the bus.

The CAN bus specifies two logical states: recessive (logic 1) and dominant (logic 0), and ISO11898 defines a differential voltage to represent recessive and dominant states (or bits) as shown in the following figure:

A Cellocator CAN unit has two pins on its main interface connector compatible to ISO-11898: CANH (pin 11/20) and CANL (pin 5/20). The unit is adapted by default to a 250kbs bus, but can be adapted to other bus speeds upon customer request (requires firmware upgrade).

3.3

J1939/FMS

The J1939 protocol is one of the most popular CAN protocols, widely used by European car manufacturers and, since 2008, mandatory on each trucks manufactured in the United States as well. It defines an Application Layer for vehicle use (see 7-layer model above.). This layer contains management functions and generally useful mechanisms to support applications, but none of the defined functions and mechanisms is mandatory.

Compact CAN Integration Overview


Version 28.3 Page 8 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

The J1939 protocol was developed by the SAE (Society of Automotive Engineers) in order to provide a standard architecture by which multiple electronic systems on a vehicle can communicate. It was developed by the Truck and Bus Control and Communications Network Subcommittee of the Truck and Bus Electrical and Electronics Committee, but its use is not limited to truck and bus applications. The Cellocator configuration tools allow easy integration with any J1939 compliant bus. The FMS (Fleet Management System) protocol, adapted by major European track manufacturers, is based on J1939 and defines a small subset of J1939 packets (PGNs) which are mandatorily supported by vehicles that have been declared as FMS compatible. The Cellocator configuration tools allow plug-n-play integration with any FMS compliant vehicle, the configuration in this case is a based upon a selection of the required parameters from drop-down menus.

Compact CAN Integration Overview


Version 28.3 Page 9 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

Integration Principles

The CAN bus extensions in the Cellocator unit are designed with flexibility in mind, and do not relate to the higher-level protocols in use above the CAN interface. The unit, by default, takes active part in the error management protocol in the CAN data layer. It generates passive and active errors upon detecting erroneous conditions. However, the unit does not take any part in higher-level communications. This approach provides several benefits:

Lack of interaction with the higher layer assures the unit will not cause any disturbance or interference with the operation of other systems in the vehicle. Not relating to specific communications on any specific higher layer assures that the unit has access to a broad range of communication protocols, with the ability to adapt to newer protocols in the future.

The Compact CAN unit is installed as one of the nodes on the bus. It is thus exposed to the entire CAN bus traffic of the vehicle while allowing selection and processing only of the relevant parameters.

. Cellocator CAN processing is based on the following three main modules:

4.1

The CAN Harvester

The CAN Harvester is an array of filters. Each packet (frame) sent over the bus is examined by this filter. The filter's condition, which is actually the XOR mask, defines which CAN frames will pass through the filter. A received CAN frame can match more than one filter. In this case it passes through all of the matching filters. If it matches none of the filters, the frame is discarded without any further processing.

Compact CAN Integration Overview


Version 28.3 Page 10 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

4.2

The Sensors Array

The sensors array is a storage space for information extracted by the CAN Harvester module. Each sensor is linked with one of the filtered parameters in the array. Every time, a containing frame is filtered from the CAN traffic, the value in the corresponding sensor is updated with the new value received from the CAN.

4.3

The Sensor Triggers

The sensor trigger defines the logical condition for generating messages to the CCC. This condition is checked every time that the content of sensor is updated with newly extracted data from the bus. More than one condition (trigger) can be assigned to a single sensor. A single trigger can also be assigned to two sensors, as described below. There are two versions of Compact Can units:

Capable of managing 8 CAN sensors. Capable of managing 25 CAN sensors.

The 8 sensors version supports creation of up to 8 triggers, the 25 sensors version supports up to 24 triggers. Note, that the 25 sensors version consumes twice more power because the frequency of its internal controller is 2.5 times faster than the frequency of controller in the 8 sensors version.

4.4

CAN Data Delivery


The CCC interrogates the unit for the content of the CAN sensors. The unit generates an active CAN message as a result of violation of one of the logical conditions (triggers) assigned to the selected CAN sensors.

The CAN data is delivered by the Compact CAN unit to the CCC in two cases:

4.4.1

Can Status Interrogation

In this case, the unit delivers content of all CAN sensors in a single type 9 sub data type 2 message (refer to Appendix Modular Message type 9 v28_1). The sensors in this message are not indexed, and are allocated in the same order as they are programmed in the EEPROM:

Cellocator header

Sensor 1

Sensor 2

Sensor X

Cellocator Check Sum

Each sensor utilizes 6 bytes reserved for data extracted from CAN and one byte indicating effective bit length; the infrastructure of an OTA type 9 message allows requesting the GPS stamp to be sent as a part of the same packet.

Compact CAN Integration Overview


Version 28.3 Page 11 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

Cellocator header

Sensor 1

Sensor 2

Sensor X

GPS Stamp

Cellocator Check Sum

Note, that the 25 sensor version of the Compact CAN does not allow for SMS interrogation because the reply would be much longer than a PDU SMS can carry (25*6byes per sensor=150 characters, while the PDU SMS can only handle 140 characters).

4.4.2

An active CAN Message

In this case, the unit generates an active message upon violation of one of the conditions, defined in a trigger. An active trigger can be generated in three ways:

As a real-time message of type 9, sub data type 2. It appears as "RealTime CAN" in Cellocator tools. This type of message is similar to that discussed in the previous paragraph. It is not recommended because: o It does not clarify which of the sensors has violated the condition. o It is not equipped with a GPS stamp. o It is not logged and not repeated, which means that the message will be lost if there is no coverage at the moment of generation. o In the 25-sensorversion, it cannot be delivered by SMS. As a real-time message of type 9, sub data type 3. It appears as "Specific Data" in Cellocator tools. This is another method of CAN event generation, with an improved message format. The generated event contains an index of the sensor, which caused a trigger, i.e. the content of this sensor and, optionally, content of other indexed sensors and the GPS stamp. This message format allows creation of four content patterns and the messages will be generated in accordance to one of them. For example: the first pattern will only include the triggered sensor itself with the GPS stamp. The second pattern will include the triggered sensor, the third sensor and the fourth sensor, as well as the GPS stamp.

Pattern 1
Cellocator Header Index of triggered sensor Spare Number of included sensors : 1 Triggered sensor content (with index) GPS Stamp Cellocator Check Sum

Pattern 2
Cellocator Header Index of triggered sensor Spare Number of included sensors: 3 Triggered sensor content Content of sensor 3 (indexed) Content of sensor 4 (indexed) GPS Stamp (optional) Cellocator Check Sum

Compact CAN Integration Overview


Version 28.3 Page 12 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

Once the patterns are set, it is possible to assign it to any trigger. There is no limit to the number of sensors delivered with the pattern, so it is possible to include all the sensors in the pattern and to add a GPS stamp to it. In this way, upon trigger, the CCC receives a message with all the defined sensors, a number (or two numbers) of triggered sensors and the GPS stamp. Note, that the message is still generated in a real time format. It means, that the message is not logged and not repeated, and therefore will be lost if there is no coverage at the moment of generation.

As a logged message of type 9, sub data type 3. It appears as "Specific Data - Logged" in Cellocator tools. This type is very similar to the one described above, with two major differences: o The message will be logged and will require Generic ACK from CCC (message type 4, (refer to Wireless Protocol)) in order to be deleted from the memory. If the ACK message is not received, it will be resent. The message utilizes the same amount of memory as a plain position event (message type 0), physically allocated in the same memory slot and threaded by the unit in the same way as message type 0. Therefore the unit can store the same number of CAN events namely 2256. o Although the message is constructed according to a pre-set pattern, the pattern's structure has constant length and is limited to the following structure:
Cellocator Header Index of triggered sensor Spare Number of included sensors: 1-3 Content of triggered sensor with index Content of addition al sensor (a) with index or zeros Content of addition al sensor (b) with index or zeros GPS Stamp Cellocator Check Sum

Note: The Complex Trigger (both logged and real-time, see description below in section 4.5) has a dedicated hardcoded pattern: both triggered sensors, an additional sensor and the GPS stamp. The only variable item in this pattern is an index of the additional sensor. Each complex trigger (out of 8) can be assigned with different additional sensor. If the message carries less than the allowed three sensors the unused bytes are sent as zeros. Complex Trigger (logged and real time) pattern:
Cellocator Header Index of triggered sensor (a) Index of triggered sensor (b) Number of included sensors: 3 Content of triggered sensor (a) with index Content of triggered sensor (b) with index Content of an additional sensor with index Cellocator Check Sum

Compact CAN Integration Overview


Version 28.3 Page 13 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

4.5

Available Trigger Types


Single Triggers Complex triggers

There are two general types of triggers:

Simple triggers are of the following types:

4.5.1

Threshold Trigger

This trigger type is used in order to detect that sensors value has exceeded the Maximum or Minimum level. It is possible to choose between single update per exceeding period and update per each exceeding update. The easiest way to illustrate those options is to provide example: If we are trying to detect overspending, we will assign Threshold trigger to a sensor, containing speed of the vehicle. This will be a Maximum threshold type (as we look for the value higher then ... km/h), of the "single update per exceeding period" (because the Speed is reported on bus 10 times a second and generating an event on each exceeding update is absolutely useless).

4.5.2

Delta Trigger

This trigger type is used in order to determine if a sensors value has exceeded the maximum allowed value between two consecutive updates of the specific sensor.

4.5.3

Periodic Trigger

This trigger type is used as a periodical update, but it is not actually time that is counted. The trigger occurs after a preprogrammed number of specific sensor updates. Since the number of updates is normally defined in the protocol, the number of updates defines a period.

4.5.4

Complex Trigger

A Complex Trigger can be occur upon concurrent violation of two simple triggers for a predefined time period, or violation of a single trigger for at least a predefined time period.

Compact CAN Integration Overview


Version 28.3 Page 14 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

A complex trigger can be defined based upon a subset of the mentioned parameters e.g. one sensor and a time filter, or concurrent activation of two Simple Triggers. In other words it is possible to select two single triggers (assigned to the same sensor or different sensors), and the time interval while they both are concurrently violated before the Complex Trigger message is generated. Notes:

A complex trigger will always cause a generation of a message, containing values of both sensors of the complex trigger, the third sensor (additional one, configurable) and the GPS (see description in Can Data Delivery Options section above in this document, 4.4.2).

The maximum number of complex triggers is 8 (in both 8 and 25 sensors version). The time counter of each trigger is up to 255 seconds. Each simple trigger can be set as either part of complex trigger or simple trigger. The same trigger cannot be defined simultaneously as part of both a complex trigger and a simple trigger. The same single trigger can be used for more than one complex trigger (although it is not supported yet by Cellocator tools). The complex trigger input can only be constructed from triggers of the "Threshold" type, with a single trigger per exceeding period.

Compact CAN Integration Overview


Version 28.3 Page 15 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

4.6

Reporting CAN Speed and Odometer in Position Messages (Msg. Type 0)

The feature is supported by a Compact CAN and allows replacing the GPS estimated speed and odometer values in message type 0 in the Wireless Protocol, by the more accurate values received from vehicle's CAN bus. Note that this feature will only be supported with J1939 compliant vehicles. In order to activate this feature, the CAN sensor 1 should be configured to capture the Odometer and CAN sensor 2 should be configured to capture the Speed from the CAN bus. The Compact CAN normalizes values received from the CAN bus into a common format described in the Cellocator Wireless Protocol: GPS Format of both fields: According to Cellocator Wireless Communication Protocol Odometer 3 bytes, in distance base units programmed in EEPROM 4 bytes, in 10-2 m/sec resolution (centimeters/sec). CAN (According to FMSStandard Interface Description)

4 bytes, in 5m resolution

Speed

2 bytes , in 1/256 km/h resolution

In order to notify the CCC that the Speed and/or Odometer fields of the message monitor CAN originated data, the unit sets corresponding bits in the Communication Control byte of the message (refer to Wireless Protocol for more details about data source monitoring).

Compact CAN Integration Overview


Version 28.3 Page 16 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

5
5.1

Configuration
Data on CAN (J1939 example)

Before describing the configuration process it is important to understand what the data on the bus looks like. The following is a short example of a J1929 log, recorded from the Scania track.

The right column contains the header of the message (PGN, the 29 bits identifier), length of data (always 8 bytes), the data itself and the timestamp. According to the FMS document, the speed is recorded in a frame structured from PGN 0xFEF1

The speed is allocated in bytes 2 and 3 (16 bits value, starting from bit 8). In our example the value is 0x00 00, which means 0 km/h.

Compact CAN Integration Overview


Version 28.3 Page 17 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

5.2

Selecting Sensors

Cellocator's configuration tool, integrated in both wire and wireless communication software packets, allows for the easy creation of a new sensor or selection of the pre-set one from the drop down list. A Selected sensor is automatically assigned with an index. If the required sensor is not in the list, it is easy to create a new one by choosing the name, the PGN according to the J1939 document, the length of data and other attributes of a required sensor.

5.3

Setting Templates for a Trigger

Once all the required sensors are selected, templates for future triggers are generatred. This is done by selecting optional sensors and, optionally, the GPS module. The example below shows a template, containing additional Speed and Odometer sensors, as well as the GPS packet.

Compact CAN Integration Overview


Version 28.3 Page 18 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

Compact CAN Integration Overview


Version 28.3 Page 19 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

5.4

Assigning Simple Triggers

The Simple Trigger configuration form provides:

Selection of the sensor to be applied (in our example sensor 1, Speed). Input processing type (simple trigger type, as described above, in our example Threshold Triggering, Maximum 100 km/h, Single trigger per exceeding update. A trigger output. Selection of "Realtime CAN message" will cause the generation of the "real-time message of type 9, sub data type 2". Selection of "Specific data" option will generate the "real-time message of type 9, sub data type 3". Selection of Specific data logged option will generate the "logged message of type 9, sub data type 3". If one of the Specific Data types is selected, the operator is offered a selection of patterns for event generation:

Compact CAN Integration Overview


Version 28.3 Page 20 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

5.5

Assigning Complex Triggers

The complex trigger interface facilitates setting two simple sensors and the time of concurrent violation to generate a trigger. Since the template of Logged complex trigger is constant, the form lets the operator assig one additional sensor: The example demonstrates a complex trigger, setting Speed and Engine RPM simultaneous violation for 15 seconds. The following example presents a screenshot of the configured complex trigger screen.

Compact CAN Integration Overview


Version 28.3 Page 21 of 21 Proprietary and Confidential Copyright 2000-2009 Cellocator

Last Update:
27/Apr/09

Potrebbero piacerti anche