Introduction to ISOBUS for Engineers

Introduction to ISOBUS for Engineers
Benjamin Jefferson Engineering Manager DISTek Integration, Inc.

Agenda Introduction – What is ISOBUS? A look at the ISO 11783 parts
Closer look ISO Virtual Terminal ISO Task Controller The ISOBUS Ecosystem all

Is ISOBUS “CAN”? What is ISOBUS?
ISOBUS uses CAN 2.0B operating at 250 kbps all

What is ISOBUS? Is ISOBUS the same as “J1939”?
ISOBUS is intended to be compatible with J1939 in most ways. An ISOBUS device can operate on a J1939 network and vice versa. But there are several differences which we will touch on when looking at the ISO parts. all

What is ISOBUS? Is ISOBUS the same as “ISO 11783”?
The technical description of ISOBUS is laid out in the ISO standard … though state-of-the-art ISOBUS is often not yet captured in the released standards. And ISO is just one component in a large set of useful tools and information sources. More on that later … all

What is ISOBUS? ISO specifies a communications system for agricultural equipment based on the CAN 2.0 B protocol. SAE J1939 documents, on which parts of ISO are based, were developed jointly for use in truck and bus applications and for construction and agriculture applications. Joint documents were completed to allow electronic units that meet the truck and bus SAE J1939 specifications to be used by agricultural and forestry equipment with minimal changes. The purpose of ISO is to provide an open, interconnected system for on-board electronic systems. It is intended to enable electronic control units (ECUs) to communicate with each other, providing a standardized system. all

What is ISOBUS? For most beginning applications, ISOBUS can be defined as … A CAN-based system A J1939 base software layer with some ISOBUS-specific supplements A set of higher level applications – Virtual Terminal, Task Controller, etc. Based on the released ISO standards An ecosystem to help adoption of ISOBUS all

Questions?

ISO Parts ISO has 14 parts 7 parts have close ties to J1939 parts Most recent release dates from >1100 total pages … though most of those are Annexes all

General standard for mobile data communication
ISO :2007 General standard for mobile data communication Similar to J1939/01 and J1939/02 Contains many abbreviations and definitions used throughout the remainder of the standard Discusses OSI seven-layer model and how ISO relates to the different layers Briefly describes the higher level applications in the standard Describes the concept of a “Working Set” with members and a master Appendices contain standard values for PGNs, Industry Groups, Preferred Addresses, etc. Physical Layer Data Link Layer Network Layer Transport Layer Session Layer Presentation Layer Application Layer all

ISO :2007 This part is so old that it identifies parts -12 and -13 as “To be published” and makes no mention of part -14. An updated version is in FDIS state. This new version will remove the appendices and instead reference all

ISO :2012 Physical layer Formerly J1939/12, similar to J1939/11and J1939/15 Specifies an unshielded twisted quad cable Four conductors are: CAN_H CAN_L TBC_PWR TBC_RTN J1939/11 specifies shielded twisted pair cable J1939/15 specifies unshielded twisted pair cable Terminating Bias Circuit (TBC), aka “Active Termination” as opposed to a resistor terminator in J1939/11 and J1939/15 Data Link Layer Network Layer Transport Layer Session Layer Presentation Layer Application Layer Physical Layer all

ISO :2012 Specifies differential voltage, voltage levels, impedance, resistance, capacitance, bit transition time, DC and AC parameters, etc. Bus topology should be linear with stubs, as much as possible Max bus length of 40m Max stub length of 1m Maximum of 30 nodes Specifies connectors IBBC – Implement bus breakaway connector Diagnostic connector – identical to J1939/13 connector Bus extension connector In-cab connector all

ISO 11783-2:2012 Specifies pinout for each connector
Specifies conformance test parameters Describes bus failure and fault confinement scenarios Annex A describes bit timing Annex B offers example physical layer circuits including circuits for TBC all

ISO :2014 Data link layer … but also includes transport layer definition Very similar to J1939/21 Extended (29-bit ID) frames Priority Extended Data Page (EDP) Data Page (DP) PDU Format (PF) PDU Specific (PS) Source Address (SA) Data Max frame length with bit stuffing = 150 bits Standard (11-bit) frames are only defined so as to avoid conflicts, but can otherwise co-exist. Physical Layer Network Layer Session Layer Presentation Layer Application Layer Data Link Layer Transport Layer all

ISO 11783-3:2014 Parameter group number (PGN) - 24 bits 6 bits of ‘0’
1 bit for EDP 1 bit for DP 8 bits for PF 8 bits for Group Extension – (typically Destination Address (DA) or ‘0x00’) 8672 possible PGN combinations EDP=0 for all ISO messages EDP=1,DP=0 is reserved EDP=1,DP=1 is used for ISO EDP DP PF GE all

ISO 11783-3:2014 PDU1 and PDU2 formats PGN Request and ACK/NACK
Transport Protocol for data length bytes BAM – Broadcast globally to the entire network with no flow control Destination-specific – Uses flow control between transmitter and receiver RTS, CTS, EndofMsgACK, Abort, BAM, Data Extended Transport Protocol for data lengths M = 117,440,512 (7*224) bytes No BAM allowed Adds DPO (Data Packet Offset) message Previously located in ISO :2010 Annex K all

TP versus ETP TP Sender Receiver TP.CM_RTS TP.CM_CTS TP.DT …
TP.CM_EndofMsgACK ETP Sender Receiver ETP.CM_RTS ETP.CM_CTS ETP.CM_DPO ETP.DT … ETP.CM_EOMA all

ISO 11783-4:2011 Network layer Similar to J1939/31
Discusses four different types of Network Interconnection Units (NIU) Repeater – Forwards messages Bridge – Filters messages Router – Allows an entire network segment to appear as a single Control Function Gateway – Repackages data into different messages NIUs should be transparent on the network The network topology should allow only 1 path between devices Physical Layer Data Link Layer Transport Layer Session Layer Presentation Layer Application Layer Network Layer all

ISO :2011 all

ISO :2011 Defines a Network Message PGN with 21 subcategories of commands and responses Devices can query an NIU for 16 different status and statistics values such as: Buffer size Number of messages dropped Number of ports Avg Number of messages received/second Avg Number of messages forwarded/second Max Number of messages received/second Tractor ECU is a special NIU connecting the implement and the tractor buses … More in -9 all

ISO 11783-5:2011 Network management Similar to J1939/81
Primarily discusses 64-bit CAN Name and Source Address arbitration An ISO device is required to have a self-configurable source address, unlike J1939 which gives the option An ISO network is compatible with devices, such as J1939, that are not self-configurable Devices can also support service-configurable or command-configurable source addresses all

ISO 11783-5:2011 The 64-bit CAN Name is nearly identical except:
The “Vehicle System” and “Vehicle System Instance” parameters in J1939 are called “Device class” and “Device class instance” ISO requires polite address claiming, i.e. a device sends a Request-for-address-claimed prior to claiming an address of its own. J1939 allows this as one option while also allowing immediate claiming of an address after power-up. ISO does not have special requirements for diagnostic/development devices as does J1939 The only required DTC is in this section, when a device receives a message from its own SA all

ISO 11783-6:2014 Virtual Terminal Formerly J1939/72
More on this later … Physical Layer Data Link Layer Network Layer Transport Layer Application Layer Session Layer Presentation Layer all

Implement messages application layer
ISO :2015 Implement messages application layer In general, I think of this as the J1939/71-esque database of messages that are specific to ISO 11783 The data tends to relate to the interaction between the tractor and an implement Some typical data fields that are used include: Wheel- or Ground-based speed/direction/distance Key switch state Hitch, PTO, Aux Valve, Lights Language and Regional information all

ISO :2015 Also includes messages to allow the implement to control the tractor: Cruise control Front/Rear Hitch/PTO slip control Front/Rear PTO torque control Minimum engine speed Vehicle speed PTO speed Hitch position Guidance commands – to steer the vehicle all

ISO 11783-8:2006 Power train messages
This part is 8 pages long … and all it says is to see J1939/71. Anything also defined in ISO should use that definition rather than J1939/71. all

ISO :2012 Tractor ECU The Tractor ECU (TECU) is a gateway (as defined in ISO ) between tractor and implement buses. Multiple TECUs can be on a network. Priority is based on function instance. all

ISO 11783-9:2012 Class 1 TECU – Not recommended for new designs
An ECU with connected sensors is likely enough Supports messages for power management, speed information, hitch information, PTO information, language, and tractor facilities Class 2 TECU – Includes all Class 1 features Adds ground- and wheel-based machine distance and direction; rear draft information; lighting messages; auxiliary valve estimated or measured flow Class 3 TECU – Includes all Class 2 features Adds hitch information and command; PTO information and commands; auxiliary valve information and command. all

ISO :2012 Additional specifiers indicate other capabilities provided by the tractor on the implement bus ‘N’ indicates navigational information on the implement bus ‘F’ indicates front-mounted (or secondary) hitch and/or PTO information on the bus ‘G’ indicates guidance status and control ‘P’ indicates powertrain status and control ‘M’ indicates motion initiation is provided Specifiers can be combined along with the TECU class, e.g. 2NG or 3NFP all

ISO 11783-9:2012 TECU also has control for ECU_PWR and PWR
TBC_PWR is either tied to ECU_PWR or sourced separately from the TECU ECU_PWR should supply a minimum of 15A at 12V PWR should supply a minimum of 50A at 12V Combined ECU_PWR and PWR should be a minimum of 55A continuous at 12V System shutdown After key off, PWR and ECU_PWR stay powered for 2 s. Other devices can request PWR and/or ECU_PWR stay on for additional time to complete power-down actions all

Task Controller and management information system data interchange
ISO :2015 Task Controller and management information system data interchange … aka Task Controller More on this later … all

Mobile data element dictionary
ISO :2011 Mobile data element dictionary Much like part 8, this part contains very little information and merely points to This now redirects to all

ISO 11783-12:2014 Diagnostic services Similar to J1939/73
Supplied information should include: ECU information (ECU ID) 64-bit CAN Name Software version (SW ID) Compliance test data Functionalities (more on this later) This version adds a Product ID message which includes: Product ID code, e.g. a VIN Product ID brand Product ID model all

ISO :2014 Annexes define the ECU ID data, software ID data, the ECU diagnostic protocol messages DM1, DM2, and DM3 – as in J1939/73 – are included, but no other DM messages from J1939 are used FMIs are defined as in J1939/73 all

ISO :2011 File server Provides the capabilities in line with its name: a location to store and retrieve files on the network Uses periodic messages to maintain a session A transaction number (TAN) is used for each request to a file server. This helps with fault tolerance and synchronization. FS can support multiple clients simultaneously FS can support multiple volumes Only certain characters are allowed in file and path names Wildcard characters “*” and “?” can be used, where applicable „Volume“ is a single accessible storage area with a single file system, typically (though not necessarily) resident on a single partition of a hard disk. „C:“, „D:“, and „E:“ are examples of volumes.

ISO 11783-14:2013 Sequence control
Used to synchronize several functions across multiple devices, e.g. for entering/exiting headlands or crossing waterways Consists of a single Sequence Control Master (SCM) and some number of Clients (SCC) Sequences are recorded or edited by the SCM and given a unique numeric value; a proprietary means to give a more descriptive identifier can be provided Uses a TAN concept Relies on the VT capability for user interface Requires a VT v5 capability which was released in 2014 Much more … could be several hours all

Questions?

ISO :2014 Perhaps the best known and most described feature of ISOBUS … any tractor can connect to any implement, use one screen in the cab for all implements, etc. Nearly every ISOBUS implement will have a VT client even if the primary purpose is something else (e.g. TC client) Has reached a maturity level where everything pretty much just works … at least the more mature features Commercial options are available for most aspects of VT development, from off-the-shelf systems to customizable components all

ISO :2014 all

VT Versions VT communications use the lesser version of the two devices VT v2 is the lowest version in common usage Uses the Aux Type 1 … More about Aux later VT v3 is the most commonly reported version in use today Nearly identical to VT v2 except it uses Aux Type 2 instead VT v4 is not in common usage, though many v3 VTs implement some v4 features Adds additional objects, split-screen capability, and other differences which will be described in more detail in the next slides (in green) VT v5 is now released, but no commercial VTs are available with this version all

VT Operator Input Soft Keys as part of a Soft Key Mask – Physical or touchscreen buttons Navigation – Encoder knob, buttons, touchscreen Data input – For numeric and string entries Real-time input Selecting different Working Sets Acknowledging alarms Auxiliary Inputs all

VT Characteristics Acoustic alarm which may be a simple on/off buzzer or may allow variable frequency and volume Two components to the display area Data Mask – Same number of pixels wide and tall (square aspect ratio), minimum 200x200 Soft Key Mask – For displaying the current Soft Keys, minimum 60x32 pixels Numbers and Types of Soft Keys Physical Soft Keys – no minimum number (6) Virtual Soft Keys – Up to 64 (exactly 64) Navigation Soft Keys – May be used if Number of Virtual Soft Keys > Physical Soft Keys 8-, 4-, or 1-bit (Monochrome) color all

Working Sets A Working Set (WS) contains 1 Master and 0+ Members
A WS Master reports the 64-bit CAN Names of the Working Set’s members Only the WS Master uploads the object pool Data input on the VT is always reported to the WS Master The master or any member can send commands to the VT Responses are sent to the WS Master (or the originator) The term “Working Set” is also used as the name of an object type all

Typical VT-Session Startup
Devices complete address claim VT sends VT Status periodically WS Master/Members messages are sent WS Maintenance message sent periodically WS requests language (regional) info from VT, and other VT metrics (Data Mask size, fonts etc.) WS loads object pool, either via CAN or from VT NVM WS commences normal operation with object pool When multiple VTs are on the network, the WS can choose any to use The WS should normally choose to keep using the same VT as the last power cycle, based on 64-bit CAN Name all

VT Metrics VT version Number of Navigation, Physical, and Virtual Soft Keys Soft Key size in (x,y) pixels Supported Font Sizes Supported Font Styles (Bold, Italics, etc.) Boot time Supported color depth Data Mask size in (x,y) pixels Touchscreen? Multi-frequency alarm? Adjustable volume alarm? Supported WideChars (Unicode) Supported Objects all

VT NVM Capabilities Get (Stored) Versions Store Version Load Version
Delete Version This does not delete the pool from RAM if it is currently loaded, it only deletes the pool from the stored version information. all

VT Requirements Overlaid objects – objects listed earlier are behind objects listed later Clipping – Done on a pixel (not character) basis Size-scaling of bitmap graphics – Other scaling must be done by the WS Text rendering – Fonts, wrapping, string encodings, Left/Middle/Right and Top/Middle/Bottom justification Output shape boundaries and fill Alarm handling – Alarms will be displayed regardless of the active Working Set Adjust function instance – function instance ‘0’ is the primary VT all

VT Requirements (Optional) Data from multiple WSs on one Mask
Divides the Data Mask area in 2x6 grid all

VT Object Pool A collection of objects that specifies the operator interface for a particular device Only one (active) object pool per Working Set Transferred to the VT via CAN at initialization Store/Load for the object pool is used based on 64-bit CAN Name Objects are generally structured as a parent-child tree Parents reference children, but not vice versa A parent may have many children A child may have many parents Object pools can be modified at run-time, e.g. to change strings when the language changes The object pool that is being updated will not be available for interaction while updating all

About objects Each object in a pool has a unique 16-bit “Object ID”
Objects have “Attribute IDs” (AID) that are read-only or modifiable by the Change Attribute command Objects have an explicit list of allowed commands that can operate on that object type Objects have an explicit list of related events and a defined VT behavior due to each event Objects can associate events to macro objects The allowed parent-child relationships are explicitly defined Additional parent-child relationships are in v4 all

Object Types Top Level Objects Working Set object Data Mask object
Alarm Mask object Container object Window Mask object Key Objects Soft Key Mask object Key object Button object Key Group object all

Button Object Button border control is only guaranteed in VT v4 and later Buttons on VT v3 or v2 can vary substantially in look-and-feel across manufacturers The button face offset is proprietary up to 8 pixels in the x and y directions all

Object Types Input Field Objects Input Boolean object
Input String object Input Number object Input List object Output Field Objects Output String object Output Number object Output List object all

Object Types Output Shape Objects Line object Rectangle object
Ellipse object Polygon object Output Graphic Objects Picture Graphic object Meter object Linear Bar Graph object Arched Bar Graph object Graphics Context object all

Shape Objects The Ellipse object can be a closed ellipse, an open ellipse (not fillable), a closed ellipse segment, or a closed ellipse section Polygon types can be Convex, Non-convex, Complex, or Open A Polygon that is not “Open” has the first and last points automatically closed by the VT all

Picture Graphic Object
Data for the bitmap is in 8-, 4-, or 1-bit color format For 4- and 1-bit color, the unused portions of bytes at the end of a line is filled with zeroes Compression is offered as Run-Length Encoding (RLE) RLE is done on a byte-by-byte basis, not on a pixel-by-pixel basis Unlike all other objects, the Picture Graphic is size-scaled by the VT all

Object Types Variable Objects Number Variable object
String Variable object Attribute Objects Font Attributes object Line Attributes object Fill Attributes object Input Attributes object Extended Input Attributes object Colour Map object Object Label Reference List object all

Object Types Other Objects Object Pointer object Macro object
Auxiliary Control Objects Aux Function Type 1 object Aux Input Type 1 object Aux Function Type 2 object Aux Input Type 2 object Aux Control Designator Type 2 Object Pointer object all

Macro Object The Macro object uses a 16-bit Object ID like every other object, but the value is restricted to 0-255 Macro commands use the same data as is defined for the corresponding CAN messages in Annex F A given macro can technically have up to commands all

Auxiliary Controls The basic concept is to allow user inputs (joystick, buttons, etc.) from Manufacturer A to control implement functions of Manufacturer B via mapping from Manufacturer C’s VT. all

Auxiliary Controls Aux Control allows implement functions to be controlled independent of the currently visible Working Set on the VT. All mapping takes place on VT at function instance 0. This can lead to the need to have a split pool between 2 VTs. Type 1 Aux is only valid for VT v2 and is discouraged for new designs. For compatibility, VT v3 and later should still parse the Type 1 Aux objects in a pool. all

Auxiliary Controls Type 2 Aux Function and Aux Input objects are defined identically An Aux Control has: A function type (encoder, analog, boolean latching, etc.) Critical control? Assigned only by Preferred Assignment? Single-Assignment? A collection of decorations, similar to a Working Set object Preferred Assignment uses CAN Name (or a subset) to automatically choose Aux Inputs by Aux Functions (Optional) Assignments can be done in a “Learn Mode” to ease the process for the user all

Auxiliary Controls Aux Control Designator Type 2 Object Pointer allows graphically representing an Aux Input or Aux Function in a graphical pool This can be used to graphically depict the mapping from an input to a function This may not be possible when not on VT with function instance other than ‘0’ all

Questions?

ISO :2015 Task Controller relates to field data collection, section control, and variable-rate application all

Task Controller The common term ISOXML comes from this part
Two primary reasons for task management Managing equipment, workers, and product used Managing farm activities in the field MICS – Mobile Implement Control System FMIS – Farm Management Information System Data passes from FMIS to MICS as planned tasks Data passes from MICS to FMIS as completed tasks Tasks can be created in FMIS or an MICS UI No MICS UI is required all

TC Requirements Select and Execute tasks Maintain task status
Initial/Planned Running Paused (Optional) Completed Template Cancelled Record event information in date/time/”GPS” position, e.g. changing of a worker Logging bus data in date/time/”GPS” position, e.g. harvest yield Logging is done in binary or XML format as defined in the standard Other PGNs can be logged in addition to Task Data all

Typical TC-Session Startup
Very similar to the VT session Devices complete address claim TC sends TC Status periodically WS Master/Members messages are sent WS Task message sent periodically WS requests TC metrics WS loads DDOP, either via CAN or from TC NVM WS commences normal operation with object pool The standard stipulates a single TC on a network at one time, though this is changing in committee discussions all

TC Site-specific Application
A Farm is made of Partfields Partfields can be subdivided into TreatmentZones A Partfield can be set up with Gridcell or Polygon TreatmentZones When a DeviceElement enters a new TreatmentZone, the TC sends a new ProcessDataVariable set point to the WS Master DeviceElements are geometrically located in space using x,y,z Due to delays in the system, a TC may use delay metrics provided by the WS and a look-ahead prediction to adjust values prior to actual transition into a new TreatmentZone Multi-layer polygon-based site-specific application is used for each setpoint type all

TC Data Logging A DDOP provides a default set of process data which can be requested, and individual items can be requested as well Individual requests should be positively ACK’d or negatively ACK’d as appropriate Different trigger mechanisms are available: time, distance, threshold, on-change, total (and combinations thereof) Totals are sent to the TC when a task is paused Task Totals are reset by WS to zero when a task is (re)started Lifetime Totals are not reset to zero Therefore, to resume a task, the totals must be remembered by TC and re-written to WS A TC may not log all data if higher-frequency data is too much for the computing power of the TC Maximum 10 PDM per PDV per second for each client-to-TC connection TC version 2 and earlier may not support the start of a measurement while a task is not active all

TC Data Logging - DL DL – Data Logger: A separate control function on a network, e.g. a telemetry data logger. The DL functionality is a subset of the TC functionality Uses the same connection mechanism Uses a DDOP transfer Uses the same process data definitions A DL does no controlling of a TC-Client No Section Control, no position-based control, no peer-control assignments A DL uses a different function definition (in the CAN Name) on the network than a TC all

Peer Control One CF can be a setpoint for another CF
Allows setpoint values from sources that cannot be determined during planning of field operations E.g. on-the-go sensor systems Both the setpoint value source and the setpoint value user are TC-Clients The CF with the setpoint value source sends values directly to the CF with the setpoint value user all

TC Data Transfer A well-defined XML schema is recommended for data transfer between FMIS and MICS Note: If a given manufacturer makes both a TC and an FMIS, a proprietary format may be used. Schema defines 45 (53) XML element designators (e.g. Partfield, TreatmentZone, TimeLog, DeviceElement) The filename is specified as “TASKDATA.XML”, but transfer mechanism is proprietary This same file is updated while the task runs (with logged data and events) and can then be sent back to the FMIS If logging is stored in binary files, the XML file references these files by file name all

DDOP - Device Description Object Pool or Device Descriptor Object Pool
Five object types DVC – Device object DET – Device Element object DPD – Device Process Data object DPT – Device Property object DVP – Device Value Presentation object Each object contains a 3-character designator for type Device object is the ‘master’ parent object Exactly one Device object per DDOP Device object always has Object ID 0 Contains several strings for a designator, software version, serial number, etc. all

Device Element Specifies a Parent Object ID which can be the Device object or another Device Element object Specifies a set of Child objects of type Device Process Data or Device Property 4096 unique Device Elements per DDOP Seven types of Device Elements Device – Always Device Element number ‘0’ Function Bin Section Unit Connector Navigation Reference all

Sample DDOP all

Device Process Data References a Data Description Index (DDI) from ISO Provides trigger type Denotes if the item is a member of the default set and if the item is a setable value References a single Device Value Presentation object (or the Null object ID) all

Device Property Also references a Data Description Index (DDI) from ISO Includes a value of the property References a single Device Value Presentation object (or the Null object ID) all

Device Value Presentation
Used to make values visually pleasing: scale and offset, number of decimals, and a units designator all

Questions?

Commercial Support Three commercial VT Pool Generators
WTK Mask Generator Jetter ISO Designer OSB vt-designer One Open-Source VT Pool Generator PoolEdit Several commercial FMIS products available One Open-Source FMIS beta – AgroSense Several commercial ISOBUS protocol stacks One Open-Source ISOBUS protocol stacks OSB ISOAgLib Training offered by CCI, REI, Kereval, and DISTek Integration all

ISOBUS Plugfests One spring event in USA and one fall event in Europe
Spring 2014 in Lincoln, NE in May ~200 attendees, 16 VTs, 13 TCs, 33 WSs, 4 FMIS, plus some TECUs and Aux Inputs Fall 2014 near Paris in October ~250 attendees, 21 VTs, 17 TCs, 82 WSs, plus FMIS, TECU, and Aux participants Spring 2016 in Lincoln, NE in May Fall 2016 in Bologna, Italy in September Similar to speed-dating between WSs and VTs/TCs A WS spends minutes at each VT/TC station Each station has a CAN backbone, power supply, etc. TC stations supply GPS simulation, field maps, etc. Additional stations for AEF Conformance Test and AEF Database all

AEF Resources Multiple Project Groups for different ISOBUS needs
Face-to-Face meetings typically held around Plugfests Teleconference meetings held as needed Meetings are good sources of information for draft standards, new features in development, new conformance test procedures Sharepoint site – the “treasure chest” of all the documents from all the Project Groups AEF annual General Assembly meeting AEF Conference Day all

The New AEF ISOBUS Certification and Database
The contents of this presentation are based largely on AEF “Train the Trainer” slides presented to AEF member companies.

About the AEF AEF (Agricultural Industry Electronics Foundation)
Founded October 28th 2008 by 7 agricultural equipment manufacturers and 2 trade associations More than 180 companies, associations and other organizations are current members Objectives of the AEF: ➡ Coordination of international development of Agricultural electronics ➡ “First priority”: ISOBUS all

Introduction The use of the AEF ISOBUS Conformance Test Tool (CT) and the AEF ISOBUS Database (DB) has started. Unrestricted publication of test results has been allowed since September 12, 2013. Five test laboratories are now ready for conformance testing ISOBUS Test Center (ITC) Reggio Emilia Innovazione (REI) Nebraska Tractor Test Laboratory (NTTL) DLG Test Center Technology and Farm Inputs Kereval At Agritechnica in November 2013, many AEF certified and labeled ISOBUS Components were on display. all

First Priority ISOBUS What do we want to achieve?
Increased international acceptance of ISOBUS technology Fewer proprietary “island” solutions Availability of all information about ISOBUS products – including functions, implementation, and compatibility – for service, marketing and sales divisions of manufacturers and suppliers ➡ AEF ISOBUS Database Help ensure clarity regarding compatibility of machines ➡ AEF ISOBUS Conformance Test Clear communication which is aligned within the Ag industry as a whole ➡ AEF ISOBUS Functionality concept all Enhanced customer benefits from using ISOBUS technology

AEF ISOBUS Functionalities
Why Functionalities? Introduction of the first ISOBUS systems in ➡ only one functionality: UT (Universal Terminal) Further development of ISO standard and AEF guidelines ➡ new functionalities were defined (e.g. Auxiliaries, Section Control, Sequence Control etc.) But: Conformance tested systems still received the DLG ISOBUS label which did not say if other functionalities (except implement-UT-communication) were included/certified or which additional functionalities were needed to get an ISOBUS system running That is why the AEF has introduced a communication concept based on functionalities and an update of the ISOBUS Certified Label which in conjunction with the AEF ISOBUS Database provides more information ➡ From the database, users will know: 1. The product is in conformance with ISO 11783 2. Which functionalities are supported by looking it up in the database all

AEF ISOBUS Functionalities
An ISOBUS functionality is a product which can be explained and sold to the end user as a separate “module“ on the ISOBUS. One or more can be bundled together into a retail product intended to interconnect with other products that contain AEF Functionalities. Only Functionalities supported by all components involved can be used. An open concept, new functionalities will be defined in the future … all

UT – Universal Terminal
The capability of operating an implement on any terminal Also the capability of using one terminal for operating different implements. all

Auxiliary Control AUX-O – Auxiliary Control “old”
AUX-N – Auxiliary Control “new” Facilitate the operation of complex equipment Capability of controlling implement functions The “old” and a “new” auxiliary control are not compatible Implements and functions certified according to AUX-N cannot be operated with input devices certified according to AUX-O and vice versa Joystick, free definition of hardkeys

TC-BAS – Task Controller Basic (totals)
Documentation of total values that are relevant for the work performed The implement provides the values Exchange of data between farm management system and Task Controller via ISO-XML data format Jobs can easily be imported to the Task Controller Finished documentation can be exported later all

TC-GEO – Task Controller Geo-based
Additional capability of acquiring location-based data Planning of location-based jobs Variable Rate Technology (VRT) all

TC-SC – Task Controller Section Control
Automatic switching of sections Based on GPS position all (photo: John Deere)

TECU – Tractor ECU Tractor’s “job calculator” Provides information
For the certification of this Functionality, a connector on the back of the tractor and a terminal outlet in the cab are needed. all

TECU-A – Advanced Tractor ECU AEF ISOBUS Functionalities under development
TECU-A features the capability of bi-directional communication Includes the tractor in its control process Provides the capability for the implement to control the tractor Under development all

SQC – Sequence Control AEF ISOBUS Functionalities under development
Grouping different functions of different ISOBUS components in a sequence (e.g. headland management) Under development all

ISB – ISOBUS Shortcut Button AEF ISOBUS Functionalities under development
Allows to deactivate functions of an implement that were activated by means of an ISOBUS terminal Necessary when the implement in question is currently not in the foreground of the UT The functions an ISB is able to deactivate on an implement can vary widely all Under development

Physical Label all The new AEF ISOBUS Certified Label with nine small squares Six of them show functionalities representing the total functionalities concept Three at the bottom Symbols for more functionalities to come Concept is open and extendable A sticker to be used for AEF certified products The latest label style guide is available via AEF Database

Physical Label In Conformance to ISO 11783 – it is an “ISOBUS product”

Physical Label Successfully passed AEF Confomance Test
Conforms to AEF Guidelines

Physical Label Display the whole ISOBUS functionality concept
More functionalities expected in the future, therefore an open and extendable concept

Physical Label all More information about the product and software capabilities available via the AEF Database

E-Label Under development
Functionalities Display Example of an implement functionality status screen The E-Label in a UT display is designed to give the user a quick and easy overview of all functionalities existing in the ISOBUS system. The functionality message protocol provides information about current software versions of all devices and provides much more information than a label fulfilling symbolic purposes only. Under development

AEF Guidelines The AEF Guideline Communication & Marketing – Functionalities for Label Structure describes functionalities in detail For example: The AEF Guideline Implementation Specification Functionality TC-SC defines the requirements for the ISOBUS Task Controller Section Control compliance All official AEF Guidelines from all project groups are available within the AEF Database Download Menu Manufacturers and test institutes

AEF ISOBUS Database www.aef-isobus-database.org
Web-based application providing quick and easy access to manufacturers’ information regarding ISOBUS Intended to deliver up-to-date, consistent and trustworthy information about compatibility of machines, implements, terminals and other components that have been certified by the new AEF ISOBUS Conformance Test After registration the admin has access to his/her account and can change the account information, open new accounts for other users (employees), deactivate users’ accounts and reset users’ passwords. all

Using the Database Manual Compatibility Check
Shows the delivery status of all certified products The customer selects a combination of tractor and implement(s) Result: = AEF ISOBUS Functionalities provided by each product = AEF ISOBUS Functionalities provided by the combination of products Dealers and Manufacturers

Using the Database all

Using the Database Automatic Compatibility Check
If the dealer needs additional information or has to help a customer solve a problem with a tractor/implement, he/she can use the Automatic Compatibility Check Download AEF ISOBUSCheck Tool (database download menu)* ➡ it generates the diagnostic file from the data of the ECUs Connect laptop to Universal Terminal Read out data from ECU/UT Log in to AEF Database Upload diagnostic file to database * ISOBUSCheck Tool from Database free of charge. ISOBUSCheck Tool with additional functions available at Sontheim Dealers and Manufacturers

Using the Database Dealers and Manufacturers

Using the Database Compatibility Ticket
If a dealer or technician cannot solve a problem, a Compatibility Ticket can be generated The Compatibility Ticket to informs the manufacturer of the problem Manufacturers will respond within 24 hours Each Compatibility Ticket is like an with an attachment ➡ problem description + diagnostic file Facilitates communication about technical problems/errors between dealer service and all manufacturers involved Manufacturers ask questions to the initiator of the ticket Manufacturers forward ticket to other manufacturers involved Manufacturers reply to the initiator with a solution to the problem If the problem is solved, initiator can close the ticket Dealers and Manufacturers

Running a Conformance Test
What do manufacturers need? License for the Database License for AEF ISOBUS Conformance Test Tool ➡ both can be ordered from AEF treasurer Philipp Fuchsenberger Getting started guide (Teststand and CT Tool instructions) Conformance Test Tool National Instruments (NI) Teststand System under Test (SUT) Description Tool ➡ Available within the Conformance Test download menu in the Database Manufacturers and test institutes

Request a Conformance Test
The AEF ISOBUS Conformance Test How to get products AEF certified / request Conformance Test from ISOBUS Test Laboratories Create SUT description file (contains all information about the device/ each control function that is to be tested) Fill in Test Request Form Upload System under Test (SUT) description file The ISOBUS Test laboratory carries out the Conformance Test and uploads the results to the AEF ISOBUS Database Upload product data to Database and link to certification For detailed information use the Manufacturer Instructions available within the Database Manufacturers and test institutes

Conformance Test Manufacturers and test institutes

Questions?

Introduction to ISOBUS for Engineers

Similar presentations

Presentation on theme: "Introduction to ISOBUS for Engineers"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Introduction to ISOBUS for Engineers

Similar presentations

Presentation on theme: "Introduction to ISOBUS for Engineers"— Presentation transcript:

Similar presentations

About project

Feedback