Some data, such as wind speed or metered rates of seeding, changes frequently.
Frequently changing data is logged in the *.fdd file. This file is in binary format.
When any of these data items changes, the *.fdd file is updated with the change event information. The following sections display the data considered to be frequently
changing by the GS2 (RCD) system.
Setup Info
Temperature
Wind Speed
Wind Direction
Sky Condition
Humidity
Soil Moisture
Soil Temperature
Planting/Seeding Operation
Seed Depth
Seeding Application Method
Target Rates
Measured Rates
Metered Rates
Control Rates Product Application Operation
Application Height
Application Method
Target Rates
Measured Rates
Metered Rates
Control Rates Tillage Operation
Tillage Depth Other Operation
(as defined and added by operator) Harvest Combine Operation
Mass Flow Rates
Moisture Rates Harvest Cotton Operation
Mass Flow Rates Harvest SPFH Operation
Mass Flow Rates
Moisture Rates
Inoculant Rates
Fuel Rates
Length of Cut Rates
8 Sample EIC Applications
This version of the EIC SDK provides code files for several example applications.
Example GSD4 and GS2 applications are found in the solution
\Samples\SampleApps.sln. Refer to the following table for a description of these applications.
Table 14 Sample EIC Applications Application
Type
Application Name Description
Common Diagrams Contains the UML diagrams for the classes/interfaces located in JohnDeere.EIC.Models.dll.
SampleCPlusPlus Demonstrates how to create an EIC application using Visual C++.
SampleGUI Demonstrates how the EIC SDK may be used to create a simple GUI application with a tree browser.
SampleVB Demonstrates how to create an EIC application using Visual Basic .NET.
GSD4 SampleImport Demonstrates how to import the various GSD4 streams.
Once the streams are imported, the data is exported to a .csv file for inspection purposes.
SamplePrescription Demonstrates how to create and export a GSD4 prescription file.
SampleSetup Demonstrates how to create and export a GSD4 setup file.
SampleStreams Demonstrates how to interact with all the GSD4 target streams.
GS2 SampleBoundary Demonstrates how to set up boundary data within the RCD field import/export stream. This data is then exported to the card.
SampleFlags Demonstrates how to create a flag layer and export it to the card.
SampleFuelDiary Demonstrates how to read information from a fuel diary stream stored on the card.
SampleGuidance Demonstrates how to create guidance data and export it to the card.
SampleJob Demonstrates how to create multiple jobs and export them to the card.
SampleLog Demonstrates how to import log files and extract spatial information from them.
SamplePrescription Demonstrates how to setup a seeding and/or application prescription layer and export it to the card.
Application Type
Application Name Description
SampleProductDetails Demonstrates how to specify product details for
chemicals, fertilizers and crop varieties in the setup file.
SampleReferenceLayer Demonstrates how to send an aerial image to the card.
SampleRxConverter Demonstrates how to convert industry standard shape files containing prescription information into a RCD prescription file.
SampleSetup Demonstrates how to create a master setup file and export it to the card.
SampleStreams Demonstrates how to interact with all the GS2 target streams.
SampleSWM Demonstrates how to read and write surface water management data.
SampleTankFillCalculator Demonstrates how to specify a tank mix template in the setup file as well as read information from a tank-fill calculator session file stored on the card.
SampleTankMix Demonstrates how create a tank mix and export it to the card.
SampleTask Demonstrates how to set up a simple task and export it to the card.
SampleTotals Demonstrates the implementation of calculations detailed in the document titled John Deere GreenStar 2 Totals Formulas.pdf.
SampleTransportLog Demonstrates how to specify a transport task in the setup file and also how to read information from a transport session log file stored on the card.
SampleVarietyLocator Demonstrates how to obtain crop variety information.
GS2 1800 SampleModelFactory Demonstrates how to use the GS3BmodelFactory class to support the GS2 1800 display.
GS3 2630 SampleModelFactory Demonstrates how to use the GS3modelFactory class to support the GS3 2630 display.
APPENDIX A: EIC Compatibility with Previous John Deere Data Formats
The following sections discuss backward-write and backward-read compatibility with previous John Deere data.
Backward Read Compatibility
EIC supports the ability to read and write earlier versions of specific GreenStar display-formatted data. As a consequence, EIC developers can test applications that utilize an earlier version of the EIC API without being required to wait for the latest GreenStar display software system release.
You can access data from any earlier version of John Deere GreenStar display software when using this version of the EIC SDK. The figure below demonstrates how EIC
accomplishes this task.
EIC-enabled Application
Models.dll
ModelsImpl.dll (version 3.4)
GS2 (all earlier versions)
Figure 12 : Illustration of EIC accessing earlier versions of GreenStar display data
Backward Write Compatibility
The EIC SDK is able to produce data that can be read by an earlier version of the
GreenStar display software. The figure below demonstrates how EIC handles this task.
Figure 13 EIC backward-write compatibility across minor versions
While an EIC developer will usually link an application to the latest version of the EIC API libraries, this version of the EIC API loads the required version of the EIC libraries
into an application domain. The data will then be converted to a binary format and serialized across the application domain boundary.
Then when an older version of the EIC SDK library receives the binary data, the older version will de-serialize the raw data into its own data structures. Any raw data that does not fit the older data structure is disregarded. The older version of the library then will serialize the data and create data files that are compliant with the older version of the GreenStar display software. In this way, the developer does not have to write
applications for each version of the EIC.
Important: Backward write compatibility is only supported across minor versions of the EIC SDK.
Backward Write Support for Setup Files
The EIC SDK enables you to write setup files for use by previous minor versions of EIC.
To accommodate this functionality, three new interface methods have be en added to the
JohnDeere.EIC.Models.IExport interface:
Export(BackwardCompatibilityInfo info)
Export(BackwardCompatibilityInfo info, bool merge)
Export(BackwardCompatibilityInfo info, bool merge, bool validate)
Global Version File
EIC uses a file named global.ver to determine whether RCD data can be read from or written to the data card. This file is located at the root directory of the RCD card path.
EIC App
Models
ModelsImpl v3.4)
ModelsImpl v3.0)
ModelsImpl v3.2)
ModelsImpl v3.3)
GS2 v1.0)
GS2 v1.2)
GS2 v1.3)
During initialization, EIC compares the global version number stored in the global.ver
file to the global version internally stored in the EIC libraries. This internal global version number represents the highest version of the data structures in the RCD card that the current EIC libraries can utilize. If the version number on the data card is greater than the version number stored within EIC, then an exception will be thrown to prevent the application reading from or writing to the data card.
If the global.ver file does not exist in the root data directory of the card, EIC will not throw an exception. This behavior allows applications to archive the card data and then read it back again without problems. The global.ver file is used primarily by the display libraries to minimize the amount of I/O overhead.
Note: If your application accesses a data card that lacks a global version file, the EIC libraries create one, and assumes that the data is compatible with the current version.
APPENDIX B: Crop List
The following table displays the crop names and crop IDs for both the GSD4 and GS2 systems. It is not possible to add crops to this list unless explicitly approved by John Deere.
The table also displays which crops are displayed in European displays for various combines used in Europe, including the LYNX combine
The Default Active and Default Inactive columns display which crops Apex uses by default during data card setup for European customers. Standard inactive means that the desktop software, such as Apex, does not add these crops by default during setup.
Note: means crop is supported in the monitor.
Table 15 EIC Crop List
GSD4
GSD4
Rape Seed (E Ind)
GSD4
Rape Seed (E Oil) 57 54 Cabbage-lettuce 58 55 Caraway seed 59 56 Carrots
60 57 Castor beans 61 58 Cauliflower 62 59 Celery 72 69 Digitalis lanate 73 70 Dill
74 71 Elephant-grass 75 72 Endives
GSD4 95 92 Italian rye-grass
96 93
104 101 Mushrooms 105 102 Onions 111 108 Potatoes sweet 112 109
Potatoes for chips
113 110 Potatoes for
GSD4 116 113 Radicchio 117 114 Raddice
125 122 Savoy cabbage 126 123 Scorzonera 127 124 Seed potatoes 128 125 Sesame
129 126 Shallots 130 127 Silver Onions 131 128 Spear grass 132 129 Spinach 133 130 Strawberries 134 131 Stubbel tuber 135 132 Sugarbeet 136 133 Sugar cane 137 134 Sugar corn 138 135 Tankard turnip 139 136 Tick beans 140 137 Tobacco 141 138 Tomatoes 142 139 Tuber fennel 143 140 Turnip cabbage 144 141
Turnip-rooted celery
145 142 Vetch
146 143 White beans 147 144 White cabbage
GSD4 Tag ID
GS2 ID
Crop Name (en)
Harvest Monitor:
Combine EUR
Harvest Monitor:
SPFH
Combine Yield Monitor
EUR
Harvest Monitor:
LYNX combine
Default Active (Europe)
Default Inactive (Europe)
148 145 Wood carrot 149 146 Set aside
150 No Crop present
151 147 Hyracinth 152 148 Tulip 153 149 Narcissus 154 150 Gladiolus 155 151 Crocus 156 152 Lily 157 153 Iris 158 154 Dahlia 159 155 Apples 160 156 Pears 161 157 Peaches 162 158 Apricots 163 159 Melons tree 164 160 Oranges 165 161 Lemons 166 162 Almonds 167 163 Vines 168 164 Olives 169 165 Jalapeño 170 166 Cantaloupe 171 167 Honeydew 172 168 Squash 173 169 Green Beans 174 170 Lima Beans 175 171 Sweet Corn 176 172 Canary Seed
APPENDIX C: Supported Encodings
Both the GSD and RCD displays are currently restricted to single byte character codes.
However, the RCD system allows character codes in the range 0x00 - 0xFF while the GSD system only allows characters within the ASCII character set (0x00 – 0x7E).
Note: The GSD4 display only supports characters in the ASCII character set while the GS2 display utilizes code pages to support multiple languages.
Neither the GSD4 nor the GS2 displays support the Unicode character set at this time.
R CD Languag e Support
The GreenStar 2 displays support multiple languages through the use of code pages. A code page is the term used when a sequence of bits, usually a single octet representing integer values 0 through 255, is associated with a specific character. A full list of the supported languages on the RCD display and their respective code pages is shown below.
Table 16 RCD Language Support
Language 2-Letter Code Encoding Used on Display
Bulgarian bg ISO-8859-5
Croatian hr ISO-8859-2
Czech cs ISO-8859-2
Danish da ISO-8859-1
Dutch nl ISO-8859-1
English en ISO-8859-1
Estonian et ISO-8859-15
Finnish fi ISO-8859-1
French fr ISO-8859-1
German de ISO-8859-1
Greek el ISO-8859-7
Hungarian hu ISO-8859-2
Italian It ISO-8859-1
Latvian lv ISO-8859-4
Lithuanian lt ISO-8859-4
Norwegian no ISO-8859-1
Polish pl ISO-8859-2
Portuguese pt ISO-8859-1
Romanian ro ISO-8859-2
Russian ru ISO-8859-5
Slovak sk ISO-8859-2
Spanish es ISO-8859-1
Swedish sv ISO-8859-1
Turkish tr ISO-8859-9
EIC always writes RCD string data files to the data card using a UTF-8 encoding. This allows any character to be transferred properly to the RCD display with no loss of information. Keep in mind, however, that an RCD display can read a UTF-8 encoded data file, but it will write data files using the code page stored in the system settings. For
example, if an RCD display is set to the English language, it will read a UTF-8 setup file produced by EIC, but write it back to the data card using the ISO-8859-1 encoding.
Note: This type of situation increases the potential for data loss. For example, if you save a Russian setup to your card using EIC with a UTF-8 encoding, the GS2 will read the file without any problem.
But a problem may occur if the language setting on the GS2 console is set to a language different than Russian. If the console is set to English, then the setup will be written back to the card using ISO-8859-1 encoding. This would cause all the Cyrillic characters to be changed to a corresponding character on the ISO-8859-1 code page.
Below is displayed a matrix showing the characters that are common to all code pages.
This common character set is often referred to as the ASCII character set. The matrix shows which characters are allowed on the RCD display.
Table 16 RCD Base Character Matrix
0 1 2 3 4 5 6 7 8 9 A B C D E F
0 nd nd nd nd nd nd nd nd nd tab lf nd nd cr nd nd 1 nd nd nd nd nd nd nd nd nd nd nd nd nd nd nd nd
2 spc ! " # $ % & ' ( ) * + , - . /
3 0 1 2 3 4 5 6 7 8 9 : ; < = > ?
4 @ A B C D E F G H I J K L M N O
5 P Q R S T U V W X Y Z [ \ ] ^ _
6 ` a b c d e f g h i j k l m n o
7 p q r s t u v w x y z { | } ~ nd
Allowed character These characters are always allowed.
Non displayable character These characters are non displayable on most systems and are not allowed for entry in the GSD4 or RCD systems.
Allowed special character These are non-alphabetic special characters that will be allowed in the GSD4 or RCD systems.
space Space allowed except at the beginning and end of a name.
non breaking space Non breaking space (not allowed) which is replaced with a space instead of underscore.
Avoid use These characters are frequently used and have special meaning in some file formats and systems.
Names for items such as farms, fields, varieties, fertilizers, etc. are limited to 20
characters within the RCD system and must be at least 1 character in length. Names must not start with or end with a white space character. White space characters are spaces, tabs, carriage returns, line feeds, or other non printable ASCII escape
characters. The following matrix details the allowed and disallowed characters.
The items listed below are represented as System.String objects within the EIC SDK.
These strings are bound to the character rules described above.
Load (when using custom)
Lot
Module ID
Prescription Name
Reference Layer Name
Job Name
Field Name
Task Template Name
Fertilizer Type Name
Fertilizer Name
Chemical Type Name
Chemical Name
Headland Name
Tank Mix Name
Crop Variety Name
Crop Name
Machine Type Name
Implement Type Name
Machine Name
Implement Name
Flag Name
Client Name
Operator Name
Farm Name
Brand Name
A/B Line Name
Circle Name
Unit of measure name and label (exception: composites such as lb/ac will allow “/”. Also,
composite names and labels may be greater than 20 characters).
<All user-defined type names>
o Tillage Type Name
o Seeding Tillage Practice Name
o Other Type Name
o Residue Management Type Name
o Load Destination Name
o Load Cart Name
<All defined type names>
o Application Method (dtApplicationMethod)
o Cotton Load
(dtCottonLoadType)
o Hitch Type (dtHitchType)
o Load Type (dtLoadType)
o Sky Condition (dtSkyCondition)
o Soil Moisture (dtSoilMoisture)
o Wind direction (dtWindDirection)
APPENDIX D: Unit and Representation System
The diagnostics utility (DiagnosticsUI.exe) that is packaged with the EIC SDK contains browsers for viewing John Deere’s representation system and unit system data
structures.
To open these browsers:
1. Run DiagnosticsUI.exe 2. ClickView on the menu bar
3. Select Representation System to view the representation system data structures.
Figure 14 Representation System Browser
4. Select Unit Systemfrom the same menu item to view the unit system data structures.
Figure 15 Unit System Browser
APPENDIX E: RCD Out of Box Types
The following table displays the Out-of-Box types that can be created with the RCD model factory. Included are the unique ID (a System.Guid object) of each type and the reference ID, used on Original GreenStar John Deere systems and sometimes referred to as the legacy ID. The GSD4 uses the reference ID.
These Out-of-Box creators, part of the
JohnDeere.EIC.ModelsImpl.Factories.GS2ModelFactory class, have a name creation pattern of CreateOutOfBoxXXX () where XXX is the type of object being created.
Table 17 RCD OOB Types
Method Enum Type Return Type ID Ref
ID*
CreateOutOfBoxChemical
Water IChemical
{53B03C91-D9E8- 4d8e-A6DC-7E7AC43B8E87}
n/a
DryFertilizer IChemical
{543A57C7-BD74- 44A0-A240-8733C4D6410F}
n/a
LiquidFertilizer IChemical
{F35B7F67-8C59- 4303-BB41-28E84BEE80CD}
n/a
WaterAndFertilizer IChemical
{FD859B30-20FA- 41DC-A449-CF71EAD27E99}
n/a
Solution_10_34_0 IChemical
{44D91E7A-3409- 4DFD-877A-C250305093B0}
n/a
UAN_28_0_0 IChemical
{DF4C35D6-C44B- 4815-BEF9-1B5904B4A842}
n/a
UAN_32_0_0 IChemical
{E767C7D2-AC9E- 4059-8F23-34EA76509ED2}
n/a CreateOutOfBoxChemical
Type Additive IChemicalType
{CDD99744-8A85- 4215-8756-215A45A554C8}
n/a
Carrier IChemicalType
{3C6CB8E5-3416- 40DA-AE1F-E683A028AC0E}
n/a
Fungicide IChemicalType
{7C1D277E-C1B0- 4a76-94E1- AC53A630F4B1}
n/a
GrowthRegulator IChemicalType
{E443333A-E60B- 4363-87F8- ACC7FCD4ECA5}
n/a
Herbicide IChemicalType
{CA0687E8-8C87- 4bac-8F65-20B124B82A70}
n/a
Insecticide IChemicalType
{FB436E9C-2B11- 43b4-8FE8- A5E69CD4BD44}
n/a
NitrogenStabilizer IChemicalType
{077DF20C-74E9- 43e4-A9FC-E3C666CAE578}
n/a CreateOutOfBox Conditioning IUserDefinedType {C1E7103D-2EE2- n/a
Method Enum Type Return Type ID Ref ID*
ConditioningType
4781-BD3C-0BC3F647905B}
CreateOutOfBox
FertilizerType Fertilizer IFertilizerType
{FD2BFE9D-51C6- 46F4-98EF-D2A02D7859EA}
n/a
Manure IFertilizerType
{EB2BE46E-8876- 44D4-9A05-5E2E874A8598}
n/a CreateOutOfBoxFlags
Rocks IFlag
{688C20BB-9609- 4590-95C9-649BA65C06DF}
n/a
Weeds IFlag
{186B9781-04E3- 4c8a-A872-FE9FA1493914}
n/a CreateOutOfBoxImplement
Model Dry_Spreader_DN345 IImplementModel
{8FC4655DE879 - 4D70-AA72-5847C61A9461}
n/a
Pickup_630 IImplementModel
{FE8204D8-AB46- 4A1C-A502-E6D6BF6472F7}
n/a
Pickup_640 IImplementModel
{D28A788E-A110- 4608-8850- ABED7C92D658}
n/a
Pickup_645 IImplementModel
{6A743D49-2438- 4153-AE32-7F2AE8D06AB1}
n/a
Planter_ 1111 IImplementModel
{F52565BE-C560- 468A-A30B-93E16BF4521A}
n/a
Planter_ 1113 IImplementModel
{BFD14398-11DE- 4A26-8F68-D1C0A938DAB5}
n/a
Planter _1770NT IImplementModel
{D143FCA4-BAD0- 4281-B53E-8F93BECD1230}
n/a
Planter_1790 IImplementModel
{7E99E14B-8929- 4E6E-9C2B-19CB9D904083}
n/a
Planter_2117 IImplementModel
{4F23ED27-7919- 45FE-98C2-C35C9E12A173}
n/a
Planter_2122 IImplementModel
{3EEB3C1F-3858- 435F-8386-9C40C708C74D}
n/a
Planter_DB44 IImplementModel
{627C6389-07C4- 43C4-AA5F-77BB56B36240}
n/a
Row Independent_345 IImplementModel
{248B70B4-3C2B- 4051-8669-8E6FAD8F7D91}
n/a
Row Independent_770 IimplementModel
{D071A985-9867- 488B-A92B-B1C02DB8F222}
n/a
Row Independent_678 IimplementModel
{26F24D37-A51B- 4658-98CB-B2ED7E514B2C}
n/a
Row Independent_676 IimplementModel
{61D95C1E-BFF3- 4F57-9125-C7DE3BA8399B}
n/a
Method Enum Type Return Type ID Ref ID*
Row Independent_710 IimplementModel
{3B2767AE-6EEF- 45D8-8002-020C6092F12B}
n/a
Row Independent_688 IimplementModel
{EE235EC3-7E08- 42EC-AE70-DF0BCAC6F505}
n/a
Row Independent_686 IimplementModel
{AF0C55C9-7A27- 4EE2-91A7-4662B520C9E1}
n/a
Row Independent_475 IimplementModel
{61543E12-BA91-
460B-9907-01E8C11918A0}
n/a
Row Independent_460 IimplementModel
{36B029C8-BCDE- 4850-818D-80471E60B03C}
n/a
Row Independent_445 IimplementModel
{0885BAFA-CE83- 499F-B154-1487CFD758E8}
n/a
Row Independent_390 IimplementModel
{BC252A49-2081- 4EE9-847F- A5A54E95A2B4}
n/a
Row Independent_375 IimplementModel
{2612DB4E-0C01- 4EA3-A45E-777140DB5824}
n/a
Row Independent_360 IimplementModel
{CD6AF416-A1C4- 4AA2-9620-CA3214A3B981}
n/a
RowUnits_35xxT IimplementModel
{F9279813-3D3A- 4B66-ABC6-B532CBEA4076}
n/a
RowUnits_ 35x2 IimplementModel
{614669B8-D7B8- 463B-947F-003A3FCDCCA7}
n/a
RowUnits_748Header IimplementModel
{42E2C573-ABB7- 4C05-A087-B14799A7105E}
n/a
RowUnits_ProSeries IimplementModel
{3C6881C6-CA37- 4401-A5C6-8338C0498A4E}
n/a
Seeder_1890_1990 IImplementModel
Tillage_ChiselPlow IImplementModel
{90C0810F-F492- 485B-8CE3-179A8BE45FBE}
n/a
Tillage_Disk IImplementModel
{0CBBE717-9AE4- 4F99-BF63-80A33F5EF24D}
n/a CreateOutOfBoxImplement
Type AirCart IImplementType
{66C0D7AE-A13F-4184-B6C8- 2
Method Enum Type Return Type ID Ref ID*
FC33FF9CCA54}
Baler IImplementType
{BC43B404-CC50- 41BF-9C44- A675545F72A1}
30
BeltPickup IImplementType
{D3C71163-9E1F- 44DB-842D-6E91E2936A2E}
10
Boom IImplementType
{242A1D81-254D- 4223-BD76- ABD3C330F2FC}
3
Cart IImplementType
{643E2308-7C81- 4078-9B28- AF60A4C4D9D9}
23
Chopping Corn Head IImplementType
{C2CEAC69-F304- 4496-A09B-C623174524FF}
24
CornHead IImplementType
{D9D1C11F-35E0- 43AF-84AE-696D9EA3C18B}
8
Draper IImplementType
{D649E05F-E784- 42E8-AC90-498077D9B5DC}
11
DrySpreader IImplementType
{1E187F19-658C- 4168-93FA- A1BD4CF86424}
5
Flex Platform IImplementType
{567D155D-8A20- 4955-90D9-E1698AAFACBA}
27
Flexible Draper IImplementType
{12FEED97-18C3- 430F-B20A-C0E20AF914DA}
26
GrainDrill IImplementType
{F786C5C1-969D- 45B6-8719-F2FBA4CE1C53}
6
Hydraflex Platform IImplementType
{247A0ADA-8F4A- 4CCA-9A57-FFBC8ED83C26}
28
RotaryDitcher IImplementType
{42B8651C-589B- 446C-8BFF- A5D8056CB9F8}
20
RowCrop IImplementType
{D2B57F21-0410- 4A57-91B5-5F81C1189465}
9
RowDependent IImplementType
{7554E347-51F5- 4656-9A00-17ACB231DF83}
13
RowUnits IImplementType
RowIndependent Implement Type
{06BE888A-A8DB- 480F-B6CB-196418EEEA68}
14
Pickup Implement Type
{F2FDE3E1-5E6C- 4FC9-94A4-4B99C3E2548E}
15 NH3Tool IImplementType {001A5C0F-6F9A- 18
Method Enum Type Return Type ID Ref ID*
4EE9-B885-C8EC9766BB40}
Other IImplementType
{BCB321B9-521D- 4761-9E64-F59816A2AB6B}
22
Planter IImplementType
{DA444C99-A25F- 4A8E-99B0-925B4071C601}
1
Platform IImplementType
{80B8206E-5094- 4A3B-88EA-E2F775F41BA1}
12
Scraper IImplementType
{5373B15D-7366- 4305-AE7D-9392F05B4B08}
21
Seeder IImplementType
{C19852E3-5ACD- 43BD-AA6F-8E536CE55275}
19
Pull Behind Sprayer IImplementType
{A29FB2E7-C75D- 4521-91FA-C9A4311C5F53}
4
Rigid Platform IImplementType
{B46BDFD3-BEA1- 44B2-BA4A-3B59014CA297}
25
Tillage IImplementType
{CD805CAF-9B07- 4943-8DDB-4D46FE4A306A}
7
Unknown Head IImplementType
{392661EF-7AD2- 46FC-ACA8-1786E2C839A0}
29 CreateOutOfBoxLoadCart
Type IUserDefinedType
{DB4F1D89-8A19- 4D02-A821-1DB3926502C4}
n/a CreateOutOfBoxLoadCart
TypeInstance Truck IuserDefinedType
Instance
Model CaneHarvester_35xxT IMachineModel
CottonPicker_7X60 IMachineModel
{554480F4-7286- 41F7-BACD-7972C7DFCDCC}
n/a
CottonPicker_99xx IMachineModel
{92A7FBDD-1A20- 429B-A20F-05E805037707}
n/a
Combine_SXXX IMachineModel
{D7DCA058-F7C6- 4C4C-A606-9745A6AC1ABE}
n/a
Combine_TXXX IMachineModel
{854A238D-3625-4C5F-BFD2- n/a
Method Enum Type Return Type ID Ref ID*
8D38F67546C5}
Combine_WXXX IMachineModel
Tractor_6x30 IMachineModel
Tractor_6xxxR IMachineModel
{54BFC1F4-D4C1- 4288-A260-0D85186D9BE6}
n/a
Tractor_7x30 IMachineModel
{80BC222D-4DEE- 4BB1-897F-0AF6E9AE2E9E}
n/a
Tractor_7xxxJ IMachineModel
{D29B6028-C49C- 4CC1-AFFB-BD36158706D1}
n/a
Tractor_7xxxR IMachineModel
{E1348933-38AC- 4387-83A4-C3E216359E43}
n/a
Tractor_8x30 IMachineModel
{B7812809-AA6E- 4149-B7CA-5DCBD8C77CAF}
n/a
Tractor_8x30T IMachineModel
{0A96ED5A-CA67- 4501-BA28-6AB6E45773CC}
n/a
Tractor_9x30 IMachineModel
{05928C56-9BB3- 464D-8FEE-67205DED3C6B}
n/a
Tractor_9x30T IMachineModel
{5C3CAB35-9829- 42FE-932F-5C8B3331A8E4}
n/a
Tractor_9xxxR IMachineModel
{8F85C6AC-2948- 4AD0-A9E9-54B81C108234}
n/a
Tractor_9xxxRT IMachineModel
{99B0A31A-914D- 47E3-A461-2355C14A83DA}
n/a
Tractor_8xxxR IMachineModel
{1EB2EF7A-74D3- 42FE-9B52- AFA6A88E4163}
n/a
Tractor_8xxxRT IMachineModel
{BE207158-932A- 4B6C-8BD7-C42954227CA4}
n/a CreateOutOfBoxMachineType
CaneHarvester IMachineType
{4086ADBF-7255- 44E0-81BA-71194737FB7C}
10
Combine IMachineType
{D8DCE5B0-
CC8D-4C34-AFAC-27D93793BD86}
3
Method Enum Type Return Type ID Ref ID*
CottonPicker IMachineType
{574705BC-C7D5- 4A07-9501-5515D02268EC}
5
CottonStripper IMachineType
{5758B5FD-F224- 4344-BFAE-C219631F1006}
6
Other IMachineType
{502355A9-53FA- 4B08-99E6-EC1F5AEFAB31}
9
PickupTruck IMachineType
{54020EBB-DEF8- 4F36-8A0C-6F713A3F9868}
8
SPFH IMachineType
{99EDF0E0-4ABB- 42D3-9798-327439A39C38}
4
Sprayer IMachineType
{6CF945EC-9E62- 4BCC-A402-41D917BD906C}
2
Tractor IMachineType
Tractor IMachineType