Diagnostic of off-highway machinery for agriculture

Transcription

1 Diagnostic of off-highway machinery for agriculture CTi special day Diagnostics for Off-Highway Applications September 25 th, 2012 Lindau, Germany Contact: Dipl.-Ing. / Phone: [email protected] / Version 1.1

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 2

3 Off-highway machines for agricultural use 3

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 4

5 Complexity of agriculture machines Light barrier Electrical system 350 plugs 3000 electrical contacts 3000 meter copper Potentiometer GPS System Valves CAN-BUS up to 30 nodes Servo motor Revolution sensor 5

6 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 6

7 Challenges for tractor implement combination Tractor as Off-highway machine includes extensive systems Implement differs from tractor system Tractor has to operate implement functions 7

8 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 8

9 CAN-Bus for communication ECU ECU ECU ECU ECU Steering-CAN Vehicle-CAN ECU Front-CAN ECU ECU ECU ECU ECU J1939-CAN ECU Engine Diagnostic Plug [ 8 ] ECU ECU ECU Each manufacturer defined user specific characteristics SAE J1939 as protocol for Power-Train applications NMEA 2000 for navigation systems 9

10 Challenges for tractor implement diagnostics VT Joystick Implement ECU1 ISO11783 Implement ECU2 TECU Machine-CAN Diagnostic Connector 10

11 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) 11

12 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) Functions TIER 3 TIER 4i TIER 4f 12

13 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 13

14 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 14

15 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 J 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 15

16 Generic interface as platform for engine supplier Different protocols User specific demands ODX CDS Download, calibration Specific engine tests JAVA Virtual machine (JVM) JNI J2534 JNI Generic ODX A ODX J2534 ODX B ODX... ODX ODX CAN protocols MT-API Generic interface Supplier A Supplier B Supplier... D-PDU-API possible D-PDU-API USB-CAN-Interface 16

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 17

18 Strategy for On-/ Off-board and remote diagnostics Off-board or remote diagnostics ODX Specification Internet USB CAN On-board diagnostic ECU s generate Software.h.c Diagnostic *.hex 18

19 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 19

20 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 20

21 CDS Download 21

22 CDS Functional diagnostics 22

23 CDS Engine test with generic interface 23

24 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 24

25 Tractor implement combination in principal VT Joystick Implement ECU1 TECU Machine-CAN Diagnostic Connector ISO11783 Implement ECU2 25

26 ISO11783 as communication protocol Different networks with additional devices in the market Complex structure for testing and diagnose 26

27 Status quo Long period of inoperability I have a problem!! Missing information Missing communication Customer I will help. Need information Dealer A Manufacturer A Manufacturer B Need information Plugfest 27

28 AEF developed ISOBUS database! I have a problem! Request information Customer Can help I will help. Data Know ledge Dealer A Dealer B I have a problem! Send Data Data Ticket Information Manufacturer A Manufacturer B Manufacturer C Plugfest 28

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 29

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 30

31 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 31

32 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 32

33 Thank you for your attention 33