1 / 13

ISO 11783 Task Controller

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 Engineering Oklahoma State University. FMIS to MICS to FMIS communication.

nayef
Download Presentation

ISO 11783 Task Controller

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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 Engineering Oklahoma State University BAE 5030-353

  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. BAE 5030-353

  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 BAE 5030-353

  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: <?xml version="1.0" encoding="UTF-8"?> <ISO11783_TaskData VersionMajor="..." VersionMinor="..." TaskControllerManufacturer="..." TaskControllerVersion="..." ManagementSoftwareManufacturer="..." ManagementSoftwareVersion="...“ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="… " DataTransferOrigin="..."> </ISO11783_TaskData> BAE 5030-353

  5. Prescription transfer FMIS to MICS BAE 5030-353

  6. Log file transfer from MICS to FMIS CTR = Customer BAE 5030-353

  7. XML element types and acronyms • Examples: BAE 5030-353

  8. XML element example (ASP) • The AllocationStamp XML element specifies a recording of an allocation event. Example: <ASP A="2003-08-20T08:10:00" D="4"> <PTN A="54.588945" B="9.989209" D="3"/> </ASP> <ASP A="2003-08-20T08:10:00" C="3512" D="4"/> PTN = Position BAE 5030-353

  9. Task File data structure Tutorial on ERDs BAE 5030-353

  10. Device Description within Task Data DVC – Device DET – DeviceElement DOR – DeviceObjectReference DPT – DeviceProperty DPD – DeviceProcessData DVP – DeviceValuePresentation BAE 5030-353

  11. Relationship among XML elements BAE 5030-353

  12. Relationship among XML elements - Task BAE 5030-353

  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 BAE 5030-353

More Related