Presentation is loading. Please wait.

Presentation is loading. Please wait.

ISO 11783 Task Controller Lecture 9 Task Controller – Part 3 ISO 11783 Part 10 BAE 5030 - 353 Spring 2009 Instructor: Marvin Stone Biosystems and Agricultural.

Similar presentations


Presentation on theme: "ISO 11783 Task Controller Lecture 9 Task Controller – Part 3 ISO 11783 Part 10 BAE 5030 - 353 Spring 2009 Instructor: Marvin Stone Biosystems and Agricultural."— Presentation transcript:

1 ISO Task Controller Lecture 9 Task Controller – Part 3 ISO Part 10 BAE Spring 2009 Instructor: Marvin Stone Biosystems and Agricultural Engineering Oklahoma State University April 6, 2009BAE

2 FMIS to MICS to FMIS communication FMIS -> MICS communication and back is based on data transfer files –XML data transfer files Formatted as XML version 1.0 and coded in UTF-8 –Optional binary-coded data files for: gridcell definitions logged process data –All files are in the same directory. –Coding data and task data stored in the same set of XML files upon transmission from FMIS to the MICS. During processing of tasks by the task controller, these files are likely to be modified and, when tasks are finished, can be transferred back to the FMIS. April 6, 2009BAE

3 Origination and modification of Task Data Modified Task Data are added to the Taskdata file by the MICS (Task Controller and transported back to the desktop April 6, 2009BAE

4 Main XML coded data transfer file Case sensitive names File Name –TASKDATA.XML Root element –ISO 11783_TaskData Recommended location –in a directory named “TASKDATA” Structure example: April 6, 2009BAE

5 Prescription transfer FMIS to MICS April 6, 2009BAE

6 Log file transfer from MICS to FMIS April 6, 2009BAE CTR = Customer

7 XML element types and acronyms Examples: April 6, 2009BAE XML element designator Coding dataXML element name AllocationStampASP CodedCommentXCCT CodedCommentGroupXCCG CodedCommentListValueXCCL ColourLegendXCLD ColourRangeXCRG CommentAllocationCAN ConnectionCNN CropTypeXCTP CropVarietyXCVT CulturalPracticeXCPC CustomerXCTR DataLogTriggerDLT DataLogValueDLV

8 XML element example (ASP) The AllocationStamp XML element specifies a recording of an allocation event. April 6, 2009BAE Example: PTN = Position Attributes Attribut e XM L UseTypeLength/Rang e Comment StartAoxs:datetimeMax. 19Time of start. Format: yyyy-mm-ddThh:mm:ss StopBoxs:datetimeMax. 19Time of end. Format: yyyy-mm-ddThh:mm:ss Duratio n Coxs:unsignedLo ng 0..( )Time between start and stop in number of second TypeDrxs:NMTOKEN1,4Type of the AllocationStamp, possible values: 1 = Planned 4 = Effective Positiono xs:element Includes a single XML element Position

9 Task File data structure April 6, 2009BAE Tutorial on ERDs

10 Device Description within Task Data April 6, 2009BAE DVC – Device DET – DeviceElement DOR – DeviceObjectReference DPT – DeviceProperty DPD – DeviceProcessData DVP – DeviceValuePresentation

11 Relationship among XML elements April 6, 2009BAE

12 Relationship among XML elements - Task April 6, 2009BAE

13 FMIS to MICS to FMIS communication Features Define a Task on the desktop (FMIS) –Includes both Coding data and Task Data –May include spatial prescriptions Encode this information in an standard XML format for use at the Task Controller –Will result in a “TASKDATA.XML” File(s) May include associated binary files Insert the “As acquired” Task Data during the task with the mobile system (MICS) –Will result in an amended “TASKDATA.XML” File(s) May include associated binary files April 6, 2009BAE


Download ppt "ISO 11783 Task Controller Lecture 9 Task Controller – Part 3 ISO 11783 Part 10 BAE 5030 - 353 Spring 2009 Instructor: Marvin Stone Biosystems and Agricultural."

Similar presentations


Ads by Google