diagnostic of off-highway machinery for · pdf filediagnostic of off-highway machinery for...

Diagnostic of off-highway machinery for agriculture

Contact: Dipl.-Ing. Norbert Schlingmann / Phone: +49 5247 12 1715 email: [email protected] / http://www.claas.com

CTi special day “Diagnostics for Off-Highway Applications”

September 25th, 2012 – Lindau, Germany

12.09.12 Version 1.1

http://www.claas.com/

Norbert Schlingmann 2

Content

Status quo of agricultural machinery

Modular systems and communication – Control units in the network

Diagnostic technology – Challenges for manufacturer and supplier

Experience with diagnostics – Concept and implementation

ISOBUS controls tractor and implement – Database for support

Conclusion and outlook

25th September 2012

Off-highway machines for agricultural use

Norbert Schlingmann 3 25th September 2012

4

Diagnostic for off-highway machines

Diagnostic environment • Diagnose complete machine as “Full-Service-Strategy”

- Service by manufacturer itself and dealer network - Using standard notebooks and equipment

• Using machine network and standard interfaces (CAN, USB,...)

Main tasks of diagnostic systems • Detect errors in a machine • Testing electrical components • Dealing with error codes • Machine configuration, parameter setting and downloading • Providing technical documentation

25th September 2012 Norbert Schlingmann

Complexity of agriculture machines


Servo motor

Revolution sensor

Electrical system 350 plugs

3000 electrical contacts 3000 meter copper Potentiometer

Light barrier

Valves

CAN-BUS up to 30 nodes

GPS System

25th September 2012

Including engines which fulfil emission standards


TIER4i / TIER4f

• Different time schedules for emission standards • Complex technology with additional ECUs (SCR, DPF) • Various strategy of engine supplier

25th September 2012

Challenges for tractor – implement combination


• Tractor as Off-highway machine includes extensive systems • Implement differs from tractor system • Tractor has to operate implement functions

25th September 2012


Content







25th September 2012

CAN-Bus for communication


ECU ECU ECU

Vehicle-CAN

ECU ECU ECU

ECU

ECU

Front-CAN

ECU ECU

Engine

ECU

Diagnostic Plug [ 8 ]

ECU ECU

ECU ECU

Steering-CAN

J1939-CAN

25th September 2012

• Each manufacturer defined user specific characteristics

• SAE J1939 as protocol for Power-Train applications

• NMEA 2000 for navigation systems

Challenges for tractor – implement diagnostics


Joystick

TECU

ISO11783

Machine-CAN

Diagnostic Connector

VT Implement ECU1

Implement ECU2

25th September 2012

Engine diagnostic as part of OEM service

Exhaust regulation for agricultural machines: • History: TIER3 TIER4interim TIER4final Each supplier has its own strategy

• Technology, ECUs, communication protocols • Different DTC handling Different ECUs and diagnostic protocols

• TIER3 K-Line and CAN (J1939, KWP) • TIER4i CAN (KWP) • TIER4f CAN (UDS)



Example: Engines for forage harvester

Full Engine Service strategy for all types of machines • Increasing complexity and efforts • High amount of diagnostic functions Different engine suppliers

Supplier A Tier3 Tier4i Tier4f Hardware EDC7 EDC16 EDC17 Protocol K-Line KWP UDS Technology - DPF DPF+SCR

DPF: Diesel Particulate Filter SCR: Selective Catalytic Reduction (Ad Blue)

0 20 40 60

TIER 3 TIER 4i TIER 4f

Functions

25th September 2012


Content







25th September 2012

Strategies for diagnostic purposes

Most of OEMs have their own diagnostic tool and interface • Usage for off-, onboard and remote diagnostic • Includes all kind of ECUs for aggregates and engines

Integration of external ECUs necessary (e.g. engine ECU) • Precondition: ECU fulfils diagnostic requirement of OEM

- Open issue in discussion with engine supplier ! • Challenges for OEMs

- Software interface mostly different and not changeable - Two possible solutions:

- OEM integrates engine supplier interface with great effort if possible

- Engine supplier performs diagnostics with own service people and tool



Diagnostic development process at CLAAS

Usage of diagnostic standards within CLAAS control units • Specification tool provides information for coding and test • Communication protocol KWP2000 and J1939-73

What about engine diagnostics? • Interface to CLAAS diagnostic system necessary

- Due to different suppliers, emission standards and protocols - Unique gateway for data exchange

• Basic approach: One interface between all systems and suppliers - One face to the customer: CLAAS diagnostic system

• Extendible for D-PDU-API for future use

25th September 2012

16

Generic interface as platform for engine supplier

Different protocols User specific demands

• Download, calibration • Specific engine tests

D-PDU-API possible


USB-CAN-Interface

MT-API

J2534

CAN protocols Generic interface

Supplier A Supplier B Supplier ...

JNI J2534

JAVA Virtual machine (JVM)

CDS ODX

ODX A JNI Generic

ODX B

ODX ...

D-PDU-API

ODX

ODX

ODX

17

Experience with generic interface

One interface to diagnostic development system • Using ODX services

Scalable dependent on demands of engine suppliers

Integration of different documentation formats incl. DLLs • Data will be prepared as ODX files by CLAAS • Linked to generic interface

Usage of proprietary and standard protocols as well

Easy and comfortable way of data usage



Strategy for On-/ Off-board and remote diagnostics

Specification

USB CAN

Off-board or remote diagnostics

ODX

Internet

generate Software Diagnostic

.c .h

ECU’s

*.hex

On-board diagnostic

25th September 2012


Content







25th September 2012


CLAAS Diagnostic System – CDS

Start with a monkey proofed system in 1996 Currently usage of a system for experts

• Show CAN information based on KWP2000, J1939 and ISO11783 • Identification and download • Fault memory • Functional diagnostic

- Link to service infos

CDS supports • Service organisation • Production line • R & D

25th September 2012


CDS – Download

25th September 2012

22

CDS – Functional diagnostics

Norbert Schlingmann 25th September 2012

CDS – Engine test with generic interface

25th September 2012 Norbert Schlingmann 23


Content







25th September 2012

Tractor – implement – combination in principal

25 Norbert Schlingmann

Joystick

TECU ISO11783

Machine-CAN

Diagnostic Connector

VT Implement ECU1

Implement ECU2

25th September 2012

ISO11783 as communication protocol

26 Norbert Schlingmann

• Different networks with additional devices in the market

• Complex structure for testing and diagnose

25th September 2012

27

Status quo – Long period of inoperability


Dealer A

Manufacturer B Manufacturer A

I will help….

I have a problem !

Need information

Need information Plugfest

! • Missing information • Missing communication

Customer

28

AEF developed ISOBUS database


Customer

Dealer A

Manufacturer A

Dealer B

Information

Can help

I have a problem !

I have a problem ! Send Data…

Plugfest

I will help….

Know ledge Data

Request information

Ticket Data

Manufacturer B Manufacturer C

!

29

General demands for ISOBUS products

Support of information about all tested systems

• Publication of conformance test results

- Certification has to be done by the new AEF conformance test tool

- Test will be done by accredited test institutes

• Data about launched ISOBUS products

- Availability about software update/upgrade

Fixed format for data-transfer

Usage of a manufacturer-wide diagnostic tool

Database shall be mandatory for all ISOBUS user


30

Use case database: Automatic compatibility check

Analyze of failing system

• Through dealer or service technician

First source of information

• Component certifications

• Knowledge objects and update/upgrade information


XML AEF

Database


Content







25th September 2012

Conclusion – Outlook

Agriculture industry is providing full-service for diagnostics • Using standards is a must Derivates are not sufficient

- Great efforts for integration, often with inadequate documentation

Generic interface is able to add different diagnostic demands • One development environment and easy handling Standardization has to be done more efficient

• Less is often more if everyone uses the “less” completely Entry of high speed networks for fast data transport

• Ethernet, Ethercat,... - Terminals, camera systems, data for task management,....

Applications for Smart phones or tablets


Thank you for your attention


diagnostic of off-highway machinery for · pdf filediagnostic of off-highway machinery for...

Documents