ISOBUS VT Version 3 and 4 Training

42
Paul Weisberg, CNH Dave Smart, JD Mike Schmidt, AGCO May 20, 2009 ISOBUS Virtual Terminal History

description

B U S

Transcript of ISOBUS VT Version 3 and 4 Training

  • Paul Weisberg, CNH

    Dave Smart, JD

    Mike Schmidt, AGCO

    May 20, 2009

    ISOBUSVirtual Terminal

    History

  • 20 May 2009

    What is a VT?

    ? Is a standard graphic displayincorporating user inputs andoutputs.

    ? Provides a common user platformin the cab

    ? All clients of the VT believe theyare the only client.

    ? No practical limit to how manyimplements or clients can beaccommodated by the VT.Limited only to the specificmanufacturers design.

    ? Similar to the idea of a webbrowser. The VT has no contextabout what is running on it. Userinterfaces are loaded from theconnected clients.

  • 20 May 2009

    Goal of Virtual Terminal is Interoperability

    3

  • 20 May 2009

    Virtual Terminal History

    ? Pre 1999 - The German LBS standard defined a User-Terminalin-cab display device.

    ? While the goal of interoperability was noble, and examples of LBSUser Terminals were implemented, the User Terminal had limitedsuccess and interoperability was not achieved.

    ? ISOBUS adopted the LBS User Terminal standard, made someminor changes and called it the Virtual Terminal.

    ? After several years of struggling with the standard, it was clear thatit was not defined in sufficient detail with enough restrictions toguarantee interoperability success.

    ? In 1999 a Task Force was formed to fix ISO 11783 Part 6 TheVirtual Terminal specification.

    ? Task Force consisted of 4 people, 3 from what would eventuallybecome CNH and 1 from John Deere.

  • 20 May 2009

    Virtual Terminal History

    ? Original ISO approach was a messaging based design all objectsattributes and commands fit in a single packet.

    ? November 1999 - After one TF meeting in Germany, it was decidedto completely rewrite the specification using an Object Orientedapproach based loosely on languages like Visual Basic, Visual C#,while preserving the original ISO concepts.

    ? 2000 - Under difficult time constraints the entire document wasredesigned and presented to ISO in about 3 to 4 months.

    ? November 2000 German Agritechnica Limited feature set VTsshown to public. This is the Version 1 VT.

    ? 2001 - Part 6 was accepted, voted on and passed to the IS(international standard) phase. This is the Version 2 VT.

    ? November 2001 - The first ISO plug-fest in Holland proved to be agreat success. VTs proven to be interchangeable.

    ? 2001 Industry embraces ISOBUS

  • 20 May 2009

    Virtual Terminal History

    ? 2005 to 2006 plugfests show increasing stability and success.Problems relate mostly to scaling on various VTs.

    ? 2006 - Due to success of the VT, demands are made for morefeatures initially for Russian character capability and for aredesign of Annex J Auxiliary Controls due to reliability concernsmainly from Deere

    ? 2006 New task force formed. Paul Weisberg (CNH) only returningmember, Dave Smart (Deere) document editor.

    ? 2006 - Task Force decides to go beyond the handful of mandatedchanges and asks ISO committee to dramatically extend thespecification, increasing clarity, closing holes and adding newfeatures. ISO agrees.

  • 20 May 2009

    Virtual Terminal History

    ? 2007 Concerns expressed by industry that the many changescannot be implemented by spring 2009. IGI group requests a splitin the document, creating the Version 3 and Version 4 VT.

    ? 2008 Nearly 200 comments received during ISO voting. Part 6document rejected and new spec is sent back to the experts groupfor review of the comments and more work.

    ? November 2008 Second draft Part 6, which describes V3 and V4VT delivered to ISO.

    ? 2008 dramatic increase in commercially available ISOBUSequipped vehicles and equipment. Plugfest attendance growssignificantly (50-60 people at the Sept 2008 meeting).

    ? Ongoing plugfests continue to prove maturity and stability of thefirst 6 parts of the ISOBUS standard (at least 4 plugfests per year).

    ? April 2009 New part 6 approved with 92% approval rate duringvoting, but 300 comments were received.

  • 20 May 2009

    Virtual Terminal History

    ? May 2009 Comments received (second round) for Part 6 V3/V4.Over 300 comments received but most are editorial. Task force toregroup to address the comments once again.

    ? Goal is FDIS by June 2009, IS by December 2009

    8

  • Dave Smart, JD

    Mike Schmidt, AGCO

    Paul Weisberg, CNH

    May 20, 2009

    ISOBUSVirtual Terminal

    Whats New in V3/V4?

  • Credits

    Development of VT v3, VT v4 wasa significant undertaking withthousands of hours invested

    Input for this work came fromthe ISOBUS world. The updatedspecification was developed byrepresentatives from

    AGCO, AGROCOM, CNH, DICKEY-john, Grimme, John Deere,Mller, Siemens, Spraying Systems, Parker-Vansco, and more

    Special thanks to CNH for donating this presentation

  • 20 May 2009

    Some Virtual Terminal Manufacturers (Many Others)

  • 20 May 2009

    Version History Review

    ? Version 1 VT was the limited feature set implemented forAgritechnica, November 2000.

    ? Version 2 VT was the first released IS (international standard)specification. All VTs in existence in mid-2008 are V2 VTs.

    ? Version 3 includes a new Aux Controls section (Annex J), changesto the VT Status and Working Set Maintenance Messages (AnnexG), VT response message destination (4.6.2), and corrections to theLatin 9 character set (Annex L).

    ? Version 4 includes the complete complement of new features as oflate 2008.

    ? NOTE: A good understanding of the Version 2 VT specification isassumed from this point forward.

  • 20 May 2009

    VT VERSION 3

    VERSION 3

    13

  • 20 May 2009

    VT VERSION 3

    ? Version 3 includes a new Aux Controls section (Annex J), changes to the VT Statusand Working Set Maintenance Messages (Annex G), VT response messagedestination (4.6.2), and corrections to the Latin 9 character set (Annex L).

    ? For simplicity, Version 3 Does NOT include the new Auxiliary Designator ObjectPointer defined in Annex J.

    ? New Aux controls are 100% NON backward compatible. A complete redesign.

    ? Goal is commercial availability spring 2009.

    ? V3 Aux Controls plugfest occurred November 20/21, 2008.

    ? V2 Aux Controls considered obsolete and should not be used.

    ? Problem: Many V2 aux input devices exist in the marketplace that cannot bereprogrammed. VT is allowed to reboot to change personality (V2/V3/V4) but it is notpossible to mix V2 and V3 devices on same bus.

  • 20 May 2009

    Whats New in Version 3

    ? Fundamental shift in the design of Aux Controls. Original wassimple, flexible but allowed the customer to create configurationsthat the manufacturer would avoid. New design is more complex,less-flexible, and appropriately restrictive.

    ? In V2, mappings were stored in VT. In V3, mappings are stored inworking set master ECU.

    ? Preferred Assignments are now the norm and the only way tocommunicate with the VT. The implement ECU can ask formappings of Aux Function to Aux Input without operator assistance.

    ? Operator can overrule mappings and re-assign if implement allows.? Auxiliary Functions can now be deemed critical. Critical functions

    can only be mapped to critical inputs of the correct type.? Auxiliary Functions can be locked operator not allowed to change

    assignment made by implement.? Auxiliary Functions can be single assignment must be only item

    mapped to its input.

  • 20 May 2009

    Whats New in Version 3

    ? V2 spec had 2 types of flexible inputs (boolean and analog). V3spec has 15 very specific input types. Anything outside this listcannot be used as a standard Aux input. List is designed to beextended in the future as new devices arise.

    ? Complex devices like analog and digital joysticks now supported.

  • 20 May 2009

    Whats New in Version 3

    ? New LEARN mode feature? On the VTs mapping screen, select the Aux Function of interest? Press, select or activate the Aux Input you want to map.? Mapping is made for you by the VT

    ? New Model Identification field for Auxiliary Input devices. Thisallows Aux Function owners to select and automatically ask formappings to preferred inputs without involving an operator.

    ? VTs role greatly reduced. It provides the user interface, verifiesand confirms the mappings. Nothing is stored in VT NVM.

  • 20 May 2009

    Whats New in Version 3 VT Response Behavior (4.6.2)

    ? In V2, VT responses to a working setmember command were sent to themaster.

    ? In V3, VT responses are sent back tothe requester.

    ? This is a part 1 requirement that part 6is now overruling.

  • 20 May 2009

    Whats New in Version 3 Status Messages (Annex G)

    ? Working Set Maintenance message is enhanced with the following.? Version of the working set

    So the VT response messages can be sent to the appropriatedestination.

    ? Initiating working set maintenance bitRapid reboots of the working set can now be detected.

    ? VT Status message is enhanced with the following status bits.? Auxiliary controls learn mode active? VT is busy parsing an object pool

  • 20 May 2009

    Whats New in Version 3 Character Sets (Annex L)

    ? Corrections for VT Font Type=1 (ISO 8859-15 Latin 9) character set? 4 characters were incorrectly stated in Version 2

    ASCII(hex)

    VTVersion2 3

    A6 ? A8 ? B4 Z B8 z

  • 20 May 2009

    VT VERSION 4

    VERSION 4

    21

  • 20 May 2009

    VT VERSION 4

    ? VT Version 4 is 100% backward compatible to Version 2 workingset designs except for the new Aux Controls (Annex J).

    ? Dramatic list of new features solving nearly every knownshortcoming in the VT specification.

    ? Many document clarifications added to assist new readers.

    ? Version 4 implements the entire complement of features in the newISO 11783 Part 6 document.

    ? Disappointingly, most existing objects could not be lengthened orenhanced and still be backward compatible. So, most objectsremain untouched.

  • 20 May 2009

    Whats New in Version 4 General

    ? New Command: Get Attribute? The values of all object attributes that have a defined attribute ID

    (AID) can now be queried by the working set.

    ? Relaxed the parent-child relationship restrictions.? V2 was unnecessarily restrictive on which objects could be

    children of other objects. These unnecessary restrictions havebeen removed.

  • 20 May 2009

    Whats New in Version 4 Aux Designator Pointer

    ? Auxiliary Control Designator Object Pointer defined. This objectallows a working set to display auxiliary input and auxiliary functiondesignators in a data mask. Automatic dereferencing to themapped object is supported.

  • 20 May 2009

    Whats New in Version 4 Aux Designator Pointer

    ? It is now possible (and expected) for Aux Input devices to have ahome data mask that shows a picture of the device with allmappings clearly displayed.

  • 20 May 2009

    Whats New in Version 4 Connection Management

    ? Initialization sequence in VT andWorking set has been enhancedand very clearly defined.

    ? Connection management clearlydefined. Working sets can nowquietly remove themselves fromthe VT. Controlled versus uncontrolledshutdown is defined.

    ? Object Pool Transfer and updatingpools at run time is now more clearlydefined.

  • 20 May 2009

    Whats New in Version 4 Overall Look & Feel

    ? New Object: Colour Map ObjectNew Command: Select Colour Map? Used to remap the colour palette for a working set.? Example use could be a night mode with a dark background

    ? New Command: Set object label? Allows working set to set proper names for all objects to aid in

    user inputs and debugging.

    ? New Command: Lock/Unlock mask? Allows for smoother animation and can be used to reduce the

    redraw cycles of the VT.

  • 20 May 2009

    Whats New in Version 4 Multiple VTs

    ? Multiple VTs on the same CAN bus are now supported.? New Command: Identify VT

    VTs can be commanded to identify themselves (like monitorsunder Windows).

    ? VTs are named by their function instance. Function instance canbe set by the operator from a VT setup interface.? VT Number = Function Instance + 1? Operators are less familiar with zero-based numbers

    ? Working Sets must support the ability tojump or move from one VT to another.

  • 20 May 2009

    Whats New in Version 4 User Defined Layout

    ? Windows from multiple working sets can be combined by theoperator onto the VTs User Layout Data Masks.

    ? Clever display designs can also use windows from working sets innon-VT areas.

  • 20 May 2009

    Whats New in Version 4 User Defined Layout

    ? New Object: Window Mask? Used on VTs User Layout Data Masks to mix data from multiple

    working sets. Predefined (standard) window formats aresupported as well as Type 0 Free Form window.

    ? New Object: Key Group Object? Used for user-defined Soft Key layouts on the User Layout Soft

    key masks that go with the User Layout Data Masks.

    ? New VT message: On User Layout Hide/Show? Informs working set of what windows and key groups are on

    screen even though the working set does not own the activemask.

  • 20 May 2009

    Whats New in Version 4 Soft Keys

    ? All VTs must now support at least 6 physical soft keys.? All VTs must now support exactly 64 virtual soft keys.? Navigation among and between soft keys is now clearly defined.

  • 20 May 2009

    Whats New in Version 4 Input and Navigation

    ? New Real Time Data Input Option? Number and List inputs can now be designated as real-time or

    live. Changes are immediately sent to the working set andcannot be undone with ESC.

    ? Editing and navigation states are now clearly defined andenhanced.

    ? Operator input and navigation was not precisely defined in V2. V4now includes a large section describing operator inputs, editing,navigation, focus, etc.

    ? Multiple press points and sliding now supported on capable touchscreens.

    ? Input objects now DO NOT draw a border. In V2 implementations,some VTs did, some VTs did not.

  • 20 May 2009

    Whats New in Version 4 Text

    ? The handling of text has been simplified.? The backspace (BS) character has been removed.? Handling of (CR) and (LF) characters is now clearly defined.? Rendering of text objects was not precisely defined in V2 and

    causes most of the headaches at plugfests. V4 now clearly defineshow text is to be rendered with many examples.

    ? Text justification is now pixel-based (not character-based). Bothhorizontal and vertical justification is now possible.

    ? Text objects can now wrap on soft or hard hyphens or this behaviorcan be turned off completely.

    ? New Object: Enhanced Input Attributes? Used for input string object to specify valid / invalid characters

    especially when UNICODE is used.

  • 20 May 2009

    TnanThank youSalamatKiitosMerciGrazasDanke?? ???????????????????????????????

    Whats New in Version 4 Character Sets / Fonts

    Faleminderit????????????????Grcies???Hvala??kujeme vmTakBedankt

    KsznmTerima kasihGrazie?????Paldies????GrazziTakkDzi?kuj?Obrigado

    Mul?umesc?????????????akujeme vmHvalaGraciasTack??????Te?ekkrler??? ?n b?n

    ? 5 new required ASCII character sets defined (now a total of 7).? UNICODE is now optionally supported on VTs.? Proportional fonts are now supported but are optional.

  • 20 May 2009

    Whats New in Version 4 Numbers

    ? Numeric object Blank as Zero is now clearly defined.A Value of exactly zero, displays blanks.

    ? Numbers can now be truncated or rounded working sets choice.

    ? All numeric ranges in VT v2 have been corrected.

  • 20 May 2009

    Whats New in Version 4 Lists

    ? New Object: Output List? Similar to input list but cannot be activated for editing.

    ? Input List behavior has been clarified when the list index is invalid.

  • 20 May 2009

    Whats New in Version 4 Line Drawing

    ? Rectangle line suppression is now clearly defined.? Line art is now clearly defined.

    W W W W

    W W W W

    WW

    a) no suppression b) top suppressed c) right suppressed d) top & right suppressed

    e) top, right & bottom suppressed f) top & bottom suppressed g) right & left suppressed h) All Suppressed

    j) no suppressionbi) no suppressiona

  • 20 May 2009

    Whats New in Version 4 Button Drawing

    ? Button object has been improved greatly while still remainingbackward compatible.? Ability to show or not show the border? Ability to use or not use the border area for child objects? Current state can be defined and changed? Can be transparent? Can now be disabled like other inputs

    ? Creative items like radio buttons can now be implemented.

  • 20 May 2009

    Whats New in Version 4 Polygons

    ? New Command: Change Polygon Scale? Polygons can now be scaled after the object pool has been

    loaded.

    ? New Command: Change Polygon Point? Polygon points can now be changed at run-time.

  • 20 May 2009

    Whats New in Version 4 Graphics

    ? New Object: Graphics Context Object? Very powerful object that allows real-time drawing on the VT.

    Uses a limited drawing-command set.? Allows simple mapping applications including precision farming

    to be done on the VT.? Panning and zooming are supported in this object.? VT does all the work.

    ? New Command:Graphics ContextCommand set

  • 20 May 2009

    Whats New in Version 4 Audio

    ? Control Audio Device command is now more clearly defined.

    ? New VT message: Control Audio Termination? Inform the working set when an audio command is complete and

    has been heard by the operator or aborted.

  • 20 May 2009

    Whats New in Version 4 Macros

    ? New Command: Execute Macro? This is a powerful command that allows the working set to

    execute any macro (sequence of commands).