Introduction to Cello-CANiQ
Dudy Markus CTO - Pointer
Igor Rogov VP R&D - Cellocator Div
Nowadays CANBUS connectivity
2
CANBUS Adapters
Telematics Device
FM Backend
Vehicle CANBUS
A Cold Fusion in CANBUS connectivity
3
Cellocator Cello-CANiQ
FM Backend
Vehicle CANBUS
Part I
• Cello-CANiQ at a glance
• Applications and benefits
• Cellocator’s Value-added
Part II
• Vehicle CAN bus basics
• Cello-CANiQ under the hood
• Tools and accessories and interfaces
Welcome to Cellocator’s partners seminar
4
• Cello-family’s flagship for advanced Fleet Management Services
• Supports connectivity & data analytics for variety of vehicle data buses • OBDII (ISO 15765, 14229)
• CAN2.0 (ISO 11898, J1939, FMS)
• Built on top of Cellocator’s legacy FM and DBM applications
• Enables wide range of applications driven by vehicle canbus data
• Easy-to-use Drag & Drop GUI to manage On-board powerful logic engine
• Cellocator’s latest HW platform
• 2G/3G (EU, NA) support
• Advanced multi-GNSS with cutoff / short-circuit detection
• Multi-purpose Dallas 1-wire bus
• Tachograph D8 ready
• Complementary Vehicle Libraries and Reverse Engineering services
5
Cello-CANiQ at a glance
System Architecture
6
API Fleet Application
CSA Safety Application
Vehicle / Infrastructure
Fleet Comm. server
C+ Server
Wireless Protocol
CSA event Comm. server
CSA file comm.
Server (FTP)
Voice (E-call)
DFD
COM PORT
-Log memory
-Log memory
Wireless Protocol
-files
FTP / TFTP interface
Row Data
Drivers i.e. Dallas, GPS, IOs
System Architecture
CAN Engine API Fleet Application
CSA Safety Application
Vehicle / Infrastructure
Fleet Comm. server
C+ Server
Wireless Protocol
CSA event Comm. server
CSA file comm.
Server (FTP)
Voice (E-call)
DFD
COM PORT
CAN event (type 11) Wireless protocol
-Log memory
-Log memory
-Log memory
Wireless Protocol
-files
FTP / TFTP interface
Row Data
Drivers i.e. Dallas, GPS, IOs
OBDII / J1939
Commercial Vehicles Telematics – Frost & Sullivan 2014
“Predictive
maintenance and
diagnostics are
growing in popularity
as cost savings are
proven”.
Applications and Benefits
App example 1 - Remote diagnostics
9
Real time Vehicle Performance profiling Engine temp, oil Pressure, tire pressure, power systems, Emission….
Diagnostics Trouble Codes (DTC) Filtering / analysis / alerting & reporting
Automatic Maintenance scheduling
Prognostics – preventive maintenance
App example 2- Operations and fuel efficiency
10
• Fuel Management • Refueling locations
• Fuel Drop / theft (syphoning)
• Fuel consumption (Engine performance)
• Fuel tax calculations
• Fuel costs reconciliation
• Vehicle operation errors • Handbrake
• Brakes / retarder handling
• Clutch & Gear handling
• Ignition & warm-up process
• Automated driver checklist
11
Enhanced DBM
Values Variable
• No need of wired installation • Reported in manoeuvre statistics (max RPM) • Reliable Vehicle idling detection (Engine on and speed < TH)
RPM
• Replaces GPS speed data whenever GPS is unavailable • Exceptional Odometer accuracy (<1% error)
Vehicle Speed
• Total fuel consumed during a trip • Two distinct conditions: Idling, Movement.
Fuel Flow Rate
• Fuel level in vehicle’s tank (upon trip start/end) – trip statistics report
Fuel Level
• The Cello-CANiQ can retrieve VIN and use it as a unique vehicle identifier upon report of crash / accident in the crash attributes file.
VIN
• Number of fastened seatbelts, Airbag status, ABS / ESP engagement etc
Future Enhancements
Supported Vehicle libraries
12
• Updated on a monthly basis
• ~200 different makes and models
• Trucks (non FMS libraries)
• Light Dudy
• Private - upcoming
• Support likelihood for many non-validated vehicles
• Projects and Opportunities
• Professional Services – Upcoming solution packages
Parameter Name
Bra
nd
Mo
de
l
Ye
ar
Typ
e
Sta
nd
ard
Ve
hic
le i
de
nti
fica
tio
n n
um
be
r
En
gin
e s
pe
ed
(R
PM
)
Wh
ee
l-B
ase
d V
eh
icle
Sp
ee
d
Hig
h R
eso
luti
on
To
tal V
eh
icle
Dis
tan
ce
En
gin
e C
oo
lan
t T
em
pe
ratu
re
En
gin
e t
ota
l fu
el u
se
d
Fu
el le
ve
l
En
gin
e I
nta
ke
Ma
nif
old
1 T
em
pe
ratu
re
PT
O (
Po
we
r T
ak
e O
ff)
Acce
lera
tor
pe
da
l p
osit
ion
Bra
ke
sw
itch
Clu
tch
sw
itch
Tra
nsm
issio
n C
urr
en
t G
ea
r
Isuzu6.2 2013 Truck J1939 v v x x v v
Isuzu 7.5 2013 Truck J1939 v v v x x v vIsuzu 12 2013 Truck J1939 v v v x x v vIsuzu 6.2 2014 Truck J1939 v v v x x v vIsuzu 7.5 2014 Truck J1939 v v v x x v vIsuzu 12 2014 Truck J1939 v v v x x v vMAN TGM 2004 Truck J1939 v v v v v v v v v v v v vMAN TGM 2005 Truck J1939 v v v v v v v v v v v v vMAN TGM 2006 Truck J1939 v v v v v v v v v v v v vMAN TGM 2007 Truck J1939 v v v v v v v v v v v v vMAN TGM 2008 Truck J1939 v v v v v v v v v v v v v
Vehicle Attributes
http://www.cellocator.com/?s2member_file_download=cellofamily/Cello-CANiQ/VEHICLE%20Database.xlsm
Part II: Cello-CANiQ – under the hood…
13
• Vehicle’s CAN bus
• Modes of CAN traffic processing
• Filtering and Processing CAN Parameters
• Provided Tools
• Reporting OTA / Protocol issues
... You have to learn the rules of the game. And then you have to play better than anyone else.
Albert Einstein
What is it all about…
14
The Types of Applications
Data link Physical
ISO 11898-1 CAN
Transport Network
Application Presentation
Session
J1939-21 J1939-11
J1939-33
J1939-71/73 Definition of
PGNs
ISO15765-2
ISO14229 UDS (Unified
Diagnostic Services)
ISO15765-3
ISO15031
OSI Layers J1939 Mode “Custom” CAN “Standard” OBDII
15
SAE J1939 Message Format
16
• Priority: controlling a message’s priority during the arbitration phase (lower value = higher priority).
• PDU Format determines whether the message can be transmitted with a destination address or if the message is always transmitted as a broadcast message
• PDU Specific field:
• If PDU Format < 240, PDU Specific = destination address.
• If PDU Format ≥ 240, PDU Specific = broadcast Group Extension.
• Source address: the address of the device transmitting the message.
SAE J1939 Message Examples
17
SAE J1939 FMS
SAE J1939 FMS
18
• The Fleet Management Systems Interface (FMS) is a standard interface to vehicle data of commercial vehicles.
• The six European manufacturers Daimler AG,MAN AG, Scania, Volvo (incl. Renault), DAF Trucks and IVECO developed the so-called FMS-Standard in 2002 to make manufacturer-independent applications for telematics possible.
19
• Vehicle improvement (all round)
• Vehicle speed (wheel based)
• Vehicle speed (from tachograph)
• Clutch switch (on/off)
• Brake switch (on/off)
• Cruise control (on/off)
• Power Take Off (Status/Mode)
• Accelerator pedal position (0–100%)
• Total fuel used (liters since lifetime)
• Fuel level (0–100%)
Data broadcasted at the FMS interface
• Engine speed
• Axle weight (kg)
• Total engine hours (h)
• FMS-Standard software version (supported modes)
• Vehicle identification number (ASCII)
• Tachograph information
• High-resolution vehicle distance
• Service distance
• Engine coolant temperature
ISO 15031 STANDARD OBD-II
• Structure of the message
• Arbitration ID for Broadcast query:
• 11 bit Request Arbitration ID 0x7DF
• 29 bit Request 0x18DB33F1
• Request Service Identifiers (SID of query ) (+0x40 in
response):
• 0x01 Request current diagnostic data
• 0x02 Request powertrain freeze frame data
• 0x03/07 Request diagnostic trouble codes (DTC)
• 0x04 Clear Diagnostic Trouble Codes and stored values
PID2 (Optional).. PID (Optional) SID Arbitration ID
ISO 15031 “Standard” OBDII
20
STANDARD OBD-II PIDS
hereFull list is
There are pre-configured 36 standard PIDs in CAN-Editor
Units Formula PID
(hex) Data bytes returned
Description
rpm ((A*256)+B)
/4 0C 2 Engine RPM
km/h A 0D 1 Vehicle speed
° relative to #1 cylinder
(A-128)/2 0E 1 Timing advance
°C A-40 0F 1 Intake air temperature
grams/sec ((A*256)+B)
/ 100 10 2 MAF air flow rate
% A*100/255 11 1 Throttle position
Processing Standard OBD-II PIDs
21
COMMON STANDARD PIDS
The following PIDs are likely to be supported by > 80% of the vehicles manufactured after 2004.
Mode / SID
PID (HEX)
Data Bytes Returned
Description
1 1 4 Monitor status since DTCs cleared (includes malfunction indicator lamp (MIL) status and number of DTCs)
1 4 1 Calculated engine load value 1 5 1 Engine coolant temperature 1 0C 2 Engine RPM 1 0D 1 Vehicle speed 1 0F 1 Intake air temperature 1 11 1 Throttle position 1 1C 1 OBD standards this vehicle conforms to 1 20 4 PIDs supported [21 - 40] 1 21 2 Distance traveled with malfunction indicator lamp
(MIL) on 3 N/A n*6 Request trouble codes (no PID required) 9 0 4 Mode 9 supported PIDs 01 to 20 9 2 5x5 Vehicle identification number (VIN)
Common Standard OBD-II PIDs
22
UDS (Unified Diagnostic Services) ISO 14229, “Custom” CAN
• The UDS (Custom) is almost identical to “Standard CAN”, except
• restructured SIDs (Modes)
• unification
• UDS defines a security layer in order to encrypt data.
• Client-Server communication:
• Client (end unit) initiates request and waits for confirmation
• Server (ECU) receives request and sends response
23
ISO 14229: CUSTOM CAN
• Services provided by UDS
• Diagnostic Management: Control of diagnostic sessions
• Data Transmission: Read from and write to ECUs
• Stored Data Transmission: Read Diagnostic Trouble Codes (DTC)
• Input/Output Control: Control of ECU I/O
• Remote Activation of Routines: ECU program startup
• Upload/Download: ECU Flashing
UDS (Unified Diagnostic Services) ISO 14229, “Custom” CAN
24
CANBUS INTERFACES
SAE J1939 Connector OBDII socket: ports 6 (CAN-High) and 14 (CAN-Low).
Sometimes CAN2.0 protocols exists also in other ports of the OBD socket (for example: Pin 3 and Pin 11 in FORD vehicles)
CANBUS Interfaces
25
SYSTEM ARCHITECTURE
Drivers :Dallas, GPS, IOs OBDII / J1939
Can Engine Fleet
API
DBM App
CSA Server Fleet / CAN
Server
C+ Server
RS2
32
DFD
System Architecture
26
CAN FEATURES
• Operating up to 25 parameters
• Filtering up to 13 Arbitration IDs sequential groups: virtually unlimited
number of filtered Arbitration IDs
• Built in OBDII standard PIDs support (ISO-15031)
• DTC reporting (ISO-15031, SIDs 03 and 07)
• Auto-baud rate and auto-header length detection
• Utilization of CANBUS parameters independently as well as in DBM and
Fleet modules
• Capacitance adapter support (only unsolicited
CAN traffic, J1939/FMS)
CAN Features
27
CAN OPERATIONAL MODES
• J1939/FMS Mode
Listening mode, designed for J1939-71 / FMS applications. Can be used with capacitance CAN adapter.
• OBDII Mode
Full duplex CAN. Designed for ISO15031 and ISO14229 based applications. Pre-configured set of ISO15031 parameters can be used.
• Service Mode
The mode is designed for working in ISO15765-2 based applications, without periodic polling of the bus. Perfectly fits Comfort Bus maintenance.
Operational Modes of our CAN Engine
28
CAN Editor
29
Tab of general settings
Select operational
mode
Select header length
Select baud Rate
SELECTING STANDARD OBDII PARAMETER
Used Parameter Library
List of Available Parameters
Selected parameter
Used Recourses
Selecting Standard OBDII Parameter
30
FILTERING PARAMETERS
CAN Traffic
CAN Traffic CAN Traffic
CAN Traffic
CAN Traffic CAN Traffic
Chosen Attrbitr. ID
Ch
ose
n
Attrb
itr. ID
CAN Traffic
Further Filtering
CAN Parameter
CAN Parameter
CAN Parameter
CAN Parameter
Filtering Arbitration IDs
31
FILTER GROUPS
First Filter: Arbitration ID group
32
Filtering Parameter
33
GRAPHICAL TOOLS
Graphical Help
34
CONSIDER PGN ONLY AND FUNCTION ASSIGNMENT
System Function Assignment
35
Queries
Periodic query
Generating CAN Queries
36
OPERATORS
The Operators
37
Available Operators
• In/Out Range
• Single threshold
• Delta between
• Is in set
• Is not in set
• Delta
• Timer
• Compare two operands
• Logical operator
• Compare operands Vs.
• Fuel Theft
• Generate Event
• Generate CAN Query Event
• Delta since last violation
38
ESPECIAL OPERATORS
Fuel Theft Generate Event
Especial Operators
39
PL SIGNATURE
PL Signature
40
XML
• The CAN Editor creates the .xml file signed with PL signature.
• This file contains script, describing each CAN parameter and trigger.
• The PL signature sent in every uplink message.
• The message on serve side is interpreted using the corresponding .xml.
The XML
41
SERVER SIDE CAN EVENT INTERPRETATION
Server Side CAN Event Interpretation
42
Server Side CAN Event Interpretation
For example from the following event
using an appropriate XML file the back office can discover that:
• Trigger ID 14 stands for “Engine temp higher than 90°C for more than 15 minutes”
• An event holds
• sensor ID 222 which means engine temp = 95°C
• sensor ID 459 which means that the vehicle speed was 80Km/h.
43
Time Stamp
Value 80 Sensor ID 459
Value 95
Sensor ID 222
Trigger ID 14
PL Signature
REPORTING CAN EVENTS
• All CAN Status Events are – logged
• CAN Status Event Attributes
Mandatory / Optional
CAN events (Type 11) are modular and composed of the following:
M Header
M Activated Trigger(s) ID (s)
M PL signature
M Triggered parameters upon activation
O Attached Sensors – up to 20 parameters
O Timer Value which caused trigger activation – if exists
M Trigger Activation time
O Trigger Activation location
O
Other information modules representing status upon trigger activation, such as: I/O status, Driver ID etc.
Reporting CAN Events
44
HARNESSES
• OBDII Basic Harness
Designed for self installation, supports DFD
• Cello-CANiQ Generic Harness
Compatible Harnesses
45
NEW COMING Y-HARNESS
• OBDII Splitter
• Provides access to CAN and Power wires
• Does not disturbs normal diagnostics service
46
Summary: Capability of CAN interface
• CAN engine works with any CAN Interface based on ISO11898 / J1939-11
• CAN engine filters and processes 25 parameters filtered from CAN
• CAN engine supports multi-levels processing logic
• Parameters from CANBUS can replace standard system parameters
• CAN engine works as an independent application
• CAN engine feeds Fleet and DBM applications
• CAN engine supports graphical configuration tools
• CAN OTA traffic enables easy interpretation of events on Server Side
47
Vehicle Uptime Maintenance costs Wear & Tear
Fuel Costs New Business models Operations management
Conclusions