AEF ISOBUS Conformance Testing

Logo for the AEF

The new AEF ISOBUS Conformance Test was officially unveiled in September 2013. It is closely tied to the AEF concepts of ISOBUS Functionalities and the AEF Database. These 3 new concepts were created to address a lack of clarity with the previous AEF certification from DLG. The DLG stamp of approval indicated that a device was ISOBUS certified, but it only tested for the Virtual Terminal capability and gave no indication about other capabilities.

ISOBUS Plugfest 2014 – What we saw

ISOBUS Schematic

The 2014 Spring Plugfest in Lincoln just wrapped up last week. I did not see the final numbers, but would guess there were 180-210 total attendees and participants. The Plugfest had 16 VT stations and 13 TC stations, plus each participant went to the AEF Database station and the AEF Conformance Test station. A total of 34 different implement ECUs were being tested: 24 were testing a TC client while the others were only testing the VT client. DISTek had 2 of these ECUs for testing our VIRTEC VT-Client and TC-Client sample applications. The Plugfest also had 4 FMIS systems available and a few TECUs. In addition to these ISOBUS components formally listed at Plugfest, we also saw at least 3 File Servers active on CAN buses and a variety of Aux Inputs located at many stations.

LIVE FROM SPRING PLUGFEST

Attendees at ISOBUS Plugfest in Liconln Nebraska

Rookie no more, I’m two days into my first ISOBUS AEF Plugfest experience. It’s close to what I expected but as with all things I made some assumptions that turned out to be incorrect. No description or story of an event can fully prepare you for something, and Plugfest is no exception. That’s not to say what I’m about to share of my experience thus far won’t be of any help to future would-be attendees, so keep reading.

Getting Ready for ISOBUS Plugfest

Participants at Plugfest 2013 in Lincoln, NE

On a long and lonesome highway, east of Omaha

Spring Plugfest is next Tuesday-Thursday … 06-08 May. It is moving this year from the east campus at UNL to a downtown hotel; the Plugfest got so big that it needed a different location. Due to the move and resultant availability, Plugfest is also later in the year than in most prior years. Unlike Bob Seger, we do not travel quite as much as a rock band so we generally look forward to travelling to the ISOBUS Plugfests. Since Spring Plugfest is in Lincoln – and has been for several years – we do spend quite a bit of time on highways east (and northeast) of Omaha, and other than Ames and Des Moines they are rather long and lonesome. But a 5-hour drive, or 7-hour drive for our Fargo office, is a rather small price to pay for the benefits provided at the event.

An introduction to ISOBUS Sequence Control – ISO 11783 – Part 14

Sequence Control as defined in ISO 11783 – part 14 provides the ability for a tractor to record and perform a sequence of actions within either the tractor or its attached implements. The value to the operator is that he can activate a sequence of steps via one button press or action step. Usually, the sequence of steps would occur at the headland of the field. Besides simplifying the actions required of the operator at the headland and allowing the operator to concentrate on positioning the tractor and implement for another pass through the field, sequence control eliminates forgotten steps that can happen near the end of a long day in the field.

What is the difference between ISOBUS VT Version 3 and Version 4?

VIRTEC display.

The ISO 11783-6 standard was most recently released in 2010. As of this release, three common versions of the Virtual Terminal (VT) are specified. These versions are referenced in the standard as “Version 2”, “Version 3”, and “Version 4”. Based on recent ISOBUS Plugfest attendance, a survey of the industry shows a few Version 2 devices still in common use, a small number of Version 4 devices in use, and a large majority of devices using Version 3. The standard requires that an Electronic Control Unit (ECU) and a VT communicating via the VT standard should use the standard according to the lowest VT version of the pair, e.g. a VT at Version 4 and an ECU at Version 3 should use Version 3 communications.