CAN-Logistic v3

Overview and User Manual

Rev. 2 August 2022

Łukasz Janecki

Formula, 72 Stefana Czarnieckiego Str., 01-541 WARSAW, POLAND

www.formula.pl, e-mail: [email protected]
Document scope
The document is an introduction for CAN-Logistic v3 device, it is intended to help you to
choose most suitable version and usage.
It presents capabilities of CAN-Logistic, various usage scenarios and extra functions.

If this is your first contact with CAN-Logistic device, please take following steps:
- select hardware and functional variant appropriate to your telematic device (section
2)
- select communication protocol basis according to your telematic device possibilities
(section 4.4)
- select data gathering scenario which fits to your needs (section 4.5)
- see extra features of CAN-Logistic (sections 4, 5.3, 5.4) to determine if they are
useful for your application
- write down all these requirements and contact us to order a sample device

DOCUMENT SCOPE.........................................................................2

1. OVERVIEW.................................................................................3
1.1. Electrical characteristics...............................................................................................3

2. VARIANTS..................................................................................4
2.1. Hardware versions......................................................................................................4
2.2. Functionality..............................................................................................................5

3. SPECIFICATIONS.......................................................................7
3.1. Serial port electrical specification..................................................................................7
3.2. Transmission..............................................................................................................8
3.3. Mechanical characteristics............................................................................................8
3.4. CAN-Logistic work modes.............................................................................................8

4. FEATURES................................................................................10
4.1. Supported data.........................................................................................................10
4.2. Automatic synchronization..........................................................................................12
4.3. Digital binary outputs................................................................................................13
4.4. Data protocols..........................................................................................................14
4.5. Typical communication scenarios.................................................................................15
4.6. Events detection.......................................................................................................18
4.7. Low power modes.....................................................................................................18
4.8. Firmware updates.....................................................................................................19
4.9. Economic drive support..............................................................................................19
4.10. Analogue input [SOON]............................................................................................20
4.11. Downloading DDD files from tachograph.....................................................................20
4.12. K-line/D8 data from tachograph................................................................................20
4.13. Development test mode...........................................................................................20
4.14. Fail-safe mode........................................................................................................20

5. ACCESSORIES..........................................................................21
5.1. Configuration application + cable................................................................................21
5.2. Fast updater application.............................................................................................22
5.3. Contactless CAN-bus reader........................................................................................22
5.4. FMS connectors........................................................................................................23
5.5. Installation diagrams.................................................................................................23

www.formula.pl CAN-Logistic v3 overview and user manual Page 2 of 24

1.Overview
CAN-Logistic is an interface between vehicle computer and fleet management systems. It
monitors continuously vehicle's data buses and provides information about vehicle's
components status, driving, exploitation materials and more over...
CAN-Logistic is a bridge between various cars, tracks, buses, building or agricultural
machines and fleet management system terminal (usually GPS/GPRS device).

Picture 1: Typical usage of CAN-Logistic in telematic system

1.1. Electrical characteristics

1.1.1. Operating parameters
Supply voltage +8 to +36V
Current consumption (operating mode @12V) 18 mA
Current consumption (operating mode @24V) 9.5 mA
Current consumption (sleep mode @12V) 7.5 mA
Current consumption (sleep mode @24V) 4 mA
Current consumption (deep sleep mode) below 1 mA
Maximum output current (outputs OUT1, OUT2, OUT3) 50 mA
Analogue input voltage range [SOON] 0 to 13V
For serial port characteristic – please see section 3.1.3

1.1.2. Absolute maximum ratings (with respect to ground)

Maximum serial port input voltage -36V to +36V
Maximum CANH/CANL voltage -42V to +42V

www.formula.pl CAN-Logistic v3 overview and user manual Page 3 of 24

2.Variants

2.1. Hardware versions

CAN-Logistic is assembled in several hardware versions different by interface to
connect telemetric device:
• serial port RS-232 compatible (marked as "STD") – to work with devices with RS-
232 port
• serial port UART compatible (marked as "INV") – to work directly with processors
• CAN-bus output (FMS 4.0 based, marked as "FMS") – to work with devices with
CAN-bus receiver
• Bluetooth Low Energy (marked as “BLE”) - for wireless communication (bluetooth
version 4.2) [SOON]
• small PCB to embed inside a telemetric device (marked as “EMBED”)

Picture 2: Typical installation scheme for STD and INV assembly version

www.formula.pl CAN-Logistic v3 overview and user manual Page 4 of 24

 Picture 3: Typical installation scheme for FMS assembly version

Picture 4: Typical installation scheme for BLE assembly version

Picture 5: CAN-Logistic Embed case (dimensions 22.4 x 21.4 x 3.4 mm)

2.2. Functionality
Particular variants of CAN-Logistic v3, beside standard functionality, may include features
of THR (tachograph DDD files downloading and D8/K-Line input support).

www.formula.pl CAN-Logistic v3 overview and user manual Page 5 of 24

 CL-embed
VARIANT CL-STD CL-INV CL-FMS CL+THR (STD) CL+THR (INV) CL-embed
+THR

APPEARANCE

XonXoff/ XonXoff XonXoff/

PROTOCOL FMS+ XonXoff ASCII XonXoff ASCII XonXoff ASCII
ASCII /ASCII ASCII

CAN-buses 2 2 2 2 2 2 2 2 2 2

J1708          
D8 (tachograph)      
UART- RS232 RS232 RS232 UART- UART UART- UART-
serial port RS232* UART-TTL
TTL * * * TTL -TTL TTL TTL

FMS+ output 
digital outputs 3 3 3 3 3 3 3 3 3 3

Logistic
         
parameters

Ecodriving
         
parameters

Tachograph
        
drivers’ timers

DDD files
  
downloading

DTC   soon       

RS232* means RS232 compatible port (see section 3.1.1)

Remember to select suitable version when placing an order.

www.formula.pl CAN-Logistic v3 overview and user manual Page 6 of 24

3.Specifications

3.1. Serial port electrical specification

CAN-Logistic's port (INV/STD assembly versions) is full-duplex asynchronous
serial port (8 bits of data, no parity control, one stop bit) with configurable baud rate.

3.1.1. RS232 compatible (STD assembly code)

Although CAN-Logistic's serial port does not meet RS-232 standard requirements
in 100%, it communicates properly with all RS-232 compatible devices. The only
difference is 0V for logic “1” output instead of negative voltage (-3V or lower) in RS232.
All modern RS232 devices reads properly 0V as logic “high”.
CAN-Logistic accepts, of course, negative RS232 voltages on its serial port input.

Picture 6: Example serial port output waveform (assembly code STD)

3.1.2. UART compatible ("inverted RS232" – INV assembly code)

INV version is simply inverted STD. It is designed to communicate with
microcontrollers UARTs at TTL voltage levels. When serial port output is inactive (logic
“1”) – it holds Vcc supply on serial port output.
CAN-Logistic serial port is compatible with low voltage devices – it accepts high
logic level voltage as low as 2V (see section 3.1.3)

Picture 7: Example serial port output waveform (assembly code INV)

3.1.3. Serial port electrical characteristic

This characteristic refers to both: STD and INV assembly versions.
min typ. max
Input high level voltage 2.0 36.0 V
Input low level voltage -36.0 0.8 V
Output high level voltage 4.0 4.5 5.0 V
Output low level voltage 0.0 0.0 0.2 V
Output current 1.0 mA
Bitrate 0.3 1000 kbps

www.formula.pl CAN-Logistic v3 overview and user manual Page 7 of 24

 3.2. Transmission
3.2.1. STD and INV assembly versions
Type: UART
Baud-rate: freely configurable from 0.3 to 1000 kbps
Byte length: 8 bits
Parity bits: none
Stop bits: 1

CAUTION! Long active pulses on serial port input (over 100 bit times,
which makes frame error) are prohibited! This will cause CAN-Logistic to
enter the configuration mode, which will stop the communication for a few
seconds.

3.2.2. FMS assembly version

Type: CAN 2.0b (implements FMS 4.0 standard)
Baud-rate: 250 kbps
Terminating resistor 120 ohm embed.
Receiver may work as both: active CAN node or in listen-only mode (with internal
acknowledge of incoming CAN frames).

3.2.3. BLE assembly version [SOON]

Operating mode: transparent UART
Bluetooth version: 4.2 (backward compatible with 4.0 and 4.1)
Authentication method: LE Secure Connections (backwards compatible with LE Legacy
Connections), 6 digit individual PIN code
RF/Analog features:
• ISM Band 2.402 to 2.480 GHz Operation
• Channels: 0-39
• RX Sensitivity: -90 dBm
• TX Power: 0 dBm
Signal range: up to 10 m (at free space)

3.3. Mechanical characteristics

Device package size (for STD, INV, FMS and BLE assembly versions):
• Width: 69 mm
• Length: 48 mm
• Height: 18 mm
CAN-Logistic embed PCB case size:
• Width: 22.4 mm
• Length: 21.4 mm
• Height: 3.4 mm

3.4. CAN-Logistic work modes

CAN-Logistic can be run in several modes. LED diode on the case shows current device
mode:

www.formula.pl CAN-Logistic v3 overview and user manual Page 8 of 24

LED diode Work mode
Blinks green once every 1s Operating mode, CAN-bus or J1708 or D8 active (only one
of those)
Blinks green twice every Operating mode, two buses active (e.g. 2 CAN-buses or
1s CAN-bus and J1708 or CAN-bus and D8)
Blinks green thrice every Operating mode, three buses active (e.g. 2 CAN-buses and
1s D8)
Blinks green once every 4s Operating mode, CAN-bus(es) and J1708 sleep or disabled
Off Low power mode (sleep)
Blinks red quickly (ca. 7 CAN-bus codes synchronization
times per second)
Green on (after CAN-bus codes synchronization finished successfully
synchronization)
Red on (after CAN-bus codes synchronization failed (CAN-bus wires are
synchronization) properly connected, but codes have not been recognized)
Flashes red 0.5s on / CAN-bus codes synchronization failed (no CAN-bus
green 0.5s on connection or CAN-bus sleep)
Blinks red twice every 1s Fail safe mode (see section 4.14 for details)
Blinks red once every 2s Invalid configuration (e.g. vehicle not synchronized)
Flashes green 2s on / Supervised mode (when connected to configurator
100ms off application)
Flashes green 1s on / Development test mode (see section 4.13)
100ms off

3.4.1. Operating mode

Operating mode is designed for device to work continuously in a vehicle. In this mode
device reads information from CAN-bus(es) and/or J1708 and/or D8 and communicates
with master device via serial port. When vehicle data buses go sleep, CAN-Logistic goes
to sleep mode (if configured). Sleep mode ends when:
– CAN-bus or J1708 or D8 activity is detected, or
– serial port activity is detected, or
– device button is pressed.
Any logistic data from CANbus is available only in this mode.

3.4.2. Supervised mode (for configuration)

Supervised mode is a special mode, which allows to communicate with CAN-Logistic
Configurator application.
Supervised mode is started, when "long break-character" is detected on RX line of serial
port (line should be active for at least 100 bit periods at current bitrate).

Support of supervised mode is never required by AVL terminals and

generally it is recommended not to start this mode at all. The supervised
mode is dedicated for communication with application of configurator on PC
computer only.

In supervised mode CAN-Logistic does not accept any commands in default protocols.

www.formula.pl CAN-Logistic v3 overview and user manual Page 9 of 24

4.Features

4.1. Supported data

CAN-Logistic reads data from various vehicle's and various protocols. It supports all CAN-
bus protocols that appears in vehicles (CAN 2.0A, CAN 2.0B, J1939, J1979, FMS
2.0/3.0/4.0, CanOpen, Single-Wire CAN and a lot of custom manufacturers protocols),
J1587 over J1708 from American trucks and K-Line/D8 from tachograph.
CAN-Logistic provides a number of information read from vehicle's buses and calculated
on-the-board.
Set of information available for particular vehicle depends on vehicle. Please refer to
most current "Supported car models list" for details.

4.1.1. Logistic parameters from vehicle's CAN-bus

Logistic data frame may contain any set of logistic parameters from the following list:
• CAN-bus/J1708 status • DPF soot level
• ignition key status • Driving wheel bias [SOON]
• Accelerator pedal pressure • Engine coolant temperature
• Adblue level • Engine load
• Ambient temperature • Engine oil level
• Analog input 3 • Engine oil temperature
• Axle weights (up to 7 axles, incl. • Engine speed
Trailer) • Engine torque
• Battery charge level (for electric and • Fuel level (liters and percentage)
hybrid cars) • 2nd fuel source for bifuel cars
• Battery charging current (for electric • Hydraulic oil temperature
cars) • Retarder current usage
• Battery temperature • Speed
• Battery voltage • Trailer gross weight
• Brake pedal pressure • Vehicle gross weight
• Current fuel consumption • Vehicle range

4.1.2. Real-time calculated values

• Total distance
• Total driving time
• Total engine idle time
• Total engine time
• Total engine time (calculated)
• Total fuel used
• Total fuel used (alternative)
• Total idle fuel used
• Distance since installation of CAN-Logistic

4.1.3. Indicators
• Doors status • lights low beams
• Central lock status • lights running
• parking heating system • reverse gear
• air conditioning • coolant level low
• driver seatbelt • brake fluid level low
• fuel level low • lights fog rear
• cruise control • lights fog front
• handbrake • engine hot
• clutch pedal • oil pressure low
• brake pedal • brake system failure
• lights high beams • battery indicator

www.formula.pl CAN-Logistic v3 overview and user manual Page 10 of 24

 • airbags indicator • oil level low
• check engine (MIL) • service call
• esp indicator • accelerator kick down
• abs indicator • lights hazard
• engine supplied by gas • DPF burning locked
• battery charging • brake linings low

4.1.4. Information from tachograph

• drivers card numbers
• drivers names
• drivers time limits
• drivers card insertion status
• drivers work mode
• vehicle moving indicator
• overspeed indicator
• drive direction indicator
• Vehicle speed tachograph based

4.1.5. Drivers’ working timers from tachograph

• Maximum daily period
• Number of times 9h daily driving times exceeded
• Number of used reduced daily rest periods
• End of last daily rest period
• End of last weekly rest period
• End of second last weekly rest period
• Remaining current drive time
• Remaining time until next break or rest
• Duration of next break rest
• Remaining time of current break rest
• Time left until next driving period
• Duration of next driving period
• Remaining driving time on current shift
• Time left until new daily rest period
• Minimum daily rest
• Remaining driving time of current week
• Time left until new weekly rest period
• Minimum weekly rest
• Open compensation in the last week
• Open compensation in week before last
• Open compensation in 2nd week before last
• Additional information
• Continuous driving time
• Cumulative break time
• Current duration of selected activity
• Cumulated driving time previous and current week
• Current daily driving time
• Current weekly driving time
• Cumulative uninterrupted rest time
• Maximum daily driving time
Drivers’ working timers are provided according ISO 16884 by certain versions of
tachographs: VDO 2.1 and 2.2 (only when „VDO Counter” option is enabled), VDO from
3.0, Stoneridge from 7.4, Efas 4.8. Note that particular set of available timers depends
on tachograph model (some timers may be missing in particular models of tachographs).

4.1.6. Ecodrive related parameters

• rapid accelerations number
• harsh brakings number
• total idle fuel used
www.formula.pl CAN-Logistic v3 overview and user manual Page 11 of 24
 • total number of brakes apply
• total accelerator kick-downs number
• engine and pedal braking factors (predictability)
• total driving time with engine speed over programmed limit
• total driving time with speed over programmed limit
• total driving time when cruise-control is on
• total driving time with engine speed in effective range
• total driving time with accelerator kick-down

4.1.7. Maintenance related parameters

• Distance remaining to required maintenance service
• Engine all starts count, incl. start/stop system
• Engine starts by ignition count
• Engine cold starts count
• Total engine cold running time
• Handbrake applies on the ride
• Total combustion engine running time [SOON]
• Total electric engine running time [SOON]

4.1.8. Vehicle information

• Vehicle Identification Number (VIN)
• Vehicle Registration Number (VRN)
• Fuel type
• Tachograph model

4.2. Automatic synchronization

Particular car models differs significantly in terms of CAN-bus. CAN-Logistic recognizes
automatically CAN-buses of many various car makes and models.
Brand new unconfigured device runs synchronization immediately after power-up. It is
enough to connect CAN-Logistic to power supply and CAN-bus and start synchronization.
You need to do nothing before letting the device to installer. You do not need to set up
any vehicle ID in CAN-Logistic. Moreover – synchronization procedure will warn the
installer, if there is no valid connection with the CAN-bus.

Note! CAN-Logistic supports much more vehicle models than listed on

"Supported car models list". As many cars have the same electrical
installation – it is enough to connect CAN-Logistic to CAN-bus and it detects
the best settings on its own!

Synchronization should be performed when connected to the CANbus(es) and/or J1708

according to installation manual of particular vehicle model. Ignition key must be
switched on.
Please refer to "Automatic CAN-bus codes synchronization" manual for details.

www.formula.pl CAN-Logistic v3 overview and user manual Page 12 of 24

 Picture 8: Automatic synchronization results - on LED diode.

4.3. Digital binary outputs

CAN-Logistic has 3 digital outputs with:
• ignition status on 1st output (positive: +12/+24V when ignition or engine is on, no
signal when off),
• CAN-bus activity status on 2nd output (negative: ground signal, when at least one
of buses - CANbus or J1708 is working; high-impedance when all buses are in
sleep mode)
• no function by default on 3rd output (this one is also negative).
Target application can use any signal provided by CAN-Logistic instead of connecting to
vehicle wire (i.e. ignition signal).

The logical function of each output can be changed by configuration. Available functions
are:
• Alarm (signal on some configured events)
• Any door opened (active, when at least one door or trunk is opened)
• CAN-bus active (active, when at least one of connected buses operates)
• Drive (active, when speed > 0 km/h)
• Driver door opened (active, when driver door is opened)
• Engine idle (active, when engine on and speed is 0 km/h)
• Engine on (active, when engine is on)
• Engine speed above limit and gear (like „Engine speed over limit”, but only when
any gear is on)
• Engine speed below limit (oposite to „Engine speed over limit”)
• Engine speed over limit (active, when engine speed is greater than configured
limit)
• Ignition (active, when ignition on)
www.formula.pl CAN-Logistic v3 overview and user manual Page 13 of 24
 • Not sleep mode (oposite to „Sleep mode”)
• Reverse gear off (oposite to „Reverse gear on”)
• Reverse gear on (active, when reverse gear is on; for activation of rear parking
sensor)
• Sleep mode (active, when CAN-Logistic is in sleep mode)
• Speed below limit (oposite to „Speed over limit”)
• Speed over limit (active, when speed is greater than configured limit)
• Tachograph: drive or other work (when tachograph driver 1 working mode is:
drive, other work or availability)
• Webasto on
Other functions possible to introduce on request.

4.4. Data protocols

CAN-Logistic supports two data protocols to communicate with master device (GPS/GSM
terminal).
The primary one is called XON/XOFF (binary protocol). It is recommended for all
solutions, where master device is beeing developed and CAN-Logistic's protocol can be
implemented.
The second protocol ASCII is strings based protocol. All numbers are encoded as text,
particular parameters are separated by special character and entire packet is terminated
by end-of-line characters. ASCII protocol is designed for third party GPS/GSM terminals,
which can forward text strings from/to server but cannot be developed easily.
ASCII protocol is widely configurable – header, separators and terminating characters
can be configured due to master device requirements.
Both protocols may be run under various scenarios (see section 4.5).

Picture 9: Example data flow for ASCII protocol inquiry

4.4.1. Advantages and disadvantages of Xon/Xoff protocol

Advantages
• Flexibility – master device can read any parameter any time and as often as it
like, which allows to make some extra calculations on master side (development
of master device is required)
• downloading DDD files from tachograph (for CLv3+THR version)
Disadvantages
• it is necessary to develop master device prior to make any test on CAN-Logistic

www.formula.pl CAN-Logistic v3 overview and user manual Page 14 of 24

 For more details of Xon/Xoff protocol – please refer to document:
„CAN-Logistic v3 protocol XON-XOFF”

4.4.2. Advantages and disadvantages of ASCII protocol

Advantages
• Plug&play – you can simply connect CAN-Logistic to a car and your computer and
you see outgoing data
• can work with almost every terminal, which can forward text string from its serial
port
• no need to develop master device (for basic functionality), although
implementation of remote update is strongly recommended
• data is presented in human readable format (depends on configuration)
• wide range of configuration allows to define own frame format
• single frame may contain all required parameters (it is configurable)
Disadvantages
• change of data format requires an upload of another configuration file
• does not support DDD files downloading from tachograph

For more details of ASCII protocol – please refer to document:

„CAN-Logistic v3 protocol ASCII general” and its sample implementation:
„CAN-Logistic v3 protocol ASCII C8”

4.5. Typical communication scenarios

Here are some examples of typical communication scenarios implemented in various
GPRS terminals. CAN-Logistic configuration can be based on one of these scenarios but
can implement more than one scenario upon certain conditions. CAN-Logistic can support
many frame types simultaneously, each of them can be triggered by different condition.
Apart from selected scenario – CAN-Logistic's events can be used to initiate transmission
(see section 4.6)

4.5.1. On demand
GPRS terminal sends inquiry to CAN-Logistic each time it gathers position frame, i.e.
GETDATA<CR><LF>
and receives a reply immediately (typically within 20 ms), i.e.
CAN=34,5546,685,234,66.5,3432,,54<CR><LF>

www.formula.pl CAN-Logistic v3 overview and user manual Page 15 of 24

 Picture 10: On demand communication example

The frame from CAN-Logistic must be transmitted to server or buffered if there is no

GPRS connection at the time.

4.5.2. Auto-update with single frame

CAN-Logistic updates its information periodically as single frame, i.e.
CAN=34,5546,685,234,66.5,3432,,54<CR><LF>
once a configured period of time.

GPRS terminal keeps the most current frame in its memory and attaches it to every
position-data packet when required.

www.formula.pl CAN-Logistic v3 overview and user manual Page 16 of 24

 Picture 11: Auto-update with single frame communication example

As for beginning we recommend a sample protocol “ASCII C8”, which is

based on this solution. Please refer to document: CAN-Logistic protocol
ASCII C8

4.5.3. Auto-update parameters separately

CAN-Logistic updates its information by sending multiple frames periodically, i.e.:
P01=34<CR><LF>
P02=5546<CR><LF>
P05=685<CR><LF>
P11=234<CR><LF>
P14=66.5<CR><LF>
P17=3432<CR><LF>
P19=<CR><LF>
P20=54<CR><LF>
Data format can be binary (Xon/Xoff protocol) or text (ASCII protocol).

Another example set of data:

A47339.3<SPACE>
B0.0<SPACE>
E100023.9<SPACE>
G45<SPACE>
S2<CR><LF>

GPRS terminal recognizes parameters by frame header (Pxx) or leading letter (A, B, E
etd.) and stores them to its memory sorted by kind (i.e. P02 is total distance, P14 is
current fuel consumption etc., G is fuel level).
Then it manages all the data by its own.

4.5.4. Frames triggered on events

CAN-Logistic updates its information when particular event occur (multiple events may
be defined) by sending chosen data frame (i.e. right after ignition is switched).

www.formula.pl CAN-Logistic v3 overview and user manual Page 17 of 24

 4.6. Events detection
CAN-Logistic can detect some events and respond with a customized frame or output
signal (when configured as „alarm”).
List of events supported:
• All doors closed (when last door or trunk is closed)
• Any door changed (any door or trunk opened or closed)
• Car locked by remote
• Car unlocked by remote
• Central lock locked
• Central lock unlocked
• Check engine indicator on
• Driver seatbelt fastened
• Driver seatbelt released
• Engine idle start
• Engine idle stop
• Engine off
• Engine on
• Engine speed over limits (lower or upper, according to defined limits)
• Engine speed returned below limits (lower or upper, according to defined limits)
• First door opened
• Handbrake pulled up
• Handbrake pulled up while driving (when speed is greater than defined limit)
• Handbrake released
• Hazard lights off
• Hazard lights on
• Ignition off
• Ignition on
• Oil pressure low indicator on
• Factory alarm mode changed
• Overspeed (speed above defined limit)
• Rapid acceleration occurred
• Rapid braking occurred
• Reverse gear off
• Reverse gear on
• Tachograph mode set to drive or work
• Tachograph driver card inserted
• Tachograph mode changed
• Trunk closed
• Trunk opened
When event occurs, CAN-Logistic can send any configured frame (which contains data or
just custom text). A delay may be programmed: a fixed period of time between event
occur and sending a frame or signalling the output.

4.7. Low power modes

CAN-Logistic goes into low-power mode when data buses in the car goes into sleep mode
(up to few minutes after engine is turned off and car is closed).
CAN-Logistic supports two levels of low power consumption:
- “low power”, where power consumption drops down about a half. It is started as soon
as vehicle’s CANbus stops sending data (vehicle goes sleep). CAN-Logistic wakes up
immediately on any activity on CANbus/J1708/D8 or serial port or BLE or on button press
without any data loss.
- “deep sleep” with minimum power consumption. It is started up to 1 minute from
entering low power mode. CAN-Logistic wakes up from deep sleep on any activity
detected on CANbus/J1708 or serial port or BLE or on button press. Waking time is up to
20 ms, so first command issued by master device on serial port will be lost.

www.formula.pl CAN-Logistic v3 overview and user manual Page 18 of 24

Low power modes are enabled by default, but can be disabled by option 8 (low power
modes at all) and 10 (deep sleep only) - see configuration options in Xon/Xoff or ASCII
protocol.
Proper settings of low power modes should be adjusted to communication scenario used
by master device.
If desired – sleep mode can be permanently disabled by configuration.

Caution! When using D8 line from tachograph, it is required to disable

deep sleep mode. Otherwise data received from tachograph during vehicle
stoppage (like changing driver work mode or inserting/removing the card)
may be lost.

4.8. Firmware updates

As CAN-Logistic is being developed continuously - the number of supported cars and
supported information extends with each new firmware version release.
Every CAN-Logistic device can be updated using its applications (sections 5.1 and 5.2).
It is also possible to update remotely CAN-Logistic's firmware or configuration (sending
appropriate series of management commands). CAN-Logistic-BLE version can be updated
via bluetooth interface.
Please contact the distributor for more details.

4.9. Economic drive support

CAN-Logistic provides a number of parameters which allows to rate driver and teach him
to drive economically.

4.9.1. Rapid brakings and accelerations detection

CAN-Logistic detects and counts rapid braking and accelerations of the vehicle.
Accelerations and braking, which are considered rapid can be configured by user. A rapid
braking/acceleration is when vehicle speed increases/decreases at least the programmed
value during programmed time or less.
When the event is detected, CAN-Logistic increments its rapid accelerations/brakings
counter and may send a customized frame or signal an output (see sections 4.3 and
4.6).

4.9.2. Usage of accelerator and brake pedals

CAN-Logistic counts total number of brake applies and compares usage of pedal braking
against engine braking. It also counts accelerators kick-downs and calculates time when
accelerator is fully pressed.
These values can be used to rate and compare drive styles of drivers.

4.9.3. Overspeeding. Effective engine speed range.

CAN-Logistic calculates time when engine works in desired and non-desired rpm ranges.
CAN-Logistic supports two programmed levels of engine speed and one of vehicle speed.
Therefore it can be read how much of time does the engine work between these two
levels (effective range) or overspeeding.
Each level crossing can generate asynchronous frame (see section 4.6) or output a signal
(see section 4.3).
Can-Logistic measures total time of cruise control engaged, too.

4.9.4. Idle fuel and time

CAN-Logistic calculates the time of engine running and fuel used when vehicle is not
moving. This can help to determinate how much fuel is spent useless.

www.formula.pl CAN-Logistic v3 overview and user manual Page 19 of 24

 Note! See “CAN-Logistic Ecodriving Application Note” for more information.

4.10. Analogue input [SOON]

CAN-Logistic provides one extra analogue input (voltage range 0 to 13V, resolution up to
12 bits) with configurable sample mode.
It can enhance capabilities of target application if master device has insufficient number
of analog inputs.

4.11. Downloading DDD files from tachograph

CAN-Logistic v3 implements features of former tachoreader (THR) device, i.e.
downloading DDD files from tachograph if target application provides remote connection
with tachograph’s company card.

4.12. K-line/D8 data from tachograph

CAN-Logistic v3 features reading tachograph data from multiple sources and protocols:
CANbus and K-line (D8). Target application may comprise connection to all available
buses or only certain ones. In all cases CAN-Logistic reads data from most reliable of
available sources and switches accordingly when one bus enters sleep mode.
K-line/D8 connection requires THR functionality (see section 2.2).

4.13. Development test mode

Development mode is intended to help to develop the program of AVL terminal.
Normally, when CAN-Logistic has no valid connection to CANbus, all parameters are
unavailable, which makes for the developer difficult to validate if AVL terminal receives
data properly. Developing program on direct connection to vehicle is not convenient
either.
When CAN-Logistic works in development test mode, values of all parameters and
indicators are simulated according to Appendix A: Development test and are available on
all output interfaces and protocols for any current CAN-Logistic settings. This way a
developer is able to validate if his system reads values of each parameter as expected.
Development mode is notified by reversed green LED diode blinking (1 s on/100 ms off).

4.14. Fail-safe mode

CAN-Logistic enters FAIL SAFE MODE mode when critical repeatable software error
occurs, which does not allow to run the device. This mode prevents CAN-Logistic from
permanent hang-off and allows to perform remote emergency firmware
upgrade/downgrade.
In Fail safe mode most functionality is disabled, only some status and diagnostic
commands are supported, including firmware upgrade commands.
Operating mode can be immediately restored by executing default reboot command. Yet,
if software problem exists, CAN-Logistic will return into fail safe mode shortly.

If you experience CAN-Logistic entering fail safe mode, please take our
apologies and report the situation to device producer.

Most likely the solution will be an upgrade/downgrade to another, bug-free

version.

www.formula.pl CAN-Logistic v3 overview and user manual Page 20 of 24

5.Accessories

5.1. Configuration application + cable

Although connecting the CAN-Logistic to

vehicle does not require any configuration
issues, there is an application for advanced
device settings and firmware upgrade.
The application also helps to develop target
application, as it can show at a real time the
data, that CAN-Logistic reads from the car, it is
currently connected to.

Picture 12: USB cable for CAN-Logistic

configuration

Caution! There are two kinds of USB cable: one for STD and FMS
assembly version (RS232 to USB converter), another for INV assembly
version (TTL to USB converter).

Picture 13: Sample screen from configurator application.

www.formula.pl CAN-Logistic v3 overview and user manual Page 21 of 24

 5.2. Fast updater application
Fast updater provides feature of update firmware software within ca. 5 seconds per
device (comparing to almost 2 minutes for CAN-Logistic Configurator).

Picture 14: Sample screen from fast updater application.

Caution! Fast updater requires connection to CAN-Logistic always with TTL

to USB converter (even for STD versions, which connects to CAN-Logistic
Configurator with RS232 to USB converter).

5.3. Contactless CAN-bus reader

Contactless Reader (CR) is the interface, which allows to connect CAN-Logistic to
vehicle's CAN-bus without cutting and soldering the cables. CR gets CAN-bus signal by
detecting electromagnetic field – without direct connection to CAN-bus wires.
This is a convinient solution to void warranty-loss concerns.
Contac tless Reader has a plug which fits directly CAN-Logistic's connector and is powered
from CAN-Logistic.

www.formula.pl CAN-Logistic v3 overview and user manual Page 22 of 24

 Picture 15: Connecting Contactless Reader to vehicles CAN-bus twisted pair

5.4. FMS connectors

Some trucks models (i.e. DAF, Volvo) have dedicated connector to plug third party
devices – called FMS connectors. For convenient installation – we provide a cable with
compatibile plug on one side and CAN-Logistic's connectors on the other.
It makes installation easy and quick and voids warranty-loss concerns.

Picture 16: CAN-Logistic wire harness for DAF Euro6 trucks (example)

5.5. Installation diagrams

Installation diagram for each supported car model is provided on partner web-site
(www.formula.pl).

www.formula.pl CAN-Logistic v3 overview and user manual Page 23 of 24

 Picture 17: Example installation diagram for CAN-Logistic

www.formula.pl CAN-Logistic v3 overview and user manual Page 24 of 24